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]
Date:	Fri, 17 Jan 2014 10:42:19 +0100
From:	Paul Bolle <pebolle@...cali.nl>
To:	Madper Xie <cxie@...hat.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [BUG] Panic when booting

On Fri, 2014-01-17 at 17:34 +0800, Madper Xie wrote:
> I meet following panic when I booting my HP Compad Elite 8300 Elite SFF
> desktop.
> 
> [call trace here:]
> [    0.569993] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
> [    0.578269] CPU: 1 PID: 1 Comm: swapper/0 Tainted: G        W    3.13.0-rc8 #1
> [    0.585496] Hardware name: Hewlett-Packard HP Compaq Elite 8300 SFF/3397, BIOS K01 v02.05 05/07/2012
> [    0.594639]  ffffffffffffffff ffff880213125d70 ffffffff815dd70e ffffffff817e8598
> [    0.602100]  ffff880213125de8 ffffffff815d72bb ffffffff00000010 ffff880213125df8
> [    0.609570]  ffff880213125d98 ffff880213125da0 ffff880213125e08 0000000000000012
> [    0.617050] Call Trace:
> [    0.619511]  [<ffffffff815dd70e>] dump_stack+0x45/0x56
> [    0.624664]  [<ffffffff815d72bb>] panic+0xc8/0x1d7
> [    0.629470]  [<ffffffff81a36502>] mount_block_root+0x2a1/0x2b0
> [    0.635309]  [<ffffffff81a36564>] mount_root+0x53/0x56
> [    0.640467]  [<ffffffff81a366a3>] prepare_namespace+0x13c/0x174
> [    0.646392]  [<ffffffff81a36184>] kernel_init_freeable+0x218/0x22b
> [    0.652578]  [<ffffffff81a358d0>] ? do_early_param+0x88/0x88
> [    0.658245]  [<ffffffff815cc450>] ? rest_init+0x80/0x80
> [    0.663493]  [<ffffffff815cc45e>] kernel_init+0xe/0x120
> [    0.668724]  [<ffffffff815ed43c>] ret_from_fork+0x7c/0xb0
> [    0.674125]  [<ffffffff815cc450>] ? rest_init+0x80/0x80
> [    0.792437] Rebooting in 3 seconds..

[...]

> I can reproduce it 100%.
> Will do a bisect next monday if no one has clue.

I'd double check my bootloader configuration and the initramfs (which
you're probably using) if I'd encountered ab backtrace like that before
bisecting. But we seem to be missing quite a bit of dmesg's output, so
that's a bit of a guess...


Paul Bolle

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ