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

Newegg Daily Deals

Reply
 
Thread Tools
Old 02-15-11, 01:53 PM   #37
oyvind
Registered User
 
Join Date: May 2004
Location: Norway
Posts: 117
Default Re: NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86

I noticed another difference, now it's:
NVRM: Xid (0000:01:00): 56, CMDre 00000000 00000080 00000000 00000005 00000005

instead of:
NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
(from older releases)

So the error number or whatever it is, changed from 53 to 56 ..
oyvind is offline   Reply With Quote
Old 02-19-11, 03:39 PM   #38
Licaon
Registered User
 
Licaon's Avatar
 
Join Date: Nov 2004
Location: Between the keyboard and the chair.
Posts: 490
Default Re: NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86

just got 2 of these and one [mi] EQ overflowing. The server is probably stuck in an infinite loop. ( something about evdev_drv.so ) followed by a (WW) NVIDIA(0): WAIT (2, 6, and a (WW) NVIDIA(0): WAIT (0, 6, while switching between 270.26 and 270.18 to test for slow composition using Kwin.

attached the logs
Attached Files
File Type: gz 270.18_nvidia-bug-report.log.gz (83.5 KB, 93 views)
File Type: gz 270.26_nvidia-bug-report.log.gz (83.1 KB, 88 views)
Licaon is offline   Reply With Quote
Old 04-12-11, 01:11 PM   #39
oyvind
Registered User
 
Join Date: May 2004
Location: Norway
Posts: 117
Default Re: NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86

Still the same error with 270.41.03, when switching to console and Compiz VSYNC is enabled.
oyvind is offline   Reply With Quote
Old 04-13-11, 04:03 PM   #40
oyvind
Registered User
 
Join Date: May 2004
Location: Norway
Posts: 117
Default Re: NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86

Quote:
Originally Posted by oyvind View Post
Still the same error with 270.41.03, when switching to console and Compiz VSYNC is enabled.
Also, suspend is broken with all drivers > 195-series, probably because suspend causes console switch, which trigger these stability issues.
oyvind is offline   Reply With Quote
Old 04-16-11, 07:42 AM   #41
misty soul
Registered User
 
Join Date: Apr 2011
Posts: 1
Default Re: NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86

I encounters the same kind of errors since yesterday on Ubuntu 10.10: random (and frequent) freeze. Sometimes, network access from a remote computer is still possible, but sometimes everything is locked down and I have to power-cycle the machine.

I tried to put 260.19.44 driver, I removed sync to vblank from compiz and tried with and without syn to vblank from nvidia settings, nothing works.

With the original drivers from Ubuntu (260.19.06), I got thousands of messages in /var:log/messages like:

Code:
Apr 15 20:53:04 lehrin kernel: [44982.434618] NVRM: os_pci_int_handle: invalid context!
Apr 15 20:53:04 lehrin kernel: [44982.434660] NVRM: os_pci_init_handlet_handle: invalid context!
Apr 15 20:53:04 lehrin kernel: [44982.434686] NVRM: os_pci_init_ht_handle: invalid context!
Apr 15 20:53:04 lehrin kernel: [44982.434736] NVRM: os_pct_handle: invalid context!
Apr 15 20:53:04 lehrin kernel: [44982.434766] NVRM: os_pct_handle: invalid context!
Apr 15 20:53:04 lehrin kernel: [44982.434807] NVRM: os_pci_int_handle: invalid context!
The "os_pci_init_handle: invalid context!" was the most repeated one (more than 120000 occurrences).

Then I got a one minute gap without any messages in /var/log/messages followed by kernel errors (see attached nvidia-bug-report.gz, where I have removed many of the repeated messages to fit the forum upload limit).

After manual power-cycling and reboot, I could work for about 10 minutes and then got another freeze, but this time without the thousands of messages.

Note that in the attached bug report, some files reference the 260.19.44 driver I installed today (April 16), but the /var/log/message that was included is from yesterday night (April 15, at about 21:00 UTC) when I had 260.19.06 installed. From a user point of view, I don't see any differences between the two drivers and get the same behavior, so I guess this mismatch is not relevant.
Attached Files
File Type: gz nvidia-bug-report.log.gz (37.1 KB, 64 views)
misty soul is offline   Reply With Quote
Old 04-30-11, 09:06 AM   #42
oyvind
Registered User
 
Join Date: May 2004
Location: Norway
Posts: 117
Thumbs up Re: NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86

270.41.06 appears to be better. I've suspend and resumed successfully many times now (uptime of 4 days on my laptop) and system stays stable. I can still provoke the ": NVRM: os_schedule: Attempted to yield..."-messages by switching to console, but they seem to cause little harm.
oyvind is offline   Reply With Quote
Old 03-13-12, 01:53 AM   #43
sjlopezb
Registered User
 
Join Date: Mar 2012
Posts: 34
Default Re: NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86

Hi:

My problem in driver 295.20, apparenty fail or consistency system.

[ 24601.674] [mi] EQ overflowing. The server is probably stuck in an infinite loop.
[ 24601.674]
Backtrace:
[ 24601.674] 0: /usr/bin/X11/X (xorg_backtrace+0x37) [0xb770ccc7]
[ 24601.674] 1: /usr/bin/X11/X (mieqEnqueue+0x185) [0xb76eb125]
[ 24601.674] 2: /usr/bin/X11/X (0xb7588000+0x4fce5) [0xb75d7ce5]
[ 24601.674] 3: /usr/bin/X11/X (xf86PostMotionEventM+0xf9) [0xb7615b09]
[ 24601.674] 4: /usr/bin/X11/X (xf86PostMotionEvent+0xae) [0xb7615d1e]
[ 24601.674] 5: /usr/lib/xorg/modules/input/synaptics_drv.so (0xb70ca000+0x41ae) [0xb70ce1ae]
[ 24601.674] 6: /usr/lib/xorg/modules/input/synaptics_drv.so (0xb70ca000+0x6369) [0xb70d0369]
[ 24601.674] 7: /usr/bin/X11/X (0xb7588000+0x78311) [0xb7600311]
[ 24601.674] 8: /usr/bin/X11/X (0xb7588000+0x9fac2) [0xb7627ac2]
[ 24601.674] 9: (vdso) (__kernel_sigreturn+0x0) [0xb756a400]
[ 24601.674] 10: /usr/lib/xorg/modules/drivers/nvidia_drv.so (0xb47f2000+0x61b72) [0xb4853b72]

Also /var/log/messages:

Mar 13 07:30:00 dell kernel: [24603.948107] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Mar 13 07:30:03 dell kernel: [24606.009424] sched: RT throttling activated


Report this problem.

Thank's.
Attached Files
File Type: gz nvidia-bug-report.log.gz (73.9 KB, 37 views)
sjlopezb 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 12:13 PM.


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