Kernel Panic on Shutdown

qualia · 2024-03-10 17:06:41

I am running into a kernel panic on shutdown and I am not sure why. I am also having trouble reproducing it. As far as I can tell the only continuity is when my laptop has been on for more than a couple hours.

Running on 6.7.9-arch1-1, and the last couple of entries in my journal before panic follow below; I am not sure if the ACPI stuff has anything to do with it (I doubt but include it just in case).

Mar 10 11:43:37 void root[47278]: ACPI group/action undefined: video/brightnessup / BRTUP
Mar 10 11:43:37 void root[47281]: ACPI group/action undefined: video/brightnessup / BRTUP
Mar 10 11:43:38 void root[47284]: ACPI group/action undefined: video/brightnessup / BRTUP
Mar 10 11:43:38 void root[47287]: ACPI group/action undefined: video/brightnessup / BRTUP
Mar 10 11:43:47 void systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Mar 10 11:44:22 void root[49239]: ACPI group/action undefined: button/right / RIGHT
Mar 10 11:44:24 void root[49348]: ACPI group/action undefined: button/right / RIGHT
Mar 10 11:44:24 void root[49358]: ACPI group/action undefined: button/right / RIGHT
Mar 10 11:44:25 void root[49364]: ACPI group/action undefined: button/right / RIGHT
Mar 10 11:44:25 void root[49373]: ACPI group/action undefined: button/right / RIGHT
Mar 10 11:44:25 void root[49379]: ACPI group/action undefined: button/right / RIGHT
Mar 10 11:45:00 void root[50837]: ACPI group/action undefined: button/left / LEFT
Mar 10 11:45:00 void root[50855]: ACPI group/action undefined: button/right / RIGHT
Mar 10 11:45:00 void root[50861]: ACPI group/action undefined: ibm/hotkey / LEN0268:00
Mar 10 11:46:19 void polkitd[921]: Registered Authentication Agent for unix-process:54154:6385217 (system bus name :1.51 [/usr/bin/pkttyagent --notify-fd 5 --fallback], object path /org/freed>
Mar 10 11:46:19 void systemd-logind[897]: The system will power off now!
Mar 10 11:46:19 void systemd-logind[897]: System is powering down.
Mar 10 11:46:19 void polkitd[921]: Unregistered Authentication Agent for unix-process:54154:6385217 (system bus name :1.51, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale>
Mar 10 11:46:19 void at-spi2-registryd[13041]: X connection to :0 broken (explicit kill or server shutdown).

If anyone needs more information to form a hypothesis or to help diagnose I am happy to provide more. Thanks.

Last edited by qualia (2024-03-10 18:13:09)

seth · 2024-03-10 18:08:08

Please use [code][/code] tags, not "quote" tags. Edit your post in this regard.
Please post your complete system journal for the previous boot:

sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

In case you've an nvidia GPU, https://bbs.archlinux.org/viewtopic.php … 0#p2155420

angrynapkin · 2024-03-10 20:57:02

I'm interested in this as well. I just began having kernel panics on shutdown since updating maybe a month or so go.
Doesn't happen all the time and I cannot seem to track down a smoking gun.
When it happens again, Ill grab the the journal log and post as suggested above.

Hoping to resolve this.
I have a DELL XPS 17 9720 if that helps.

seth · 2024-03-10 21:02:05

You can access older journals, eg. "-b -3" for the third last boot instead of the last one.
There's a prevalent issue w/ the 550xx nvidia drivers that causes weird kernel halts, in some cases during shutdowns (only) - so that might be a hint if you've such hardware and the driver.

angrynapkin · 2024-03-10 21:09:25

seth wrote:

You can access older journals, eg. "-b -3" for the third last boot instead of the last one.
There's a prevalent issue w/ the 550xx nvidia drivers that causes weird kernel halts, in some cases during shutdowns (only) - so that might be a hint if you've such hardware and the driver.

Thank for the heads up. Yes I have 'NVIDIA GeForce RTX 3050 Laptop GPU' with driver 550.54.14.
Ill look into trying to disable it and see if any panics happen after. Seems it will do it while watching YT for a while, but its not consistent. Also I do not believe the GPU is getting used unless I call up the prime-run command first.

seth · 2024-03-10 21:23:07

It's not the use, the kernel module (maybe along a bug in the kernel) dereferences a nullptr.
Edit: IFFF that's the suspected nvidia bug, of course.

Last edited by seth (2024-03-10 21:23:29)

angrynapkin · 2024-03-10 21:38:49

OK, I blacklisted all my nvidia stuff.
lsmod | grep nvidia shows nothing.

So now I use as usual and hope for no crash.

angrynapkin · 2024-03-15 19:17:25

seth wrote:

...
There's a prevalent issue w/ the 550xx nvidia drivers that causes weird kernel halts, in some cases during shutdowns (only) - so that might be a hint if you've such hardware and the driver.

Where might I find more info on this? I havent had a single crash since blacklisting nvidia. I would like to keep a watch on the progress of this bug.

Thanks.

seth · 2024-03-15 21:15:24

seth in post #2 wrote:

In case you've an nvidia GPU, https://bbs.archlinux.org/viewtopic.php … 0#p2155420

There's also a link to an nvidia thread and the vfs_rmdir pattern showed up a couple of more times on this board.

angrynapkin · 2024-03-16 15:36:54

seth wrote:

seth in post #2 wrote:
In case you've an nvidia GPU, https://bbs.archlinux.org/viewtopic.php … 0#p2155420
There's also a link to an nvidia thread and the vfs_rmdir pattern showed up a couple of more times on this board.

Thanks for the link. Seems the fix was to roll back. I tried that and I could not get 3d to work as before. This sort of sucks. Going to have to wait for nvidia to fix their mistake.

seth · 2024-03-16 15:38:11

I tried that and I could not get 3d to work

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855

You ned the nvidia-dkms package and the headers for your current kernel (eg. linux-lts) to build the module.

angrynapkin · 2024-03-16 22:31:54

I didnt mean to paraphrase.
What I meant to say was, yes I installed the nvidia-dkms and have all headers and modules were built and installed but my dedicated graphics had extremely poor performance compared to what it was. I use it mostly in a VM for fusion 360. Outside of that I dont really care.
Anyways, it sucked so bad where I was under the impression it was actually worse than my intel graphics when I had nvidia uninstalled.
I just dont have time at the moment to spend countless hours reading the wiki and trying to make sense of this stuff. I do ok in linux, but there are some things that are just over my head...graphics seems to be one of them. I tried reading through, the wiki for nvidia switchable graphics and its just confuses me to no end. So I decided to wait for a fix.

seth · 2024-03-16 22:48:21

I use it mostly in a VM for fusion 360

If you're passing through the device, the host drivers are irrelvant.
If your WM is a virtualbox instance, nb. that vbox comes w/ an OOT module as well and you'll need https://archlinux.org/packages/extra/x8 … host-dkms/ likewise

You can check the host condition w/ eg. "glxinfo -B", "nvidia-smi" and your xorg log, https://wiki.archlinux.org/title/Xorg#General

angrynapkin · 2024-03-16 22:56:59

seth wrote:

If you're passing through the device, the host drivers are irrelvant.

I am using VMWare Workstation. I honestly dont know if its passing through. I always launched vmware with prime-run and I had nice graphics inside the vm.
Just to see if I had jacked something up in my adding and removing various nvidia packages, I reinstalled the defective ones and tested inside vmware.
Seems I jazzed something up because those no longer work either.
So if I can figure out what I did to break it, I would probably get the rolled back versions to work just fine.

seth · 2024-03-16 22:58:24

Please post your Xorg log, https://wiki.archlinux.org/title/Xorg#General

angrynapkin · 2024-03-16 23:16:38

Here is my xorg Log: http://0x0.st/HCkT.txt

seth · 2024-03-16 23:21:35

You're running on the intel chip, the nvidia one is ignored.
=> kernel module issue.

pacman -Qs nvidia
dkms status
modinfo nvidia | head -n10

You can remove ibt=off, but enable https://wiki.archlinux.org/title/NVIDIA … de_setting - use the "nvidia_drm.modeset=1" kernel parameter (modprobe.conf won't do!)

angrynapkin · 2024-03-16 23:30:42

Installed nvidia with: pacman -U https://archive.archlinux.org/packages/ … kg.tar.zst https://archive.archlinux.org/packages/ … kg.tar.zst https://archive.archlinux.org/packages/ … kg.tar.zst

pacman -Qs nvidia
local/egl-wayland 2:1.1.13-1
    EGLStream-based Wayland external platform
local/libvdpau 1.5-2
    Nvidia VDPAU library
local/libxnvctrl 550.54.14-1
    NVIDIA NV-CONTROL X extension
local/nvidia-dkms 545.29.06-4
    NVIDIA drivers - module sources
local/nvidia-settings 545.29.06-1
    Tool for configuring the NVIDIA graphics driver
local/nvidia-utils 545.29.06-4
    NVIDIA drivers utilities

dkms status
Error! Could not locate dkms.conf file.
File: /var/lib/dkms/vmware-workstation15/15.5.7_17171714/source/dkms.conf does not exist.
nvidia/545.29.06: added

modinfo nvidia | head -n10
modinfo: ERROR: Module nvidia not found.

seth · 2024-03-16 23:40:01

The nvida-dkms package is installed but no module was built, make sure you've linux-headers installed and if its installation doesn't trigger a rebuild, see https://wiki.archlinux.org/title/Dynami … ld_modules

There's also somthign fishy w/ /var/lib/dkms/vmware-workstation15 - remnant from a removed vmware dkms package?

angrynapkin · 2024-03-16 23:46:53

warning: linux-headers-6.8.1.arch1-1 is up to date -- reinstalling

Reinstalling wants to update nvidia to 550

It does seem like installed the rolled back drivers never build any modules. my CPU went nuts....let me reinstall them and show you the output...one sec.

loading packages...
warning: nvidia-dkms-545.29.06-4 is up to date -- reinstalling
warning: nvidia-utils-545.29.06-4 is up to date -- reinstalling
warning: nvidia-settings-545.29.06-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (3) nvidia-dkms-545.29.06-4  nvidia-settings-545.29.06-1  nvidia-utils-545.29.06-4

Total Installed Size:  711.15 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n] y
(3/3) checking keys in keyring                                                                                                 [#############################################################################] 100%
(3/3) checking package integrity                                                                                               [#############################################################################] 100%
(3/3) loading package files                                                                                                    [#############################################################################] 100%
(3/3) checking for file conflicts                                                                                              [#############################################################################] 100%
(3/3) checking available disk space                                                                                            [#############################################################################] 100%
:: Running pre-transaction hooks...
(1/1) Remove upgraded DKMS modules
==> dkms remove nvidia/545.29.06
:: Processing package changes...
(1/3) reinstalling nvidia-utils                                                                                                [#############################################################################] 100%
If you run into trouble with CUDA not being available, run nvidia-modprobe first.
If you use GDM on Wayland, you might have to run systemctl enable --now nvidia-resume.service
(2/3) reinstalling nvidia-dkms                                                                                                 [#############################################################################] 100%
(3/3) reinstalling nvidia-settings                                                                                             [#############################################################################] 100%
:: Running post-transaction hooks...
(1/8) Creating system user accounts...
(2/8) Reloading system manager configuration...
(3/8) Reloading device manager configuration...
(4/8) Arming ConditionNeedsUpdate...
(5/8) Install DKMS modules
==> dkms install --no-depmod nvidia/545.29.06 -k 6.8.1-arch1-1
Error! Bad return status for module build on kernel: 6.8.1-arch1-1 (x86_64)
Consult /var/lib/dkms/nvidia/545.29.06/build/make.log for more information.
==> WARNING: `dkms install --no-depmod nvidia/545.29.06 -k 6.8.1-arch1-1' exited 10
(6/8) Updating linux initcpios...
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'default'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux.img
==> Starting build: '6.8.1-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [autodetect]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_420xx'
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
==> Building image from preset: /etc/mkinitcpio.d/linux.preset: 'fallback'
==> Using default configuration file: '/etc/mkinitcpio.conf'
  -> -k /boot/vmlinuz-linux -g /boot/initramfs-linux-fallback.img -S autodetect
==> Starting build: '6.8.1-arch1-1'
  -> Running build hook: [base]
  -> Running build hook: [udev]
  -> Running build hook: [microcode]
  -> Running build hook: [modconf]
  -> Running build hook: [block]
==> WARNING: Possibly missing firmware for module: 'qla2xxx'
==> WARNING: Possibly missing firmware for module: 'qed'
==> WARNING: Possibly missing firmware for module: 'wd719x'
==> WARNING: Possibly missing firmware for module: 'qla1280'
==> WARNING: Possibly missing firmware for module: 'aic94xx'
==> WARNING: Possibly missing firmware for module: 'bfa'
==> WARNING: Possibly missing firmware for module: 'xhci_pci'
  -> Running build hook: [filesystems]
  -> Running build hook: [keyboard]
  -> Running build hook: [keymap]
  -> Running build hook: [encrypt]
==> WARNING: Possibly missing firmware for module: 'qat_420xx'
  -> Running build hook: [fsck]
==> Generating module dependencies
==> Creating zstd-compressed initcpio image: '/boot/initramfs-linux-fallback.img'
  -> Early uncompressed CPIO image generation successful
==> Initcpio image generation successful
(7/8) Reloading system bus configuration...
(8/8) Updating the desktop file MIME type cache...

Last edited by angrynapkin (2024-03-16 23:49:34)

seth · 2024-03-16 23:48:50

re-installing what wants to update nvidia how?
Since you have the headers, just trigger the dkms rebuild and look out for errors.

angrynapkin · 2024-03-16 23:52:58

seth wrote:

re-installing what wants to update nvidia how?
Since you have the headers, just trigger the dkms rebuild and look out for errors.

My apologies, I force of habit to have -Syu
Here is reinstall of linux headers

warning: linux-headers-6.8.1.arch1-1 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...

Packages (1) linux-headers-6.8.1.arch1-1

Total Installed Size:  127.76 MiB
Net Upgrade Size:        0.00 MiB

:: Proceed with installation? [Y/n] y
(1/1) checking keys in keyring                                                                                                 [#############################################################################] 100%
(1/1) checking package integrity                                                                                               [#############################################################################] 100%
(1/1) loading package files                                                                                                    [#############################################################################] 100%
(1/1) checking for file conflicts                                                                                              [#############################################################################] 100%
(1/1) checking available disk space                                                                                            [#############################################################################] 100%
:: Running pre-transaction hooks...
(1/1) Remove upgraded DKMS modules
==> dkms remove --no-depmod vmware-workstation/17.5.1_23298084 -k 6.8.1-arch1-1
:: Processing package changes...
(1/1) reinstalling linux-headers                                                                                               [#############################################################################] 100%
:: Running post-transaction hooks...
(1/3) Arming ConditionNeedsUpdate...
(2/3) Updating module dependencies...
(3/3) Install DKMS modules
==> dkms install --no-depmod nvidia/545.29.06 -k 6.8.1-arch1-1
Error! Bad return status for module build on kernel: 6.8.1-arch1-1 (x86_64)
Consult /var/lib/dkms/nvidia/545.29.06/build/make.log for more information.
==> WARNING: `dkms install --no-depmod nvidia/545.29.06 -k 6.8.1-arch1-1' exited 10
==> dkms install --no-depmod vmware-workstation/17.5.1_23298084 -k 6.8.1-arch1-1
==> depmod 6.8.1-arch1-1

Ahh I see the error in there.

angrynapkin · 2024-03-16 23:57:27

Here is the nvidia make log: http://0x0.st/HCk2.txt

seth · 2024-03-17 00:14:28

6.8 GPL gonorrhea
https://gitlab.archlinux.org/archlinux/ … 6f7767ad54 or https://launchpadlibrarian.net/71308223 … u5.debdiff should work around that, but it would seem the former is part of your dkms package as well?

angrynapkin · 2024-03-17 00:17:41

Is it possible to downgrade the kernel to a version around the same date? Or are there to manay things dependent on the current kernel and I would end up downgrading everything.
Also that dkms status result with vmware workstation, that has been uninstalled. Must have been some left over config somwhere.

Arch Linux

#1 2024-03-10 17:06:41

Kernel Panic on Shutdown

#2 2024-03-10 18:08:08

Re: Kernel Panic on Shutdown

#3 2024-03-10 20:57:02

Re: Kernel Panic on Shutdown

#4 2024-03-10 21:02:05

Re: Kernel Panic on Shutdown

#5 2024-03-10 21:09:25

Re: Kernel Panic on Shutdown

#6 2024-03-10 21:23:07

Re: Kernel Panic on Shutdown

#7 2024-03-10 21:38:49

Re: Kernel Panic on Shutdown

#8 2024-03-15 19:17:25

Re: Kernel Panic on Shutdown

#9 2024-03-15 21:15:24

Re: Kernel Panic on Shutdown

#10 2024-03-16 15:36:54

Re: Kernel Panic on Shutdown

#11 2024-03-16 15:38:11

Re: Kernel Panic on Shutdown

#12 2024-03-16 22:31:54

Re: Kernel Panic on Shutdown

#13 2024-03-16 22:48:21

Re: Kernel Panic on Shutdown

#14 2024-03-16 22:56:59

Re: Kernel Panic on Shutdown

#15 2024-03-16 22:58:24

Re: Kernel Panic on Shutdown

#16 2024-03-16 23:16:38

Re: Kernel Panic on Shutdown

#17 2024-03-16 23:21:35

Re: Kernel Panic on Shutdown

#18 2024-03-16 23:30:42

Re: Kernel Panic on Shutdown

#19 2024-03-16 23:40:01

Re: Kernel Panic on Shutdown

#20 2024-03-16 23:46:53

Re: Kernel Panic on Shutdown

#21 2024-03-16 23:48:50

Re: Kernel Panic on Shutdown

#22 2024-03-16 23:52:58

Re: Kernel Panic on Shutdown

#23 2024-03-16 23:57:27

Re: Kernel Panic on Shutdown

#24 2024-03-17 00:14:28

Re: Kernel Panic on Shutdown

#25 2024-03-17 00:17:41

Re: Kernel Panic on Shutdown

Board footer