From: "Torquil Macdonald Sørensen" <torquil@gmail.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Boot kernel panic after upgrade 3.0.1 -> 3.0.2
Date: Wed, 17 Aug 2011 15:18:26 +0200 [thread overview]
Message-ID: <4E4BBFA2.8060008@gmail.com> (raw)
In-Reply-To: <1313581478.24749.25.camel@x61.thuisdomein>
On 17/08/11 13:44, Paul Bolle wrote:
> On Wed, 2011-08-17 at 12:33 +0200, Torquil Macdonald Sørensen wrote:
>> At boot time, I get the following message on screen (copied by hand, but I'm
>> hoping there are not too many mistakes...):
>>
>> Kernel panic, not syncing: VFS Unable to mount root fs on unknown block(0,0)
>> Pid: 1. comm: swapper Not tainted 3.0.2 #1
>> Call Trace:
>> [<fffffff8127e4a9>] ? panic 0xa4 0x19b
>> [<fffffff813f1e56>] ? mount_block_root+0x236/0x254
>> [<fffffff81002930>] ? do_bounds+0x57/0x65
>> [<fffffff813f1ff6>] ? prepare_namespace+0x133/0x169
>> [<fffffff813f1b7c>] ? kernel_init+0x105/0x10a
>> [<fffffff81284a94>] ? kernel_thread_helper+0x4/0x10
>> [<fffffff813f1a77>] ? start_kernel+0x341/341
>> [<fffffff81284a90>] ? gs_change+0xb/0xb
>
> I tend to see messages like that when I've messed up some basic setting
> needed to boot a kernel.
>
> My first suggestion would be to check your kernel command line. Does it
> have a "root=" parameter? Another thing I'd check is the initramfs. Does
> the bootloader pass the kernel an initramfs? Is the initramfs a valid
> initramfs? Does the (valid) initramfs have the stuff the kernel needs
> (block modules, fs modules). Stuff like that ...
You were right. I "forced" Debian to create an initrd for me, and update the
grub configuration. Now I'm happily running 3.0.2. :-)
Thanks again!
Torquil Sørensen
prev parent reply other threads:[~2011-08-17 13:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-17 10:33 Boot kernel panic after upgrade 3.0.1 -> 3.0.2 Torquil Macdonald Sørensen
2011-08-17 11:44 ` Paul Bolle
2011-08-17 13:08 ` Torquil Macdonald Sørensen
2011-08-17 13:18 ` Torquil Macdonald Sørensen [this message]
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=4E4BBFA2.8060008@gmail.com \
--to=torquil@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pebolle@tiscali.nl \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox