xfs
[Top] [All Lists]

Re: RFC: i386: kill !4KSTACKS

To: Adrian Bunk <bunk@xxxxxxxxx>
Subject: Re: RFC: i386: kill !4KSTACKS
From: Nathan Scott <nathans@xxxxxxx>
Date: Mon, 3 Oct 2005 06:35:58 +1000
Cc: Alexander Nyberg <alexn@xxxxxxxxx>, Neil Brown <neilb@xxxxxxx>, Chris Wedgwood <cw@xxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx
In-reply-to: <20051001225012.GE4212@stusta.de>; from bunk@stusta.de on Sun, Oct 02, 2005 at 12:50:12AM +0200
References: <20050902003915.GI3657@stusta.de> <20050902053356.GA20603@taniwha.stupidest.org> <20050902162931.A4496772@wobbly.melbourne.sgi.com> <17175.62454.623678.209697@cse.unsw.edu.au> <20050913080552.GA1815@localhost.localdomain> <20051001225012.GE4212@stusta.de>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5i
On Sun, Oct 02, 2005 at 12:50:12AM +0200, Adrian Bunk wrote:
> On Tue, Sep 13, 2005 at 10:05:52AM +0200, Alexander Nyberg wrote:
> > 
> > http://bugzilla.kernel.org/show_bug.cgi?id=5210
> 
> Nathan, can you look into this bug?
> 

OK - looks like a scheduling-while-atomic warning on a metdata
buffer read, then a panic (sometime later?) at do_page_fault
with no useful stack trace (removed by bug reporter? - thats
the one you need...).  The first stack trace (atomic/shedule)
would not be >4K afaict, so thats a red herring I think.

cheers.

-- 
Nathan


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