Kernel Panic

saleem · 2017-06-08 16:15:46

I just updated my system ( i686 ) with updates , fetching kernel package upgrade from 4.10.13 to stock version. All the packages were upgraded without any issue. Upon reboot I faced Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b . From chroot I downgraded to the previous working kernel but still getting kernel panic , once again downgraded to kernel 4.9 but same kernel panic error. I am using intel driver for GPU . Reading this thread https://www.reddit.com/r/archlinux/comm … st_update/ I downgraded linux-firmware but no effect. As a last resort tried lts version kernel but that did not help either. Tried linux-ck but no help.

Any suggestions what is causing this kernel panic issue?

seth · 2017-06-08 20:15:57

That will not be all of the message (in doubt remove the "quiet" kernel parameter).
=> Take a photo of the screen and upload that to some image board. Please do only link text or a thumbnail, not the full resolution photo.

mich41 · 2017-06-08 22:21:44

From chroot, check if all updates were installed correctly and everything is up to date. This is a userspace process crashing or failing to start at all, not the kernel.

What got updated besides the kernel?

trytipARCH · 2017-06-08 22:21:50

...

Last edited by trytipARCH (2017-06-11 03:55:58)

jasonwryan · 2017-06-08 22:28:54

trytipArch: please don't dump things in threads unless you are 100% certain they are relevant: the above is not. OP can clearly chroot, has tried other kernels and their choice of boot loader/manager is irrelevant.

trytipARCH · 2017-06-08 22:41:07

...

Last edited by trytipARCH (2017-06-11 03:56:10)

saleem · 2017-06-09 04:18:12

seth wrote:

That will not be all of the message (in doubt remove the "quiet" kernel parameter).
=> Take a photo of the screen and upload that to some image board. Please do only link text or a thumbnail, not the full resolution photo.

I am at work at moment , once I am home I will upload the error message from stock kernel because yes I did note that though I get repeated kernel panic with all different kernels I tried but with every kernel the error message is different every time.

saleem · 2017-06-09 04:20:05

trytipARCH wrote:

there are many kernel panics, IF i assume ARCH is your boot loader and you can chroot into some terminal with internet connection try
sudo pacman -Syu
sudo pacman -S filesystem
sudo mkinitcpio -p linux
sudo grub-mkconfig -o /boot/grub/grub.cfg
if not, boot with a live linux and do the same BUT mounting your ARCH in ROOT terminal first
sudo mount /dev/sdb4 /mnt <<< replace [sdb4] with your arch mount point
sudo arch-chroot /mnt
sudo pacman -Syu
sudo pacman -S filesystem
sudo mkinitcpio -p linux
sudo grub-mkconfig -o /boot/grub/grub.cfg

I will give it a try , no harm in trying but I'm not sure if these steps might help

saleem · 2017-06-09 04:22:47

mich41 wrote:

From chroot, check if all updates were installed correctly and everything is up to date. This is a userspace process crashing or failing to start at all, not the kernel.
What got updated besides the kernel?

There were quite of updates , around 600 plus mb of updates , and during updates I did not get any errors. How can know ( what command ) which exact packages were updated?

jasonwryan · 2017-06-09 04:51:57

Read pacman's log.

saleem · 2017-06-09 08:12:34

Kernel panic arch https://imgur.com/gallery/WyBbS
Hope this gives some clue

saleem · 2017-06-09 08:32:15

Here is pacman log

https://pastebin.com/FeSzeS5G

Trilby · 2017-06-09 10:49:03

trytipARCH, perhaps my light tone here made it sound like code tags were optional. They are not. I'd strongly encourage you to reduce your use of colors on the forums in general, but I will insist that you properly use code tags for commands and code output from now on. Do not put command output in color tags.

seth · 2017-06-09 13:50:54

Try passing "init=/bin/bash" (this will not conduct a "normal" boot but tell us whether this is a problem in the kernel/rootfs or the init binary) and/or reinstall systemd.
If that doesn't "boot" either, try the failsafe initrmfs.

Also the text on the photo is rather brief, ensure that this actually an updated kernel image (the kernel should be mentioned few lines above; try shift+pgup) - do you have other OS installed which share the same boot partition?

saleem · 2017-06-09 17:08:24

seth wrote:

Try passing "init=/bin/bash" (this will not conduct a "normal" boot but tell us whether this is a problem in the kernel/rootfs or the init binary) and/or reinstall systemd.
If that doesn't "boot" either, try the failsafe initrmfs.
Also the text on the photo is rather brief, ensure that this actually an updated kernel image (the kernel should be mentioned few lines above; try shift+pgup) - do you have other OS installed which share the same boot partition?

passing "init=/bin/bash" did not change the error message .

I did not try the failsafe initrmfs method at this stage.

yes the kernel is the latest stock one i.e linux 4.11.3-1. My system is multiboot but the boot partition of this particular installation is not shared by any other OS.

saleem · 2017-06-09 19:37:22

To double check and reproduce this error I did a fresh install of arch linux i686 on a spare partition and I was able to produce exactly same kernel panic error on this fresh install . I request someone to do a fresh install in a virtual box or on a spare partition to see if the same kernel panic error is produced on not. I feel there is something going on with i686 packages. With this kernel panic error I am kind of in a hands up position at present.

seth · 2017-06-09 19:39:01

No, the kernel version that is indicated in the panic - the problem could be that you update into an unmounted /boot partition.
In general, try to get us more heading output - there might be further indications (eg. if the root device cannot be mounted in time, you'd get that message "in your face" ;-)

Edit: if this is nothing in your HW but actually due to the i686 packages, glibc and the rebuild against gcc 7.1 would be highly suspicious ... ie. try downgrading this and gcc-libs.

Last edited by seth (2017-06-09 19:55:45)

saleem · 2017-06-09 20:28:19

seth wrote:

No, the kernel version that is indicated in the panic - the problem could be that you update into an unmounted /boot partition.
In general, try to get us more heading output - there might be further indications (eg. if the root device cannot be mounted in time, you'd get that message "in your face" ;-)
Edit: if this is nothing in your HW but actually due to the i686 packages, glibc and the rebuild against gcc 7.1 would be highly suspicious ... ie. try downgrading this and gcc-libs.

I am trying to downgrade to these two packages

3) gcc-6.3.1-2-i686.pkg.tar.xz (remote)

3) gcc-libs-6.3.1-2-i686.pkg.tar.xz (remote)

but I am getting packages conflicts

warning: cannot resolve "gcc-libs=6.3.1-2", a dependency of "gcc"
:: The following package cannot be upgraded due to unresolvable dependencies:
gcc

:: Do you want to skip the above package for this upgrade? [y/N]

warning: downgrading package gcc-libs (7.1.1-2 => 6.3.1-2)
resolving dependencies...
looking for conflicting packages...
error: failed to prepare transaction (could not satisfy dependencies)
:: gcc: installing gcc-libs (6.3.1-2) breaks dependency 'gcc-libs=7.1.1-2'

how to fix this?

Last edited by saleem (2017-06-09 20:29:39)

seth · 2017-06-09 20:32:16

YouÄll have to downgrade everything that depends on gcc-libs (see "pacman -Qi gcc-libs") and that notably includes glibc, the library you actually want to downgrade.

loqs · 2017-06-09 21:30:35

https://bugs.archlinux.org/task/54240?

saleem · 2017-06-10 06:18:23

seth wrote:

YouÄll have to downgrade everything that depends on gcc-libs (see "pacman -Qi gcc-libs") and that notably includes glibc, the library you actually want to downgrade.

Downgraded all the packages related to gcc but did not help

seth · 2017-06-10 06:28:26

"pacman -Qi glibc" - should be glibc-2.25-1 now.

You also need to mkinitcpio again!

subwaypassenger · 2017-06-10 12:33:30

Check packages.
"pacman -Qkk"

saleem · 2017-06-10 16:03:09

seth wrote:

"pacman -Qi glibc" - should be glibc-2.25-1 now.
You also need to mkinitcpio again!

Finally with the help of seth and loqs I am able to trace down and bypass and overcome the kernel panic issue I was facing . I will summarize the steps as follows , so those who face this issue might find it easy how to fix this issue.

1 . It is for sure that glibc update from 2.25-1 to 2.25-2 is the root cause of kernel panic or inability of system after installing updates, also mentioned in this thrad https://bugs.archlinux.org/task/54240

2. Once I was sure that this is the root cause , I restored backup image of my installation without the recent updates installed . This backup image had older older version of kernel ( 4.10 ) and was bootable and had glibc 2.25-1 installed on it.

3. I edited pacman.conf and added this line into it "IgnorePkg = glibc"

4. Installed all the updates normally with "sudo pacman -Syu" . After installing all the updates rebooted and system started normally without any error.

5. Now my system is running with kernel "$ uname -a Linux home-pc 4.11.3-1-ARCH #1 SMP PREEMPT Sun May 28 11:00:30 CEST 2017 i686 GNU/Linux" and glibc 2.25-1 locked/held.

I am reporting these findings to help this issue fixed in next updates by the developers and to help others with this issue.

Lastly should I label this thread as SOLVED now ?

Regards,

Last edited by saleem (2017-06-10 16:05:04)

V1del · 2017-06-10 18:43:46

If it solved from your POV go ahead. Just be aware that you are essentially running a partial upgrade now, and you should keep an eye on that bug, and reupdate glibc once this is considered fixed.

Arch Linux

#1 2017-06-08 16:15:46

Kernel Panic

#2 2017-06-08 20:15:57

Re: Kernel Panic

#3 2017-06-08 22:21:44

Re: Kernel Panic

#4 2017-06-08 22:21:50

Re: Kernel Panic

#5 2017-06-08 22:28:54

Re: Kernel Panic

#6 2017-06-08 22:41:07

Re: Kernel Panic

#7 2017-06-09 04:18:12

Re: Kernel Panic

#8 2017-06-09 04:20:05

Re: Kernel Panic

#9 2017-06-09 04:22:47

Re: Kernel Panic

#10 2017-06-09 04:51:57

Re: Kernel Panic

#11 2017-06-09 08:12:34

Re: Kernel Panic

#12 2017-06-09 08:32:15

Re: Kernel Panic

#13 2017-06-09 10:49:03

Re: Kernel Panic

#14 2017-06-09 13:50:54

Re: Kernel Panic

#15 2017-06-09 17:08:24

Re: Kernel Panic

#16 2017-06-09 19:37:22

Re: Kernel Panic

#17 2017-06-09 19:39:01

Re: Kernel Panic

#18 2017-06-09 20:28:19

Re: Kernel Panic

#19 2017-06-09 20:32:16

Re: Kernel Panic

#20 2017-06-09 21:30:35

Re: Kernel Panic

#21 2017-06-10 06:18:23

Re: Kernel Panic

#22 2017-06-10 06:28:26

Re: Kernel Panic

#23 2017-06-10 12:33:30

Re: Kernel Panic

#24 2017-06-10 16:03:09

Re: Kernel Panic

#25 2017-06-10 18:43:46

Re: Kernel Panic

Board footer