From: Andi Kleen <andi@firstfloor.org>
To: travis@sgi.com, mingo@elte.hu, tglx@linutronix.de,
linux-kernel@vger.kernel.org
Cc: dada1@cosmosbay.com, clameter@sgi.com
Subject: " Change size of node ids from u8 to u16 fixup" causes early panic in __build_all_zonelists
Date: Sat, 19 Jan 2008 07:29:12 +0100 [thread overview]
Message-ID: <20080119062912.GA15850@basil.nowhere.org> (raw)
One of my test systems didn't boot with latest git-x86.
I bisected it down to f1321f875910172bcc3e1f302fe145a9e4d3bdf7
With later patches the fault seemed to happen even earlier before
other initialization messages.
Config is available at http://halobates.de/config
-Andi
commit f1321f875910172bcc3e1f302fe145a9e4d3bdf7
Author: travis@sgi.com <travis@sgi.com>
Date: Fri Jan 18 23:05:33 2008 +0100
x86: Change size of node ids from u8 to u16 fixup
Change the size of node ids for X86_64 from 8 bits to 16 bits
to accomodate more than 256 nodes.
Introduce a "numanode_t" type for x86-generic usage.
...
swsusp: Registered nosave memory region: 00000000ff700000 - 0000000100000000
Allocating PCI resources starting at e2000000 (gap: e0000000:1ec00000)
SMP: Allowing 4 CPUs, 0 hotplug CPUs
PERCPU: Allocating 34912 bytes of per cpu data
PANIC: early exception 0e rip 10:ffffffff802602cd error 0 cr2 6b0
Pid: 0, comm: swapper Not tainted 2.6.24-rc8-g3c2d7552 #27
Call Trace:
[<ffffffff802602cd>] __build_all_zonelists+0x2a9/0x40a
[<ffffffff80260110>] __build_all_zonelists+0xec/0x40a
[<ffffffff802605ce>] build_all_zonelists+0x1a0/0x244
[<ffffffff80811950>] start_kernel+0x110/0x2bd
[<ffffffff808111c6>] _sinittext+0x1c6/0x1cd
RIP 0x10
next reply other threads:[~2008-01-19 6:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-19 6:29 Andi Kleen [this message]
2008-01-19 8:19 ` Ingo Molnar
2008-01-19 22:18 ` Mike Travis
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=20080119062912.GA15850@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=clameter@sgi.com \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=travis@sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome