xfs
[Top] [All Lists]

Re: kernel oops in 2.5.69

To: Ingo Juergensmann <ij@xxxxxxxxxxxxxxxx>
Subject: Re: kernel oops in 2.5.69
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Mon, 19 May 2003 21:21:42 +0100
Cc: linux-xfs@xxxxxxxxxxx
In-reply-to: <3EC932C9.80604@xxxxxxxxxxxxxxxx>; from ij@xxxxxxxxxxxxxxxx on Mon, May 19, 2003 at 09:38:49PM +0200
References: <3EC932C9.80604@xxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5.1i
On Mon, May 19, 2003 at 09:38:49PM +0200, Ingo Juergensmann wrote:
> 21:32 < ij_> oerx...
> 21:32 < ij_> xfs in kernel 2.5.69 is not really usuable?
> 21:32 < hch> it's useable for me at least
> 21:33 < ij_> kernel oops?
> 21:33 < hch> as long as you don't use non-standard blocksize or 
> unwritten extents+odirect at least
> 21:33 < ij_> bad: scheduling while atomic!
> 21:33 < ij_> Call Trace:
> 21:33 < ij_>  [<c011bba2>] schedule+0x3b2/0x3c0
> 21:33 < ij_>  [<c02098d4>] xfs_iunlock+0x34/0x70
> 21:33 < ij_> ...
> 21:33 < hch> ij_: send the full trace to linux-xfs@xxxxxxxxxxx please
> 
> here it is (attached)

This starts to oops in NFS first (and for a long time).  As NFS in 2.5.69
is know buggy can you reproduce this with the current -bk snapshot?


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