From: Christoph Hellwig <hch@infradead.org>
To: Valdis.Kletnieks@vt.edu
Cc: Claas Langbehn <claas@rootdir.de>,
linux-kernel@vger.kernel.org, linux-xfs@oss.sgi.com
Subject: Re: XFS forced shutdown with kernel 2.6.0
Date: Fri, 2 Jan 2004 20:35:55 +0000 [thread overview]
Message-ID: <20040102203555.A1420@infradead.org> (raw)
In-Reply-To: <200401022027.i02KRe7X013502@turing-police.cc.vt.edu>; from Valdis.Kletnieks@vt.edu on Fri, Jan 02, 2004 at 03:27:40PM -0500
On Fri, Jan 02, 2004 at 03:27:40PM -0500, Valdis.Kletnieks@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.
next prev parent reply other threads:[~2004-01-02 20:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-02 9:50 XFS forced shutdown with kernel 2.6.0 Claas Langbehn
2004-01-02 18:29 ` Christoph Hellwig
2004-01-02 20:27 ` Valdis.Kletnieks
2004-01-02 20:35 ` Christoph Hellwig [this message]
[not found] ` <04a601c415a5$0513b020$d100000a@sbs2003.local>
2004-03-29 16:05 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20040102203555.A1420@infradead.org \
--to=hch@infradead.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=claas@rootdir.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.