Re: Kernel boot panic 3.12-34 > 3.12.35

[Richard Farthing <rfarthing@iee.org>]

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


On 15/12/2014 09:28, Jiri Slaby wrote:
> On 12/14/2014, 07:25 PM, Borislav Petkov wrote:
>> On Sun, Dec 14, 2014 at 03:41:20PM +0000, Richard Farthing wrote:
>>> 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?
> 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,