Kernel Panic on System Shutdown

glitch · April 10, 2024, 2:04am

I’m experiencing strange behaviour that I’m unable to understand on my system.

Around 25% of the times I shut down my system, I get a kernel panic that I can’t recover from.
SysRq (REISUB) doesn’t work either, since, I’m assuming it’s halfway to shutdown and has stopped taking in keyboard input. I have to long press the power button and force shut down.

I am on LTS kernel 6.6.25-lts.

I think my boot also has some issues as I see some error logs. But I’ve been told the ACPI bugs can be and the others are more or less a cosmetic problem and can be ignored as well. My day-to-day working of the system including WiFi, Bluetooth is not affected. I do have to restart asusd now and again on boot though.

Boot journalctl

❯ journalctl -b1 -p3
Apr 03 13:14:59 zephyrus kernel:
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\CTDP], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.IETM.IDSP due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._CRT.S1CT], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._CRT due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._HOT.S1HT], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._HOT due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._PSV.S1PT], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._PSV due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN1._AC0.S1AT], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN1._AC0 due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._CRT.S2CT], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._CRT due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._HOT.S2HT], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._HOT due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._PSV.S2PT], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._PSV due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN2._AC0.S2AT], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN2._AC0 due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN3._CRT.S3CT], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN3._CRT due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN3._HOT.S3HT], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN3._HOT due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN3._PSV.S3PT], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN3._PSV due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._CRT.S4CT], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._CRT due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._HOT.S4HT], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._HOT due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._PSV.S4PT], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._PSV due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:02 zephyrus kernel: ACPI BIOS Error (bug): Could not resolve symbol [\_SB.PC00.LPCB.EC0.SEN4._AC0.S4AT], AE_NOT_FOUND (20230628/psargs-330)
Apr 03 13:15:02 zephyrus kernel: ACPI Error: Aborting method \_SB.PC00.LPCB.EC0.SEN4._AC0 due to previous error (AE_NOT_FOUND) (20230628/psparse-529)
Apr 03 13:15:03 zephyrus kernel: asus 0003:0B05:19B6.0004: Asus input not registered
Apr 03 13:15:03 zephyrus kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
Apr 03 13:15:04 zephyrus (udev-worker)[600]: event14: Failed to call EVIOCSKEYCODE with scan code 0x70065, and key code 99: Invalid argument
Apr 03 13:15:04 zephyrus (udev-worker)[560]: event17: Failed to call EVIOCSKEYCODE with scan code 0x70065, and key code 99: Invalid argument
Apr 03 13:15:04 zephyrus kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Apr 03 13:15:04 zephyrus kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
Apr 03 13:15:05 zephyrus kernel: iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
Apr 03 13:15:12 zephyrus lightdm[2332]: gkr-pam: unable to locate daemon control file
Apr 03 13:19:38 zephyrus dbus-broker-launch[1852]: Activation request for 'org.bluez' failed.
Apr 03 13:19:38 zephyrus dbus-broker-launch[1852]: Activation request for 'org.bluez' failed.
Apr 03 13:19:40 zephyrus dbus-broker-launch[1852]: Activation request for 'org.freedesktop.nm_dispatcher' failed.
Apr 03 13:19:40 zephyrus dbus-broker-launch[1852]: Activation request for 'org.freedesktop.nm_dispatcher' failed.

Here’s my system info from inxi -Fz


❯ inxi -Fz
System:
  Kernel: 6.6.25-1-lts arch: x86_64 bits: 64
  Desktop: i3 v: 4.23 Distro: EndeavourOS
Machine:
  Type: Laptop System: ASUSTeK product: ROG Zephyrus M16 GU603ZW_GU603ZW
    v: 1.0 serial: <superuser required>
  Mobo: ASUSTeK model: GU603ZW v: 1.0 serial: <superuser required>
    UEFI: American Megatrends LLC. v: GU603ZW.311 date: 12/22/2022
Battery:
  ID-1: BAT0 charge: 67.2 Wh (80.2%) condition: 83.8/90.0 Wh (93.1%)
    volts: 15.9 min: 15.9
CPU:
  Info: 14-core (6-mt/8-st) model: 12th Gen Intel Core i9-12900H bits: 64
    type: MST AMCP cache: L2: 11.5 MiB
  Speed (MHz): avg: 511 min/max: 400/4900:5000:3800 cores: 1: 400 2: 400
    3: 656 4: 400 5: 400 6: 1186 7: 400 8: 400 9: 400 10: 400 11: 1008 12: 400
    13: 774 14: 400 15: 400 16: 400 17: 400 18: 604 19: 400 20: 400
Graphics:
  Device-1: Intel Alder Lake-P GT2 [Iris Xe Graphics] driver: i915 v: kernel
  Device-2: NVIDIA GA104 [Geforce RTX 3070 Ti Laptop GPU] driver: nvidia
    v: 550.67
  Device-3: IMC Networks USB2.0 HD UVC WebCam driver: uvcvideo type: USB
  Display: x11 server: X.Org v: 21.1.12 with: Xwayland v: 23.2.6 driver: X:
    loaded: modesetting,nvidia dri: iris gpu: i915 resolution: 2560x1600~165Hz
  API: EGL v: 1.5 drivers: iris,nvidia,swrast
    platforms: gbm,x11,surfaceless,device
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.0.4-arch1.2
    renderer: Mesa Intel Graphics (ADL GT2)
Audio:
  Device-1: Intel Alder Lake PCH-P High Definition Audio driver: snd_hda_intel
  Device-2: NVIDIA GA104 High Definition Audio driver: snd_hda_intel
  API: ALSA v: k6.6.25-1-lts status: kernel-api
  Server-1: PipeWire v: 1.0.4 status: active
Network:
  Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi
  IF: wlan0 state: up mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE driver: r8169
  IF: eno2 state: down mac: <filter>
Bluetooth:
  Device-1: Intel AX211 Bluetooth driver: btusb type: USB
  Report: btmgmt ID: hci0 state: up address: <filter> bt-v: 5.3
Drives:
  Local Storage: total: 2.75 TiB used: 80.34 GiB (2.9%)
  ID-1: /dev/nvme0n1 vendor: Micron model: 2450 MTFDKBA1T0TFK
    size: 953.87 GiB
  ID-2: /dev/nvme1n1 vendor: Western Digital model: WD Blue SN580 2TB
    size: 1.82 TiB
Partition:
  ID-1: / size: 1.75 TiB used: 80.31 GiB (4.5%) fs: ext4 dev: /dev/nvme1n1p1
Swap:
  ID-1: swap-1 type: partition size: 42.76 GiB used: 0 KiB (0.0%)
    dev: /dev/nvme1n1p2
Sensors:
  System Temperatures: cpu: 53.0 C mobo: N/A
  Fan Speeds (rpm): N/A
Info:
  Memory: total: 40 GiB note: est. available: 38.87 GiB used: 3 GiB (7.7%)
  Processes: 363 Uptime: 14m Shell: Zsh inxi: 3.3.33

I’m also using nvidia-dkms

A photo of a kernel panic (I will update it with the latest one if I get another one again). Not sure how helpful it is though…

dalto · April 10, 2024, 2:13am

How long has it been happening? It may be the bug in the current version of the proprietary nvidia drivers.

glitch · April 10, 2024, 5:14am

I didn’t know there was a bug! Could you link it maybe?

I don’t exactly remember but I’m sure it’s been happening for atleast a couple weeks?

Anything I can do to debug/give you more info?

elrond · April 10, 2024, 5:52am

I faced the same issue. Then I found this post in Nvidia forum - https://forums.developer.nvidia.com/t/series-550-freezes-laptop/284772/44

This seems to be a bug in Nvidia driver 550. I have reverted to Nvidia driver 535 and it is working well so far.

herr_marschall · April 10, 2024, 5:57am

Can kind of confirm. Also on a Zephyrus M16 here. Since I’m using the open source drivers for NVIDIA, the kernel panics stopped happening.

There was an announcement of new official NVIDIA drivers yesterday regarding issues with Wayland:

Not sure if this is related, though.

glitch · April 10, 2024, 6:37am

Thanks for the link @elrond!
Were you using nvidia-dkms for your drivers? The guide over at asus-linux recommends nvidia-dkms instead of the regular package: https://asus-linux.org/guides/arch-guide/

How did you manage to downgrade your version?
Were you able to use the GPU normally? I’m assuming CUDA etc would still work?

@herr_marschall
Afaik, it’s not recommended to use nouveau on Asus Zephyrus laptops.
Also I’m running i3wm which means X so not sure if those bugs in particular affect that?
What do you think?

elrond · April 10, 2024, 10:05am

sudo pacman -R nvidia-dkms nvidia-settings nvidia-utils
sudo pacman -S nvidia-535xx-dkms nvidia-535xx-utils nvidia-535xx-settings

glitch · April 10, 2024, 12:42pm

Thanks.

I’ll do this and report back on stability in a little bit.

xircon · April 10, 2024, 3:28pm

DO NOT DOWNGRADE if you are on the current mainline kernel (6.8.n) it will break.

glitch · April 11, 2024, 3:36am

I’m using LTS (6.6.25-1-lts) kernel.

Can I downgrade on that?

xircon · April 11, 2024, 1:03pm

I never tried, but I think so (based on the nvidia forum thread I saw), just have your install media around in case you need to chroot in to fix.

herr_marschall · April 12, 2024, 11:43am

@glitch : I was not aware of that. Do you have any sources at hand? Otherwise I’ll habe a look into that. From my experience with EOS the Nvidia forced me either to use Xorg or experience crashes under wayland. So nvidia+x at least for me worked better.

I’m currently using nouveau for the last month continously without any issues. I hope it stay that way and my timeshift snaps dont let me down

glitch · April 26, 2024, 2:59am

Well I guess for using CUDA/gaming it’s recommended to use the official drivers atleast.

Source: https://asus-linux.org/guides/arch-guide/ (they ask you to disable nouveau in the kernel parameters and use nvidia-dkms)

Sorry for the late response. I typed it out but forgot to press send!

herr_marschall · April 26, 2024, 7:30am

Thanks.

I followed the advise on asus-linux.org and other sources. In the end the system runs stable enough to be usable. From time to time the systems freezes (un-REISUB-able) when rebooting.

Would it be a strategy to use linux-lts 6.6.28 with nvidia 535?
If so, what would be the way to do that?

dalto · April 26, 2024, 10:28am

Install linux-lts and linux-lts-headers.
Reboot and choose the LTS kernel while booting
Use downgrade to lower the version on all nvidia packages.

herr_marschall · April 26, 2024, 11:19am

Thanks. This worked.

After numerous reboots I can say, that there was not a single freeze or crash so far.

So, linux-lts 6.628 + nvidia 535 it is.

system · May 1, 2024, 3:21am

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.