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

Newegg Daily Deals

Closed Thread
 
Thread Tools
Old 08-17-05, 10:52 AM   #277
taz007
Registered User
 
Join Date: Mar 2005
Posts: 6
Default Re: Trying to make headway into finding the Xid crashes source...

it "seems" it's gone for me (played +2hours ut2004 and not a single Xid error appeared)
what i did : the ram timing were set to 2.5-3-3-6
i changed that to 2.5-3-3-8 (in the bios of course lol)
and voila

but i still have a similar box with this 2.5-3-3-6 timing which has never seen any xid in his life

but, it does NOT mean it's a hardware problem, i still think it's a nvidia driver bug which is triggered only in some case, related to timing or something i dont know

i hope this trick will help some people with their XID errors until nvidia fix the issue (dream is still allowed ...)
taz007 is offline  
Old 08-17-05, 12:31 PM   #278
taz007
Registered User
 
Join Date: Mar 2005
Posts: 6
Default Re: Trying to make headway into finding the Xid crashes source...

nop, it's not gone, just got a crash now
taz007 is offline  
Old 08-17-05, 07:05 PM   #279
chunkey
#!/?*
 
Join Date: Oct 2004
Posts: 662
Default Re: Trying to make headway into finding the Xid crashes source...

Quote:
Originally Posted by taz007
nop, it's not gone, just got a crash now
Yes, after many diffrent experiments... I got finally some sort of haveworking setup... using 1.0-7174 together with "evdev"... it still XID alot, but it didn't get any hardfreezes anymore... just, a "moving mouse, but no keyboard" for some five seconds...



OT: what's wrong here:
Code:
 
$ nvidia-settings -q BusType

  Attribute 'BusType' (debian64:0.0): 2.
    The valid values for 'BusType' are in the range 0 - 1 (inclusive).
    'BusType' is a read-only attribute.

Last edited by chunkey; 08-18-05 at 06:19 AM.
chunkey is offline  
Old 08-20-05, 03:36 AM   #280
nukem
Registered User
 
Join Date: Dec 2004
Posts: 226
Default Re: Trying to make headway into finding the Xid crashes source...

Well I just made the switch to PCI-X and the problem is gone for me. When I first ran Doom III I did run into a problem were the system would freeze but it was not the XiD error and it told me to add irqpoll to my boot options and it fixed it. I remember awhile back that someone said this might have something to do with irq so I would try that.

nuke
nukem is offline  
Old 08-21-05, 02:04 PM   #281
BrianzaMan
Dragon Flame
 
Join Date: Nov 2002
Posts: 51
Default Re: Trying to make headway into finding the Xid crashes source...

I had this problem too on my Geforce 3 system, I tried to disable RenderAccel and now the problem seems gone. My system is up from 2 days and keeps going

Anyway, I'm not sure that the problem is completely gone, I'll make you know if it will happen again. (I've lost an eBay bid because of this problem. System freeze at 2 minutes to the end of the bid ... too bad)
BrianzaMan is offline  
Old 08-25-05, 03:30 PM   #282
JaXXoN
Registered User
 
Join Date: Jul 2005
Location: Munich
Posts: 910
Default Re: Trying to make headway into finding the Xid crashes source...

Hi everybody!

I checked "Cone3-nvcrash-x86" with an Athlon64/nforce3/Geforce6800GT
setup and it freezes the X-server with "beef"-messages. However, the system
is not fully dead, because with some patience, you can still type commands
when being ssh-logged in or on the serial console. Since the system is not very
responsive (it can take several seconds until a letter shows up when pressing a
key) and re-niceing X, window manager and Cone3-nvcrash-x86 didn't
improoved situation, i assumed the problem to be somewhere int the nvidia
kernel driver module.

So I added some debug output in the nvidia kernel driver module and finally
figured out that the system hangs in rm_ioctl() or in rm_isr_bh().

I guess somewhere in these functions, the system is polling some hardware
registers and the desired state doesn't show up within a reasonable time frame.
BTW.: Interesstingly, a XID messages always shows up after an ioctl command
0x41. Also, ioctls only hang with an 0x41 or 0x42 command.

When using fvwm95, then there is a fair chance that system recovers
within a minute (NV crash windows closing). With twm, the system
rarely revocers and without window manager, the system recovers
within a second, most of the time. So it seems that the window manager
also has an influence.

Please find attached the patch for the nvidia kernel driver and
the obligatory nvidia-bug-report.

Here's a sample output i get after clicking "NV Crash":

Code:
rm_ioctl: cmd=0x42, arg=0xbf98558c, size=0xc elapsed=0 ms
rm_ioctl: cmd=0x41, arg=0xbf985614, size=0x38 elapsed=0 ms                      
rm_ioctl: cmd=0x4a, arg=0xbfe04068, size=0x60 elapsed=0 ms                      
rm_ioctl: cmd=0x42, arg=0xbfe03f60, size=0xc elapsed=0 ms                       
rm_ioctl: cmd=0x41, arg=0xbfe03e94, size=0x38 elapsed=9 ms                      
rm_ioctl: cmd=0x4a, arg=0xbfe04068, size=0x60 elapsed=0 ms                      
rm_ioctl: cmd=0x42, arg=0xbfe03f60, size=0xc elapsed=0 ms                       
rm_ioctl: cmd=0x41, arg=0xbfe03e94, size=0x38 elapsed=0 ms                      
NVRM: Xid: 25,  L1 -> L0                                                        
NVRM: Xid: 6, PE0002 0184 beef0201 00110568 00000000 01a10113                   
NVRM: Xid: 25,  L0 -> L0                                                        
NVRM: Xid: 6, PE0002 0184 beef0201 00000000 00000000 00000000                   
isr_bh: elapsed=327 ms                                                          
rm_ioctl: cmd=0x37, arg=0xbf9852dc, size=0x20 elapsed=0 ms                      
NVRM: Xid: 6, PE0002 0184 beef0201 00000000 00000000 00000000                   
isr_bh: elapsed=134 ms                                                          
rm_ioctl: cmd=0x41, arg=0xbfe046ec, size=0x38 elapsed=0 ms                      
rm_ioctl: cmd=0x41, arg=0xbfe046bc, size=0x38 elapsed=0 ms                      
rm_ioctl: cmd=0x42, arg=0xbfe045c8, size=0xc elapsed=0 ms                       
rm_ioctl: cmd=0x42, arg=0xbfe04548, size=0xc elapsed=0 ms                       
rm_ioctl: cmd=0x41, arg=0xbfe0447c, size=0x38 elapsed=0 ms                      
rm_ioctl: cmd=0x42, arg=0xbfe04548, size=0xc elapsed=0 ms                       
rm_ioctl: cmd=0x41, arg=0xbfe0447c, size=0x38 elapsed=0 ms                      
rm_ioctl: cmd=0x41, arg=0xbfe046ec, size=0x38 elapsed=0 ms                      
NVRM: Xid: 6, PE0002 0be4 00080008 00000030 00000000 00000001                   
isr_bh: elapsed=134 ms                                                          
NVRM: Xid: 6, PE0002 0be4 00080008 00000000 00000000 00000000                   
isr_bh: elapsed=134 ms                                                          
rm_ioctl: cmd=0x41, arg=0xbfe0460c, size=0x38 elapsed=0 ms                      
rm_ioctl: cmd=0x41, arg=0xbfe0456c, size=0x38 elapsed=0 ms                      
rm_ioctl: cmd=0x42, arg=0xbfe04518, size=0xc elapsed=0 ms                       
rm_ioctl: cmd=0x42, arg=0xbfe04438, size=0xc elapsed=0 ms                       
[...]            
rm_ioctl: cmd=0x41, arg=0xbfe03e94, size=0x38 elapsed=9 ms                      
rm_ioctl: cmd=0x4a, arg=0xbfe04068, size=0x60 elapsed=0 ms                      
rm_ioctl: cmd=0x42, arg=0xbfe03f60, size=0xc elapsed=0 ms                       
rm_ioctl: cmd=0x41, arg=0xbfe03e94, size=0x38 elapsed=0 ms                      
NVRM: Xid: 25,  L1 -> L0                                                        
NVRM: Xid: 6, PE0002 0314 ffffffff 01c04000 00fd024b 00000001                   
isr_bh: elapsed=190 ms                                                          
rm_ioctl: cmd=0x37, arg=0xbf9852dc, size=0x20 elapsed=0 ms                      
rm_ioctl: cmd=0x41, arg=0xbfe046ec, size=0x38 elapsed=0 ms                      
rm_ioctl: cmd=0x41, arg=0xbfe046bc, size=0x38 elapsed=0 ms                      
rm_ioctl: cmd=0x42, arg=0xbfe045c8, size=0xc elapsed=0 ms                       
rm_ioctl: cmd=0x42, arg=0xbfe04548, size=0xc elapsed=0 ms                       
rm_ioctl: cmd=0x41, arg=0xbfe0447c, size=0x38 elapsed=8992 ms                   
rm_ioctl: cmd=0x42, arg=0xbfe04548, size=0xc elapsed=2574 ms                    
rm_ioctl: cmd=0x41, arg=0xbfe0447c, size=0x38 elapsed=8992 ms                   
rm_ioctl: cmd=0x41, arg=0xbfe046ec, size=0x38 elapsed=0 ms                      
rm_ioctl: cmd=0x41, arg=0xbfe0460c, size=0x38 elapsed=0 ms                      
NVRM: Xid: 25,  L0 -> L0                                                        
NVRM: Xid: 8, Channel 00000001                                                  
rm_ioctl: cmd=0x41, arg=0xbfe0456c, size=0x38 elapsed=0 ms                      
rm_ioctl: cmd=0x42, arg=0xbfe04518, size=0xc elapsed=2579 ms                    
rm_ioctl: cmd=0x42, arg=0xbfe04438, size=0xc elapsed=2573 ms                    
rm_ioctl: cmd=0x4a, arg=0xbfe044a0, size=0x60 elapsed=0 ms                      
rm_ioctl: cmd=0x42, arg=0xbfe04438, size=0xc elapsed=2572 ms                    
rm_ioctl: cmd=0x4a, arg=0xbfe044a0, size=0x60 elapsed=0 ms                      
rm_ioctl: cmd=0x41, arg=0xbfe046ec, size=0x38 elapsed=0 ms                      
rm_ioctl: cmd=0x41, arg=0xbf9854b4, size=0x38 elapsed=0 ms                      
rm_ioctl: cmd=0x38, arg=0xbf9853dc, size=0x20 elapsed=0 ms                      
rm_ioctl: cmd=0x41, arg=0xbf98537c, size=0x38 elapsed=0 ms                      
rm_ioctl: cmd=0x4a, arg=0xbf985394, size=0x60 elapsed=0 ms                      
rm_ioctl: cmd=0x29, arg=0xbf9853f4, size=0x10 elapsed=0 ms                      
rm_ioctl: cmd=0x42, arg=0xbf9853fc, size=0xc elapsed=2575 ms
In order to further track down the problem, access to the source
code would be required ... (please don't start a discussion in this
statement).

regards

Bernhard
Attached Files
File Type: zip patch-nv-rdtsc.zip (779 Bytes, 247 views)
File Type: zip nvidia-bug-report.log.zip (26.1 KB, 233 views)
JaXXoN is offline  
Old 08-25-05, 05:23 PM   #283
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...

hello.. while configuring a new kernel I saw the option: Device Drivers -> Graphics support -> Enable Video Mode Handling Helpers
the description says: This enables functions for handling video modes using the Generalized Timing Formula and the EDID parser.
It says that it is used only by the fb drivers... but I'm wondering if it's causing interrupt problems with the nvidia's binary driver... I'd try to disable it now... but the freezes are so random that I don't know when they'll show up...

PS: I forgot to enable that option to a friend and he has no Xids at all... but it's a totally different platform than mine... (his: amd64, nforce4, gf6800 and mine: athlonXP, nforce2, fx5900)
kmare is offline  
Old 12-17-05, 06:54 PM   #284
zigovr
Registered User
 
Join Date: Jan 2005
Posts: 2
Default Re: Trying to make headway into finding the Xid crashes source...

As far as I understand, this xid problem can have various causes, so it is possible that people on this forum have it for different reasons.

Anyway here is my case : I was happily running a 2.6.9 kernel under gentoo with the nvidia driver 6629, processor is amd ahtlon 64 and the motherboard has an nforce 250 chipset. All was working perfectly. In fact I've even upgraded to the latest nvidia driver and their own agp driver so that fastwrite , renderaccel are turned on. Still works perfectly.

But now I wanted to upgrade to a 2.6.12 kernel. And that's when xid problems started to arise. No matter what I try , how I configure the kernel and the nvidia driver (agpgart, no agp at all, etc ...) it itsn't stable. With some configurations it may work a bit better, but eventually it will freeze. Before that I also tried 2.6.14, and I got about the same problems, although I didn't test as many configuration combinations with it.

So to sum up, my own problem (not necessarily the same as others on this forum) seem to be related with the kernel version. It doesn't mean the bug is in the kernel, but at least my fix for now is to use kernel 2.6.9.

When I'll have the courage , I'll try also 2.6.10 and 2.6.11 to see what is the actual threshold.
zigovr is offline  

Old 12-17-05, 06:59 PM   #285
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...

why don't you try with a newer kernel like 2.6.14? it has many fixes for your amd64. Also did you try the recently released driver 8174?
kmare is offline  
Old 12-17-05, 07:10 PM   #286
zigovr
Registered User
 
Join Date: Jan 2005
Posts: 2
Default Re: Trying to make headway into finding the Xid crashes source...

Quote:
Originally Posted by kmare
why don't you try with a newer kernel like 2.6.14? it has many fixes for your amd64. Also did you try the recently released driver 8174?
As I explained I have tried both 2.6.14 and 2.6.12.
zigovr is offline  
Old 12-31-05, 08:13 AM   #287
PeaceFaker
Registered User
 
Join Date: May 2004
Location: Vaasa, Finland
Posts: 15
Send a message via MSN to PeaceFaker
Default Re: Trying to make headway into finding the Xid crashes source...

This problem is starting to get to me a bit.
I have the exact same thing, this one from ingame Doom3 first I only had it in UT2004 menu but now today Doom3 decided to do it too after enabling "com_showFPS 1"
Code:
BUG: soft lockup detected on CPU#0!

Pid: 10978, comm:                    X
EIP: 0060:[<f0e24d2d>] CPU: 0
EIP is at _nv002304rm+0x61/0x6c [nvidia]
 EFLAGS: 00003246    Tainted: P       (2.6.14-ck6)
EAX: 00000100 EBX: e8738800 ECX: 00000001 EDX: f1600000
ESI: 00000000 EDI: 00000000 EBP: e63f37c8 DS: 007b ES: 007b
CR0: 8005003b CR2: 0816b010 CR3: 3c719000 CR4: 000006d0
 [<f0f69f59>] _nv004943rm+0xa9/0xe8 [nvidia]
 [<f0fcc1fe>] _nv003548rm+0x1a/0x7c [nvidia]
 [<f0f5fcd2>] _nv006468rm+0xfa/0x1bc [nvidia]
 [<f0f6a65d>] _nv005103rm+0x19/0x40 [nvidia]
 [<f0f6008f>] _nv005717rm+0xfb/0x1b4 [nvidia]
 [<f0e147d6>] _nv002423rm+0x26/0x2c [nvidia]
 [<f0e466be>] _nv008109rm+0x1b6/0x518 [nvidia]
 [<f0e476f5>] _nv008252rm+0x411/0x41c [nvidia]
 [<f0e147cd>] _nv002423rm+0x1d/0x2c [nvidia]
 [<f0e147d6>] _nv002423rm+0x26/0x2c [nvidia]
 [<f0e147cd>] _nv002423rm+0x1d/0x2c [nvidia]
 [<f0e147d6>] _nv002423rm+0x26/0x2c [nvidia]
 [<f10079b3>] _nv001408rm+0x17/0x20 [nvidia]
 [<f0e3946b>] _nv008121rm+0x397/0x458 [nvidia]
 [<f0e39455>] _nv008121rm+0x381/0x458 [nvidia]
 [<f0ff4afe>] _nv002106rm+0x786/0xa4c [nvidia]
 [<f0e147cd>] _nv002423rm+0x1d/0x2c [nvidia]
 [<f0e14650>] _nv002428rm+0x38/0x50 [nvidia]
 [<f0ff3ee1>] _nv002074rm+0x5d/0x68 [nvidia]
 [<f0ff219c>] _nv002141rm+0x3c/0x6c [nvidia]
 [<f0ff51c5>] _nv002073rm+0x59/0x45c [nvidia]
 [<f0ff53ba>] _nv002073rm+0x24e/0x45c [nvidia]
 [<f0e1471f>] _nv002437rm+0x53/0x84 [nvidia]
 [<f10044db>] _nv001857rm+0x5b/0x194 [nvidia]
 [<f10044f5>] _nv001857rm+0x75/0x194 [nvidia]
 [<f0e2345b>] _nv002269rm+0x17/0x1c [nvidia]
 [<f0fc43ec>] _nv003554rm+0xe0/0x118 [nvidia]
 [<f1004ac1>] _nv001858rm+0x4ad/0x504 [nvidia]
 [<f1004b0b>] _nv001858rm+0x4f7/0x504 [nvidia]
 [<f0e14603>] _nv002429rm+0x6f/0x84 [nvidia]
 [<f100643f>] _nv001849rm+0x2b/0x12c [nvidia]
 [<f1004415>] _nv001856rm+0x1d5/0x240 [nvidia]
 [<f1004425>] _nv001856rm+0x1e5/0x240 [nvidia]
 [<f0faa6c1>] _nv004608rm+0xd99/0x118c [nvidia]
 [<f0e2b61f>] rm_isr_bh+0x47/0x74 [nvidia]
 [<f0e2b63a>] rm_isr_bh+0x62/0x74 [nvidia]
 [<f0e147cd>] _nv002423rm+0x1d/0x2c [nvidia]
 [<f0e147d6>] _nv002423rm+0x26/0x2c [nvidia]
 [<f104c9cc>] nv_kern_isr_bh+0x20/0x25 [nvidia]
 [<f0f6a70b>] _nv005100rm+0x23/0x28 [nvidia]
 [<f0e147d6>] _nv002423rm+0x26/0x2c [nvidia]
 [<f0f6a65d>] _nv005103rm+0x19/0x40 [nvidia]
 [<f0f6a70b>] _nv005100rm+0x23/0x28 [nvidia]
 [<f0e147d6>] _nv002423rm+0x26/0x2c [nvidia]
 [<f0e24ce6>] _nv002304rm+0x1a/0x6c [nvidia]
 [<f0e147d6>] _nv002423rm+0x26/0x2c [nvidia]
 [<f0fcb979>] _nv003506rm+0x1a9/0x4e8 [nvidia]
 [<f0fcb969>] _nv003506rm+0x199/0x4e8 [nvidia]
 [<f0f69e1e>] _nv004947rm+0x6a/0x7c [nvidia]
 [<f0f06540>] _nv000436rm+0x20/0xa0 [nvidia]
 [<f0fc25d0>] _nv003514rm+0x90/0xd4 [nvidia]
 [<f0e13cfc>] _nv002448rm+0x58/0x100 [nvidia]
 [<f0f6a70b>] _nv005100rm+0x23/0x28 [nvidia]
 [<f0e271a7>] _nv001646rm+0x87/0xa8 [nvidia]
 [<f0e2b61f>] rm_isr_bh+0x47/0x74 [nvidia]
 [<f0e2b63a>] rm_isr_bh+0x62/0x74 [nvidia]
 [<f104c9cc>] nv_kern_isr_bh+0x20/0x25 [nvidia]
 [<b011d990>] tasklet_action+0x40/0x70
 [<b011d6e3>] __do_softirq+0x43/0x90
 [<b011d756>] do_softirq+0x26/0x30
 [<b0104ece>] do_IRQ+0x1e/0x30
 [<b0103786>] common_interrupt+0x1a/0x20
NVRM: Xid: 27,  L0 -> L0
NVRM: Xid: 13, 0000 03005f00 0000009f 00000308 00040001 00004000
NVRM: Xid: 13, 0000 03005f00 0000009f 00000308 00040001 00004000
NVRM: Xid: 13, 0000 03005f00 0000009f 00000308 00040001 00004000
NVRM: Xid: 13, 0000 03005f00 0000009f 00000308 00040001 00004000
NVRM: Xid: 13, 0000 03005f00 0000009f 00000308 00040001 00004000
NVRM: Xid: 13, 0000 03005f00 0000009f 00000308 00040001 00004000
NVRM: Xid: 13, 0000 03005f00 0000009f 00000308 00040001 00004000
NVRM: Xid: 13, 0000 03005f00 0000009f 00000308 00040001 00004000
NVRM: Xid: 13, 0000 03005f00 0000009f 00000308 00040001 00004000
NVRM: Xid: 13, 0000 03005f00 0000009f 00000308 00040001 00004000
NVRM: Xid: 13, 0000 03005f00 0000009f 00000308 00040001 00004000
NVRM: Xid: 13, 0000 03005f00 0000009f 00000308 00040001 00004000
and
Code:
(WW) NVIDIA(0): WAIT (0, 6, 0x8000, 0x00005e10, 0x00005e10, 0)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00005e10, 0x0000613c, 0)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00005e10, 0x0000613c, 0)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00005e10, 0x00006c94, 0)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00005e10, 0x00006c94, 0)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00005e10, 0x00007a14, 0)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00005e10, 0x00007a14, 0)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00005e10, 0x000099c4, 0)
(WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00005e10, 0x000099c4, 0)
(WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00005e10, 0x0000a3fc, 0)
Funny thing is that I don't have this with my older ASUS FX5900XT, nor did notice anything with my first 6600GT (which decided to die and was replaced under warranty), unfortunately while my 6600GT was being replaced I changed X version, nvidia driver version and kernel atleast twice. But my Fx5900XT doesn't do these things, also noteworthy is that my FX5900XT has a thermal diode or rather two (gpu and ambient) courtesy of ASUS. neither cards diode ever goes over 65C
__________________
Athlon64 X2 5600+ / ASUS M2N-SLI deluxe / 4x1GB DDR2-667 / Gainward GeForce 7900GS 512MB / 3x320GB RAID-5 / NEC DL-DVD+-RW / Gentoo Linux
HP tx2020eo / Turion X2 TL-60 / nVidia 6150 / Debian Linux
PeaceFaker is offline  
Old 01-01-06, 06:50 AM   #288
Darkvater
Registered User
 
Join Date: Feb 2005
Posts: 57
Default Re: Trying to make headway into finding the Xid crashes source...

Great, and another Xid crash, this time with 8178

Quote:
NVRM: Xid: 6, PE0000 0a84 ff286fa8 0000df4c 00000000 ff286fa8
I don't think I am going to accept this any longer (cost me another dvdr coaster) and am probably moving back to windows .
Darkvater 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 04:27 AM

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


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