nvidia on 8.0-CURRENT

[Adam K Kirchhoff]

Sorry, I should have been more clear.  If I'm talking about the nv driver, I'd 
call it that.  When I said 'nvidia drivers' I did actually mean 'nvidia' :-)

Adam

On Friday 18 January 2008 16:10:28 Aryeh M. Friedman wrote:
> Adam K Kirchhoff wrote:
> > I realize that the nvidia drivers are not the FreeBSD developers'
> > responsibility and that they are not supported on -CURRENT, but I'm
> > curious if anyone has managed to get them working lately?  They worked
> > for me until about a week ago when I updated again.  I've since
> > reinstalled the nvidia drivers, but shortly after starting X, the system
> > crashes with this:
>
> Are you talking about nv or nvidia-driver.... nv works fine
>
> > FreeBSD/i386 (sorrow.ashke.com) (ttyd0)
> >
> > login: panic: pmap_remove_all: page 0xc5f27ae4 is fictitious
> > cpuid = 0
> > KDB: enter: panic
> > [thread pid 952 tid 100139 ]
> > Stopped at      kdb_enter+0x3a: movl    $0,kdb_why
> > db> trace
> > Tracing pid 952 tid 100139 td 0xc649b220
> > kdb_enter(c0b061a3,c0b061a3,c0b35767,ea3d9b70,0,...) at kdb_enter+0x3a
> > panic(c0b35767,c5f27ae4,c0b28ed1,746,c0b28ed1,...) at panic+0x12c
> > pmap_remove_all(c5f27ae4,0,c639b660,746,c0b28ed1,...) at
> > pmap_remove_all+0x22 vm_object_page_remove(c5ffac00,66dd,0,66de,0,...) at
> > vm_object_page_remove+0x159
> > vm_object_sync(c5ffac00,66dd000,0,1000,1,...) at vm_object_sync+0x330
> > vm_map_sync(c57240e8,28f32000,28f33000,1,1,...) at vm_map_sync+0x281
> > msync(c649b220,ea3d9cfc,c,c0b0bd32,c0bb7bb8,...) at msync+0x6c
> > syscall(ea3d9d38) at syscall+0x2b3
> > Xint0x80_syscall() at Xint0x80_syscall+0x20
> > --- syscall (65, FreeBSD ELF32, msync), eip = 0x28355a4b, esp =
> > 0xbfbfe44c, ebp = 0xbfbfe468 ---
> > db> reboot
> >
> > Adam
> > _______________________________________________
> > freebsd-x11 at freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-x11
> > To unsubscribe, send any mail to "freebsd-x11-unsubscribe at freebsd.org"