Hi Zoltan, There is about 1400 commits between 5.15.0-78 (good) and 5.15.0-82 (bad):
$ git log --oneline Ubuntu-5.15.0-78.85..Ubuntu-5.15.0-82.91 | wc -l 1379 Are you interested in helping us with a kernel bisect? I would build you kernels halfway between each good and bad kernel until we land on the commit that causes the issue. This might take about 10 or so back and forths until we land on the commit that causes the issue. From there we can see what that commit did and if a fix is available. Let me know if you are interested. Otherwise you could alternatively configure kdump and see if you could capture the panic, this would only take one attempt: https://ubuntu.com/server/docs/kernel-crash-dump Then you can message me and we can find a way to look at the coredump in /var/crash, or upload the resulting dmesg file in /var/crash. Maybe try capturing a kdump first, and if that doesn't work, then we can go through with a bisect. Thanks, Matthew -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2039388 Title: Resuming from RAM causes a freeze after recent kernel upgrade Status in linux package in Ubuntu: Incomplete Bug description: Dear Ubuntu Developers, I have been using suspend-to-RAM using the pm-suspend command without issues for around 2 years. After a recent kernel upgrade (from linux- image-5.15.0-78-generic to linux-image-5.15.0-82-generic on a 20.04 LTS release using linux-image-generic-hwe-20.04), my computer started freezing upon resume without any kind of output (no HDMI signal, no keyboard lights). I waited a few kernel upgrades in case it gets fixed but as of linux-modules-5.15.0-86-generic the issue still persists. Since the machine always freezes immediately upon resuming, I don't know how to troubleshoot the issue further. I can only investigate the logs after a reboot but `journalctl -b -1` doesn't show anything either. When booting linux-image-5.15.0-78-generic, everything works fine and I am attaching the logs for a successful resume with this kernel version. # lsb_release -rd Description: Ubuntu 20.04.6 LTS Release: 20.04 # inxi -Fz # (for the HW aspect, executed with the good kernel version) System: Kernel: 5.15.0-78-generic x86_64 bits: 64 Desktop: Cinnamon 4.4.8 Distro: Ubuntu 20.04.6 LTS (Focal Fossa) Machine: Type: Mini-pc System: ASUSTeK product: MINIPC PN50-E1 v: 0405 serial: <filter> Mobo: ASUSTeK model: PN50-E1 serial: N/A UEFI: ASUSTeK v: 0405 date: 03/18/2021 CPU: Topology: 8-Core model: AMD Ryzen 7 4700U with Radeon Graphics bits: 64 type: MCP L2 cache: 4096 KiB Speed: 1397 MHz min/max: 1400/2000 MHz Core speeds (MHz): 1: 1399 2: 1396 3: 1397 4: 1397 5: 1397 6: 1397 7: 1258 8: 1330 Graphics: Device-1: Advanced Micro Devices [AMD/ATI] Renoir driver: amdgpu v: kernel Display: server: X.Org 1.20.13 driver: amdgpu,ati unloaded: fbdev,modesetting,vesa resolution: 2560x1440~144Hz OpenGL: renderer: AMD RENOIR (DRM 3.42.0 5.15.0-78-generic LLVM 12.0.0) v: 4.6 Mesa 21.2.6 Audio: Device-1: Advanced Micro Devices [AMD/ATI] driver: snd_hda_intel Device-2: Advanced Micro Devices [AMD] Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A Device-3: Advanced Micro Devices [AMD] Family 17h HD Audio driver: snd_hda_intel Sound Server: ALSA v: k5.15.0-78-generic Network: Device-1: Realtek RTL8125 2.5GbE driver: r8169 IF: enp2s0 state: down mac: <filter> Device-2: Intel Wireless 8265 / 8275 driver: iwlwifi IF: wlp3s0 state: up mac: <filter> IF-ID-1: virbr0 state: down mac: <filter> IF-ID-2: virbr0-nic state: down mac: <filter> Thanks, Zoltan To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2039388/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
