From: Andi Kleen <andi@firstfloor.org>
To: mingo@elte.hu, tglx@linutronix.de, torvalds@osdl.org,
linux-kernel@vger.kernel.org
Subject: mainline boot failures I: qemu
Date: Sat, 26 Apr 2008 16:02:10 +0200 [thread overview]
Message-ID: <20080426140210.GA13365@basil.nowhere.org> (raw)
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
next reply other threads:[~2008-04-26 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-26 14:02 Andi Kleen [this message]
2008-04-26 14:51 ` mainline boot failures I: qemu II Andi Kleen
2008-04-26 15:02 ` mainline boot failures I: qemu Dmitri Vorobiev
2008-04-26 18:38 ` Andi Kleen
2008-04-26 15:42 ` Al Viro
2008-04-26 20:37 ` walt
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=20080426140210.GA13365@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=torvalds@osdl.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.