From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
Peter Zijlstra <peterz@infradead.org>,
Venkatesh Pallipadi <venki@google.com>,
Nikhil Rao <ncrao@google.com>,
Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>,
linux-kernel@vger.kernel.org
Subject: Re: divide error in select_task_rq_fair()
Date: Thu, 4 Nov 2010 20:00:13 -0600 [thread overview]
Message-ID: <20101105020013.GA13484@helgaas.com> (raw)
In-Reply-To: <1288881474.2659.123.camel@edumazet-laptop>
On Thu, Nov 04, 2010 at 03:37:54PM +0100, Eric Dumazet wrote:
> Le jeudi 04 novembre 2010 à 08:28 -0600, Bjorn Helgaas a écrit :
> > On Thu, Nov 04, 2010 at 06:19:52AM +0100, Eric Dumazet wrote:
> > > Le mercredi 03 novembre 2010 à 22:12 -0600, Bjorn Helgaas a écrit :
> > > > Hi,
> > > >
> > > > With current upstream, I see the following crash at boot-time:
> > > >
> > > > Brought up 64 CPUs
> > > > Total of 64 processors activated (289366.52 BogoMIPS).
> > > > divide error: 0000 [#1] SMP
> > > > last sysfs file:
> > > > CPU 1
> > > > Modules linked in:
> > > >
> > > > Pid: 2, comm: kthreadd Not tainted 2.6.37-rc1-00027-gff8b16d #271 /ProLiant DL980 G7
> > > > RIP: 0010:[<ffffffff81034645>] [<ffffffff81034645>] select_task_rq_fair+0x62a/0x7a0
> > > >
> > > > Complete dmesg below; let me know if you need more info.
> > >
> > > Is the machine runs OK if you build a kernel with NR_CPUS=128 ?
> >
> > Nope, it fails the same way with NR_CPUS=128. Dmesg below.
>
> Sorry, just try 256 or 512, it seems you have a pretty big machine ?
Is that going to help you debug the problem? The solution is not going
to be something like "set NR_CPUS=x". If NR_CPUS is too small, the
machine should still *boot*, even if we can't use all the CPUs in the
box.
Bjorn
next prev parent reply other threads:[~2010-11-05 2:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 4:12 divide error in select_task_rq_fair() Bjorn Helgaas
2010-11-04 5:19 ` Eric Dumazet
2010-11-04 14:28 ` Bjorn Helgaas
2010-11-04 14:37 ` Eric Dumazet
2010-11-05 2:00 ` Bjorn Helgaas [this message]
2010-11-05 6:17 ` Eric Dumazet
2010-11-11 18:28 ` Myron Stowe
2010-11-12 6:22 ` Nikanth Karthikesan
2010-11-12 14:06 ` Myron Stowe
2010-11-14 17:36 ` Myron Stowe
2010-11-14 19:11 ` Yinghai Lu
2010-11-18 23:32 ` Myron Stowe
2010-11-22 5:25 ` [PATCH] x86, acpi: Parse all SRAT cpu entries even have cpu num limitation Yinghai Lu
2010-12-15 22:09 ` divide error in select_task_rq_fair() Venkatesh Pallipadi
2010-11-14 1:15 ` Yinghai Lu
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=20101105020013.GA13484@helgaas.com \
--to=bjorn.helgaas@hp.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=ncrao@google.com \
--cc=peterz@infradead.org \
--cc=venki@google.com \
--cc=yoshikawa.takuya@oss.ntt.co.jp \
/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