On Fri, Jan 02, 2004 at 03:27:40PM -0500, Valdis.Kletnieks _at_ vt.edu 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. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
References:
- XFS forced shutdown with kernel 2.6.0Claas Langbehn
- Re: XFS forced shutdown with kernel 2.6.0Christoph Hellwig
- Re: XFS forced shutdown with kernel 2.6.0Valdis.Kletnieks
- Prev by Date: Re: udev - please help me to understand
- Next by Date: Re: udev and devfs - The final word
- Previous by thread: Re: XFS forced shutdown with kernel 2.6.0
- Next by thread: Re: XFS forced shutdown with kernel 2.6.0
- Indexes:[Main][Thread]