| To: | Brian Grossman <brian@xxxxxxxxxxxx> |
|---|---|
| Subject: | Re: xfs oops |
| From: | Chris Wedgwood <cw@xxxxxxxx> |
| Date: | Sat, 8 Feb 2003 15:41:39 -0800 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <courier.3E4587E9.00000AD2@xxxxxxxxxxxxxxxxxx> |
| References: | <courier.3E3F5B9E.0000441C@xxxxxxxxxxxxxxxxxx> <20030204091538.A29171@xxxxxxxxxxxxx> <courier.3E4587E9.00000AD2@xxxxxxxxxxxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.3.28i |
On Sat, Feb 08, 2003 at 03:42:49PM -0700, Brian Grossman wrote: > 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. > Are there any known issues combining xfs with v4l2, nvidia or > preempt? Or with ext3 or reiserfs? I'm trying with preemtp and without the nv driver... previously when I got this the nv driver has been loaded although wasn't active at the time. Sadly, 2.5.x and the nv driver don't play well together right now in terms of locking. I'd love to know if you can reproduce this *without* the nv driver as so far I've been unable to. --cw |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [Bug 217] Kernel compilation error, bugzilla-daemon |
|---|---|
| Next by Date: | Re: xfs oops, Brian Grossman |
| Previous by Thread: | Re: xfs oops, Brian Grossman |
| Next by Thread: | Re: xfs oops, Brian Grossman |
| Indexes: | [Date] [Thread] [Top] [All Lists] |