From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org, discuss@x86-64.org, ak@suse.de
Subject: Re: 2.6.16-rc5-mm3: spinlock bad magic on CPU#0 on AMD64
Date: Sun, 12 Mar 2006 11:27:28 +0100 [thread overview]
Message-ID: <200603121127.28657.rjw@sisk.pl> (raw)
In-Reply-To: <20060311153618.2e4b113d.akpm@osdl.org>
On Sunday 12 March 2006 00:36, Andrew Morton wrote:
> "Rafael J. Wysocki" <rjw@sisk.pl> wrote:
> > With the 2.6.16-rc5-mm3 kernel w/ the patch
> >
> > revert-x86_64-mm-i386-early-alignment.patch
> >
> > applied I'm able to hang my box (Asus L5D, 1 CPU, x86-64 kernel) solid
> > by running OpenOffice.org from under KDE (100% of the time but on one
> > user account only). Before it hangs I get something like this on the serial console:
> >
> > BUG: spinlock bad magic on CPU#0, soffice.bin/5293
> > lock: ffff81005e174e28, .magic: 000001ff, .owner: .5).@4).06)./0, .owner_cpu: -2141827648
> > BUG: spinlock lockup on CPU#0, soffice.bin/5293, ffff81005e174e28
> >
>
> Is it a !CONFIG_SMP kernel?
Yes.
> There's no stack trace?
Well, probably there was one but it didn't appear on the serial console because
the console loglevel was too low. I'll try to increase console_loglevel in
spin_bug() and see what happens.
[BTW, looking at the relevant code, in my case .owner_cpu appears to have only
the most significant bit set (??).]
next prev parent reply other threads:[~2006-03-12 10:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-11 23:24 2.6.16-rc5-mm3: spinlock bad magic on CPU#0 on AMD64 Rafael J. Wysocki
2006-03-11 23:36 ` Andrew Morton
2006-03-12 10:27 ` Rafael J. Wysocki [this message]
2006-03-12 12:49 ` [discuss] " Rafael J. Wysocki
2006-03-12 22:26 ` Andrew Morton
2006-03-12 15:10 ` Andi Kleen
2006-03-12 23:23 ` Andrew Morton
2006-03-13 11:34 ` Rafael J. Wysocki
2006-03-13 11:45 ` Andrew Morton
2006-03-13 12:07 ` Rafael J. Wysocki
2006-03-13 16:02 ` Badari Pulavarty
2006-03-13 18:12 ` Rafael J. Wysocki
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=200603121127.28657.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=discuss@x86-64.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox