[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090105130638.GB6014@elte.hu>
Date: Mon, 5 Jan 2009 14:06:38 +0100
From: Ingo Molnar <mingo@...e.hu>
To: Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com>
Cc: Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Linux Kernel <linux-kernel@...r.kernel.org>,
Balbir Singh <balbir@...ux.vnet.ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Mike Galbraith <efault@....de>
Subject: Re: [BUG] 2.6.28-git LOCKDEP: Possible recursive rq->lock
* Vaidyanathan Srinivasan <svaidy@...ux.vnet.ibm.com> wrote:
> * Peter Zijlstra <a.p.zijlstra@...llo.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists