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

Newegg Daily Deals

Closed Thread
 
Thread Tools
Old 06-30-06, 10:29 AM   #313
rcgroot
Registered User
 
Join Date: Jun 2006
Posts: 1
Default Re: Trying to make headway into finding the Xid crashes source...

I just bought a new machine and outfitted it with my old videocard (nVidia Corporation NV36.2 [GeForce FX 5700]). This videocard was rockstable on my old machine, but locks in the new machine. NVRM: Xid (0001:00): 6 and 28 with X locking and needing to be restarted with ssh from a remote machine.

Both machines run xorg version 7.0.22 (debian testing), both machines run
exactly the same kernel (home build vanilla linux-image-2.6.17.1 .deb package) and both run NVidia driver version 8762.

Both machines have the "VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]".

The buggy machine has an MSI mainboard (K8MM3-V) and the stable machine has a Abit (AV8) mainboard.

On the buggy machine I've tried both agpart, nvagp and no agp, all trouble.
Also different driver versions, 6629, 7182 and 8762, which in the old machine
were stable, are troublesum.

With:
Option "NvAGP" "0"
Option "RenderAccel" "false"
and agp=off as kernel parameter, the X is currently on a new record of an hour of working.

This problem has me quite riddled.
rcgroot is offline  
Old 06-30-06, 10:35 AM   #314
ticoli
Registered User
 
Join Date: Jan 2006
Posts: 13
Default Re: Trying to make headway into finding the Xid crashes source...

I'v just bought a new machine for my job, the graphic card is an intel embedded .... no problem!

I hope nvidia will put this tips in the faq!


Quote:
Originally Posted by rcgroot
I just bought a new machine and outfitted it with my old videocard (nVidia Corporation NV36.2 [GeForce FX 5700]). This videocard was rockstable on my old machine, but locks in the new machine. NVRM: Xid (0001:00): 6 and 28 with X locking and needing to be restarted with ssh from a remote machine.

Both machines run xorg version 7.0.22 (debian testing), both machines run
exactly the same kernel (home build vanilla linux-image-2.6.17.1 .deb package) and both run NVidia driver version 8762.

Both machines have the "VIA Technologies, Inc. VT8237 PCI bridge [K8T800/K8T890 South]".

The buggy machine has an MSI mainboard (K8MM3-V) and the stable machine has a Abit (AV8) mainboard.

On the buggy machine I've tried both agpart, nvagp and no agp, all trouble.
Also different driver versions, 6629, 7182 and 8762, which in the old machine
were stable, are troublesum.

With:
Option "NvAGP" "0"
Option "RenderAccel" "false"
and agp=off as kernel parameter, the X is currently on a new record of an hour of working.

This problem has me quite riddled.
ticoli is offline  
Old 07-01-06, 04:28 PM   #315
TPG
Unregistered User
 
TPG's Avatar
 
Join Date: Apr 2006
Location: Poland, Warsaw
Posts: 203
Default Re: Trying to make headway into finding the Xid crashes source...

I found lately that while i'm playing Enemy Territory, randomy my system freezes. My keyboard seems to not responding same as my mouse, sound is "choking" same as graphics, everythings "stutters".Only hard reset helps.I've checked logs and found this:

Quote:
Jul 1 22:59:40 tpgbox kernel: NVRM: Xid (0001:00): 6, PE0000 0004 00120008 00110620 00120007 014b014c
That was the last entry in /var/log/messages before i did hard reset.
__________________
mandriva > all
kthnxbai
TPG is offline  
Old 07-02-06, 12:02 AM   #316
energyman76b
Registered User
 
Join Date: Dec 2002
Location: Clausthal/Germany
Posts: 1,104
Default Re: Trying to make headway into finding the Xid crashes source...

Quote:
Originally Posted by Dabljuh

Oh, and one way to reduce the occurence of the XIDs has always been to decrease the performance of the card. By disabling AGP, using slower drivers, underclocking it etc...

If it isn't nvidia's fault, why didn't they show up meanwhile and tell us what the problem is? If it is something else (kernel etc) they'd certainly happily point at that direction, shifting the blame. But kernels come and go, the problems with nvidia cards persist. the high number of "works for me" posts indicates all but one thing:
blablabla.

Why are you so convinced that the Xid's are nvidias fault?

There are the manufacturers of the cards, and this guys can make A LOT of errors.

Examples? Not enough cooling by design, not correctly installed heatsink (both would lead to overheating and Xids... solveable by underclocking ... hmmm).
Bad caps. Bad routing on the PCB. Bad current supply. Low-cost-low-quality resistors.
This are all points that might lead to misbehaving cards - and this is all stuff that nvidia can not solve.

If a card is unstable, RMA it and get a new one. The party that is responsible for that fault will loose some money - and if enough people do it, learn something that way.
energyman76b is offline  
Old 07-02-06, 02:51 PM   #317
d13f00l
Registered User
 
Join Date: Apr 2005
Posts: 197
Default Re: Trying to make headway into finding the Xid crashes source...

To anyone having XID errors still...

Take off the side of your PC, put a box fan next to it, a fan that would go in a window and set it to high.

http://www.memtest86.com/#download0
Download the CD ISO, burn it, and boot your PC off the CD. Let memtest run a few hrs, if it doesn't find any errors..try playing a game or running X and see if you still get XID errors. Make sure the fan stays on.
d13f00l is offline  
Old 07-02-06, 03:05 PM   #318
ticoli
Registered User
 
Join Date: Jan 2006
Posts: 13
Default Re: Trying to make headway into finding the Xid crashes source...

Quote:
Originally Posted by energyman76b
blablabla.

Why are you so convinced that the Xid's are nvidias fault?

There are the manufacturers of the cards, and this guys can make A LOT of errors.

Examples? Not enough cooling by design, not correctly installed heatsink (both would lead to overheating and Xids... solveable by underclocking ... hmmm).
Bad caps. Bad routing on the PCB. Bad current supply. Low-cost-low-quality resistors.
This are all points that might lead to misbehaving cards - and this is all stuff that nvidia can not solve.

If a card is unstable, RMA it and get a new one. The party that is responsible for that fault will loose some money - and if enough people do it, learn something that way.
Perhaps ... but with windows XP, I can play several hours with very recent games!
ticoli is offline  
Old 07-02-06, 03:52 PM   #319
d13f00l
Registered User
 
Join Date: Apr 2005
Posts: 197
Default Re: Trying to make headway into finding the Xid crashes source...

Quote:
Originally Posted by ticoli
Perhaps ... but with windows XP, I can play several hours with very recent games!
When my PC was overheating, windows would give IRQL_NOT_LESS_OR_EQUAL blue screens of death, but linux was fine for months. Reapplying thermal gunk and getting a new HSF fixed my issues.
d13f00l is offline  
Old 07-02-06, 05:37 PM   #320
energyman76b
Registered User
 
Join Date: Dec 2002
Location: Clausthal/Germany
Posts: 1,104
Default Re: Trying to make headway into finding the Xid crashes source...

Quote:
Originally Posted by ticoli
Perhaps ... but with windows XP, I can play several hours with very recent games!
so what?

the manufacturer' test their card with windows. As long as it works there, it is good enough. Maybe hide a flaw here and there in the cards bios...

but they don't test them with linux. And suddenly you have a slighty different usage.
energyman76b is offline  

Old 07-07-06, 01:10 PM   #321
mlfarrell
Registered User
 
Join Date: Mar 2005
Posts: 65
Angry Re: Trying to make headway into finding the Xid crashes source...

I just found this thread yesterday and it has me extremely concerned. I've been using nvidia under linux for years soley because of its "reliability" and stability in that system. I just bought an hp laptop with a geforce go 7400 card in it. Rock solid in winxp; not a problem. In linux, I get the same XID lockup only when SDL programs are started, and at no other time. Of course my luck, I'm writing a game using SDL as my main library. I'm not about to switch api's over this stupid freeze

Jul 5 16:43:56 slickbox kernel: NVRM: Xid (0001:00):
6, PE0000 0184 beef0201 00000054 ff507fcc 042f0303
Jul 5 16:43:56 slickbox kernel: NVRM: Xid (0001:00):
28, L1 -> L0

Tried all the quickfixes on this forum, tried flashing bios, tried disabling acpi, apic, and anything else I can think of, saaaame glitch. It didn't start happening until after the laptop return grace period (of course).

I emailed an nvidia rep about this who was working with me on it for a few days until now which I haven't heard back in about 2 days. I'm really worried that this bug is going to just be "let go" for a really long time and I'll have to give up the idea of linux 3d programming on my new laptop. The very thought of this is infuriating. Does anyone even know what l1->l0 means or how to distinguish beween the different xid values?
mlfarrell is offline  
Old 07-07-06, 01:23 PM   #322
chunkey
#!/?*
 
Join Date: Oct 2004
Posts: 662
Default Re: Trying to make headway into finding the Xid crashes source...

Quote:
Originally Posted by mlfarrell
I just found this thread yesterday and it has me extremely concerned. I've been using nvidia under linux for years soley because of its "reliability" and stability in that system. I just bought an hp laptop with a geforce go 7400 card in it. Rock solid in winxp; not a problem. In linux, I get the same XID lockup only when SDL programs are started, and at no other time. Of course my luck, I'm writing a game using SDL as my main library. I'm not about to switch api's over this stupid freeze

Jul 5 16:43:56 slickbox kernel: NVRM: Xid (0001:00):
6, PE0000 0184 beef0201 00000054 ff507fcc 042f0303
Jul 5 16:43:56 slickbox kernel: NVRM: Xid (0001:00):
28, L1 -> L0

Tried all the quickfixes on this forum, tried flashing bios, tried disabling acpi, apic, and anything else I can think of, saaaame glitch. It didn't start happening until after the laptop return grace period (of course).

I emailed an nvidia rep about this who was working with me on it for a few days until now which I haven't heard back in about 2 days. I'm really worried that this bug is going to just be "let go" for a really long time and I'll have to give up the idea of linux 3d programming on my new laptop. The very thought of this is infuriating. Does anyone even know what l1->l0 means or how to distinguish beween the different xid values?
Sorry, but "noone" knows what exactly "XiD" means, Nvidia describes it as:
Quote:
Originally Posted by Nvidia's Readme
"Xid" messages indicate that a general GPU error occurred, most often due
to the driver misprogramming the GPU or to corruption of the commands sent
to the GPU. These messages provide diagnostic information that can be used
by NVIDIA to aid in debugging reported problems.
but, you say you've a laptop? have you already tried all NVreg_MOBILE & NVreg_SOFTEDID paramters?
see: Appendix I. Configuring a Laptop
chunkey is offline  
Old 07-08-06, 02:50 AM   #323
mlfarrell
Registered User
 
Join Date: Mar 2005
Posts: 65
Default Re: Trying to make headway into finding the Xid crashes source...

Unfortunately all the mobile settings (1-5) didn't fix the crash, although some seemed to make it run more stable than others but that could have just been a mirage. Secondly, I didn't bother tuning the mobile settings while softedid was enabled because the readme said that softedid would override it anyway. Just to be sure though I tried it with softedid=1 and mobile=3 and it still froze.

Is there a chance that upgrading my kernel (currently suse 10.1's 2.6.16) could fix the crash?

Second idea. Since sdl programs are the only culprits of this freeze (and google earth once) is there a way I can trace the glx calls of my SDL program to see what they are doing to induce the crash so that maybe I can recompile my own "safe" sdl library. AllegroGL (another GL targeted library) has never produced the crash/freeze once in linux.


I'm really at a loss here, I really didn't want a windows only laptop.
mlfarrell is offline  
Old 07-10-06, 10:00 PM   #324
mlfarrell
Registered User
 
Join Date: Mar 2005
Posts: 65
Default Re: Trying to make headway into finding the Xid crashes source...

Can anyone make any sense out of this:

Code:
NVRM: Xid (0001:00): 6, PE0000 0184 beef0201 0000a0e8 00000000 042f0303
NVRM: Xid (0001:00): 28,  L2 -> L1
psmouse.c: TouchPad at isa0060/serio4/input0 lost synchronization, throwing 1 bytes away.
psmouse.c: resync failed, issuing reconnect request
SysRq : SAK
SysRq : SAK
SysRq : SAK
SysRq : SAK
divide error: 0000 [#1]
SMP
Modules linked in: tifm_sd joydev st sr_mod xt_pkttype ipt_LOG xt_limit af_packet cpufreq_ondemand cpufreq_userspace cpufreq_powersave speedstep_centrino freq_table ircomm_tty ircomm irda crc_ccitt edd button battery ac ip6t_REJECT xt_tcpudp ipt_REJECT xt_state iptable_mangle iptable_nat ip_nat iptable_filter ip6table_mangle ip_conntrack nfnetlink ip_tables ip6table_filter ip6_tables x_tables ipv6 nls_iso8859_1 nls_cp437 vfat fat nls_utf8 ntfs loop dm_mod nvidia snd_hda_intel snd_hda_codec hw_random snd_pcm_oss pcmcia firmware_class snd_mixer_oss snd_pcm uhci_hcd intel_agp ehci_hcd sdhci ohci1394 snd_timer snd soundcore snd_page_alloc tifm_7xx1 tifm_core agpgart mmc_core ieee1394 e100 usbcore i2c_i801 i2c_core mii yenta_socket rsrc_nonstatic pcmcia_core ide_cd cdrom reiserfs fan thermal processor sg ahci libata piix sd_mod scsi_mod ide_disk ide_core
CPU:    1
EIP:    0060:[<f94f646e>]    Tainted: PF     VLI
EFLAGS: 00013246   (2.6.17.4-smp #1)
EIP is at _nv006247rm+0x296/0x2c4 [nvidia]
eax: 00005bff   ebx: 00000000   ecx: 00005bff   edx: 00000000
esi: f7db5d24   edi: f7db5d28   ebp: f7db5ca0   esp: f7db5c58
ds: 007b   es: 007b   ss: 0068
Process X (pid: 3533, threadinfo=f7db4000 task=dfcd3550)
Stack: f6d6b800 00100204 f7db5ca0 f94f6422 f6d6b800 00100200 f7db5ca0 f93b3d29
       f7db5d28 0000002e e13a7ef4 f7db5cb0 f93b3f21 f6d6b800 f7db5cb0 00000040
       00000080 00000020 f7db5ce0 f94f61c1 f6d6b800 f7541000 f7db5d24 0000002e
Call Trace:
 <f94f6422> _nv006247rm+0x24a/0x2c4 [nvidia]  <f93b3d29> _nv002674rm+0x45/0x84 [nvidia]
 <f93b3f21> _nv002668rm+0x1d/0x2c [nvidia]  <f94f61c1> _nv006409rm+0x45/0x50 [nvidia]
 <f93b33cc> _nv002693rm+0x58/0x100 [nvidia]  <f9529d71> _nv005434rm+0x15/0x1c [nvidia]
 <f95777b7> _nv006416rm+0xd3/0x14c [nvidia]  <f9528e82> <5>SAK: killed process 3533 (X): p->signal->session==tty->session
_nv005473rm+0x11a/0x47c [nvidia]
 <f95d436f> <5>SAK: killed process 3533 (X): p->signal->session==tty->session
_nv001524rm+0x593/0x2060 [nvidia]  <c01bf0b1> pci_bus_read_config_dword+0x58/0x63
 <f93b3f21> _nv002668rm+0x1d/0x2c [nvidia]  <f9529d71> _nv005434rm+0x15/0x1c [nvidia]
 <c01bb8a3> copy_from_user+0x54/0x80  <f961c473> os_memcpy_from_user+0x11/0x1c [nvidia]
 <f93c3322> _nv002574rm+0x1a/0x20 [nvidia]  <f93ab90c> _nv001898rm+0xe0/0x134 [nvidia]
 <c0287827> __down_failed+0x7/0xc  <f93a64b1> _nv003351rm+0x71/0xa4 [nvidia]
 <f93ccedd> _nv001809rm+0x3d/0x5d0 [nvidia]  <f93cd0db> _nv001809rm+0x23b/0x5d0 [nvidia]
 <f961c00c> os_pci_read_dword+0x2b/0x34 [nvidia]  <f9619687> nv_verify_pci_config+0x194/0x224 [nvidia]
 <f93cb87c> rm_ioctl+0x1c/0x24 [nvidia]  <c01bb8a3> copy_from_user+0x54/0x80
 <f9619c5f> nv_kern_ioctl+0x34f/0x3c0 [nvidia]  <c028826d> schedule+0x9e9/0xa93
 <c0204637> respond_string+0x3a/0xa5  <f9619d05> nv_kern_unlocked_ioctl+0x18/0x1d [nvidia]
 <f9619ced> nv_kern_unlocked_ioctl+0x0/0x1d [nvidia]  <c016a4e8> do_ioctl+0x1c/0x5e
 <c016a774> vfs_ioctl+0x24a/0x25c  <c016a7ce> sys_ioctl+0x48/0x62
 <c0103c27> syscall_call+0x7/0xb  <c0204637> respond_string+0x3a/0xa5
Code: c1 e8 0c 83 e0 0f 89 da c1 ea 03 8d 48 f8 d3 e2 83 fa 10 73 05 ba 10 00 00 00 89 d3 0f af 1e 01 db 8b 17 4a 8d 0c 13 89 c8 31 d2 <f7> f3 89 c6 89 d8 0f af c6 89 07 f7 07 ff 3f 00 00 74 0c 05 ff
EIP: [<f94f646e>] _nv006247rm+0x296/0x2c4 [nvidia] SS:ESP 0068:f7db5c58
 <6>SysRq : SAK
SysRq : SAK
SysRq : SAK
SysRq : SAK
SysRq : SAK
SysRq : SAK
SysRq : SAK
SysRq : SAK
SysRq : SAK
mlfarrell 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 04:01 AM.


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