Kernel Panic on Shutdown

seth · 2024-03-17 00:20:08

You can reasonably downgrade the kernel in isolation, it's mostly self-contained and won't get you into troubles all that quickly.
You can also just try the LTS kernel.

angrynapkin · 2024-03-17 00:27:06

Ok, yeah Ill install the LTS and see if that works.

I really appreciate you taking the time trying to help me.

Last edited by angrynapkin (2024-03-17 00:27:47)

angrynapkin · 2024-03-17 01:54:51

Ok, thanks again for the assistance,
I got the lts kernel and headers installed from back when the nvidia driver worked (not sure if thats required, but thats what I did).
installed the rolled back nvidia-dkms drivers to 545.x.
removed the ibt=off I had from kernel parameter ( cant even remember why that was there) and replaced it with 'nvidia_drm.modeset=1' so I could get the

 To verify nvidia_drm.modeset=1 was correctly applied after a reboot, execute the following:
# cat /sys/module/nvidia_drm/parameters/modeset

to show Y and not N,
and now I seem to have working 3D back in vmware workstation.

HURRAYYY

seth · 2024-03-17 07:50:23

Now let's see whether the kernel panic is gone, too (though since you're now on LTS it's less meaningful)

Once nvidia releases a driver update, you want to check those and the current kernel and in case then please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

angrynapkin · 2024-03-17 17:31:17

seth wrote:

Now let's see whether the kernel panic is gone, too (though since you're now on LTS it's less meaningful)
Once nvidia releases a driver update, you want to check those and the current kernel and in case then please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Yeah No kernel panic at all. I guess I can try installing a non lts older version kernel too, but I am happy its just working again.
Ill test each new release of nvidia too and see if gets fixed.

Not sure how to edit the subject. I hijacked this thread and I am not the OP.

qualia · 2024-03-18 02:25:13

seth wrote:

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

I have uploaded it here: https://0x0.st/XrNy.txt. Yes, I have an Nvidia GPU and will look into what you linked.

seth · 2024-03-18 08:00:13

Backtrace s differ but look related.
nb.

Mar 17 17:11:09.914566 void kernel: simple-framebuffer simple-framebuffer.0: swiotlb buffer is full (sz: 35647488 bytes), total 32768 (slots), used 0 (slots)

That's the SIMPLYDUMB device, enable https://wiki.archlinux.org/title/NVIDIA … de_setting - use the "nvidia_drm.modeset=1" kernel parameter (modprobe.conf won't do!)

Arch Linux

#26 2024-03-17 00:20:08

Re: Kernel Panic on Shutdown

#27 2024-03-17 00:27:06

Re: Kernel Panic on Shutdown

#28 2024-03-17 01:54:51

Re: Kernel Panic on Shutdown

#29 2024-03-17 07:50:23

Re: Kernel Panic on Shutdown

#30 2024-03-17 17:31:17

Re: Kernel Panic on Shutdown

#31 2024-03-18 02:25:13

Re: Kernel Panic on Shutdown

#32 2024-03-18 08:00:13

Re: Kernel Panic on Shutdown

Board footer