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

Newegg Daily Deals

Reply
 
Thread Tools
Old 11-12-10, 11:53 AM   #1
oyvind
Registered User
 
Join Date: May 2004
Location: Norway
Posts: 117
Default NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86-64]

Still getting these errors when switching to console, with the very latest nvidia driver:

NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context

X becomes extremely laggy and unusable after switching back to it.

The old 195.36.24 driver works fine and does not have these problems.

Ubuntu Lucid x86-64, 2.6.35-22-generic, NVS 3100M, Dell E6510 laptop.
Nvidia bug report log attached.

PS I also just saw these, after restarting X to restore normal behaviour:
NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
NVRM: Xid (0001:00): 53, CMDre 00000001 00000080 00000000 00000005 0000000b
NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
NVRM: Xid (0001:00): 53, CMDre 00000001 00000080 00000000 00000005 0000000b
NVRM: Xid (0001:00): 53, CMDre 00000001 00000080 00000000 00000005 0000000b
NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
NVRM: Xid (0001:00): 53, CMDre 00000001 00000080 00000000 00000005 0000000b
NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
Attached Files
File Type: gz nvidia-bug-report.log.gz (47.7 KB, 140 views)
oyvind is offline   Reply With Quote
Old 11-15-10, 05:07 AM   #2
fcelda
Registered User
 
Join Date: Oct 2010
Posts: 2
Default Re: NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86

Same issue here. In my case, "laggy and unusable" means "it's completely frozen" and sometimes even alt+sysrq+b doesn't work.

Same laptop, latest BIOS (A5), Debian testing, vanilla 2.6.36, x86_64, 260.19.21.
(Tried these kernel options and it didn't help: pci=noacpi, pci=biosirq, noapic, irqpool)
fcelda is offline   Reply With Quote
Old 11-15-10, 06:20 AM   #3
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

Good to know I'm not the only one. Every nvidia driver after 195.36.24 has been problematic for me on this laptop. Must be some kind of regression since the 195-driver is actually very stable. I've never received any official feedback on this issue, although I posted a related bug report earlier (which focused on suspend/resume).
oyvind is offline   Reply With Quote
Old 11-15-10, 08:23 AM   #4
dura91
Registered User
 
Join Date: Aug 2009
Location: Near Paris France
Posts: 40
Default Re: NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86

Quote:
Originally Posted by oyvind View Post
Good to know I'm not the only one. Every nvidia driver after 195.36.24 has been problematic for me on this laptop.
Does this mean that it doesn't work even with 195.36.31? If this is the case, I may have the same problem with completly different hardware. (My problem here: http://www.nvnews.net/vbulletin/showthread.php?t=154735)
dura91 is offline   Reply With Quote
Old 11-15-10, 08:41 AM   #5
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 dura91 View Post
Does this mean that it doesn't work even with 195.36.31? If this is the case, I may have the same problem with completly different hardware. (My problem here: http://www.nvnews.net/vbulletin/showthread.php?t=154735)
I have never tested 195.36.31. Ubuntu does not provide a package of that version, and since the changelog does not mention any interesting/relevant fixes for me (compared to 195.36.24), I never bothered to create a package of it and install it. It is indeed interesting that the problem might have been introduced between .24 and .31.

I might find time to create the necessary debs and and test it. The changelog is tiny and only mentions:
Quote:
Fixed a problem with SLI SFR, AFR, and SLIAA modes with GeForce GTX 480 and GeForce GTX 470 and high-resolution display modes.
oyvind is offline   Reply With Quote
Old 11-15-10, 10:52 PM   #6
chibimushi
Registered User
 
Join Date: Dec 2007
Posts: 8
Default Re: NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86

I upgraded to a GTX 460 about a week ago from an 8800GS. When I start playing 1080p videos using mplayer and vdpau X sometimes will start lagging and become unresponsive for a while for me. It happens more often when I use gnome-mplayer instead of just plain mplayer. I also notice lots of those "NVRM: Xid" lines in dmesg when it happens. I never had that happen till I started using the GTX 460. I was using fedora 13 and am now using Fedora 14 and still have the same problem.

I noticed when I upgraded to the 260.19.21 from 260.19.12 it does it a lot less.
chibimushi is offline   Reply With Quote
Old 11-18-10, 08:20 AM   #7
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

Same problem with the very latest backport-kernel available on Ubuntu Lucid: 2.6.37-5-generic, based on upstream 2.6.37-rc2. Switching to console triggers "NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context" messages with latest nvidia driver 260.19.21. X becomes unusable after switching back. It is sometimes possible to recover by switching a few times back and forth.

195.X does not work with this kernel (module will not compile).
oyvind is offline   Reply With Quote
Old 11-18-10, 08:57 AM   #8
dura91
Registered User
 
Join Date: Aug 2009
Location: Near Paris France
Posts: 40
Default Re: NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86

Quote:
Originally Posted by oyvind View Post
It is sometimes possible to recover by switching a few times back and forth.
The behaviour is exactly the same here. I'm glad to see that I'm not the only one who's got this problem. Perhaps NVidia devs will now show some interest in this problem that I've reported nine months ago...
dura91 is offline   Reply With Quote

Old 11-22-10, 05:44 AM   #9
dura91
Registered User
 
Join Date: Aug 2009
Location: Near Paris France
Posts: 40
Default Re: NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86

Like I stated in my other thread the problem is now solved for me with 260.19.21. Perhaps our problems are different or the 260.19.21 correction is incomplete?
dura91 is offline   Reply With Quote
Old 11-22-10, 06:43 AM   #10
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 dura91 View Post
Like I stated in my other thread the problem is now solved for me with 260.19.21. Perhaps our problems are different or the 260.19.21 correction is incomplete?
Perhaps there are differences, this problem definitely occurs for me with 260.19.21, on several different kernels.

The only thing I saw disappear in recent releases was the "os_raise_smp_barrier(), invalid context!" errors, those stopped with 260.19.12. "Yield CPU while atomic" still happens with latest driver and wrecks havoc when it does.
oyvind is offline   Reply With Quote
Old 12-03-10, 06:22 AM   #11
oyvind
Registered User
 
Join Date: May 2004
Location: Norway
Posts: 117
Thumbs down Re: NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86

Still getting these errors after updating laptop BIOS and installing the latest nvidia beta driver 260.19.26. They are easily triggered just by switching to console and back a couple of times. Once they start, certain drawing ops or something seems to trigger severe lagging in Xorg.

The latest E6510 BIOS update A06 from Dell included lots of interesting things:
1. Fixed issue where OMCI fails to enumerate the DCIM_Doced instance.
2. Added SMBIOS support for TAA MAC address.
3. Fixed one boot sequence issue when switching between RAID and AHCI.
4. Fixed issue where touch screen stops working when system is docked.
5. Improve system POST and boot performance.
6. Improve the IDE-R support.
7. Improve AHCI HDD performance.
8. Added support for China SLIC.
9. Updated Arrandale C2-stepping Microcode to patch 0x0C.
10. Updated PCH 1.6 reference code.
11. Enabled ACPI SPCR for Serial-Over-Lan.
12. Added support to display On-Board NIC MAC address in BIOS SETUP.
13. Updated Intel Clarksfield Framework Reference Code to v1.31.
14. Updated Arrandale MRC to v1.40.
15. Improve Optical drive performance in ATA mode.
16. Fixed TDM SSO structure location.
17. Fixed issue where system hangs in PBA when running Sophos software.
18. Updated Intel Video BIOS.
19. Updated the manageability engine firmware to version 6.1.20.1059.
20. Fixed issues related to F12 one time boot menu.

But alas, the behaviour is exactly the same as before, wrt. newer nvidia drivers.

Please nvidia, consider looking into this, if you believe it might be a nvidia driver problem, since it renders all newer drivers effectively useless on this laptop. The old 195-series continues to work fine.

Attaching updated bug report ..
Attached Files
File Type: gz nvidia-bug-report.log.gz (43.8 KB, 128 views)
oyvind is offline   Reply With Quote
Old 12-14-10, 06:43 AM   #12
oyvind
Registered User
 
Join Date: May 2004
Location: Norway
Posts: 117
Thumbs down Re: NVRM: os_schedule: Attempted to yield the CPU while in atomic[...] [260.19.21 x86

Still happening in 260.19.29, as usual triggered by VT-switching..

Was hoping that this might be a relevant fix:
"Fixed a bug that caused some OpenGL applications to become unresponsive for up to a minute on some GPUs when changing the resolution or refresh rate."

But alas .. Oh boy I'm tired of malfunctioning graphics on Linux ..

[ 3.525825] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 260.19.29 Wed Dec 8 12:08:56 PST 2010
[ 91.848556] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[ 93.843149] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[ 128.864447] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[ 141.848564] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[ 169.560945] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[ 211.397708] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[ 311.392919] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[ 389.311172] NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
[ 392.767764] NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
[ 392.767878] NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
[ 393.693192] NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
[ 396.589307] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[ 398.583965] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[ 457.766844] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[ 459.761167] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[ 464.190296] NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
[ 467.211833] NVRM: Xid (0001:00): 53, CMDre 00000001 00000080 00000000 00000005 0000000b
[ 467.211940] NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
[ 467.211946] NVRM: Xid (0001:00): 53, CMDre 00000001 00000080 00000000 00000005 0000000b
[ 478.181564] NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
[ 478.181722] NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
[ 478.181828] NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
[ 478.181953] NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
[ 478.182062] NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
[ 478.182168] NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
[ 478.267258] NVRM: Xid (0001:00): 53, CMDre 00000001 00000080 00000000 00000005 0000000b
[ 491.071457] NVRM: Xid (0001:00): 53, CMDre 00000000 00000080 00000000 00000005 00000005
[ 590.498141] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
oyvind 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 01:25 PM.


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