Puppy Linux Discussion Forum

Kernel 5.11.4-rt11 PREEMPT (low latency) with virtualization support enabled, for desktop use.

▶—— Linux Kernel ——◀

Kernel Release: 5.11.4-rt11
Build Date: Sat Mar 13 18:36:56 EST 2021
Build GCC: 9.3.0-10ubuntu2)
OS Support: GNU/Linux
Architecture: x86_64
SMP Enabled: Yes

here it is -> https://rockedge.org/kernels/
or direct -> http://rockedge.org/kernels/data/kernel ... 11.tar.bz2

Compiled and tested in Fossapup64-9.0.5 and also tested in Bionic64-CE

Interesting timing...
So I have built a 5.10.17 low latency kernel a few weeks ago and have been testing it heavily since on my two main machines (audio, midi, compiling...) one samsung laptop, one msi/amd thing.
Seemed ready for sharing but last night, the first tester reported an unclean shutdown.. I was eventually able to reproduce it on another pc, an hp probook i3. The other user also had the issue on an hp i5 (not sure how close the models are yet)
Turns out this kernel also has the same error at shutdown on the hp probook. Dumps the below, then hangs...
At one point in testing, I accidentally booted only vmlinuz and that did shutdown cleanly. oops, but interesting... So I went through and checked, and it is repeatable that both kernels shutdown cleanly without the modules loaded.
I thought I should report this.

I have not had any shutdown problems yet, but I can not get the kernel sources from 5.11.4-rt11 to be recognized when I attempt to build a VirtualBox 6.1 disk driver module

I posted a similar shutdown problem with any kernel after 5.8. It seems to be an HP problem, as other laptops (Lenovo & Acer I tried) are OK. Tried this kernel - same result on 2 HPs (i3-5005u & Celeron 1000M).

I have the answer for my 5.8+ kernel crashes - I need to blacklist snd_hda_codec_realtek.
Done by appending kernel line in grub.cfg or syslinux.cfg thus: modprobe.blacklist=snd_hda_codec_realtek
OR by including adding to /etc/modprobe.d/blacklist.conf: blacklist snd_hda_codec_realtek

@puddlemoon - you should try blacklisting snd_hda_codec_idt by using either above method.

success!
I blacklisted the snd_hda_codec_idt as suggested via my refind.conf and got a clean shutdowm from both the 5.10.17 and the 5.11.4..
Thanks @ozsouth for sharing your findings.

Now to determine if it will be critically missed by anything, with it loaded lsmod shows it is not used by any other module.
on the samsung laptop (with no issues) "lsmod | grep idt" returns nothing.