Go Back   nV News Forums > Linux Support Forums > NVIDIA Linux

Newegg Daily Deals

Closed Thread
 
Thread Tools
Old 05-23-05, 09:58 AM   #169
Koradji
Registered User
 
Join Date: May 2005
Posts: 18
Default Re: Trying to make headway into finding the Xid crashes source...

OK, got the FX5800 into my GF's machine. This card has been solid for about two years, with a hefty amount of 3d stuff in that.
glxgears ran fine, on one attempt.
cpbotha's Cone3 crashed it very nicely in one attempt, common set of Xid messages, and X at ~99.7%

I'm now completely convinced this bug is software.

So why is there not more screaming?
Is it only hitting people who've replaced drivers in April/May ?
__________________
The problem with open source drivers, is they work.
Koradji is offline  
Old 05-23-05, 10:14 AM   #170
gilboa
Linux addict...
 
Join Date: Jan 2004
Posts: 540
Default Re: Trying to make headway into finding the Xid crashes source...

The Xid problem seem to hit people with newer cards or hardware (FX6xxx, PCI-Express) who can't use older drivers.
For instance , the FX6600 seems to be one of the biggest culprit.

Cheers,
__________________
DEV-NG: Intel S2600C0, 2xE52658V2, 32GB, 4x2TB, GTX680, F19/x86_64, Dell U2711.
DEV: Intel S5520SC, 2xX5680, 36GB, 5x320GB, GTX550, F19/x86_64, Dell U2711 (^).
SRV: Tyan Tempest i5400XT, 2xE5335, 8GB, 4x2TB, 9800GTX, F19/x86-64, Dell U2412.
LAP: ASUS N56VJ, i7-3630QM, 16GB, 1TB, 635M, F19/x86_64.
gilboa is offline  
Old 05-23-05, 10:49 AM   #171
deadhamster
Registered User
 
Join Date: Oct 2002
Posts: 10
Default Re: Trying to make headway into finding the Xid crashes source...

My problems also didn't start until the 6111 drivers, but I had some issues even on my old gf3 ti500. However I noticed something much more interesting last night. When I rebooted, my screen went corrupt. I had to leave it off for a minute to get it to boot back up properly. It became corrupt during driver loading, I think while it was loading my scsi drivers. So X and the nvidia drivers certainly had no part in it. It looks like my problem might be heat related (didn't have time to cool after the last crash?), though the card doesn't feel hot. I get xid crashes, but maybe mine are unrelated.

-DH
deadhamster is offline  
Old 05-23-05, 03:03 PM   #172
gilboa
Linux addict...
 
Join Date: Jan 2004
Posts: 540
Default Re: Trying to make headway into finding the Xid crashes source...

Quote:
Originally Posted by cpbotha
Okay everyone, maybe NVidia is listening...

My test case is now available in binary form as well. Download this tarball: http://visualisation.tudelft.nl/~cpb...ash-x86.tar.gz then unpack it and read the README.

You should be able to run this binary on ANY x86 Linux system newer or just as old as Debian 3.0. It should reproduce the reported X freeze: Xids in dmesg, WAIT()s in X.log, X is frozen, CPU at 100%, wait long enough and X unfreezes.

The source is available at: http://visualisation.tudelft.nl/~cpb...nvcrash.tar.gz

I can reproduce the X freeze on driver versions 7174, 7167 and 6629. On 6111 and 6106 only the application itself freezes during the destruction of the 3D windows. On 5336, there is no crash. So, there was a definite progression from 5336 (no freeze) through 6106 and 6111 (application freeze) through 6629 to 7174 (X freezes).
Machnie crashed within 2 seconds.
Had to reboot it. (Couldn't even ssh to it)

Good job!
__________________
DEV-NG: Intel S2600C0, 2xE52658V2, 32GB, 4x2TB, GTX680, F19/x86_64, Dell U2711.
DEV: Intel S5520SC, 2xX5680, 36GB, 5x320GB, GTX550, F19/x86_64, Dell U2711 (^).
SRV: Tyan Tempest i5400XT, 2xE5335, 8GB, 4x2TB, 9800GTX, F19/x86-64, Dell U2412.
LAP: ASUS N56VJ, i7-3630QM, 16GB, 1TB, 635M, F19/x86_64.
gilboa is offline  
Old 05-24-05, 04:59 AM   #173
LubosD
Registered User
 
Join Date: Jan 2005
Location: Czech Republic
Posts: 451
Send a message via ICQ to LubosD
Default Re: Trying to make headway into finding the Xid crashes source...

It is 2 months since 7174 was released. What about some new *working* drivers?

This makes me crazy:
Code:
Unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:
f926ab47
*pde = 00000000
Oops: 0000 [#1]
PREEMPT 
Modules linked in: snd_seq_oss snd_seq_midi udf floppy sd_mod sg sr_mod it87 eeprom i2c_sensor i2c_isa i2c_sis96x vmnet vmmon lirc_gpio lirc_dev md5 ipv6 rfcomm l2cap ipt_MASQUERADE iptable_nat ip_conntrack ip_tables 8139too mii ohci1394 loop snd_emu10k1_synth snd_pcm_oss snd_mixer_oss snd_emu10k1 snd_ac97_codec snd_pcm snd_page_alloc snd_emux_synth snd_seq_virmidi snd_rawmidi snd_seq_midi_event snd_seq_midi_emul snd_seq snd_timer snd_seq_device snd_hwdep snd snd_util_mem tuner bttv video_buf firmware_class i2c_algo_bit btcx_risc tveeprom fuse ufsd cdemu nvidia eth1394 ieee1394 sata_sil libata usb_storage ehci_hcd usbhid usblp ohci_hcd usbcore video thermal processor fan button battery ac rtc raw
CPU:    0
EIP:    0060:[<f926ab47>]    Tainted: P      VLI
EFLAGS: 00013297   (2.6.11.7) 
EIP is at _nv001656rm+0xf/0x1c [nvidia]
eax: 00000000   ebx: f5c1fd80   ecx: f7b30400   edx: 00000000
esi: ea887800   edi: ea887800   ebp: f5c95d7c   esp: f5c95d7c
ds: 007b   es: 007b   ss: 0068
Process X (pid: 20276, threadinfo=f5c94000 task=ee7b6a20)
Stack: f5c95d9c f93f8594 f7b30400 ea887800 00000000 000002d0 c1edfb80 f5c95dc8 
       f5c95dd8 f93f81bf ea887800 f5c1fd80 00000000 00000000 f5c1fd80 ea887800 
       f9268d12 c6f50000 f5c1fd80 f5c95e78 f93220e7 f7b30400 c6f50000 f5c95e78 
Call Trace:
 [<f93f8594>] _nv003383rm+0x20/0x28 [nvidia]
 [<f93f81bf>] _nv003385rm+0x1f/0x3c [nvidia]
 [<f9268d12>] _nv001739rm+0x16/0x2c [nvidia]
 [<f93220e7>] _nv001871rm+0xcb/0x390 [nvidia]
 [<f9322102>] _nv001871rm+0xe6/0x390 [nvidia]
 [<f9388130>] _nv004351rm+0xb0/0xbc [nvidia]
 [<f9268b51>] _nv001678rm+0x31/0x3c [nvidia]
 [<f926b7e1>] _nv001208rm+0x101/0x150 [nvidia]
 [<f926bebe>] _nv001176rm+0x14e/0x15c [nvidia]
 [<f925beaa>] _nv001889rm+0x36/0xe0 [nvidia]
 [<f926c023>] _nv001214rm+0xcb/0x2f4 [nvidia]
 [<f926c06b>] _nv001214rm+0x113/0x2f4 [nvidia]
 [<f9268ef6>] _nv001740rm+0x12/0x18 [nvidia]
 [<f926f49f>] rm_init_adapter+0x5f/0x90 [nvidia]
 [<f926f493>] rm_init_adapter+0x53/0x90 [nvidia]
 [<f9477b0c>] nv_kern_open+0x284/0x313 [nvidia]
 [<c015d2a1>] chrdev_open+0x104/0x1f6
 [<c0155697>] get_empty_filp+0x8d/0xeb
 [<c0153cbc>] dentry_open+0x1c1/0x266
 [<c0153af5>] filp_open+0x40/0x46
 [<c040464d>] gunzip+0x223/0x36b
 [<c0153dce>] get_unused_fd+0x6d/0xd0
 [<c016147b>] getname+0x67/0xd3
 [<c0153f52>] sys_open+0x3c/0x92
 [<c0102eb9>] sysenter_past_esp+0x52/0x75
Code: 55 89 e5 8b 45 0c 8b 4d 14 8b 55 10 c1 ea 02 8b 80 70 01 00 00 89 0c 90 89 ec 5d c3 55 89 e5 8b 45 0c 8b 55 10 8b 80 70 01 00 00 <8a> 04 02 0f b6 c0 89 ec 5d c3 8d 76 00 55 89 e5 8b 45 0c 8b 55
Code:
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x000044c8, 0x00007218, 0)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x000044c8, 0x00007218, 0)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00004ec8, 0x00008228, 0)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00004ec8, 0x00008228, 0)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00004ec8, 0x00008acc, 0)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00004ec8, 0x00008acc, 0)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00004ec8, 0x00008b34, 0)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00004ec8, 0x00008b34, 0)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00004ec8, 0x0000c01c, 0)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00004ec8, 0x0000c01c, 0)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00004ec8, 0x0000d0fc, 0)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00004ec8, 0x0000d0fc, 0)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00004ec8, 0x000011e4, 0)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00004ec8, 0x000011e4, 0)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00004ec8, 0x00002350, 0)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00004ec8, 0x00002350, 0)
LubosD is offline  
Old 05-24-05, 10:56 AM   #174
chunkey
#!/?*
 
Join Date: Oct 2004
Posts: 662
Default Re: Trying to make headway into finding the Xid crashes source...

Quote:
Originally Posted by LubosD
It is 2 months since 7174 was released. What about some new *working* drivers?

This makes me crazy:
Code:
Unable to handle kernel NULL pointer dereference at virtual address 00000000
 printing eip:
f926ab47
*pde = 00000000
Oops: 0000 [#1]
PREEMPT 
Modules linked in: snd_seq_oss ...
CPU:    0
EIP:    0060:[<f926ab47>]    Tainted: P      VLI
EFLAGS: 00013297   (2.6.11.7) 
EIP is at _nv001656rm+0xf/0x1c [nvidia]
eax: 00000000   ebx: f5c1fd80   ecx: f7b30400   edx: 00000000
esi: ea887800   edi: ea887800   ebp: f5c95d7c   esp: f5c95d7c
ds: 007b   es: 007b   ss: 0068
Process X (pid: 20276, threadinfo=f5c94000 task=ee7b6a20)
Stack: f5c95d9c f93f8594 f7b30400 ea887800 00000000 000002d0 c1edfb80 f5c95dc8 
       f5c95dd8 f93f81bf ea887800 f5c1fd80 00000000 00000000 f5c1fd80 ea887800 
       f9268d12 c6f50000 f5c1fd80 f5c95e78 f93220e7 f7b30400 c6f50000 f5c95e78 
Call Trace:
 [<f93f8594>] _nv003383rm+0x20/0x28 [nvidia]
 [<f93f81bf>] _nv003385rm+0x1f/0x3c [nvidia]
 [<f9268d12>] _nv001739rm+0x16/0x2c [nvidia]
Code:
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x000044c8, 0x00007218, 0)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x000044c8, 0x00007218, 0)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00004ec8, 0x00008228, 0)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00004ec8, 0x00008228, 0)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00004ec8, 0x00008acc, 0)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00004ec8, 0x00008acc, 0)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00004ec8, 0x00008b34, 0)
...
Yeah, nVidia should really consider to release new and of course WORKING drivers... which MUST have LESS bugs like the old one... I'll test everything even or especally these completly untested beta stuff. if they can just _fix_ these god damned Xid issues everyone has...

(Anyway, what do you think, when nVidia release a new driver? I say in 3 month)

and BTW... yeah these Cone - crash is really _good_ I don't even need to _click_ "nvcrash", it's enough when I close some of the windows...
(with the little X-Button, not with _Quit_)...

EDIT: just a XID, but

Code:
NVRM: Xid: 23,  L1 -> L0
NVRM: Xid: 6, PE0004 0100 00000000 00200018 deadbeef 00000098
so deadbeef, probably a not initialized variable somewhere?

Last edited by chunkey; 05-24-05 at 04:00 PM.
chunkey is offline  
Old 05-24-05, 12:47 PM   #175
kmare
Registered User
 
Join Date: Jul 2003
Location: greece
Posts: 180
Send a message via ICQ to kmare
Default Re: Trying to make headway into finding the Xid crashes source...

yeah... I'd like a new driver with the fix... but just knowing that they found and fixed the problem and that the fix will be available in the next driver release is enough for now for me... it seems like my pc freezes every 40-50 hours in 2d more and running a 3d app a few secs are enough.. so I can live without 3d apps/games for few more days
kmare is offline  
Old 05-24-05, 06:01 PM   #176
Koradji
Registered User
 
Join Date: May 2005
Posts: 18
Default Re: Trying to make headway into finding the Xid crashes source...

It's unfair to say it's specifically a bug with nvidia's drivers, just because it's a bug that seems to occur with nvidia's drivers. They might well be awesomely written drivers.
It is fair to say, wherever the bug is, nvidia's product is broken, and nvidia have to fix it, because they are the only ones with access to all the relevant source.

On similar subject.
Someone on the gentoo boards suggested they had this bug with ATI. This means little in the abscence of them giving good description of the bug, but, it might be worth looking at if anyone has the hardware. Of course that wouldn't stop it being nvidia's job to fix it, and may even simply be an indication that they're using the same code. But if enough samples show ATI specifically don't have the bug, we know a little more.

maybe we should call this the beef bug, it turns up so often in those Xid messages.
__________________
The problem with open source drivers, is they work.
Koradji is offline  

Old 05-25-05, 12:06 AM   #177
gilboa
Linux addict...
 
Join Date: Jan 2004
Posts: 540
Default Re: Trying to make headway into finding the Xid crashes source...

Quote:
so deadbeef, probably a not initialized variable somewhere?
Hehe, I think I also saw badf00d in one of the Xid messages... good old uninitialized memory allocations...
__________________
DEV-NG: Intel S2600C0, 2xE52658V2, 32GB, 4x2TB, GTX680, F19/x86_64, Dell U2711.
DEV: Intel S5520SC, 2xX5680, 36GB, 5x320GB, GTX550, F19/x86_64, Dell U2711 (^).
SRV: Tyan Tempest i5400XT, 2xE5335, 8GB, 4x2TB, 9800GTX, F19/x86-64, Dell U2412.
LAP: ASUS N56VJ, i7-3630QM, 16GB, 1TB, 635M, F19/x86_64.
gilboa is offline  
Old 05-25-05, 08:18 AM   #178
LubosD
Registered User
 
Join Date: Jan 2005
Location: Czech Republic
Posts: 451
Send a message via ICQ to LubosD
Default Re: Trying to make headway into finding the Xid crashes source...

Quote:
Originally Posted by Koradji
maybe we should call this the beef bug, it turns up so often in those Xid messages.
I have switched back to AGP GART a few days ago and I have no more beefs.
I have only "simple" crashes and they don't happen so often:
Code:
May 18 18:39:08 localhost kernel: NVRM: Xid: 23,  L1 -> L0
May 18 18:39:08 localhost kernel: NVRM: Xid: 8, Channel 00000020
May 23 21:02:40 localhost kernel: NVRM: Xid: 23,  L1 -> L0
May 23 21:02:40 localhost kernel: NVRM: Xid: 8, Channel 00000020
LubosD is offline  
Old 05-25-05, 10:24 AM   #179
sir_tez
Registered User
 
Join Date: Apr 2005
Posts: 23
Default Re: Trying to make headway into finding the Xid crashes source...

Is everyone that's having a problem using UDEV?
sir_tez is offline  
Old 05-25-05, 10:28 AM   #180
gilboa
Linux addict...
 
Join Date: Jan 2004
Posts: 540
Default Re: Trying to make headway into finding the Xid crashes source...

Problems with udev? What problems?
You only need to add the nVidia driver entry to /etc/udev and it'll work just fine. (Apart from crashing all time...)
__________________
DEV-NG: Intel S2600C0, 2xE52658V2, 32GB, 4x2TB, GTX680, F19/x86_64, Dell U2711.
DEV: Intel S5520SC, 2xX5680, 36GB, 5x320GB, GTX550, F19/x86_64, Dell U2711 (^).
SRV: Tyan Tempest i5400XT, 2xE5335, 8GB, 4x2TB, 9800GTX, F19/x86-64, Dell U2412.
LAP: ASUS N56VJ, i7-3630QM, 16GB, 1TB, 635M, F19/x86_64.
gilboa is offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


Similar Threads
Thread Thread Starter Forum Replies Last Post
Random crashes, NVRM Xid messages Iesos NVIDIA Linux 90 10-04-12 03:27 AM

All times are GMT -5. The time now is 03:45 PM.


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