linux-kernel - 3.6.9 boot panic: block dev UUID all zeroes

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-next>] [day] [month] [year] [list]

Message-ID: <20121204003215.GA5288@xanatos>
Date:	Mon, 3 Dec 2012 16:32:15 -0800
From:	Sarah Sharp <sarah.a.sharp@...ux.intel.com>
To:	stable@...r.kernel.org
Cc:	linux-kernel@...r.kernel.org
Subject: 3.6.9 boot panic: block dev UUID all zeroes

The 3.6.9 kernel panics on boot with one of my experimental Intel test
machines.  The 3.6.7 kernel worked fine.

I think this may be machine-specific, since the 3.6.9 kernel works fine
on my Lenovo x230 laptop.

dmesg captured via serial port shows the boot disk has an all-zero UUID:

[    9.627480] RAMDISK: gzip image found at block 0
[   10.053958] RAMDISK: incomplete write (4873 != 32768)
[   10.059687] write error
[   10.064166] VFS: Cannot open root device "UUID=1d77da56-e224-44bc-9c69-5a5549ff808b" or unknown-block(0,0): error -6
[   10.076108] Please append a correct "root=" boot option; here are the available partitions:
[   10.085578] 0800       586061784 sda  driver: sd
[   10.090827]   0801       577724416 sda1 00000000-0000-0000-0000-000000000000
[   10.098828]   0802               1 sda2 00000000-0000-0000-0000-000000000000
[   10.106830]   0805         8334336 sda5 00000000-0000-0000-0000-000000000000
[   10.114829] 0b00         1048575 sr0  driver: sr
[   10.120117] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
[   10.129482] Pid: 1, comm: swapper/0 Not tainted 3.6.9+ #100
[   10.135794] Call Trace:
[   10.138569]  [<ffffffff816c089a>] panic+0xc6/0x1e1
[   10.144001]  [<ffffffff81d0c0b1>] mount_block_root+0x1df/0x291
[   10.150612]  [<ffffffff81d0c2e9>] mount_root+0x53/0x57
[   10.156437]  [<ffffffff81d0c45a>] prepare_namespace+0x16d/0x1a6
[   10.163148]  [<ffffffff81d0be0e>] kernel_init+0x1bb/0x1c0
[   10.169266]  [<ffffffff81d0b610>] ? do_early_param+0x86/0x86
[   10.175679]  [<ffffffff816d8244>] kernel_thread_helper+0x4/0x10
[   10.182386]  [<ffffffff816ce4b0>] ? retint_restore_args+0x13/0x13
[   10.189286]  [<ffffffff81d0bc53>] ? start_kernel+0x3e9/0x3e9
[   10.195698]  [<ffffffff816d8240>] ? gs_change+0x13/0x13

Full dmesg and config file are attached.  I'm currently bisecting to
find the bad commit.

Sarah Sharp

View attachment "lpt-b0-3.6.9-boot-issue-2012-12-03-16-11.txt" of type "text/plain" (33802 bytes)

View attachment "config-3.6.9.txt" of type "text/plain" (133408 bytes)