[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20120425181905.GA8989@google.com>
Date: Wed, 25 Apr 2012 11:19:05 -0700
From: Tejun Heo <tj@...nel.org>
To: Jens Axboe <axboe@...nel.dk>
Cc: vgoyal@...hat.com, ctalbott@...gle.com, rni@...gle.com,
linux-kernel@...r.kernel.org, cgroups@...r.kernel.org,
containers@...ts.linux-foundation.org
Subject: Re: [PATCHSET] block: per-queue policy activation, take#2
On Fri, Apr 20, 2012 at 09:08:35PM +0200, Jens Axboe wrote:
> On 2012-04-20 19:17, Tejun Heo wrote:
> > Hello, Jens.
> >
> > On Fri, Apr 20, 2012 at 02:02:05PM +0200, Jens Axboe wrote:
> >> Tejun, everything merged in cleanly. A boot test didn't not go so well,
> >> I'm afraid. It complains about stuck RCU. Even with extra RCU
> >> debugging/info turned on, it doesn't give my any extra info.
> >>
> >> Config is attached. I can try and debug this on Monday, for now I've
> >> pulled it out of for-next again.
> >
> > Hmmm... it works fine with the same config here (qemu w/ 4 cpus
> > configured). Doesn't stuck RCU usually come from unbalanced RCU
> > lock/unlocking? That should trigger context or RCU warnings before
> > anything else, weird. Anyways, it would be great if you can provide
> > more info on how to reproduce the problem.
>
> The machine just sat there. I'll get some more info out of it and run a
> bisect too.
Any progress on this?
Thanks.
--
tejun
--
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