From: Dave Chinner <david@fromorbit.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: BUG: spinlock lockup on task_rq_lock in 2.6.33
Date: Wed, 3 Mar 2010 09:17:29 +1100 [thread overview]
Message-ID: <20100302221729.GG18369@discord.disaster> (raw)
In-Reply-To: <alpine.LFD.2.00.1003021106330.4245@localhost.localdomain>
On Tue, Mar 02, 2010 at 11:08:50AM +0100, Thomas Gleixner wrote:
> Dave,
>
> On Tue, 2 Mar 2010, Dave Chinner wrote:
>
> > Hi Folks,
> >
> > I just locked up a machine with the following trace:
> >
> > [ 5247.149256] BUG: spinlock lockup on CPU#1, dd/7018, ffff8800059d4380
> > [ 5247.150009] BUG: spinlock lockup on CPU#0, dd/6211, ffff8800059d4380
> > [ 5247.150009] Pid: 6211, comm: dd Not tainted 2.6.33-dgc #86
> > [ 5247.150009] Call Trace:
> > [ 5247.150009] [<ffffffff8140ad40>] do_raw_spin_lock+0x160/0x170
> > [ 5247.150009] [<ffffffff8170fec6>] _raw_spin_lock+0x56/0x70
> > [ 5247.150009] [<ffffffff8103d092>] ? task_rq_lock+0x52/0x90
> > [ 5247.150009] [<ffffffff8103d092>] task_rq_lock+0x52/0x90
> > [ 5247.150009] [<ffffffff81044a70>] try_to_wake_up+0x40/0x3d0
> > [ 5247.150009] [<ffffffff81044e55>] wake_up_process+0x15/0x20
>
> I can't say it for sure, but that might be related to a problem with
> TASK_WAKING which we discovered recently. The fix is in linus tree
> (commit 0970d2992dfd7d5ec2c787417cf464f01eeaf42a) and on the way to stable.
Thanks Thomas - I'll pull that commit in and see if it has any
effect on the problems I'm seeing.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2010-03-02 22:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 6:31 BUG: spinlock lockup on task_rq_lock in 2.6.33 Dave Chinner
2010-03-02 10:08 ` Thomas Gleixner
2010-03-02 22:17 ` Dave Chinner [this message]
2010-03-02 22:49 ` Thomas Gleixner
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=20100302221729.GG18369@discord.disaster \
--to=david@fromorbit.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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