From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: BUG: sleeping function called from invalid context at kernel/rwsem.c:131 XFS? (was: Re: linux-next: Tree for October 17) Date: Fri, 17 Oct 2008 13:55:10 -0700 Message-ID: <20081017135510.7127c4e7@infradead.org> References: <20081017164116.GA17375@infradead.org> <20081017165738.GA20818@infradead.org> <20081017203710.GA27187@infradead.org> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: Received: from casper.infradead.org ([85.118.1.10]:42577 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753440AbYJQUzE (ORCPT ); Fri, 17 Oct 2008 16:55:04 -0400 In-Reply-To: <20081017203710.GA27187@infradead.org> Sender: linux-next-owner@vger.kernel.org List-ID: Cc: Alexander Beregalov , Christoph Hellwig , xfs@oss.sgi.com, linux-next@vger.kernel.org, LKML On Fri, 17 Oct 2008 16:37:10 -0400 Christoph Hellwig 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