From: Jiri Slaby <jslaby@suse.cz>
To: Borislav Petkov <bp@alien8.de>, Richard Farthing <rfarthing@iee.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel boot panic 3.12-34 > 3.12.35
Date: Mon, 15 Dec 2014 10:28:21 +0100 [thread overview]
Message-ID: <548EA9B5.70602@suse.cz> (raw)
In-Reply-To: <20141214182518.GA607@pd.tnic>
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,
--
js
suse labs
next prev parent reply other threads:[~2014-12-15 9:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-14 15:41 Kernel boot panic 3.12-34 > 3.12.35 Richard Farthing
2014-12-14 18:25 ` Borislav Petkov
2014-12-15 9:28 ` Jiri Slaby [this message]
2014-12-15 10:06 ` Richard Farthing
2014-12-15 11:30 ` Jiri Slaby
2015-01-02 10:46 ` Richard Farthing
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=548EA9B5.70602@suse.cz \
--to=jslaby@suse.cz \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rfarthing@iee.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.