xfs
[Top] [All Lists]

Re: BUG: sleeping function called from invalid context at kernel/rwsem.c

To: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Subject: Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17)
From: Arjan van de Ven <arjan@xxxxxxxxxxxxx>
Date: Fri, 17 Oct 2008 13:55:10 -0700
Cc: Alexander Beregalov <a.beregalov@xxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx, linux-next@xxxxxxxxxxxxxxx, LKML <linux-kernel@xxxxxxxxxxxxxxx>
In-reply-to: <20081017203710.GA27187@xxxxxxxxxxxxx>
Organization: Intel
References: <a4423d670810170543vd6b4c39p44bf125610d8540@xxxxxxxxxxxxxx> <20081017164116.GA17375@xxxxxxxxxxxxx> <a4423d670810170954h7ca130aaw8895380a4c6b125@xxxxxxxxxxxxxx> <20081017165738.GA20818@xxxxxxxxxxxxx> <a4423d670810171013g5bc19c1cm3f7d9c014ee70349@xxxxxxxxxxxxxx> <20081017203710.GA27187@xxxxxxxxxxxxx>
On Fri, 17 Oct 2008 16:37:10 -0400
Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:

> I just ran the xfs testsuite over linux-next on qemu (i386), and I
> can't find anything at all.  Really strange.  Let's see if this still
> there with mondays linux-next, and if yes can you just try the xfs
> patch from the splitout linux-next patches and see if that alone
> causes it?
> 
> In fact that might be useful for todays linux-next, too.
> --

also if you enable lockdep, it tracks where irq's got turned off (with
a stacktrace I think) so it would provide some good clues.


-- 
Arjan van de Ven        Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

<Prev in Thread] Current Thread [Next in Thread>