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]
Date:	Sat, 26 Apr 2008 16:02:10 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	mingo@...e.hu, tglx@...utronix.de, torvalds@...l.org,
	linux-kernel@...r.kernel.org
Subject: mainline boot failures I: qemu


FYI

I see lots of boot failures on various setups with current mainline
(git8, b1721d0da266b4af8cb4419473b4ca36206ab200). Unfortunately 
they are all different. 

All with a defconfig kernel. Haven't investigated closely yet:

The only strange thing is that qemu says "Parsing ELF file". I assume
that's related to the new updated bzImage format? Perhaps it is related?

Here's the qemu failure:

xterm -e qemu-system-x86_64 -hda ... -kernel arch/x86/boot/bzImage -append "console=ttyS0 earlyprintk=serial"  -m 512 -nographic

...
ACPI: APIC 1FFF0938, 0040 (r0 QEMU   QEMUAPIC        1 QEMU        1)
No NUMA configuration found
Faking a node at 0000000000000000-000000001fff0000
Bootmem setup node 0 0000000000000000-000000001fff0000
  NODE_DATA [000000000000b000 - 0000000000011fff]
  bootmap [0000000000012000 -  0000000000015fff] pages 4
early res: 0 [0-fff] BIOS data page
PANIC: early exception 06 rip 10:ffffffff8083b23e error 0 cr2 0
Pid: 0, comm: swapper Not tainted 2.6.25-git8 #41

Call Trace:
 [<ffffffff8082c195>] early_idt_handler+0x55/0x69
 [<ffffffff8083b23e>] reserve_bootmem_generic+0x31/0xcc
 [<ffffffff80845194>] acpi_table_parse+0x4c/0x66
 [<ffffffff80833edb>] early_res_to_bootmem+0x43/0x52
 [<ffffffff80832816>] setup_arch+0x306/0x418
 [<ffffffff8082caa3>] start_kernel+0x6e/0x309
 [<ffffffff8082c3cf>] x86_64_start_kernel+0x1de/0x1e5

RIP 0x10


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