nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   Corrupted display - 295.59 - Dell Precision T3500 (G98 [Quadro NVS 295]) (http://www.nvnews.net/vbulletin/showthread.php?t=183966)

gbailey 06-13-12 05:36 PM

Corrupted display - 295.59 - Dell Precision T3500 (G98 [Quadro NVS 295])
 
Tried upgrading NVIDIA driver to 295.59 to see if it would help with frequent crashes and machine lockups experienced with 295.53 given at:

http://www.nvnews.net/vbulletin/showthread.php?t=181666

First crash with 295.59:

Jun 13 15:19:35 ss-geb-dev kernel: NVRM: Xid (0000:02:00): 13, 0001 00000000 00005097 000015e0 00000000 00000040
Jun 13 15:19:35 ss-geb-dev kernel: NVRM: Xid (0000:02:00): 6, PE0004
Jun 13 15:19:36 ss-geb-dev kernel: NVRM: GPU at 0000:02:00.0 has fallen off the bus.

I've downgraded to 290.10 as it seems some people are reporting better luck with that version.

I'm really running out of ideas here...

gbailey 06-14-12 06:49 PM

Re: Corrupted display - 295.59 - Dell Precision T3500 (G98 [Quadro NVS 295])
 
Bummer; crash with 290.10 as well. So 290.10, 295.53, and 295.59 have all resulted in crashes... Do I have any other options? Run the beta stuff? Eat shards of glass in frustration? Hello, NVIDIA???

Jun 14 16:40:09 ss-geb-dev kernel: NVRM: Xid (0000:02:00): 13, 0001 00000000 00005097 0000194c 00000000 00000040
Jun 14 16:40:09 ss-geb-dev kernel: NVRM: Xid (0000:02:00): 6, PE0002
Jun 14 16:40:09 ss-geb-dev kernel: NVRM: Xid (0000:02:00): 6, PE0005
Jun 14 16:40:09 ss-geb-dev kernel: NVRM: Xid (0000:02:00): 6, PE0004
Jun 14 16:40:11 ss-geb-dev abrt[24193]: saved core dump of pid 5597 (/usr/bin/Xorg) to /var/spool/abrt/ccpp-2012-06-14-16:40:09-5597.new/coredump (58822656 bytes)
Jun 14 16:40:11 ss-geb-dev abrtd: Directory 'ccpp-2012-06-14-16:40:09-5597' creation detected
Jun 14 16:40:11 ss-geb-dev kernel: NVRM: Xid (0000:02:00): 6, PE0001
Jun 14 16:40:13 ss-geb-dev gnome-keyring-daemon[11115]: dbus failure unregistering from session: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jun 14 16:40:16 ss-geb-dev kernel: NVRM: Xid (0000:02:00): 26, Ch 00000003 M 00000104 D 00000000 intr 04400000
Jun 14 16:40:16 ss-geb-dev kernel: NVRM: Xid (0000:02:00): 26, Ch 00000003 M 000003c0 D 4739d100 intr 04c00000
Jun 14 16:40:16 ss-geb-dev kernel: NVRM: Xid (0000:02:00): 26, Ch 00000003 M 000003c0 D 4739d100 intr 00400000


All times are GMT -5. The time now is 11:25 PM.

Powered by vBulletin® Version 3.7.1
Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Copyright 1998 - 2014, nV News.