Re: Oops: 0000 with kernel 2.4.17pre2

[Daniel T. Chen]

Are these the latest (2313) drivers? I saw this last night as well and
updated to devfs-v199v2 immediately. I've since updated to v199v3 and
switched to nvgart and will be pushing my system pretty hard over the next
couple hours to try to reproduce it.

---
Dan Chen                 [e-mail]
GPG key: www.cs.unc.edu/~chenda/pubkey.gpg.asc

On Tue, 4 Dec 2001, Marcelo Tosatti wrote:

> On Tue, 4 Dec 2001, Christian Bornträger wrote:
> 
> > I found this in my logs.
> > I have no idea, why the log says not tainted, because I am quite sure that 
> > the nvidia-driver was loaded at this moment.
> > It seems that this happened while trying to kill a quake3-session.(I noticed 
> > today, that there is a linux version..... ;-))
> > 
> > I don´t know if I should blame the nvidia-driver, but please have a look at 
> > it, because there were some other oops messages with 2.4.16 in the LKML.
> > The call trace has functions of the VM, of the file system layer and reiserfs.
> > 
> > 
> > greetings
> > 
> > 4e 08 8b 41 04 89
> > Dec  4 16:48:12 cubus kernel:  <6>NVRM: AGPGART: freed 16 pages
> 				    ^^^
> > Dec  4 16:48:14 cubus kernel:  printing eip:
> > Dec  4 16:48:14 cubus kernel: e097134a
> 
> It really seems to be the nvidia driver which is causing problems.