5.15.0-53-generic no longer boots

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 1996740

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.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

The logs added later were generated while running the previous kernel. The newer problematic one does not boot completely and does not allow me to connect to it via SSH (or anything else) to collect more info.

Linux Mint Cinnamon 21. After updating to 5.15.0-53, the system no longer boots.

System information: https://termbin.com/4gby

Running "Ubuntu 22.04.1". After updating today, was unable to fully boot. Screen goes black, unable to get to a terminal. Booted into 5.15.0-52 to report/confirm issue. Please instruct.

I too experienced this after rebooting with the 5.15.0-53-generic update on 22.04.1 desktop. After the UEFI/BIOS loads, the system goes to a black screen. Wasn't even able to bring up a shell, I had to enter recovery mode to get back on 5.15.0-52.

GPU model: 0c:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1) (prog-if 00 [VGA controller]) - Using DisplayPort.

Running "Ubuntu 22.04.1". After updating today, was unable to fully boot. Screen goes black, unable to get to a terminal. Booted into 5.15.0-52 to report/confirm issue. Please instruct.

The computer starts with the new kernel when there is no monitor connected via Display Port.
Only a HDMI monitor is connected.

After the system booted I can reconnect the Display Port monitor, but then the HDMI monitor is no longer recognized.

Could you please list the GPU model, preferably from 'lspci -v|grep VGA' so we'd know if it's limited to a certain generation. I see at least Navi 10 mentioned by Johan, but what about others?

The computer starts with the new kernel when there is no monitor connected via Display Port.
Only a HDMI monitor is connected.

After the system booted I can reconnect the Display Port monitor, but then the HDMI monitor is no longer recognized.

After disconnecting the HDMI cable and reconnecting it, the other monitor works too.

2b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c4) (prog-if 00 [VGA controller])

Manufacturer link: https://www.powercolor.com/product?id=1565954303

Sorry for the duplicated message before.

here's a kernel build with commits for bug 1990920 reverted:

https://aaltoset.kapsi.fi/lp1996740/amdgpu.tar.gz

should be enough to just install the image, modules & modules-extra

I experienced this problem on 20.04.5 with kernel 5.15.0-53. I have two displays running over DisplayPort via a 5700xt.

Reverting to kernel 5.15.0-52 fixes the problem for me as well.

5.15.0-53 fails for me too, also with a Radeon graphics card with monitor connected via DisplayPort. Is that a common theme?

2d:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1) (prog-if 00 [VGA controller])

Same as above, 5.15.0-52 still works.

please test the kernel build from #31

@Timo,
Your packages work, the system boots now correctly.
Thanks for your help!

thanks for testing!

could you also try oem-6.0, install 'linux-oem-22.04b' for jammy. It should not suffer from this, meaning that the backport for the other bug was maybe incomplete.

oem-6.0 boots and the displays work.
BUT: there is a delay and I see a few messages "blacklist: Problem blacklisting hash (-13)". This is probably related to secure boot.

ALSO:
Multiple error blocks like this:
[ 6.497583] rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 9-.... } 6 jiffies s: 77 root: 0x1/.
[ 6.497611] rcu: blocking rcu_node structures (internal RCU debug): l=1:0-15:0x200/.
[ 6.497627] Task dump for CPU 9:
[ 6.497628] task:systemd-udevd state:R running task stack: 0 pid: 445 ppid: 440 flags:0x0000400a
[ 6.497632] Call Trace:
[ 6.497634] <TASK>
[ 6.497637] ? 0xffffffffc16e4000
[ 6.497640] ? find_kallsyms_symbol+0x8e/0x1a0
[ 6.497646] ? vega20_ih_get_wptr+0x80/0x80 [amdgpu]
[ 6.497875] ? module_address_lookup+0x68/0xc0
[ 6.497878] ? vega20_ih_set_clockgating_state+0x20/0x20 [amdgpu]
[ 6.498087] ? kallsyms_lookup_buildid+0xf7/0x180
[ 6.498091] ? kallsyms_lookup+0x14/0x20
[ 6.498094] ? test_for_valid_rec+0x38/0x80
[ 6.498097] ? change_page_attr_set_clr+0x150/0x1c0
[ 6.498101] ? ftrace_module_enable+0xad/0x2c0
[ 6.498103] ? set_memory_x+0x40/0x50
[ 6.498105] ? load_module+0x9dd/0xc60
[ 6.498108] ? kernel_read_file+0x24e/0x2a0
[ 6.498111] ? __do_sys_finit_module+0xc8/0x140
[ 6.498113] ? __do_sys_finit_module+0xc8/0x140
[ 6.498116] ? __x64_sys_finit_module+0x18/0x20
[ 6.498118] ? do_syscall_64+0x5c/0x90
[ 6.498120] ? ksys_mmap_pgoff+0x112/0x260
[ 6.498123] ? __secure_computing+0x93/0xf0
[ 6.498124] ? exit_to_user_mode_prepare+0x37/0xb0
[ 6.498126] ? syscall_exit_to_user_mode+0x26/0x50
[ 6.498128] ? __x64_sys_mmap+0x33/0x50
[ 6.498131] ? do_syscall_64+0x69/0x90
[ 6.498132] ? exit_to_user_mode_prepare+0x37/0xb0
[ 6.498134] ? syscall_exit_to_user_mode+0x26/0x50
[ 6.498135] ? __x64_sys_lseek+0x18/0x20
[ 6.498138] ? do_syscall_64+0x69/0x90
[ 6.498139] ? exit_to_user_mode_prepare+0x37/0xb0
[ 6.498141] ? syscall_exit_to_user_mode+0x26/0x50
[ 6.498142] ? do_syscall_64+0x69/0x90
[ 6.498144] ? do_syscall_64+0x69/0x90
[ 6.498145] ? entry_SYSCALL_64_after_hwframe+0x63/0xcd
[ 6.498149] </TASK>

So it has improved but it is not perfect.

Can you please give this kernel a try:
https://people.canonical.com/~khfeng/lp1996740/

Thanks for the help!
This kernel works OK.

I also can confirm that this kernel version is now working as expected.

thanks for quick solution!

Thanks for the test!

Affected as well, same environment:

* Ubunutu 22.04.1
* Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT]
* Connection uses DisplayPort
* Booting with kernel version 5.15.0-53 fails early (no logs from systemd), no video signal

I too have the same problem on Ubuntu 22.04.1. If I boot into 5.15.0-53 I just a black screen but if I select the previous kernel in grub (5.15.0-52-generic) then everything is normal.

lspci -v|grep VGA:

b:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev c1) (prog-if 00 [VGA controller])

Ubuntu 22.04 radeon 5700
Same problem...
Kernel from khfeng fixes the problem...

Any news on officially updating the problematic kernel?

I don't like installing "hacked" kernels on my main system.

For me also crash with 5.15.0-53-generic with AMD Ryzen 9 integrated GPU.
5.15.0-52-generic works.

The attached report form /var/crash/amdgpu-dkms.0.crash

shows failing to build amdgpu kernel module

 /var/lib/dkms/amdgpu/5.16.9.22.20-1438747~22.04/build/amd/amdgpu/amdgpu_ttm.c: In function ‘amdgpu_ssg_init’:
 /var/lib/dkms/amdgpu/5.16.9.22.20-1438747~22.04/build/amd/amdgpu/amdgpu_ttm.c:2313:31: error: incompatible types when assigning to type ‘struct percpu_ref’ from type ‘struct percpu_ref *’
  2313 | adev->ssg.pgmap.ref = &adev->ssg.ref;
       | ^
   CC [M] /var/lib/dkms/amdgpu/5.16.9.22.20-1438747~22.04/build/amd/amdgpu/amdgpu_ctx.o
 make[2]: *** [scripts/Makefile.build:297: /var/lib/dkms/amdgpu/5.16.9.22.20-1438747~22.04/build/amd/amdgpu/amdgpu_ttm.o] Error 1
 make[2]: *** Waiting for unfinished jobs....
 make[1]: *** [scripts/Makefile.build:560: /var/lib/dkms/amdgpu/5.16.9.22.20-1438747~22.04/build/amd/amdgpu] Error 2
 make: *** [Makefile:1903: /var/lib/dkms/amdgpu/5.16.9.22.20-1438747~22.04/build] Error 2
 make: Leaving directory '/usr/src/linux-headers-5.15.0-53-generic'
DKMSKernelVersion: 5.15.0-53-generic
Date: Wed Nov 16 19:40:19 2022
DuplicateSignature: dkms:amdgpu-dkms:1:5.16.9.22.20.50200-1438747~22.04:/var/lib/dkms/amdgpu/5.16.9.22.20-1438747~22.04/build/amd/amdgpu/amdgpu_ttm.c:2313:31: error: incompatible types when assigning to type ‘struct percpu_ref’ from type ‘struct percpu_ref *’
Package: amdgpu-dkms 1:5.16.9.22.20.50200-1438747~22.04
PackageVersion: 1:5.16.9.22.20.50200-1438747~22.04
SourcePackage: amdgpu-dkms
Title: amdgpu-dkms 1:5.16.9.22.20.50200-1438747~22.04: amdgpu kernel module failed to build

Also affected:

0a:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] (rev ca) (prog-if 00 [VGA controller])

(using display port)

I just ran apt update && apt upgrade, noticed the dkms upgrade, rebooted into 5.15.0-53-generic and still got a no-signal black monitor. See my previous comment for hardware. Is the fix not out yet or was the upgraded dkms package supposed to be the fix?

Same issue here, also with Ryzen5 3600 and Radeon RX 5600 XT on Displayport.

As with others on this thread, able to boot fine into 5.15.0-52-generic.

As a 'user' rather than an 'enthusiast', I would have to look up how to manually install one of your alternative kernels, and I have other priorities at the moment, so I'll just wait for an official fix to roll out.

Thanks to those of you who dedicate the time and energy to sorting this stuff out.

the hotfix for this issue will be combined with other urgent fixes, and it should land in updates in the not-too-distant future.. can't give a more accurate estimate, sorry.

Notice that the fix is available at ppa:canonical-kernel-team/ppa2 as linux 5.15.0-56.

I added ppa:canonical-kernel-team/ppa2 but still get the same error in the log file. This is after apt upgrade and booting into the newer kernel image. Should it have worked or am I missing a step to test?

...
Loading new amdgpu-5.16.9.22.20-1438747~22.04 DKMS files...
Building for 5.15.0-56-generic
Building for architecture x86_64
Building initial module for 5.15.0-56-generic
ERROR (dkms apport): kernel package linux-headers-5.15.0-56-generic is not supported
Error! Bad return status for module build on kernel: 5.15.0-56-generic (x86_64)
Consult /var/lib/dkms/amdgpu/5.16.9.22.20-1438747~22.04/build/make.log for more information.
dpkg: error processing package amdgpu-dkms (--configure):
 installed amdgpu-dkms package post-installation script subprocess returned error exit status 10
...

Shaun, that's something completely irrelevant for this bug, you're using a dkms from AMD, which we don't support

ok, I see. I"ll try to figure out how to report the same issue for the AMD release.

This bug was fixed in the package linux - 5.15.0-56.62

---------------
linux (5.15.0-56.62) jammy; urgency=medium

  * jammy/linux: 5.15.0-56.62 -proposed tracker (LP: #1997079)

  * CVE-2022-3566
    - tcp: Fix data races around icsk->icsk_af_ops.

  * CVE-2022-3567
    - ipv6: annotate some data-races around sk->sk_prot
    - ipv6: Fix data races around sk->sk_prot.

  * CVE-2022-3621
    - nilfs2: fix NULL pointer dereference at nilfs_bmap_lookup_at_level()

  * CVE-2022-3564
    - Bluetooth: L2CAP: Fix use-after-free caused by l2cap_reassemble_sdu

  * CVE-2022-3524
    - tcp/udp: Fix memory leak in ipv6_renew_options().

  * CVE-2022-3565
    - mISDN: fix use-after-free bugs in l1oip timer handlers

  * CVE-2022-3594
    - r8152: Rate limit overflow messages

  * CVE-2022-43945
    - SUNRPC: Fix svcxdr_init_decode's end-of-buffer calculation
    - SUNRPC: Fix svcxdr_init_encode's buflen calculation
    - NFSD: Protect against send buffer overflow in NFSv2 READDIR
    - NFSD: Protect against send buffer overflow in NFSv3 READDIR
    - NFSD: Protect against send buffer overflow in NFSv2 READ
    - NFSD: Protect against send buffer overflow in NFSv3 READ
    - NFSD: Remove "inline" directives on op_rsize_bop helpers
    - NFSD: Cap rsize_bop result based on send buffer size

  * CVE-2022-42703
    - mm/rmap: Fix anon_vma->degree ambiguity leading to double-reuse

  * 5.15.0-53-generic no longer boots (LP: #1996740)
    - drm/amd/display: Add helper for blanking all dp displays

 -- Thadeu Lima de Souza Cascardo <email address hidden> Tue, 22 Nov 2022 12:08:58 -0300

Yup. That kernel update fixed the problem for me.
Thanks a million for all your work!

Confirmed, 5.15.0-56-generic fixed the issue.

Confirmed, 5.15.0-56.62 boots as normal.

I can confirm this is now fixed by 5.15.0-56-generic on our affected machine:

Kubuntu 22.04
Ryzen 3 2200G
Using integrated Vega 8 graphics on default driver
Monitor connected via VGA

We previously experienced the same issue as other users on 5.15.0-53-generic.

Thank you!

This bug is awaiting verification that the linux-aws/5.15.0-1027.31 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!

I want to raise the possibility that this fix (or another one) in the new kernel update has begun preventing me from Blanking my DP monitors.

I had previously been experiencing xorg cpu spikes and softlocks when my monitors Blanked, but now, they refuse to Blank at all. They disconnect for a brief moment and they reactivate. I can see my mouse cursor reappear on screen.

I have an AMD Ryzen 5700u (includes renoir graphics). Using amdgpu (default).

So this new kernel is better than the last kernel with xorg softlocks that prevented me from accessing my system but might have introduced/revealed another less severe bug.

I tried to hunt down what amdgpu impacting changes were made to the latest ubuntu kernel and I think this is the only one?

Is it a laptop? Does the internal eDP panel also have this issue?

file a new bug

It is a minipc - Asus PN51-E1, using a laptop class chipset I'd guess. There is no internal display. I forgot to mention I'm on Focal.

based on my rudimentary assessment, this bug was fixed in the latest focal kernel. As this bug report only indicates Jammy, I figured I'd point out I'm using Focal and it seems to have changed behavior (for the better).

I will create a new bug if the crashes/freezes return.

This bug is awaiting verification that the linux-nvidia/5.15.0-1011.11 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!

This bug is awaiting verification that the linux-azure/5.15.0-1030.37 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!

Based on #61 I'm marking this bug as verification complete.

This bug is awaiting verification that the linux-azure-5.15/5.15.0-1033.40~20.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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

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!

This bug is awaiting verification that the linux-bluefield/5.15.0-1012.14 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!

This bug is awaiting verification that the linux-aws-5.15/5.15.0-1030.34~20.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-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'.

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!

This bug is awaiting verification that the linux-mtk/5.15.0-1030.34 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-mtk' to 'verification-done-jammy-linux-mtk'. If the problem still exists, change the tag 'verification-needed-jammy-linux-mtk' to 'verification-failed-jammy-linux-mtk'.

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!