From: "Vegard Nossum" <vegard.nossum@gmail.com>
To: "Dave Hansen" <dave@linux.vnet.ibm.com>
Cc: "Kamalesh Babulal" <kamalesh@linux.vnet.ibm.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, kernel-testers@vger.kernel.org,
linux-mm@kvack.org, "Andy Whitcroft" <apw@shadowen.org>,
"Balbir Singh" <balbir@linux.vnet.ibm.com>,
"Mike Travis" <travis@sgi.com>, "Ingo Molnar" <mingo@elte.hu>
Subject: Re: [BUG] 2.6.26-rc5-mm2 - kernel BUG at arch/x86/kernel/setup.c:388!
Date: Wed, 11 Jun 2008 20:37:09 +0200 [thread overview]
Message-ID: <19f34abd0806111137t4291b9fkb66951aa8f4d456f@mail.gmail.com> (raw)
In-Reply-To: <1213208897.20475.19.camel@nimitz>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=UTF-8, Size: 2070 bytes --]
On 6/11/08, Dave Hansen <dave@linux.vnet.ibm.com> wrote:> On Wed, 2008-06-11 at 23:26 +0530, Kamalesh Babulal wrote:> > Hi Andrew,> >> > The 2.6.26-rc5-mm2 kernel panic's, while booting up on the x86_64> > box with the attached .config file.>>> Just to save everyone the trouble, it looks like this is a new BUG_ON().> > http://www.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.26-rc5/2.6.26-rc5-mm2/broken-out/fix-x86_64-splat.patch>> The machine in question is a single-node machine, but with> CONFIG_NUMA=y.>
Yes. Sorry, I already responded in a separate e-mail (see below), butthat obviously missed all the Ccs. So here it goes again...:
I'm betting
commit a953e4597abd51b74c99e0e3b7074532a60fd031Author: Mike Travis <travis@sgi.com>Date: Mon May 12 21:21:12 2008 +0200
sched: replace MAX_NUMNODES with nr_node_ids in kernel/sched.c
will fix this if it's not in -mm2 already.
The BUG() is simply there to prevent silent corruption. Mike alreadyhas a patch that changes it to a WARN(), but it obviously didn't getthrough (either)...
Vegard
On 6/11/08, Vegard Nossum <vegard.nossum@gmail.com> wrote:> On 6/9/08, Kamalesh Babulal <kamalesh@linux.vnet.ibm.com> wrote:> > Hi Andrew,> >> > The 2.6.26-rc5-mm2 kernel panic's, while booting up on the x86_64> > box with the attached .config file.>> (Please apologize for the strange way of replying to this message. It> seems that LKML gave up delivering to my address, so I'm currently> reading off lkml.org.)>> This should already be fixed, but Andrew refused to apply the patch> before releasing the -mm1 (and -mm2 apparently). I'm attaching the> patch, can you see if it helps?>> Thanks.>>> Vegard
-- "The animistic metaphor of the bug that maliciously sneaked in whilethe programmer was not looking is intellectually dishonest as itdisguises that the error is the programmer's own creation." -- E. W. Dijkstra, EWD1036ÿôèº{.nÇ+·®+%Ëÿ±éݶ\x17¥wÿº{.nÇ+·¥{±þG«éÿ{ayº\x1dÊÚë,j\a¢f£¢·hïêÿêçz_è®\x03(éÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?¨èÚ&£ø§~á¶iOæ¬z·vØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?I¥
next prev parent reply other threads:[~2008-06-11 18:37 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 5:31 2.6.26-rc5-mm2 Andrew Morton
2008-06-10 6:12 ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-10 7:28 ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-10 8:34 ` 2.6.26-rc5-mm2 Andrew Morton
2008-06-10 8:48 ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-10 9:15 ` 2.6.26-rc5-mm2 Andrew Morton
2008-06-10 12:34 ` 2.6.26-rc5-mm2 Rik van Riel
2008-06-11 18:09 ` 2.6.26-rc5-mm2 Rik van Riel
2008-06-11 23:58 ` 2.6.26-rc5-mm2 Nick Piggin
2008-06-12 19:29 ` 2.6.26-rc5-mm2 Rik van Riel
2008-06-12 21:15 ` 2.6.26-rc5-mm2 (swap_state.c:77) Hugh Dickins
2008-06-13 17:45 ` Rik van Riel
2008-06-13 21:15 ` Hugh Dickins
2008-06-13 22:03 ` Rik van Riel
2008-06-10 15:34 ` 2.6.26-rc5-mm2 Lee Schermerhorn
2008-06-10 16:50 ` 2.6.26-rc5-mm2 Hugh Dickins
2008-06-10 10:20 ` 2.6.26-rc5-mm2 lockup up on Intel G33+ICH9R+Core2Duo, -mm1 okay Grant Coady
2008-06-10 18:18 ` Andrew Morton
2008-06-10 21:48 ` Grant Coady
2008-06-10 11:50 ` 2.6.26-rc5-mm2 compile error in vmscan.c Helge Hafting
2008-06-10 12:23 ` Johannes Weiner
2008-06-10 18:37 ` Andrew Morton
2008-06-12 8:13 ` Helge Hafting
2008-06-11 2:26 ` 2.6.26-rc5-mm2 (compile error in mm/memory_hotplug.c) Yasunori Goto
2008-06-11 6:00 ` 2.6.26-rc5-mm2: OOM with 1G free swap Alexey Dobriyan
2008-06-11 6:11 ` Nick Piggin
2008-06-11 6:15 ` Nick Piggin
2008-06-11 6:27 ` Andrew Morton
2008-06-11 6:31 ` Nick Piggin
2008-06-11 6:36 ` KOSAKI Motohiro
2008-06-11 7:31 ` Frederik Deweerdt
2008-06-11 12:57 ` Rik van Riel
2008-06-11 13:44 ` Nick Piggin
2008-06-11 17:56 ` [BUG] 2.6.26-rc5-mm2 - kernel BUG at arch/x86/kernel/setup.c:388! Kamalesh Babulal
2008-06-11 18:28 ` Dave Hansen
2008-06-11 18:37 ` Vegard Nossum [this message]
2008-06-12 6:55 ` Kamalesh Babulal
2008-06-11 18:08 ` pnp changes -> suspend oops [Was: 2.6.26-rc5-mm2] Jiri Slaby
2008-06-11 19:03 ` Bjorn Helgaas
2008-06-12 21:10 ` Jiri Slaby
2008-06-12 21:22 ` Bjorn Helgaas
2008-06-12 21:39 ` Jiri Slaby
2008-06-12 21:57 ` Bjorn Helgaas
2008-06-12 21:57 ` Jiri Slaby
2008-06-13 16:05 ` Jiri Slaby
2008-06-13 17:23 ` Bjorn Helgaas
2008-06-16 10:43 ` Jiri Slaby
2008-06-11 18:12 [BUG] 2.6.26-rc5-mm2 - kernel BUG at arch/x86/kernel/setup.c:388! Vegard Nossum
2008-06-11 19:43 ` Andrew Morton
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=19f34abd0806111137t4291b9fkb66951aa8f4d456f@mail.gmail.com \
--to=vegard.nossum@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=dave@linux.vnet.ibm.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=kernel-testers@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--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
all inboxes | Powered by JetHome®