From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: Ingo Molnar <mingo@elte.hu>, Mike Travis <travis@sgi.com>
Cc: Jack Steiner <steiner@sgi.com>,
tglx@linutronix.de, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, "H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH] - Increase MAX_APICS for large configs
Date: Thu, 17 Apr 2008 11:02:13 -0700 [thread overview]
Message-ID: <86802c440804171102q2be96c67m881394c1e6fa3867@mail.gmail.com> (raw)
In-Reply-To: <20080417110727.GA942@elte.hu>
On Thu, Apr 17, 2008 at 4:07 AM, Ingo Molnar <mingo@elte.hu> wrote:
>
> * Jack Steiner <steiner@sgi.com> wrote:
>
> > Increase the maximum number of apics when running very large
> > configurations. This patch has no affect on most systems.
>
> x86.git overnight random-qa testing found a boot crash and i bisected it
> down to this patch. The config is:
>
> http://redhat.com/~mingo/misc/config-Thu_Apr_17_10_17_14_CEST_2008.bad
>
> the failure is attached below. (I needed the exact boot parameters
> listed in that bootup log to see this failure.)
>
> it seems to be CONFIG_MAXSMP=y triggers the new more-apic-ids code and
> that causes some breakage elsewhere. [btw., this again shows how useful
> the CONFIG_MAXSMP debug feature is!]
so this one and Mike's 4096 NR_CPUS cause the problem?
2048 CPUs works.
YH
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-04-17 18:02 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 16:39 [PATCH] - Increase MAX_APICS for large configs Jack Steiner
2008-04-16 18:45 ` Ingo Molnar
2008-04-16 19:22 ` Jack Steiner
2008-04-17 11:07 ` Ingo Molnar
2008-04-17 18:02 ` Yinghai Lu [this message]
2008-04-18 21:14 ` Jack Steiner
2008-04-18 22:01 ` Yinghai Lu
2008-04-19 0:01 ` Jack Steiner
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=86802c440804171102q2be96c67m881394c1e6fa3867@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=steiner@sgi.com \
--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;
as well as URLs for NNTP newsgroup(s).