From: Ingo Molnar <mingo@elte.hu>
To: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Balbir Singh <balbir@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Galbraith <efault@gmx.de>
Subject: Re: [BUG] 2.6.28-git LOCKDEP: Possible recursive rq->lock
Date: Mon, 5 Jan 2009 14:06:38 +0100 [thread overview]
Message-ID: <20090105130638.GB6014@elte.hu> (raw)
In-Reply-To: <20090105040635.GF4301@dirshya.in.ibm.com>
* Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com> wrote:
> * Peter Zijlstra <a.p.zijlstra@chello.nl> [2009-01-04 19:08:43]:
>
> > On Sun, 2009-01-04 at 23:14 +0530, Vaidyanathan Srinivasan wrote:
> > > Hi Ingo,
> > >
> > > Kernbench runs on latest Linux git tree stalled with the following
> > > lockdep warning.
> > >
> > > Lockdep warning and lockup on Jan 3 Linus git tree
> > > commit 7d3b56ba37a95f1f370f50258ed3954c304c524b
> > >
> > > kernbench run with two threads stalled. sched_mc was zero.
> > > x86_64 system with 8 logical CPUs in dual socket quad core
> > > configuration.
> > >
> > > I will post more information as I debug this warning/bug.
> >
> > Its ca109491f612aab5c8152207631c0444f63da97f, I've some ideas on how to
> > fix this, just haven't gotten around to actually doing anything --
> > seeing how it was holidays and such..
>
> Hi Peter,
>
> I can definitely test your fix when you have them. I have an
> autotest job that hits this bug.
could you check latest tip/master, it has Peter's and Thomas's hrtimer
fixes.
Ingo
next prev parent reply other threads:[~2009-01-05 13:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-04 17:44 [BUG] 2.6.28-git LOCKDEP: Possible recursive rq->lock Vaidyanathan Srinivasan
2009-01-04 18:08 ` Peter Zijlstra
2009-01-05 4:06 ` Vaidyanathan Srinivasan
2009-01-05 13:06 ` Ingo Molnar [this message]
2009-01-06 7:10 ` Vaidyanathan Srinivasan
2009-01-06 14:02 ` Vaidyanathan Srinivasan
2009-01-07 11:49 ` Vaidyanathan Srinivasan
2009-01-07 12:29 ` Vaidyanathan Srinivasan
2009-01-07 13:12 ` Peter Zijlstra
2009-01-07 14:20 ` Vaidyanathan Srinivasan
2009-01-07 14:28 ` Peter Zijlstra
2009-01-07 16:31 ` Vaidyanathan Srinivasan
2009-01-07 18:09 ` Vaidyanathan Srinivasan
2009-01-07 18:12 ` Ingo Molnar
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=20090105130638.GB6014@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=svaidy@linux.vnet.ibm.com \
/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