LinuxQuestions.org - [SOLVED] kernel panic on boot with generic kernel 3.10.17 on slackware 14.1

- 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/)

kernel panic on boot with generic kernel 3.10.17 on slackware 14.1

I am unable to boot the generic kernel on my slackware 14.1 box.

The motherboard is an asus Z9PA-D8 dual xeon. It boots without any problems using the huge kernel.

I made an initrd with

Code:

mkinitrd -c -k 3.10.17 -f ext4 -r /dev/sda1 -m usbhid:hid_generic:xhci-hcd:mbache:jbd2:ext4 -u -o /boot/initrd.gz

according to the output of the mkinitrd_comand_generator.sh. I then added the generic kernel to lilo.conf (file to follow in next post) and ran lilo as root.

I have filmed the boot process with my cellphone, unfortunately it is not fully informative as the text scrolls too quickly past the initial error:

https://www.youtube.com/watch?v=nFElfhykd38

However on a previous boot it showed the error clearly, and it was the good old

Code:

kernel panic-not syncing: VFS: unable to mount root fs

This is perplexing as I am sure I have built the initrd correctly with the ext4 module, and updated lilo. I have tried reinstalling from scratch and switching to the generic kernel on the fresh installation, but the result is the same.

Does anyone have any idea what the problem is?

Dunno, but you should be able to look into (assuming that you are able to boot into the system at all) /boot/initrd-tree to see what would be in your initrd.

I'd double-check the contents of /boot/initrd-tree/rootdev and /boot/initrd-tree/rootfs to ensure that they match what you think they should be.

You should also check your lilo.conf file to see if it matches. Perhaps you could post the contents of it here.

Here is my lilo.conf:

Code:

# LILO configuration file

# generated by 'liloconfig'

#

# Start LILO global section

# Append any additional kernel parameters:

append=" vt.default_utf8=1 resume=/dev/sda2"

boot = /dev/sda



#compact        # faster, but won't work on all systems.



# Boot BMP Image.

# Bitmap in BMP format: 640x480x8

  bitmap = /boot/slack.bmp

# Menu colors (foreground, background, shadow, highlighted

# foreground, highlighted background, highlighted shadow):

  bmp-colors = 255,0,255,0,255,0

# Location of the option table: location x, location y, number of

# columns, lines per column (max 15), "spill" (this is how many

# entries must be in the first column before the next begins to

# be used.  We don't specify it here, as there's just one column.

  bmp-table = 60,6,1,16

# Timer location x, timer location y, foreground color,

# background color, shadow color.

  bmp-timer = 65,27,0,255



# Wait until the timeout to boot (if commented out, boot the

# first entry immediately):

prompt

# Timeout before the first entry boots.

# This is given in tenths of a second, so 600 for every minute:

timeout = 1200

# Override dangerous defaults that rewrite the partition table:

change-rules

  reset

# Normal VGA console

vga = normal



# End LILO global section

# Linux bootable partition config begins

image = /boot/vmlinuz

  root = /dev/sda1

  label = 3.10.17-huge

  read-only

image = /boot/vmlinuz-generic-3.10.17

  initrd = /boot/initrd.gz

  root = /dev/sda1

  label = 3.10.17-generic

  read-only

# Linux bootable partition config ends

Richard, my /boot/initrd-tree/rootdev and /boot/initrd-tree/rootfs
contain /dev/sda1 and ext4 as expected.

What's the output of running lilo with the -vv flag added?

And while we are at it, how about the output of...

Code:

find /boot/initrd-tree/lib/modules

...?

Here running lilo:

Code:

# lilo    

Warning: LBA32 addressing assumed

Added 3.10.17-huge  *

Added 3.10.17-generic  +

One warning was issued.

Here running lilo -w:

Code:

# lilo -w

Added 3.10.17-huge  *

Added 3.10.17-generic  +

One warning was suppressed.

Code:

# find /boot/initrd-tree/lib/modules/

/boot/initrd-tree/lib/modules/

/boot/initrd-tree/lib/modules/3.10.17

/boot/initrd-tree/lib/modules/3.10.17/modules.dep

/boot/initrd-tree/lib/modules/3.10.17/modules.alias

/boot/initrd-tree/lib/modules/3.10.17/modules.devname

/boot/initrd-tree/lib/modules/3.10.17/modules.symbols.bin

/boot/initrd-tree/lib/modules/3.10.17/modules.order

/boot/initrd-tree/lib/modules/3.10.17/modules.dep.bin

/boot/initrd-tree/lib/modules/3.10.17/kernel

/boot/initrd-tree/lib/modules/3.10.17/kernel/drivers

/boot/initrd-tree/lib/modules/3.10.17/kernel/drivers/hid

/boot/initrd-tree/lib/modules/3.10.17/kernel/drivers/hid/usbhid

/boot/initrd-tree/lib/modules/3.10.17/kernel/drivers/hid/usbhid/usbhid.ko

/boot/initrd-tree/lib/modules/3.10.17/kernel/drivers/hid/hid.ko

/boot/initrd-tree/lib/modules/3.10.17/kernel/drivers/hid/hid-generic.ko

/boot/initrd-tree/lib/modules/3.10.17/kernel/drivers/usb

/boot/initrd-tree/lib/modules/3.10.17/kernel/drivers/usb/host

/boot/initrd-tree/lib/modules/3.10.17/kernel/drivers/usb/host/xhci-hcd.ko

/boot/initrd-tree/lib/modules/3.10.17/kernel/fs

/boot/initrd-tree/lib/modules/3.10.17/kernel/fs/ext4

/boot/initrd-tree/lib/modules/3.10.17/kernel/fs/ext4/ext4.ko

/boot/initrd-tree/lib/modules/3.10.17/kernel/fs/mbcache.ko

/boot/initrd-tree/lib/modules/3.10.17/kernel/fs/jbd2

/boot/initrd-tree/lib/modules/3.10.17/kernel/fs/jbd2/jbd2.ko

/boot/initrd-tree/lib/modules/3.10.17/modules.builtin

/boot/initrd-tree/lib/modules/3.10.17/modules.alias.bin

/boot/initrd-tree/lib/modules/3.10.17/modules.builtin.bin

/boot/initrd-tree/lib/modules/3.10.17/modules.symbols

/boot/initrd-tree/lib/modules/3.10.17/modules.softdep

Quote:

mkinitrd -c -k 3.10.17 -f ext4 -r /dev/sda1 -m usbhid:hid_generic:xhci-hcd:mbache:jbd2:ext4 -u -o /boot/initrd.gz

There is a typo in there. 'mbache' should be 'mbcache'.

PS - I have deja vu on this.

Thanks, but I asked for the "-vv" flag, not the "-w" flag.

Is this the 32 bit version of 14.1 or the 64 bit version? The kernel names are slightly different between the two.

Quote:

Originally Posted by allend (Post 5570001)

There is a typo in there. 'mbache' should be 'mbcache'.

PS - I have deja vu on this.

I'm glad you're lurking. I think that makes you 2-for-2 on this issue. :)

Thanks to Johnson, I have recently had repeated practice in the use of mkinitrd. :)

Quote:

Originally Posted by Richard Cranium (Post 5570004)

Thanks, but I asked for the "-vv" flag, not the "-w" flag.

Is this the 32 bit version of 14.1 or the 64 bit version? The kernel names are slightly different between the two.

Dang, with the default font on 14.2 in Firefox, that still looks like a 'W', not 2 'V's.

Quote:

Originally Posted by bassmadrigal (Post 5570012)

Dang, with the default font on 14.2 in Firefox, that still looks like a 'W', not 2 'V's.

Yeah, I know. I should have enlarged it the first time, but I wasn't paying attention. I don't blame the OP one bit for misinterpreting it.

Quote:

Originally Posted by allend (Post 5570001)

There is a typo in there. 'mbache' should be 'mbcache'.

PS - I have deja vu on this.

Well spotted, but unfortunately that's not the problem. It's a typo from me copying out the command longhand to this forum using a different computer (wifi problems).

When actually running the command, I copied it verbatim using the clipboard, i.e.

Code:

mkinitrd -c -k 3.10.17 -f ext4 -r /dev/sda1 -m usbhid:hid_generic:xhci-hcd:mbcache:jbd2:ext4 -u -o /boot/initrd.gz