From: Paul Jackson <pj@sgi.com>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: linuxppc64-dev@lists.linuxppc.org, linux-kernel@vger.kernel.org,
piggin@cyberone.com.au
Subject: Re: Oops in find_busiest_group(): 2.6.8-rc1-mm1
Date: Wed, 28 Jul 2004 23:42:55 -0700 [thread overview]
Message-ID: <20040728234255.29ef4c13.pj@sgi.com> (raw)
In-Reply-To: <1089871489.10000.388.camel@nighthawk>
I just hit what might be the same oops.
I had not upgraded my working kernel for a month, and just now, when I
upgraded to 2.6.8-rc2-mm1, running sn2_defconfig on a small SN2 system,
it fails to boot everytime, ending with an Oops that starts out with:
======================================================
Freeing unused kernel memory: 320kB freed
Unable to handle kernel NULL pointer dereference (address 0000000000000008)
swapper[0]: Oops 8813272891392 [1]
Modules linked in:
Pid: 0, CPU 0, comm: swapper
psr : 0000101008022018 ifs : 8000000000000e20 ip : [<a0000001000bd710>] Not tainted
ip is at find_busiest_group+0xb0/0x640
======================================================
I added a conditional printk_ratelimit'ed print at the top of
find_busiest_group() whenever group is NULL, just before the first
dereference of group in the line:
local_group = cpu_isset(this_cpu, group->cpumask);
That print fires about 20,480 times each 5 second suppression window.
But it boots, if I also add code to break out of the "do { ... } while
(group != sd->groups)" loop, whenever group goes NULL.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <pj@sgi.com> 1.650.933.1373
next prev parent reply other threads:[~2004-07-29 6:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 6:04 Oops in find_busiest_group(): 2.6.8-rc1-mm1 Dave Hansen
2004-07-15 6:15 ` Nick Piggin
2004-07-29 6:42 ` Paul Jackson [this message]
2004-07-29 8:33 ` Nick Piggin
2004-07-29 9:29 ` Paul Jackson
2004-07-29 10:36 ` Nick Piggin
2004-07-29 12:22 ` Dave Hansen
2004-07-29 15:35 ` Dimitri Sivanich
2004-07-29 15:49 ` Jesse Barnes
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=20040728234255.29ef4c13.pj@sgi.com \
--to=pj@sgi.com \
--cc=haveblue@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc64-dev@lists.linuxppc.org \
--cc=piggin@cyberone.com.au \
/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