Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: [SOLVED] Hardened kernel panic (Read 758 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

[SOLVED] Hardened kernel panic

 Hello, anyone has problems with the latest hardened kernel? (6.5.13.hardened1-1) Looks like it throws a panic and complains  about the iptables module.

 The normal kernel doesn't give me any issues works perfect.

Re: Hardened kernel panic

Reply #1 –
Same problems here. I'll try linux-Kernel.

Re: Hardened kernel panic

Reply #2 –

 Good to know is something general and it's not just me. 😌 I've looked briefly into the patch but couldn't figure out much. There are many changes between latest and the previous version.

 This is why I'm having two kernels installed, just in case one fails.

 Tnx

Re: Hardened kernel panic

Reply #3 –
Yes, I have the same problem after upgrading to linux-hardened-6.5.13.hardened1-1

UPDATE

And for several updates now I can’t connect my Android smartphone to my PC. I don’t know yet whether the kernel is to blame...

Re: Hardened kernel panic

Reply #4 –

 Well looks like we are already 3 guys having ~ the same issue. I think this will be fixed soon as this bug seems to be rather wide spread for those who boot this kernel. I remember having same problem not long ago with this kernel and waited for the next release that finally worked.

Re: Hardened kernel panic

Reply #5 –
I've also got the same problem. Had to use a rescue stick to install an alternative (non-hardened) kernel.
Would some of the pain this involved be alleviated by always keeping an old kernel as a backup when the update process runs?

Re: Hardened kernel panic

Reply #6 –
Quote from: habiloid – on
I've also got the same problem. Had to use a rescue stick to install an alternative (non-hardened) kernel.
Would some of the pain this involved be alleviated by always keeping an old kernel as a backup when the update process runs?
When upgrading a kernel in debian, the old kernel is not replaced with a new one, but the entries in the bootloader are simply updated. As a result, after an update and a failed boot, you simply reboot and select the old kernel in the grub menu and boot. You can do the same on your artix :)

Re: Hardened kernel panic

Reply #8 –
I just launched a rebuild a the previous version of the kernel.
If you can't wait for the package to reach your mirror (it will be ready in a few hours since it is behind a chromium build) just downgrade manually.

Re: Hardened kernel panic

Reply #9 –

 Any idea what nuked the kernel? Not a kernel specialist but would be nice to know ???
Quote
keeping an old kernel as a backup when the update process runs?
No not old kernel just a working one. I'm using 2 kernels the hard one and the default/current. If hardened panics I just use the current.  :D

Hardened kernel should be alternatively named 'the anything but zen kernel' ;D

I'll go update now and I think I can close it. Tnx everyone who looked into this and Merry Christmas for those who celebrate!
🎄🌨️🌨☃️

Re: [SOLVED] Hardened kernel panic

Reply #11 –

 The only change is this. They added 13 lines of code, idk, from what I could find they say it's shell 🤔



 

Re: [SOLVED] Hardened kernel panic

Reply #12 –
They changed a patch (diff) file which changes a file written in kernel C, which is not quite like GLIBC C. You now need to look at include/net/neighbour.h to see how the changes alter things in the relevant section.
The only actual change was the line u8 primary_key[0] changed  to u8 primary_key[]
https://elixir.bootlin.com/linux/latest/source/include/net/neighbour.h