| To: | Chris Wedgwood <cw@xxxxxxxx> |
|---|---|
| Subject: | Re: xfs oops |
| From: | Brian Grossman <brian@xxxxxxxxxxxx> |
| Date: | Sat, 08 Feb 2003 17:36:39 -0700 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | Message from Chris Wedgwood <cw@f00f.org> of "Sat, 08 Feb 2003 15:41:39 PST." <20030208234139.GB23898@f00f.org> |
| References: | <courier.3E3F5B9E.0000441C@lindy.SoftHome.net> <20030204091538.A29171@infradead.org> <courier.3E4587E9.00000AD2@lindy.SoftHome.net> <20030208234139.GB23898@f00f.org> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
> > It still gets oopses. Most recently in kswapd. I'll try factoring > > out nvidia next. > > I've seen this too... I'm actually trying to reproduce this now but so > far it's been pretty good other than some lock contention issues. My most recent problem was deleting three ~1.5GB files. Oops in kswapd. RM in diskwait. Any further access to the filesystem diskwaited, too. After reboot, I discovered that the third file remained. > Sadly, 2.5.x and the nv driver don't play well together right now in > terms of locking. My problems are with 2.4.20. I'll factor out nvidia in a couple days. Brian |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs oops, Chris Wedgwood |
|---|---|
| Next by Date: | Re: xfs oops, Chris Wedgwood |
| Previous by Thread: | Re: xfs oops, Chris Wedgwood |
| Next by Thread: | Re: xfs oops, Chris Wedgwood |
| Indexes: | [Date] [Thread] [Top] [All Lists] |