Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230

 

 

 

Kernel panic 5.10.0-17

Off-Topic discussions about science, technology, and non Debian specific topics.
Post Reply
Message
Author
Irina060
Posts: 3
Joined: 2022-08-18 08:35

Kernel panic 5.10.0-17

#1 Post by Irina060 »

Hi everyone, first post here. I've been using Q4OS for a while which is based on debian and since I've updated the kernel to 5.10.0-17-686-pae its been giving me this kernel panic error.
I can use 5.10.0-16-686-pae just fine as the grub allows me to select another kernel at boot but I would prefer to use the latest kernel available to the distro Im using.
Although I've used different distros for around a year or two Im not used to having this kind of problems, not sure if this is an issue with the kernel or with my pc.
The pc is an IBM Thinkpad t23, 768mb of ram (up to 1gb), intel pentium 3 at 1.13ghz, 256gb ssd msata to pata, pcmcia with usb 2.0 and wifi.
Personally I cant tell whats wrong, sure the laptop is old but it's been working fine until I updated the kernel. I'll provide some pics with details.
Maybe the problem was fixed with later versions of the kernel but, again, I cant really tell.

Thanks.
Attachments
screen2.jpeg
screen2.jpeg (193.93 KiB) Viewed 2164 times
screen1.jpeg
screen1.jpeg (204.59 KiB) Viewed 2164 times


Aki
Global Moderator
Global Moderator
Posts: 2823
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 69 times
Been thanked: 385 times

Re: Kernel panic 5.10.0-17

#3 Post by Aki »

Hello,
Your CPU is very old, even if it should be supported by current Debian Stable. Furthermore, you have very little RAM for current standards.

Have you tested the “not-pae” version of the kernel (linux-image-5.10.0-16-686) [1] ?

[1] https://packages.debian.org/bullseye/li ... 0.0-16-686
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Irina060
Posts: 3
Joined: 2022-08-18 08:35

Re: Kernel panic 5.10.0-17

#4 Post by Irina060 »

I already asked in q4os forum, they clarified that it is a debian kernel thats why I ask here.
I havent tried non pae kernel, I will and let you know the results.
I know the cpu is old and ram is not a lot but as you can see, the os uses less than 200mb and cpu supports kernel 5.10.0-16 thays why I it surprises me that version 5.10.0-17 doesnt work. Q4OS has a version for older pcs like mine which is nice

Aki
Global Moderator
Global Moderator
Posts: 2823
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 69 times
Been thanked: 385 times

Re: Kernel panic 5.10.0-17

#5 Post by Aki »

Hello,

Nice to hear from you again.
Irina060 wrote: 2022-08-19 12:27 I already asked in q4os forum, they clarified that it is a debian kernel thats why I ask here.
The kernel linux-image-5.10.0-17-amd64 is a Debian package, indeed. It's currently in the bullseye-security repository (Debian Stable release). For example, I've installed it today in my Debian Stable (for amd64, not i386):

Code: Select all

root@debian-aki:~# apt-cache policy linux-image-5.10.0-17-amd64
linux-image-5.10.0-17-amd64:
  Installato: 5.10.136-1
  Candidato:  5.10.136-1
  Tabella versione:
 *** 5.10.136-1 500
        500 https://deb.debian.org/debian-security bullseye-security/main amd64 Packages
        100 /var/lib/dpkg/status
It booted it without any issue.

I did further research about your issue.

The bad news is that the issue you reported seems to be a specific bug of the upstream kernel (see [1]). Debian developers have forwarded the bug upstream and are still analyzing possible solutions. The cause seems to be software mitigations for new CPU's software vulnerabilities in recent kernels that are incompatible with intel pentium 3 instruction set (and amd similar cpus).

The good news is that a workaround is available [2]:
As a temporary workaround, disabling the Spectre v2 mitigation with the
kernel parameter "nospectre_v2" should allow this kernel version to run
on older CPUs without SSE2. We'll fix this properly in a later update.
Therefore, you should configure grub to add the kernel parameter nospectre_v2. Of course, this disables all mitigations for the Spectre variant 2 (indirect branch prediction) vulnerability. System may allow data leaks with this option. But it should be faster, at least. :roll:

Hope that helps

[1] https://bugs.debian.org/cgi-bin/bugrepo ... ug=1017425
[2] https://bugs.debian.org/cgi-bin/bugrepo ... 1017425#22
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Irina060
Posts: 3
Joined: 2022-08-18 08:35

Re: Kernel panic 5.10.0-17

#6 Post by Irina060 »

Thanks for the workaround, sorry for replying so late. I also read your links. If I understood correctly it will be patched at some point which is a relief tbh. While olders cpus lack instruction sets required for security features some late 32bit cpus (early pentium4) had those instruction sets. I want to ask tho, I feel like some pentium4 could benefit from this security update but the rest of 32bit cpus like pentium3, athlon and athlonxp wont work at all unless doing the work around, what is going to happen? Is there going to be a branched update path for old 32bit cpu? Im curious

Aki
Global Moderator
Global Moderator
Posts: 2823
Joined: 2014-07-20 18:12
Location: Europe
Has thanked: 69 times
Been thanked: 385 times

Re: Kernel panic 5.10.0-17

#7 Post by Aki »

Hi,
The bug report https://bugs.debian.org/cgi-bin/bugrepo ... ug=1017425 has been reported as fixed with Linux kernel version 5.10.140-1
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org
⠈⠳⣄⠀

Post Reply