linux-kernel - Re: Boot kernel panic after upgrade 3.0.1 -> 3.0.2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4E4BBD60.10306@gmail.com>
Date:	Wed, 17 Aug 2011 15:08:48 +0200
From:	Torquil Macdonald Sørensen 
	<torquil@...il.com>
To:	Paul Bolle <pebolle@...cali.nl>
CC:	linux-kernel@...r.kernel.org
Subject: Re: Boot kernel panic after upgrade 3.0.1 -> 3.0.2

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 ...

Thanks Paul! It seems that the Debian kernel building/installation system has 
not generated an initrd for me... That must be the problem.

I'll get that straightened out, and report back with success or failure. So this 
is most likely not a kernel issue.

Best regards
Torquil Sørensen
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/