LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Kamalesh Babulal" <kamalesh@linux.vnet.ibm.com>
Cc: "Bartlomiej Zolnierkiewicz" <bzolnier@gmail.com>,
"Nish Aravamudan" <nish.aravamudan@gmail.com>,
"Pavel Machek" <pavel@ucw.cz>,
"kernel list" <linux-kernel@vger.kernel.org>,
linux-ide@vger.kernel.org, ananth@in.ibm.com,
"Andi Kleen" <andi@firstfloor.org>
Subject: Re: 2.6.26-git0: IDE oops during boot
Date: Sun, 24 Feb 2008 23:23:09 -0800 [thread overview]
Message-ID: <86802c440802242323p58d0e234q9b6f33449c8ebaf8@mail.gmail.com> (raw)
In-Reply-To: <86802c440802242305o7cfce4d1h6444aab01304cb21@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
On Sun, Feb 24, 2008 at 11:05 PM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> On Fri, Feb 15, 2008 at 3:15 AM, Kamalesh Babulal
>
> <kamalesh@linux.vnet.ibm.com> wrote:
> >
> >
>
> > Thanks for pointing the patch, I do not have the SES config option enabled,
> > then too i tried your patch, but that does not solve the panic. The kernel
> > panic's with the same panic message as before. I have attached the .config
> > file which i am using, please let me know if i am missing out/getting wrong
> > any option in the configuration.
>
> can you try x86.git#testing?
>
> http://people.redhat.com/mingo/x86.git/README
>
and try attached patch.
YH
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: fix_intel_numa.patch --]
[-- Type: text/x-patch; name=fix_intel_numa.patch, Size: 495 bytes --]
diff --git a/arch/x86/kernel/setup_64.c b/arch/x86/kernel/setup_64.c
index 6fd804f..f0d6a80 100644
--- a/arch/x86/kernel/setup_64.c
+++ b/arch/x86/kernel/setup_64.c
@@ -801,7 +801,7 @@ static void __cpuinit srat_detect_node(void)
/* Don't do the funky fallback heuristics the AMD version employs
for now. */
node = apicid_to_node[apicid];
- if (node == NUMA_NO_NODE)
+ if (node == NUMA_NO_NODE || !node_online(node))
node = first_node(node_online_map);
numa_set_node(cpu, node);
next prev parent reply other threads:[~2008-02-25 7:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080206105334.GA3664@elf.ucw.cz>
2008-02-06 11:08 ` Pavel Machek
2008-02-06 20:05 ` Bartlomiej Zolnierkiewicz
2008-02-07 9:35 ` Kamalesh Babulal
2008-02-07 14:01 ` Bartlomiej Zolnierkiewicz
2008-02-10 21:32 ` Nish Aravamudan
2008-02-11 7:54 ` Kamalesh Babulal
2008-02-11 19:35 ` Bartlomiej Zolnierkiewicz
2008-02-12 9:04 ` Kamalesh Babulal
2008-02-13 23:00 ` Bartlomiej Zolnierkiewicz
2008-02-14 9:46 ` Kamalesh Babulal
2008-02-14 10:28 ` Yinghai Lu
2008-02-15 11:15 ` Kamalesh Babulal
2008-02-25 7:05 ` Yinghai Lu
2008-02-25 7:23 ` Yinghai Lu [this message]
2008-02-14 12:01 ` "mount: could not find filesystem" - aacraid? (was: Re: 2.6.26-git0: IDE oops during boot) Bartlomiej Zolnierkiewicz
2008-02-14 12:07 ` Bartlomiej Zolnierkiewicz
2008-02-14 15:47 ` James Bottomley
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=86802c440802242323p58d0e234q9b6f33449c8ebaf8@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=ananth@in.ibm.com \
--cc=andi@firstfloor.org \
--cc=bzolnier@gmail.com \
--cc=kamalesh@linux.vnet.ibm.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.com \
--cc=pavel@ucw.cz \
--subject='Re: 2.6.26-git0: IDE oops during boot' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).