From: Jack Steiner <steiner@sgi.com>
To: nickpiggin@yahoo.com.au
Cc: linux-kernel@vger.kernel.org
Subject: Hang in sched_balance_self()
Date: Fri, 3 Jun 2005 17:55:44 -0500 [thread overview]
Message-ID: <20050603225544.GA8499@sgi.com> (raw)
Nick -
The latest 2.6.12-rc5-mm2 tree fails to boot on some of the 64p
SGI systems. The system hangs immediately after printing:
...
Inode-cache hash table entries: 8388608 (order: 12, 67108864 bytes)
Mount-cache hash table entries: 1024
Boot processor id 0x0/0x0
Brought up 64 CPUs
Total of 64 processors activated (118415.36 BogoMIPS).
I have isolated the failure to cpu 0 hanging in sched_balance_self() during
a fork (or clone). The "while" loop at the end of function never
terminates, ie. sd is never NULL.
Is this a problem that you have seen before. If not, I'll do some
more digging & isolate the problem.
--
Thanks
Jack Steiner (steiner@sgi.com) 651-683-5302
Principal Engineer SGI - Silicon Graphics, Inc.
next reply other threads:[~2005-06-03 22:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 22:55 Jack Steiner [this message]
2005-06-04 2:09 ` Hang in sched_balance_self() Nick Piggin
2005-06-07 14:09 ` Nick Piggin
2005-06-07 14:54 ` 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=20050603225544.GA8499@sgi.com \
--to=steiner@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nickpiggin@yahoo.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