New Kernel seems broken for me

[GoinEasy9]

Hi

I purged mdadm removed quiet and this is what came up.

[GoinEasy9]

Hello

OK, just did an update, got a new kernel, 5.15.2-2, boot worked without error. I guess we received some towo magic.

I'm curious, do we know what caused it?

I'm leaving mdadm purged, I have no raid devices that need monitoring.

Thanks

[towo]

If the new kernel is working, the problem was upstream, since the new kernel has only patch-5.15.3-rc2 added.

[michaa7]

Off topic but I posting it here due to tthe latest posting:


@ towo purely out of couriosity:

I assumed the siduction kernels are based on the latest stable kernel, which currently is 5.15.


Now seeing in the above posting that the newest kernel has the 5.15-rc2 patch it looks like the current siduction kernel is 5.14 plus selected 5.15 patches? So at which point do you switch to the next kernel number? Or what does it mean?


So is the general idea to use the pre-stabel kernel as the basis for siduction kernels and then add step by step the RC patches of the latest released kernel and see how it works out for siduction users? And then the numbering does not refere to the released kernel but only to the use of some RC-patches of said kernel?

This is for my (and maybe other's) couriosity only ...

All working well here and thanks again.

[towo]

You should open your eyes.
I sayed the kernel has patch 5.15.3-rc2 in, not 5.15-rc2.

[michaa7]

Ok, thanks, right you are. Now understood.

[ralul]

Auf Kernel.org jetzt gerade eingestellt:
stable:    5.15.3    2021-11-18
Bestimmt identisch mit Towos _rc2 Linux kernel.

[GoinEasy9]

Hi

Strangest thing, on this same computer ... during this mornings full-upgrade I got a kernel panic. I had to do a cold boot to recover, and, during dpkg --reconfigure -a, I got another kernel panic. I'm not sure, but I think it was trying to rebuild intramfs when it happened. dpkg --reconfigure -a after the second panic came up with nothing. Upon reboot, the new 5.15.4 kernel booted just fine and there doesn't seem to be any residual problems from the kernel panic.

DU's on the new machine and the old lxqt laptop went without incident.

BTW - Thunderbird just  released it's 5.15 kernel, and, it blew up on this machine also. Instead of just dropping me to busybox, it just left me with some colored artifacts.