LinuxQuestions.org
Page 3 of 3 12 3
Show 50 post(s) from this thread on one page

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   kernel panic on boot with generic kernel 3.10.17 on slackware 14.1 (https://www.linuxquestions.org/questions/slackware-14/kernel-panic-on-boot-with-generic-kernel-3-10-17-on-slackware-14-1-a-4175583694/)

Gerard Lally 07-08-2016 03:04 PM
Quote:
Originally Posted by josefin (Post 5572689)
Unfortunately not, there's no bios option to disable them.
How about the LSI SAS adapter then? Is it possible the initrd is enumerating the controllers in the wrong sequence, with sda shifted to sdb or sdc? The huge kernel boots of course, but it's worth a try. If you can't disable it, how about adding the LSI SAS module to the initrd?

Gerard Lally 07-08-2016 03:06 PM
Quote:
Originally Posted by astrogeek (Post 5572693)
Second, reference the / partition by UUID in the initrd to avoid any boot time weirdness. You can find it by running blkid.
Excellent.

josefin 07-08-2016 03:08 PM
Quote:
Originally Posted by astrogeek (Post 5572693)
A couple of shots in the dark...

First, --IGNORE - COMPLETELY MISSED x86_64--

Second, reference the / partition by UUID in the initrd to avoid any boot time weirdness. You can find it by running blkid.

Here are example lines using UUID and a versioned initrd name just to keep them explicitly separate.

Code:

  initrd = /boot/initrd-3.10.17-uuid.gz
...
mkinitrd -c -k 3.10.17 -f ext4 -r "UUID=xxxx-yyyyy-zzzzz" -m usbhid:hid_generic:xhci-hcd:mbcache:jbd2:ext4 -u -o /boot/initrd-3.10.17-uuid.gz
Unfortunately it didn't help. Still the same kernel panic.

Richard Cranium 07-08-2016 03:31 PM
How about re-installing the cpio and gzip packages and re-create your initrd?

FWIW, do you use a separate /boot partition? If so, does it have enough space for the initrd?

josefin 07-08-2016 08:04 PM
Quote:
Originally Posted by Richard Cranium (Post 5572712)
How about re-installing the cpio and gzip packages and re-create your initrd?

FWIW, do you use a separate /boot partition? If so, does it have enough space for the initrd?
I didn't have a separate /boot partition.

I still have no idea what was going wrong, but I wiped 14.1 and installed 14.2 instead and now the generic kernel boots without a hitch.

Thanks everyone for all your help and suggestions! :party:

astrogeek 07-08-2016 08:08 PM
You are welcome, thanks for the patience and the resolution, such as it is!

My guess is that there was something corrupted on the 14.1 system... very strange!

Have fun with 14.2!


All times are GMT -5. The time now is 12:15 AM.
Page 3 of 3 12 3
Show 50 post(s) from this thread on one page