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

Newegg Daily Deals

Reply
 
Thread Tools
Old 11-23-11, 12:19 AM   #13
cheechr1
Registered User
 
cheechr1's Avatar
 
Join Date: Nov 2010
Posts: 94
Default Re: [BUG] nvidia crashes kernel with 'Xid 13' and attempted to yield the CPU while at

Hasn't changed with 290.10. Froze in minutes in wine.

Nov 22 22:02:54 zod kernel: [ 531.977368] NVRM: Xid (0000:04:00): 13, 0008 00000000 00009097 0000037c 00000021 0000000c
Nov 22 22:02:54 zod kernel: [ 531.985052] NVRM: Xid (0000:03:00): 13, 0008 00000000 00009097 0000037c 00000021 0000000c
Nov 22 22:03:00 zod kernel: [ 538.288719] NVRM: Xid (0000:03:00): 32, Channel ID 00000008 intr 00040000
Nov 22 22:03:01 zod kernel: [ 539.684711] NVRM: Xid (0000:04:00): 13, 0008 00000000 00009097 00001514 00000020 0000000c
Nov 22 22:03:04 zod kernel: [ 542.579782] NVRM: Xid (0000:03:00): 12, COCOD 00000008 beef9097 00009097 000016c4 00000000
Nov 22 22:03:04 zod kernel: [ 542.587445] NVRM: Xid (0000:04:00): 12, COCOD 00000008 beef9097 00009097 000016c4 00000000
Nov 22 22:03:10 zod kernel: [ 548.201495] NVRM: Xid (0000:04:00): 13, 0008 00000000 00009097 000012ec 00000021 0000000c
Nov 22 22:03:15 zod kernel: [ 552.856442] NVRM: Xid (0000:03:00): 13, 0008 00000000 00009097 00001688 00000020 0000000c

Got this one in the few minutes it takes to purge xorg-edgers, fix nvidia module problems with the downgrade, (http://ubuntuforums.org/showthread.php?t=1861526), and re-install 275.09.07.

Nov 22 22:13:47 zod kernel: [ 402.043064] NVRM: Xid (0000:04:00): 13, 0004 00000000 00009097 00002144 00001220 00000004

Please look into this Nvidia, I haven't been able to update my driver in a long time. I have a friend who is also having this issue I believe. If this is the case I will post his log this weekend.
cheechr1 is offline   Reply With Quote
Old 11-23-11, 03:14 AM   #14
vojta
Registered User
 
Join Date: Nov 2011
Posts: 19
Default Re: [BUG] nvidia crashes kernel with 'Xid 13' and attempted to yield the CPU while at

I have this problem, too. I can reporoduce it when running KDE 4.7 with enabled composition. I also tried to set __GL_YIELD=NOTHING, but nothing helps.

Here is snippet from messages log:
Code:
[   63.413967] NVRM: Xid (0000:01:00): 8, Channel 00000001
[   65.410431] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[ 1783.334827] NVRM: Xid (0000:01:00): 8, Channel 00000001
[ 2030.734933] NVRM: Xid (0000:01:00): 8, Channel 00000004
[ 2032.731434] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[ 2282.124759] NVRM: Xid (0000:01:00): 8, Channel 00000001
nvidia-bug-report attached.

EDIT: Xorg.log (with -logverbose 10) attached.
Attached Files
File Type: gz nvidia-bug-report.log.gz (81.0 KB, 79 views)
File Type: gz Xorg.0.log.gz (21.2 KB, 73 views)
vojta is offline   Reply With Quote
Old 11-25-11, 08:24 PM   #15
vojta
Registered User
 
Join Date: Nov 2011
Posts: 19
Default Re: [BUG] nvidia crashes kernel with 'Xid 13' and attempted to yield the CPU while at

I've compiled KDE 4.8 Beta 1 today. Problem still persists.
vojta is offline   Reply With Quote
Old 12-15-11, 12:11 AM   #16
cheechr1
Registered User
 
cheechr1's Avatar
 
Join Date: Nov 2010
Posts: 94
Default Re: [BUG] nvidia crashes kernel with 'Xid 13' and attempted to yield the CPU while at

Bump. With World Of Tanks 7.0 the Xid lockups seem to be getting worse. They did update the graphics a bit from 6.7. Please can a dev look into these Xid error issues? Could one of the 3 Xid topics in the last 3 pages of the forums get some sort of response to acknowledge this issue?

Here's a colorful log:

Dec 12 21:19:47 zod kernel: [ 142.116510] NVRM: Xid (0000:03:00): 13, 0004 00000000 00009039 00000300 00100111 00000053
Dec 12 21:19:47 zod kernel: [ 142.124022] NVRM: Xid (0000:03:00): 13, 0004 00000000 00009039 00000304 00000000 00000000
Dec 12 21:19:47 zod kernel: [ 142.131424] NVRM: Xid (0000:04:00): 13, 0004 00000000 00009039 00000300 00100111 00000053
Dec 12 21:19:47 zod kernel: [ 142.138832] NVRM: Xid (0000:04:00): 13, 0004 00000000 00009039 00000304 00000000 00000000
Dec 12 21:19:47 zod kernel: [ 142.146511] NVRM: Xid (0000:03:00): 13, 0004 00000000 00009039 00000304 4101c400 00000000
Dec 12 21:19:48 zod kernel: [ 142.153897] NVRM: Xid (0000:04:00): 13, 0004 00000000 00009039 00000304 4101c400 00000000
Dec 12 22:03:28 zod kernel: [ 2758.412832] NVRM: Xid (0000:03:00): 37, 0004 00009039 00000000 00000000 000002bc 3fa60140
Dec 12 22:03:28 zod kernel: [ 2758.420490] NVRM: Xid (0000:03:00): 37, 0004 00009039 00000000 00000000 000002bc 3fa60140
Dec 12 22:03:28 zod kernel: [ 2760.412672] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Dec 12 22:03:28 zod kernel: [ 2762.412601] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Dec 12 22:03:30 zod kernel: [ 2764.412499] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Dec 12 22:03:32 zod kernel: [ 2766.412395] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Dec 12 22:03:34 zod kernel: [ 2768.412293] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Dec 12 22:03:36 zod kernel: [ 2770.412194] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Dec 12 22:03:38 zod kernel: [ 2772.412091] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context

Everyday my computer freezes once or multiple times and it is always due to errors like these.

Edit: Not even 30 seconds after writing this post while reviewing it I froze again for the third time tonight. This was the first time that Firefox was the only window open with this being the only tab.

Dec 14 23:12:41 zod kernel: [ 899.821529] NVRM: Xid (0000:02:00): 31, Ch 00000007, engmask 00000101, intr 10000000
Dec 14 23:13:08 zod kernel: [ 926.554887] NVRM: Xid (0000:02:00): 32, Channel ID 00000007 intr 00800000

Then this one while editing this post right now with no hard freeze yet:

Dec 14 23:17:05 zod kernel: [ 196.893660] NVRM: Xid (0000:04:00): 12, COCOD 00000003 5c000150 000090c0 00002304 00000001

Same situation, 1 window 1 tab open with Boinc doing CUDA apps in the background.

Last edited by cheechr1; 12-15-11 at 12:20 AM. Reason: More, more and more errors
cheechr1 is offline   Reply With Quote
Old 04-01-12, 07:43 AM   #17
rockob
Registered User
 
Join Date: Nov 2008
Posts: 95
Default Re: [BUG] nvidia crashes kernel with 'Xid 13' and attempted to yield the CPU while at

295.20 was rather woeful - I could reliably crash it every time at the same point in Crysis2 - but 295.33 is a bit better in that it doesn't crash at that exact point in Crysis2.

But it still does crash with the Xid 13 error. The latest one I got was:

Code:
NVRM: Xid (0000:01:00): 13, 0006 00000000 00009197 00001614 00000000 00000000
along with some weird call traces looking like the iwlwifi and nvidia drivers have somehow become merged:

Code:
Apr  1 18:06:03 sierra kernel: [ 7075.413974] WARNING: at drivers/net/wireless/iwlwifi/iwl-trans-pcie-tx.c:858 iwl_tx_cmd_complete+0x30e/0x350 [iwlwifi]()
Apr  1 18:06:03 sierra kernel: [ 7075.413979] Hardware name: Dell System XPS L502X
Apr  1 18:06:03 sierra kernel: [ 7075.413985] wrong command queue 0 (should be 4), sequence 0x0 readp=0 writep=0
...
Apr  1 18:06:03 sierra kernel: [ 7075.414133] Pid: 20341, comm: Crysis2.exe Tainted: P        W  O 3.3.0-generic #1
Apr  1 18:06:03 sierra kernel: [ 7075.414137] Call Trace:
Apr  1 18:06:03 sierra kernel: [ 7075.414140]  <IRQ>  [<ffffffff8104b1df>] warn_slowpath_common+0x7f/0xc0
Apr  1 18:06:03 sierra kernel: [ 7075.414152]  [<ffffffff8104b2d6>] warn_slowpath_fmt+0x46/0x50
Apr  1 18:06:03 sierra kernel: [ 7075.414164]  [<ffffffffa03a0d6e>] iwl_tx_cmd_complete+0x30e/0x350 [iwlwifi]
Apr  1 18:06:03 sierra kernel: [ 7075.414175]  [<ffffffffa039eb78>] iwl_irq_tasklet+0x348/0x880 [iwlwifi]
Apr  1 18:06:03 sierra kernel: [ 7075.414181]  [<ffffffff810521a8>] tasklet_action+0x78/0x140
Apr  1 18:06:03 sierra kernel: [ 7075.414186]  [<ffffffff810527e8>] __do_softirq+0xa8/0x210
Apr  1 18:06:03 sierra kernel: [ 7075.414192]  [<ffffffff81606eee>] ? _raw_spin_lock+0xe/0x20
Apr  1 18:06:03 sierra kernel: [ 7075.414198]  [<ffffffff8161065c>] call_softirq+0x1c/0x30
Apr  1 18:06:03 sierra kernel: [ 7075.414203]  [<ffffffff810152d5>] do_softirq+0x65/0xa0
Apr  1 18:06:03 sierra kernel: [ 7075.414208]  [<ffffffff81052bce>] irq_exit+0x8e/0xb0
Apr  1 18:06:03 sierra kernel: [ 7075.414214]  [<ffffffff81610ec3>] do_IRQ+0x63/0xe0
Apr  1 18:06:03 sierra kernel: [ 7075.414220]  [<ffffffff816073ae>] common_interrupt+0x6e/0x6e
Apr  1 18:06:03 sierra kernel: [ 7075.414223]  <EOI>  [<ffffffffa184be6a>] ? os_release_spinlock+0x1a/0x20 [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.414379]  [<ffffffffa1816c6d>] ? _nv014474rm+0xb3/0xc1 [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.414513]  [<ffffffffa158db9b>] ? _nv003996rm+0x69ee/0xd0b8 [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.414593]  [<ffffffffa173bab3>] ? _nv015615rm+0x3c/0x188 [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.414671]  [<ffffffffa1740c97>] ? _nv015507rm+0x4d3/0x30ec [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.414764]  [<ffffffffa168e2f6>] ? _nv012985rm+0x171/0x1e5b [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.414890]  [<ffffffffa1543df4>] ? _nv008664rm+0x3c/0x77 [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.415013]  [<ffffffffa1543cbf>] ? _nv007902rm+0xaf/0xda [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.415135]  [<ffffffffa1539e5c>] ? _nv007991rm+0x48b/0x638 [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.415256]  [<ffffffffa153a1dd>] ? _nv008532rm+0x1d4/0x1e8 [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.415377]  [<ffffffffa1544c7b>] ? _nv008612rm+0x60/0x7e [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.415426]  [<ffffffffa115e7e1>] ? _nv001067rm+0x2456/0x4040 [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.415475]  [<ffffffffa115c2d4>] ? _nv001033rm+0x1203/0x1239 [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.415524]  [<ffffffffa115c473>] ? _nv001067rm+0xe8/0x4040 [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.415573]  [<ffffffffa1153b57>] ? _nv000941rm+0x26/0x147 [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.415634]  [<ffffffffa1811fd5>] ? _nv001099rm+0x325/0x731 [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.415694]  [<ffffffffa1820084>] ? rm_ioctl+0x6d/0x169 [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.415752]  [<ffffffffa184130b>] ? nv_kern_ioctl+0x15b/0x460 [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.415810]  [<ffffffffa1841631>] ? nv_kern_compat_ioctl+0x21/0x30 [nvidia]
Apr  1 18:06:03 sierra kernel: [ 7075.415815]  [<ffffffff811c1bc1>] ? compat_sys_ioctl+0xc1/0x1390
Apr  1 18:06:03 sierra kernel: [ 7075.415819]  [<ffffffff8113db8e>] ? remove_vma+0x6e/0x90
Apr  1 18:06:03 sierra kernel: [ 7075.415823]  [<ffffffff8113ee53>] ? do_munmap+0x1f3/0x3a0
Apr  1 18:06:03 sierra kernel: [ 7075.415827]  [<ffffffff81610896>] ? sysenter_dispatch+0x7/0x21
Apr  1 18:06:03 sierra kernel: [ 7075.415830] ---[ end trace eec1460760754c89 ]---
rockob is offline   Reply With Quote
Old 04-16-12, 09:10 AM   #18
sandipt
NVIDIA Corporation
 
sandipt's Avatar
 
Join Date: Dec 2010
Posts: 260
Default Re: [BUG] nvidia crashes kernel with 'Xid 13' and attempted to yield the CPU while at

NVIDIA internal Bug ID: 970252 to track this issue.
sandipt is offline   Reply With Quote
Old 04-16-12, 08:38 PM   #19
rockob
Registered User
 
Join Date: Nov 2008
Posts: 95
Default Re: [BUG] nvidia crashes kernel with 'Xid 13' and attempted to yield the CPU while at

Thanks, is there any more information I can provide? In case it helps, I looked at the os_schedule method and found that it fails because in_interrupt() returns false after the Xid error.
rockob is offline   Reply With Quote
Old 04-24-12, 01:03 AM   #20
Psicopatico
Registered User
 
Join Date: Apr 2012
Posts: 2
Default Re: [BUG] nvidia crashes kernel with 'Xid 13' and attempted to yield the CPU while at

Hi all,

I just wanted to share my experience with those hard lock-ups and inform that I've found a solution for my case, although limited in its application.

First of all, my relevant hardware:
- MoBo is an Asrock AM2NF3-VSTA with latest available BIOS update (P3.30)
- CPU is an AMD PhenomII X4 965 non overclocked (more than that, I usually keep underclocked in its max clocking from 3.4GHz down to 2.7GHz via cpufreq kernel module)
- GPU is an GeForce 7600GT AGP with bios version 05.73.22.51.95. Following is the relevant output of "lspci -v":
Quote:
01:00.0 VGA compatible controller: nVidia Corporation G73 [GeForce 7600 GT] (rev a2) (prog-if 00 [VGA controller])
Subsystem: XFX Pine Group Inc. Device 2247
Flags: bus master, 66MHz, medium devsel, latency 248, IRQ 19
Memory at fd000000 (32-bit, non-prefetchable) [size=16M]
Memory at e0000000 (32-bit, prefetchable) [size=256M]
Memory at fc000000 (32-bit, non-prefetchable) [size=16M]
[virtual] Expansion ROM at feae0000 [disabled] [size=128K]
Capabilities: [60] Power Management version 2
Capabilities: [44] AGP version 3.0
Kernel driver in use: nvidia
System in use is OpenSUSE 11.4 "Celadon":
Quote:
Linux linux 2.6.37.6-0.7-desktop #1 SMP PREEMPT 2011-07-21 02:17:24 +0200 i686 athlon i386 GNU/Linux
I've been plagued by NVRM Xid faults for so much time I've lost count.
Here's a very little sample of the offending ones obtained by grepping system logs:
Quote:
Apr 18 11:25:09 linux kernel: [1662639.915779] NVRM: Xid (0000:01:00): 6, PE0000 1718 00000000 00316ee0 ffffffff 00000000
Apr 18 11:25:37 linux kernel: [1662667.396163] NVRM: Xid (0000:01:00): 8, Channel 00000020
Apr 18 11:43:42 linux kernel: [ 937.566287] NVRM: Xid (0000:01:00): 6, PE0002 1f0c 4608239b 00110ce4 bf000000 be800000
Apr 18 11:43:42 linux kernel: [ 937.604027] NVRM: Xid (0000:01:00): 6, PE0000 1f28 3f0f0775 00000000 ffffffff 00000000
Apr 18 12:39:02 linux kernel: [ 853.312233] NVRM: Xid (0000:01:00): 7, Ch 0000001e M 00000000 D 00000000 intr 00011000
Apr 18 12:42:41 linux kernel: [ 106.738263] NVRM: Xid (0000:01:00): 13, 0000 e0014200 00000062 00000184 0000baf5 00000002
Apr 19 01:56:22 linux kernel: [ 2429.440420] NVRM: Xid (0000:01:00): 50, L0 -> L0
Apr 19 02:58:52 linux kernel: [ 8865.582396] NVRM: Xid (0001:00): 47, L0 -> L0
Apr 19 08:09:18 linux kernel: [ 5752.276583] NVRM: Xid (0001:00): 3, C 00000000 SC 00000006 M 00000318 Data 00000000
Don't mind the difference in how data is presented, I've switched drivers version during this.
As you can see, there's a wide range of cases, all mixed with repeated "NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context" messages.

I think I tried every and each trick I found with the help of the Mighty Google:
- switched back to each and every older driver version (betas included) back to the 260.19.04 release (older ones wouldn't build for my system);
- switched between kernel's AGPGart and Nvidia drivers' supplied one;
- lowered GPU and memory clocks to rule out temperature issues (but this card doesn't get hot: maximum I've seen is 78C under full load at max stock clocks);
- switched off ACPI PCI IRQ sharing at boot, as this is a multi-core system with HPET;
- switched off SideBand and FastWrite AGP options;
- others I can't even remember.

Always got a failure: graphic system hung repeatedly. Remote access via SSH was always possible to clean reboot the machine.
The interesting bit is this occurred always while running software via Wine (mostly games, most offending ones were the already cited World of Tanks and Need for Speed World, as well as others) but never with native applications (be them games, or Compiz and similar, or even GlxGears, etc.).

Well in the end, I tried mostly by chance to lower the AGP rate from 8X down to 4X via reloading kernel module with the NVreg_ReqAGPRate=4 option.
Result: it's almost a week my system is rock-solid. Not a single crash. Not one.
Yes, it took a noticeable performance hit, but I'd gladly take that against a stability issue any day.
Also, I understand this solution may not be applicable for everyone as today common system are PCI-X, but - hey! - it's a start.
Net result: now I'm on the latest suggested driver version (295.20) with module loaded and set up for AGP 4X and so far, so good.

I hope this may help and enlighten someone.

Regards
Psicopatico is offline   Reply With Quote

Old 05-23-12, 08:45 AM   #21
wxwok
Registered User
 
Join Date: May 2012
Posts: 2
Default Re: [BUG] nvidia crashes kernel with 'Xid 13' and attempted to yield the CPU while at

I disabled flash in web browser and logined into gnome-no-effect, the bug gone doesn't occur.
wxwok is offline   Reply With Quote
Old 05-25-12, 08:37 AM   #22
ssambantham
Registered User
 
Join Date: Jun 2011
Posts: 10
Default Re: [BUG] nvidia crashes kernel with 'Xid 13' and attempted to yield the CPU while at

Hi rockob,

you mentioned, (04-01-12 06:13 PM), with crysis 2 you could reliable crash at some point in the game.

Can you mention the game stage or the scenario where you experience this crash?

Can you mention a game or software(like glxgears), where this issue repro is very consistant?
ssambantham is offline   Reply With Quote
Old 06-20-12, 03:33 AM   #23
rockob
Registered User
 
Join Date: Nov 2008
Posts: 95
Default Re: [BUG] nvidia crashes kernel with 'Xid 13' and attempted to yield the CPU while at

Well, at the time I mentioned it, it crashed every single time in Gatekeepers (4/4). I was next to the church overlooking the road where you eventually descend to get to the next level, and when the armoured vehicle came along, I would zoom in with the sniper rifle on the guy at the mounted gun, and the nvidia driver would crash as soon as I clicked to fire the gun. But it stopped crashing consistently at that point with a later nvidia driver.

I can still crash the nvidia driver playing Crysis2 at pretty much *any* stage of the game, even with the latest 'stable' 302.17 driver, it's just a matter of how long I have to play until the nvidia GPU falls off the damned bus.

<sarcasm> nvidia say they are trying to give us a consistent experience across all platforms, so I assume the driver also crashes Windoze frequently? </sarcasm>.
rockob is offline   Reply With Quote
Old 06-20-12, 11:22 AM   #24
Lamieur
The god of fertility
 
Lamieur's Avatar
 
Join Date: Apr 2006
Posts: 24
Default Re: [BUG] nvidia crashes kernel with 'Xid 13' and attempted to yield the CPU while at

I haven't had a crash in months after disabling VDPAU everywhere I could (only occasional pink walls etc., see my gallery: http://imgur.com/a/yjxRl :)). Finally I got good chunk of Xid errors when trying to run RAGE in WINE (I guess it tries to use CUDA?) and like 2 weeks later the system crashed so hard alt-sysrq-b didn't work. "Attempted to yield the CPU while in atomic or interrupt context" in the log.

Sigh.

It's still better than the situation on older kernels though ;)
Lamieur is offline   Reply With Quote
Reply


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


All times are GMT -5. The time now is 11:53 AM.


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