Ubuntu
linux package

Fix AMDGPU: the screen freeze with W7500

Bug #2027957 reported by koba
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HWE Next
Fix Released
Undecided
Unassigned
linux (Ubuntu)
Fix Released
Undecided
koba
Jammy
Won't Fix
Undecided
Unassigned
Kinetic
Won't Fix
Undecided
Unassigned
Lunar
Fix Released
Undecided
koba
Mantic
Fix Released
Undecided
koba
Noble
Fix Released
Undecided
koba
linux-oem-6.1 (Ubuntu)
Invalid
Undecided
Unassigned
Jammy
Fix Released
Undecided
koba
Kinetic
Invalid
Undecided
Unassigned
Lunar
Invalid
Undecided
Unassigned
Mantic
Invalid
Undecided
Unassigned
Noble
Invalid
Undecided
Unassigned

Bug Description

[impact]
While booting into OOBE, the screen freeze [AMD W7500 only]

[fix]
AMDGPU would allocate pcie gen/lane dynamically after ASPM is enabled.
Intel CPU may not support the dynamic lane/speed switching.

Solution is,
- Detect Intel x86 systems that don't support dynamic switching
- Override the input caps to maximum supported for that system
- Force all PCIe levels to use the same settings, rather than try to configure each level differently.

[test cases]
1. boot with w7500
2. the screen doesn't freeze and can't find the error message in dmesg.
"amdgpu: [drm] *ERROR* [CRTC:72:crtc-0] flip_done timed out"

[where the issue could happen]
low, this could lead issue when setting higher speeds than supported.

[Misc]
1. jammy, amdgpu isn't loaded on this platform with 5.15-73-generic.
2. kinetic, amdgpu failed to probe the vga controller with 5.19-46-generic.
3. Passed cbd build against Mantic&Lunar.

See original description
koba (kobako)
description: updated
koba (kobako)
description: updated
description: updated
koba (kobako)
Changed in linux-oem-6.1 (Ubuntu Jammy):
assignee: nobody → koba (kobako)
status: New → In Progress
Changed in linux (Ubuntu Jammy):
assignee: nobody → koba (kobako)
status: New → In Progress
Changed in linux (Ubuntu Kinetic):
assignee: nobody → koba (kobako)
status: New → In Progress
Changed in linux (Ubuntu Lunar):
assignee: nobody → koba (kobako)
status: New → In Progress
Changed in linux (Ubuntu Mantic):
assignee: nobody → koba (kobako)
status: New → In Progress
tags: added: oem-priority originate-from-2024460 somerville
tags: added: originate-from-2026462
Revision history for this message
koba (kobako) wrote (last edit ):

#Kinetic

Failed to probe amdgpu with 5.19.0-46-generic
~~~
$ sudo dmesg | grep -ie amdgpu
[ 5.065150] [drm] amdgpu kernel modesetting enabled.
[ 5.065224] amdgpu: CRAT table not found
[ 5.065226] amdgpu: Virtual CRAT table created for CPU
[ 5.065231] amdgpu: Topology: Add CPU node
[ 5.065349] amdgpu 0000:57:00.0: enabling device (0146 -> 0147)
[ 5.067023] amdgpu 0000:57:00.0: amdgpu: Failed to add dm ip block(DCE_HWIP:0x30201)
[ 5.067025] amdgpu 0000:57:00.0: amdgpu: Fatal error during GPU init
[ 5.067026] amdgpu 0000:57:00.0: amdgpu: amdgpu: finishing device.
[ 5.067206] amdgpu: probe of 0000:57:00.0 failed with error -22
$ uname -a
Linux 5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 15:35:31 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
~~~

Changed in linux (Ubuntu Jammy):
assignee: koba (kobako) → nobody
status: In Progress → Won't Fix
Changed in linux (Ubuntu Kinetic):
assignee: koba (kobako) → nobody
status: In Progress → Won't Fix
Revision history for this message
koba (kobako) wrote (last edit ):

#Jammy,
amdgpu isn't loaded in boot against 5.15.0-73-generic

koba (kobako)
description: updated
description: updated
Mario Limonciello (superm1)
Changed in linux-oem-6.1 (Ubuntu Mantic):
status: New → Invalid
Changed in linux-oem-6.1 (Ubuntu Lunar):
status: New → Invalid
Changed in linux-oem-6.1 (Ubuntu Kinetic):
status: New → Invalid
Timo Aaltonen (tjaalton)
Changed in linux-oem-6.1 (Ubuntu Jammy):
status: In Progress → Fix Committed
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-oem-6.1/6.1.0-1018.18 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-oem-6.1 verification-needed-jammy
Roxana Nicolescu (roxanan)
Changed in linux (Ubuntu Lunar):
status: In Progress → Fix Committed
Revision history for this message
koba (kobako) wrote :

As per Cyrus,
~~~
Verified pass with 6.1.0-1018 kernel.

steps:
1. Install 1018 kernel
2. Boot up to gdm
3. Wait 1 minute

SKU: HVR-SPR-DVT2-L10-C1_202211-30883
Kernel: 6.1.0-1018-oem
BIOS: 1.0.5
~~~

tags: added: verification-done-jammy
removed: verification-needed-jammy
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux/6.2.0-30.30 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux' to 'verification-done-lunar-linux'. If the problem still exists, change the tag 'verification-needed-lunar-linux' to 'verification-failed-lunar-linux'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-lunar-linux-v2 verification-needed-lunar-linux
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-oem-6.1 - 6.1.0-1019.19

---------------
linux-oem-6.1 (6.1.0-1019.19) jammy; urgency=medium

  * jammy/linux-oem-6.1: 6.1.0-1019.19 -proposed tracker (LP: #2029478)

  * ubuntu_bpf failed to build with j-oem-6.1.0-1018.18 (LP: #2028932)
    - SAUCE: Revert "libbpf: fix offsetof() and container_of() to work with CO-RE"

  * Regression: amdgpu mirror mode broken in -1018 (LP: #2028848)
    - Revert "drm/amd/display: edp do not add non-edid timings"

  * Miscellaneous Ubuntu changes
    - [Config] Update gcc/pahole versions.

 -- Timo Aaltonen <email address hidden> Sat, 05 Aug 2023 14:53:47 +0300

Changed in linux-oem-6.1 (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-nvidia-6.2/6.2.0-1010.10 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-nvidia-6.2' to 'verification-done-jammy-linux-nvidia-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-6.2' to 'verification-failed-jammy-linux-nvidia-6.2'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-nvidia-6.2-v2 verification-needed-jammy-linux-nvidia-6.2
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-starfive/6.2.0-1004.5 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-done-lunar-linux-starfive'. If the problem still exists, change the tag 'verification-needed-lunar-linux-starfive' to 'verification-failed-lunar-linux-starfive'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-lunar-linux-starfive-v2 verification-needed-lunar-linux-starfive
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-aws-6.2/6.2.0-1013.13~22.04.1 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-done-jammy-linux-aws-6.2'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.2' to 'verification-failed-jammy-linux-aws-6.2'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-jammy-linux-aws-6.2-v2 verification-needed-jammy-linux-aws-6.2
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote :

This bug is awaiting verification that the linux-azure/6.2.0-1013.13 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lunar-linux-azure' to 'verification-done-lunar-linux-azure'. If the problem still exists, change the tag 'verification-needed-lunar-linux-azure' to 'verification-failed-lunar-linux-azure'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: kernel-spammed-lunar-linux-azure-v2 verification-needed-lunar-linux-azure
koba (kobako)
Changed in linux (Ubuntu Mantic):
status: In Progress → Fix Committed
Anthony Wong (anthonywong)
Changed in hwe-next:
status: New → Fix Released
koba (kobako)
Changed in linux (Ubuntu Noble):
status: In Progress → Fix Released
Changed in linux (Ubuntu Mantic):
status: Fix Committed → Fix Released
Changed in linux (Ubuntu Lunar):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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