xfs
[Top] [All Lists]

Re: XFS forced shutdown with kernel 2.6.0

To: Valdis.Kletnieks@xxxxxx
Subject: Re: XFS forced shutdown with kernel 2.6.0
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Fri, 2 Jan 2004 20:35:55 +0000
Cc: Claas Langbehn <claas@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx
In-reply-to: <200401022027.i02KRe7X013502@xxxxxxxxxxxxxxxxxxxxxxx>; from Valdis.Kletnieks@xxxxxx on Fri, Jan 02, 2004 at 03:27:40PM -0500
Mail-followup-to: Christoph Hellwig <hch@xxxxxxxxxxxxx>, Valdis.Kletnieks@xxxxxx, Claas Langbehn <claas@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, linux-xfs@xxxxxxxxxxx
References: <20040102095051.GA19872@xxxxxxxxxx> <20040102182921.A27237@xxxxxxxxxxxxx> <200401022027.i02KRe7X013502@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mutt/1.2.5.1i
On Fri, Jan 02, 2004 at 03:27:40PM -0500, Valdis.Kletnieks@xxxxxx wrote:
> On Fri, 02 Jan 2004 18:29:21 GMT, Christoph Hellwig said:
> 
> > I've seen the same bug a few times lately, but only if I had previous
> > memory corruption due to code I was hacking on.  Can you reproduce it
> > without the nvidia module loaded as that is likely source of such
> > corruption?
> 
> While you're at it, see what *else* you can turn off - RAID, devfs, NFS, etc.
> 
> It's equally likely that you're tripping over some other kernel module's
> use-after-free or chase-the-wrong-pointer bug.  I've seen a lot more bugfixes
> for *those* on this list than cases where "I turned off nvidia and it started
> working".

The difference is that I can look at those while I can't look at nvidias
driver. Pretty simple.


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