From: Keith Owens <kaos@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: 2.6.14-rc1 BUG: spinlock wrong owner on CPU#0
Date: Tue, 13 Sep 2005 19:45:10 +1000 [thread overview]
Message-ID: <4882.1126604710@ocs3.ocs.com.au> (raw)
In-Reply-To: Your message of "Tue, 13 Sep 2005 11:17:59 +0200." <20050913091759.GA11485@elte.hu>
On Tue, 13 Sep 2005 11:17:59 +0200,
Ingo Molnar <mingo@elte.hu> wrote:
>
>* Keith Owens <kaos@sgi.com> wrote:
>
>> Booting 2.6.14-rc1 on ia64, I sometimes get
>>
>> BUG: spinlock wrong owner on CPU#0, swapper/1
>> lock: e000003003014940, .magic: dead4ead, .owner: pdflush/75, .owner_cpu: 0
>
>hm, ia64 uses __ARCH_WANT_UNLOCKED_CTXSW and thus it releases the
>runqueue lock early - so a certain assumption in the new, improved
>spinlock debugging code does not apply. Does the patch below help?
Works for me, but it needs to be a -p1 patch, not -p0.
prev parent reply other threads:[~2005-09-13 9:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 7:58 2.6.14-rc1 BUG: spinlock wrong owner on CPU#0 Keith Owens
2005-09-13 9:17 ` Ingo Molnar
2005-09-13 9:45 ` Keith Owens [this message]
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=4882.1126604710@ocs3.ocs.com.au \
--to=kaos@sgi.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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