All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Collins <bcollins@debian.org>
To: sparclinux@vger.kernel.org
Subject: Re: 2.6.2-rc1 smp crash
Date: Fri, 23 Jan 2004 13:46:28 +0000	[thread overview]
Message-ID: <20040123134628.GH27566@phunnypharm.org> (raw)

On Fri, Jan 23, 2004 at 09:34:34AM -0500, Chris Ricker wrote:
> I just had a dual Ultra 2 running 2.6.2-rc1 lock up hard. The only messages 
> on the screen are from the spin-lock debugging:
> 
> spin_lock(fffff8003fab0208) CPU#1 stuck at 0053fd88, owner PC(0053d1ac):CPU(1)
> spin_lock(00000000006bee00) CPU#0 stuck at 004a551c, owner PC(005205a0):CPU(1)
> spin_lock(fffff8003fab0208) CPU#1 stuck at 0053fd88, owner PC(0053d1ac):CPU(1)
> spin_lock(00000000006bee00) CPU#0 stuck at 004a551c, owner PC(005205a0):CPU(1)
> spin_lock(fffff8003fab0208) CPU#1 stuck at 0053fd88, owner PC(0053d1ac):CPU(1)
> spin_lock(00000000006bee00) CPU#0 stuck at 004a551c, owner PC(005205a0):CPU(1)
> 
> What should I do next to start hunting this down?

Check your System.map for where the addresses for "stuck at XXX" and
"owner PC(XXX)". Also check for 0x006bee00, which is the spinlock in
question.

-- 
Debian     - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
WatchGuard - http://www.watchguard.com/

             reply	other threads:[~2004-01-23 13:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-23 13:46 Ben Collins [this message]
2004-01-23 14:34 ` 2.6.2-rc1 smp crash Chris Ricker
2004-01-23 15:19 ` Chris Ricker
2004-01-23 15:32 ` Ben Collins
2004-01-23 19:49 ` David S. Miller
2004-01-24 14:46 ` Chris Ricker

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=20040123134628.GH27566@phunnypharm.org \
    --to=bcollins@debian.org \
    --cc=sparclinux@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.