Fix AMDGPU: kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0

Bug #2009044 reported by koba
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HWE Next
New
Undecided
Unassigned
linux (Ubuntu)
Incomplete
Undecided
Unassigned
Kinetic
Won't Fix
Medium
koba

Bug Description

[Impact]
With AMD W6800, call trace will be printed during system boot
kernel: RIP: 0010:kernel_fpu_begin_mask+0xa4/0xb0

[Fix]
move FPU codes from dcn folder to dml folder.
also clean up the FPU codes on dcn folder.

[Test Case]
1. boot a machine the AMD W6800/W6400.
2. get into desktop and check the dmesg

[Where problems could occur]
Medium, code refactoring so may occur some codes are left in original folder.

[Misc Info]
all patches have been landed on Unstable/Lunar so SRU only for Kinetic.

koba (kobako)
Changed in linux (Ubuntu Kinetic):
status: New → In Progress
assignee: nobody → koba (kobako)
tags: added: oem-priority originate-from-1990281 somerville
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 2009044

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
koba (kobako)
description: updated
Changed in linux (Ubuntu):
status: Incomplete → Invalid
status: Invalid → New
Changed in linux (Ubuntu):
status: New → Incomplete
koba (kobako)
description: updated
Stefan Bader (smb)
Changed in linux (Ubuntu Kinetic):
importance: Undecided → Medium
Revision history for this message
Utkarsh Gupta (utkarsh) wrote :

Ubuntu 22.10 (Kinetic Kudu) has reached end of life, so this bug will not be fixed for that specific release.

Changed in linux (Ubuntu Kinetic):
status: In Progress → Won't Fix
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.