Backport request: drm/amdgpu: fix clearing mappings for BOs that are always valid in VM

Bug #2034718 reported by kisak
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Fix Committed
Undecided
Unassigned

Bug Description

Good day Ubuntu kernel maintainers,

Please evaluate https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ea2c3c08554601b051d91403a241266e1cf490a5 for backport into all actively maintained Ubuntu flavors of the Linux kernel.

This commit is needed to stabilize Starfield with mesa/RADV. There was a stopgap workaround put into mesa 23.1.4, but that workaround harmed other games and it needed to be fixed properly in the kernel. The mesa workaround is removed in mesa 23.1.7 and mesa git main.

As far as I can tell, all Ubuntu kernels do not meet the 5.15.121+, 6.1.40+ or 6.4.5+ baseline noted in https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/24774

There's what looks like an automated mailing list message that this commit was queued for the upstream 5.4 series at some point near 5.4.250, but it's not in the linux changelog, so there might be a conflict denominating it from that kernel.

Expected kernels affected: Focal HWE and Jammy (5.15 based), Jammy HWE and Lunar (6.2 based), and Mantic (6.3 based)

Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Missing required logs.

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 2034718

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
kisak (kisak) wrote :

I do not believe that logs are necessary or beneficial for this bug report given that the nature of the issue is well understood.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
kisak (kisak) wrote :

It appears that 5.15.0-85.95 (https://launchpad.net/ubuntu/+source/linux/5.15.0-85.95) is a general rebase to 5.15.122, which includes this commit from upstream. Also, Mantic looks like it's in the process of switching to 6.5.?? (https://launchpad.net/ubuntu/+source/linux/6.5.0-5.5).

If/when those ship, that should reduce the scope of this bug report to the 6.2 based Jammy HWE and Lunar kernels.

Revision history for this message
kisak (kisak) wrote :
Changed in linux (Ubuntu):
status: Confirmed → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.