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

Newegg Daily Deals

Reply
 
Thread Tools
Old 06-13-12, 03:41 PM   #49
muadib25
Registered User
 
Join Date: Apr 2012
Location: Sweden
Posts: 10
Default Re: Random crashes, NVRM Xid messages

I just compiled a new kernel 3.4.2 using one of Puppy's kernel seeds and compiled Nvidia driver 295.49.

In Flightgear I experienced only 2 freezes (ahem) after 10 minutes of flight!! That's an improvement!


Note 1: Havent tried with other kernels yet but I used 300Hz for the Timer Frequency, instead of 1000Hz. Puppy explains why here: http://kernel-seeds.org/working.html

Note 2: The NVidia driver could not be compiled at first on 3.4.2, due to some missing kernel headers. I did a little search and I found this workaround:
Code:
cd /usr/src/linux-headers-3.4.0-1/arch
sudo cp arm/include/asm/system.h x86/include/asm/
sudo cp arm/include/asm/compiler.h x86/include/asm/
sudo cp arm/include/asm/system_info.h x86/include/asm/
sudo cp arm/include/asm/system_misc.h x86/include/asm/
I will do some more flying and let you guys know a bit more about it.

Cheers!
__________________
Motherboard:Gigabyte EX58-UD5 F12,
CPU: i7 920@2.80 GHz Quad core,
Memory: 12Gb RAM,
GFXCard: Gigabyte GeForce GTX 260 896Mb
OS: Gentoo Linux x86_64
muadib25 is offline   Reply With Quote
Old 06-14-12, 12:53 PM   #50
cheechr1
Registered User
 
cheechr1's Avatar
 
Join Date: Nov 2010
Posts: 94
Default Re: Random crashes, NVRM Xid messages

Ive been playing Oil Rush with 3x GTX480 in SLI on 2.6.38 kernel. I have been getting much of the same, Xid's 6,8,31,56 and fallen off bus and atomic interrupt errors as well. Sometimes the computer will freeze after 10 minutes of playing. Once I was able to log out using Alt+PrntScn+K, but this only worked once only to freeze minutes after logging back in and starting Oil Rush again.
cheechr1 is offline   Reply With Quote
Old 06-16-12, 05:04 AM   #51
Iesos
Registered User
 
Join Date: Apr 2012
Posts: 15
Default Re: Random crashes, NVRM Xid messages

Quote:
Originally Posted by sandipt View Post
Tried this issue with 295.40 driver with wine installed and Starcraft II game.

Able to observe 1-3 secs lockup while playing the game. But could not observe permanent lockup with Xid messages.

Played the game for more than 2hours.

Wine version- 1.3.28

1. After how much hours of game play issue occur?
2. Any specific repro steps (game stage, game settings etc.,)
1. Anything from 20 minutes to 4 hours of gameplay.
2. Game settings can not be altered, when I change res, graphics settings, etc, the game fails to start and I have to reset the settings.
Some maps are more likely to trigger the bug. The map "Desert strike", I think its called, I would say the avarage time to failure is 40-60 minutes (one game takes ~20 minutes, usually crash in second or third game).

The same crash exists in diablo 3, although it occurs more seldom.
Iesos is offline   Reply With Quote
Old 06-17-12, 09:08 AM   #52
sandipt
NVIDIA Corporation
 
sandipt's Avatar
 
Join Date: Dec 2010
Posts: 260
Default Re: Random crashes, NVRM Xid messages

Does this issue reproduce with latest driver as well? we are able to reproduce similar types of error logs, might be fixing this issue will resolve issue reported here as well:

[ 409.636857] NVRM: Xid (0000:03:00): 13, 0006 00000000 00008397 000019d0 0000003c 00000100
[ 412.521049] NVRM: Xid (0000:03:00): 13, 0008 00000000 00008397 000019d0 0000003c 00000100
[ 671.574186] NVRM: Xid (0000:03:00): 13, 000a 00000000 00008397 000019d0 0000003c 00000100
[ 722.539237] NVRM: Xid (0000:03:00): 8, Channel 00000003
[ 724.535233] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[ 726.531372] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context

getting below backtrace during X crash

Backtrace:
0: X (xorg_backtrace+0x26) [0x462396]
1: X (mieqEnqueue+0x201) [0x45c911]
2: X (xf86PostMotionEventM+0xa3) [0x482203]
3: X (xf86PostMotionEventP+0x37) [0x4822f7]
4: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f6fb9196000+0x4b2e) [0x7f6fb919ab2e]
5: X (0x400000+0x6f7c7) [0x46f7c7]
6: X (0x400000+0x11ebfe) [0x51ebfe]
7: /lib64/libpthread.so.0 (0x7f6fbfbc0000+0xfd00) [0x7f6fbfbcfd00]
8: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f6fb9cfd000+0x8fbb0) [0x7f6fb9d8cbb0]
9: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f6fb9cfd000+0xfad46) [0x7f6fb9df7d46]
10: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f6fb9cfd000+0x48d472) [0x7f6fba18a472]
11: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f6fb9cfd000+0x48d63e) [0x7f6fba18a63e]
12: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f6fb9cfd000+0x48991a) [0x7f6fba18691a]
13: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f6fb9cfd000+0x442947) [0x7f6fba13f947]
14: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f6fb9cfd000+0x45380c) [0x7f6fba15080c]
15: X (0x400000+0x332a9) [0x4332a9]
16: X (0x400000+0x272ce) [0x4272ce]
17: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f6fbeb3723d]
18: X (0x400000+0x275bd) [0x4275bd]
sandipt is offline   Reply With Quote
Old 06-18-12, 01:52 PM   #53
KnutJorgen
Registered User
 
Join Date: Dec 2003
Posts: 38
Default Re: Random crashes, NVRM Xid messages

Hi I get this error message which is similar with the latest Nvidia driver. I have Dell Latitude E6520 with optimus disablied.
Backtrace:
[ 38589.944] 0: /usr/bin/Xorg (xorg_backtrace+0x26) [0x7f0d48b51866]
[ 38589.944] 1: /usr/bin/Xorg (0x7f0d489c9000+0x62934) [0x7f0d48a2b934]
[ 38589.944] 2: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f0d40de2000+0x5d88) [0x7f0d40de7d88]
[ 38589.944] 3: /usr/bin/Xorg (0x7f0d489c9000+0x8ae07) [0x7f0d48a53e07]
[ 38589.945] 4: /usr/bin/Xorg (0x7f0d489c9000+0xb0d4a) [0x7f0d48a79d4a]
[ 38589.945] 5: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f0d47cef000+0xfcb0) [0x7f0d47cfecb0]
[ 38589.945] 6: /lib/x86_64-linux-gnu/libc.so.6 (nanosleep+0x10) [0x7f0d46c21020]
[ 38589.945] 7: /lib/x86_64-linux-gnu/libc.so.6 (usleep+0x34) [0x7f0d46c4ef74]
[ 38589.945] 8: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f0d418ca000+0x48d0eb) [0x7f0d41d570eb]
[ 38589.945] 9: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f0d418ca000+0x48e486) [0x7f0d41d58486]
[ 38589.945] 10: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f0d418ca000+0x48e4e5) [0x7f0d41d584e5]
[ 38589.945] 11: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f0d418ca000+0x48ea4c) [0x7f0d41d58a4c]
[ 38589.945] 12: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/nvidia_drv.so (0x7f0d418ca000+0x4940fe) [0x7f0d41d5e0fe]
[ 38589.945] 13: /usr/lib/x86_64-linux-gnu/xorg/extra-modules/libglx.so (0x7f0d45049000+0x46e7bf) [0x7f0d454b77bf]
[ 38590.163] [mi] Increasing EQ size to 512 to prevent dropped events.
[ 38590.163] [mi] EQ processing has resumed after 161 dropped events.
[ 38590.163] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
[ 38592.480] [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
[ 38592.480]
Backtrace:

Knut J
Attached Files
File Type: gz nvidia-bug-report.log.gz (50.0 KB, 44 views)
File Type: gz Xorg.0.log.old.gz (7.5 KB, 45 views)
KnutJorgen is offline   Reply With Quote
Old 06-18-12, 02:28 PM   #54
cheechr1
Registered User
 
cheechr1's Avatar
 
Join Date: Nov 2010
Posts: 94
Default Re: Random crashes, NVRM Xid messages

With 302.17 and running Cuda Primegrid in Boinc, I almost immediately recieve XID's:

Jun 18 13:20:43 zod kernel: [ 1097.873068] NVRM: Xid (0000:03:00): 31, Ch 00000007, engmask 00000101, intr 10000000
Jun 18 13:22:51 zod kernel: [ 1225.812182] NVRM: Xid (0000:03:00): 31, Ch 00000007, engmask 00000101, intr 10000000
Jun 18 13:23:05 zod kernel: [ 1240.015651] NVRM: Xid (0000:03:00): 31, Ch 00000007, engmask 00000101, intr 10000000
Jun 18 13:24:05 zod kernel: [ 1300.019007] NVRM: Xid (0000:02:00): 31, Ch 00000009, engmask 00000101, intr 10000000
Jun 18 13:24:40 zod kernel: [ 1335.026621] NVRM: Xid (0000:03:00): 31, Ch 00000007, engmask 00000101, intr 10000000
Jun 18 13:24:56 zod kernel: [ 1351.334176] NVRM: Xid (0000:03:00): 31, Ch 00000007, engmask 00000101, intr 10000000

and they just keep coming every minute.

I am unable to do any Primegrid work units because these result in errors. Please look into this Nvidia!!
cheechr1 is offline   Reply With Quote
Old 06-21-12, 10:00 PM   #55
Iesos
Registered User
 
Join Date: Apr 2012
Posts: 15
Default Re: Random crashes, NVRM Xid messages

Quote:
Originally Posted by sandipt View Post
Does this issue reproduce with latest driver as well?
Crash is still there in 302.17.

Quote:
Jun 22 04:51:01 localhost kernel: NVRM: Xid (0000:01:00): 13, 0003 00000000 00009197 00002390 00000000 00000000
Jun 22 04:51:01 localhost kernel: NVRM: Xid (0000:01:00): 39, CCMDs 00000004 000090b5
Jun 22 04:51:05 localhost kernel: NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
I do not get any X backtrace for the crash.
Iesos is offline   Reply With Quote
Old 06-21-12, 10:09 PM   #56
rockob
Registered User
 
Join Date: Nov 2008
Posts: 95
Default Re: Random crashes, NVRM Xid messages

Yes, I still get this crash on 302.17 as well:
Code:
Jun 20 16:03:59 sierra kernel: [ 2026.426817] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  302.17  Tue Jun 12 16:03:22 PDT 2012
Jun 20 16:08:14 sierra kernel: [ 2280.965226] NVRM: Xid (0000:01:00): 13, 0006 00000000 00009197 00002380 00004100 00000000
Jun 20 16:08:16 sierra kernel: [ 2282.968756] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jun 20 16:08:18 sierra kernel: [ 2284.978743] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jun 20 16:08:22 sierra kernel: [ 2288.977479] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jun 20 16:08:41 sierra kernel: [ 2308.048400] NVRM: GPU at 0000:01:00.0 has fallen off the bus.
In case it helps, it also logs a kernel warning for the stalled process, with stack references to the nvidia module:

Code:
Jun 20 16:09:49 sierra kernel: [ 2375.565364] INFO: rcu_sched self-detected stall on CPU { 5}  (t=60000 jiffies)
Jun 20 16:09:49 sierra kernel: [ 2375.565367] Pid: 7890, comm: Crysis2 Tainted: P           O 3.5.0-rc3-git-20120618.0713 #3
Jun 20 16:09:49 sierra kernel: [ 2375.565369] Call Trace:
Jun 20 16:09:49 sierra kernel: [ 2375.565375]  <IRQ>  [<ffffffff810df10a>] __rcu_pending+0x19a/0x4d0
Jun 20 16:09:49 sierra kernel: [ 2375.565377]  [<ffffffff810df46c>] rcu_pending+0x2c/0x60
Jun 20 16:09:49 sierra kernel: [ 2375.565380]  [<ffffffff810dfc51>] rcu_check_callbacks+0xa1/0x140
Jun 20 16:09:49 sierra kernel: [ 2375.565383]  [<ffffffff8105c7d8>] update_process_times+0x48/0x90
Jun 20 16:09:49 sierra kernel: [ 2375.565386]  [<ffffffff810a1286>] tick_sched_timer+0x66/0xc0
Jun 20 16:09:49 sierra kernel: [ 2375.565388]  [<ffffffff810725b9>] __run_hrtimer+0x79/0x1d0
Jun 20 16:09:49 sierra kernel: [ 2375.565390]  [<ffffffff810a1220>] ? tick_nohz_handler+0xf0/0xf0
Jun 20 16:09:49 sierra kernel: [ 2375.565392]  [<ffffffff81072e87>] hrtimer_interrupt+0xd7/0x200
Jun 20 16:09:49 sierra kernel: [ 2375.565395]  [<ffffffff8161efdc>] ? call_softirq+0x1c/0x30
Jun 20 16:09:49 sierra kernel: [ 2375.565397]  [<ffffffff8161f919>] smp_apic_timer_interrupt+0x69/0x99
Jun 20 16:09:49 sierra kernel: [ 2375.565399]  [<ffffffff8161e68a>] apic_timer_interrupt+0x6a/0x70
Jun 20 16:09:49 sierra kernel: [ 2375.565472]  <EOI>  [<ffffffffa18826db>] ? os_free_mem+0x1b/0x30 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.565512]  [<ffffffffa12b7633>] ? _nv014435rm+0x86/0x180 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.565551]  [<ffffffffa12b7633>] ? _nv014435rm+0x86/0x180 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.565655]  [<ffffffffa161565f>] ? _nv009674rm+0x14/0xa1 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.565757]  [<ffffffffa1636091>] ? _nv003990rm+0x4653/0xa790 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.565810]  [<ffffffffa1311ca1>] ? _nv002291rm+0x2d2/0x2e3 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.565861]  [<ffffffffa1311ea1>] ? _nv002004rm+0x1ef/0x205 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.565946]  [<ffffffffa1510de1>] ? _nv005836rm+0x6d0/0x701 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566029]  [<ffffffffa1513a5d>] ? _nv005952rm+0xba/0x60e [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566111]  [<ffffffffa1513a18>] ? _nv005952rm+0x75/0x60e [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566212]  [<ffffffffa15f5cc0>] ? _nv008579rm+0x108/0x179 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566311]  [<ffffffffa160ae5f>] ? _nv008740rm+0x11a/0x336 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566365]  [<ffffffffa131c4ea>] ? _nv002370rm+0x1b/0x20 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566418]  [<ffffffffa131f0d9>] ? _nv002345rm+0x265/0x292 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566471]  [<ffffffffa131ef02>] ? _nv002345rm+0x8e/0x292 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566571]  [<ffffffffa1608805>] ? _nv008014rm+0x2d1/0x3bc [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566670]  [<ffffffffa1608d41>] ? _nv008016rm+0x6d/0x90 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566769]  [<ffffffffa160005a>] ? _nv008075rm+0x12c/0x501 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566807]  [<ffffffffa12a7e5d>] ? _nv001063rm+0x1ccb/0x2afb [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566846]  [<ffffffffa12a60db>] ? _nv001029rm+0xc6a/0xca0 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566883]  [<ffffffffa12a617a>] ? _nv016149rm+0xe/0x26 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566921]  [<ffffffffa12a668c>] ? _nv001063rm+0x4fa/0x2afb [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566959]  [<ffffffffa12a60db>] ? _nv001029rm+0xc6a/0xca0 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.566996]  [<ffffffffa12a617a>] ? _nv016149rm+0xe/0x26 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.567034]  [<ffffffffa12a6411>] ? _nv001063rm+0x27f/0x2afb [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.567071]  [<ffffffffa12a60db>] ? _nv001029rm+0xc6a/0xca0 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.567109]  [<ffffffffa12a614e>] ? _nv016151rm+0x3d/0x5b [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.567157]  [<ffffffffa1858457>] ? _nv001072rm+0xdf/0x1c3 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.567205]  [<ffffffffa185a8e9>] ? rm_free_unused_clients+0x98/0x120 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.567207]  [<ffffffff810744e2>] ? up+0x32/0x50
Jun 20 16:09:49 sierra kernel: [ 2375.567253]  [<ffffffffa1879a4d>] ? nv_kern_ctl_close+0x7d/0x130 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.567300]  [<ffffffffa187a9a3>] ? nv_kern_close+0x3b3/0x440 [nvidia]
Jun 20 16:09:49 sierra kernel: [ 2375.567302]  [<ffffffff8118adf6>] ? d_kill+0xe6/0x140
Jun 20 16:09:49 sierra kernel: [ 2375.567304]  [<ffffffff81176b58>] ? fput+0x118/0x260
Jun 20 16:09:49 sierra kernel: [ 2375.567307]  [<ffffffff811729e6>] ? filp_close+0x66/0xa0
Jun 20 16:09:49 sierra kernel: [ 2375.567309]  [<ffffffff8104fa65>] ? put_files_struct+0xa5/0x100
Jun 20 16:09:49 sierra kernel: [ 2375.567311]  [<ffffffff8104fb85>] ? exit_files+0x55/0x70
Jun 20 16:09:49 sierra kernel: [ 2375.567312]  [<ffffffff81050063>] ? do_exit+0x183/0x8e0
Jun 20 16:09:49 sierra kernel: [ 2375.567314]  [<ffffffff81050b1f>] ? do_group_exit+0x3f/0xa0
Jun 20 16:09:49 sierra kernel: [ 2375.567316]  [<ffffffff81060549>] ? get_signal_to_deliver+0x1a9/0x5c0
Jun 20 16:09:49 sierra kernel: [ 2375.567319]  [<ffffffff810132bf>] ? do_signal+0x3f/0x610
Jun 20 16:09:49 sierra kernel: [ 2375.567322]  [<ffffffff81189b8d>] ? d_free+0x5d/0x70
Jun 20 16:09:49 sierra kernel: [ 2375.567324]  [<ffffffff81076a3a>] ? lg_local_unlock+0x1a/0x20
Jun 20 16:09:49 sierra kernel: [ 2375.567326]  [<ffffffff81192f16>] ? mntput_no_expire+0x46/0x160
Jun 20 16:09:49 sierra kernel: [ 2375.567328]  [<ffffffff8101391d>] ? do_notify_resume+0x6d/0xb0
Jun 20 16:09:49 sierra kernel: [ 2375.567330]  [<ffffffff8161dea2>] ? int_signal+0x12/0x17
rockob is offline   Reply With Quote

Old 08-06-12, 09:27 PM   #57
rockob
Registered User
 
Join Date: Nov 2008
Posts: 95
Default Re: Random crashes, NVRM Xid messages

I also get the "Xid 13 + GPU has fallen off the bus + PC locks up" bug with nvidia v304.32. Has there been any progress in tracking down this bug?

Bumblebee found that rapid polling could cause a "GPU has fallen off the bus" crash as well (https://github.com/Bumblebee-Project...bee/issues/201). Might this be relevant? fwiw, I still experience the crash even if I make bumblebee use blocking sockets.
rockob is offline   Reply With Quote
Old 08-10-12, 03:07 AM   #58
rockob
Registered User
 
Join Date: Nov 2008
Posts: 95
Default Re: Random crashes, NVRM Xid messages

The nvidia driver crashes much more frequently on kernel 3.6-rc1 (with both nvidia 302.17 and 304.32). It used to only crash 'reliably' when playing crysis2, but now it also crashes frequently while playing cod mw3.
rockob is offline   Reply With Quote
Old 08-10-12, 07:13 AM   #59
19721201
Registered User
 
Join Date: Sep 2005
Posts: 16
Default Re: Random crashes, NVRM Xid messages

Hello, I'm using the 3xx driver from this PPA: https://launchpad.net/~ubuntu-x-swat...ive/x-updates/ in Ubuntu Precise 12.04

The issue can be reproduced with the latest PES2013 demo, the system hangs once a while, e.g. /var/log/Xorg.0.log:
[ 12660.405] (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00001b30, 0x0000d728)
[ 12669.428] (WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00001b30, 0x0000d728)

/var/log/syslog:
Aug 10 14:08:45 xxxxxx kernel: [12665.428072] NVRM: Xid (0000:01:00): 8, Channel 00000005
Aug 10 14:08:47 xxxxxx kernel: [12667.428023] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Aug 10 14:09:18 xxxxxx kernel: [12697.873559] NVRM: Xid (0000:01:00): 6, PE0001
19721201 is offline   Reply With Quote
Old 08-12-12, 04:18 AM   #60
Srikar
Registered User
 
Join Date: Apr 2008
Posts: 13
Default Re: Random crashes, NVRM Xid messages

Hello. I'm using the the 302.17 driver on Ubuntu 12.04 running kernel 3.2.0.27 and consistently get this error. All I need to do is browse for a few minutes using Chrome or Firefox. The same issue has been reproduced on my Mandriva installation running the kernel 3.2.x. The error snippet from /var/log/syslog is below. Any updates on the fix for this issue ? Renders my system pretty much useless on Linux when I use the nVidia driver

Aug 12 13:44:11 ubuntu AptDaemon.Worker: INFO: Finished transaction /org/debian/apt/transaction/bb9f6f9f3d584a8f83ec3c80a7bcb222
Aug 12 13:45:58 ubuntu kernel: [ 228.274506] NVRM: Xid (0000:01:00): 13, 0001 00000000 00008597 0000194c 00000000 00000100
Aug 12 13:46:14 ubuntu kernel: [ 243.621043] NVRM: Xid (0000:01:00): 8, Channel 00000003
Aug 12 13:46:16 ubuntu kernel: [ 245.617599] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Aug 12 13:46:18 ubuntu kernel: [ 247.615513] NVRM: Xid (0000:01:00): 1, Channel 00000001 Method 00000060 Data 0100cb22
Aug 12 13:46:18 ubuntu kernel: [ 247.624309] NVRM: Xid (0000:01:00): 1, Channel 00000001 Method 00000060 Data 0100cb22
Aug 12 13:46:20 ubuntu kernel: [ 249.623700] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Srikar 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 02:10 AM.


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