Skip to contentSkip to conversation

Kernel boot panic 3.12-34 > 3.12.35

DISCUSSION Richard Farthing 3 participants 6 messages Dec 14, 2014 – Jan 2, 2015

lore
Share & tools
lore
#0 lore raw

I patched 3.12.34 to 3.12.35 and the attached now happens at boot. Sorry I don't have better than a photo, cannot get past this.

The root FS is EXT2. It's admittedly an old test machine that I'm using to build up a new configuration, so the BIOS is a bit old, but it's at least dual core, not totally ancient.

Let me know if you need more diagnostic

Thanks

#1 lore raw
Quoted 8 lines · Richard Farthing

I patched 3.12.34 to 3.12.35 and the attached now happens at boot. Sorry I don't have better than a photo, cannot get past this.

The root FS is EXT2. It's admittedly an old test machine that I'm using to build up a new configuration, so the BIOS is a bit old, but it's at least dual core, not totally ancient.

Let me know if you need more diagnostic

That happens very early and the first oops which is the most relevant one is cut off and one cannot see what the bug actually is, unfortunately.

Can you catch dmesg of that boot over serial or netconsole or so? Ask if you don't know how.

You could send your .config, maybe it is reproducible in kvm. Also, can you send a full dmesg of the successful boot with 3.12.34?

Thanks.

Signature · 5 lines
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
#2 lore raw
Quoted 14 lines · Borislav Petkov
Quoted 8 lines · Richard Farthing

I patched 3.12.34 to 3.12.35 and the attached now happens at boot. Sorry I don't have better than a photo, cannot get past this.

The root FS is EXT2. It's admittedly an old test machine that I'm using to build up a new configuration, so the BIOS is a bit old, but it's at least dual core, not totally ancient.

Let me know if you need more diagnostic

That happens very early and the first oops which is the most relevant one is cut off and one cannot see what the bug actually is, unfortunately.

Quoted 5 lines

Can you catch dmesg of that boot over serial or netconsole or so? Ask if you don't know how.

You could send your .config, maybe it is reproducible in kvm. Also, can you send a full dmesg of the successful boot with 3.12.34?

Hmm...

panic from mount_block_root?

That would be:
"VFS: Unable to mount root fs on %s"

Did you use proper root= kernel parameter? Do you have initrd properly created and installed?

thanks,

Signature · 2 lines
js
suse labs
#3 lore raw

I installed the kernel via YAST2 which makes and installs the initrd too, and have done this many times before on this test machine, so it seems unlikely to be my mistake, but it's always possible! I will have a look at it again

Richard

Quoted 30 lines · Jiri Slaby
Quoted 13 lines · Borislav Petkov
Quoted 8 lines · Richard Farthing

I patched 3.12.34 to 3.12.35 and the attached now happens at boot. Sorry I don't have better than a photo, cannot get past this.

The root FS is EXT2. It's admittedly an old test machine that I'm using to build up a new configuration, so the BIOS is a bit old, but it's at least dual core, not totally ancient.

Let me know if you need more diagnostic

That happens very early and the first oops which is the most relevant one is cut off and one cannot see what the bug actually is, unfortunately.

Quoted 5 lines

Can you catch dmesg of that boot over serial or netconsole or so? Ask if you don't know how.

You could send your .config, maybe it is reproducible in kvm. Also, can you send a full dmesg of the successful boot with 3.12.34?

Hmm...

panic from mount_block_root?

That would be:
"VFS: Unable to mount root fs on %s"

Did you use proper root= kernel parameter? Do you have initrd properly created and installed?

thanks,

#4 lore raw
Quoted 4 lines · Richard Farthing

I installed the kernel via YAST2 which makes and installs the initrd too, and have done this many times before on this test machine, so it seems unlikely to be my mistake, but it's always possible! I will have a look at it again

Oh, yast... What about trying RPMs from
http://download.opensuse.org/repositories/Kernel:/SLE12/standard/
?

Either kernel-vanilla which is pure 3.12.35 (or later) or kernel-default which is SLE12 kernel based on 3.12.35 (or later).

thanks,

Signature · 2 lines
js
suse labs
#5 lore raw

Hi,

So I built 3.12.35 from the SLE12 repo and another crash on boot ! See attached screenshot.
Something weird going on with btrfs here (it's built with the same options as 3.12.34). All the other longterm kernels I've tested have been OK (stock kernel, 3.2.65, 3.4.105, 3.10.63 and 3.12.34 of course.

regards
Richard

Quoted 13 lines · Jiri Slaby
Quoted 4 lines · Richard Farthing

I installed the kernel via YAST2 which makes and installs the initrd too, and have done this many times before on this test machine, so it seems unlikely to be my mistake, but it's always possible! I will have a look at it again

Oh, yast... What about trying RPMs from
http://download.opensuse.org/repositories/Kernel:/SLE12/standard/
?

Either kernel-vanilla which is pure 3.12.35 (or later) or kernel-default which is SLE12 kernel based on 3.12.35 (or later).

thanks,