10de:01df [Asus P5K] system freezes for some seconds: Attempted to yield the CPU while in atomic or interrupt context

[Michael Mess]

After the first freeze, dmesg showed:

...
[194346.116070] NVRM: Xid (0000:01:00): 8, Channel 00000002
[194348.116026] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[194350.117812] NVRM: Xid (0000:01:00): 9, Channel 00000020 Instance 00000000 Intr 00000080

After the second freeze, dmesg showed:

...
[194346.116070] NVRM: Xid (0000:01:00): 8, Channel 00000002
[194348.116026] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[194350.117812] NVRM: Xid (0000:01:00): 9, Channel 00000020 Instance 00000000 Intr 00000080
[194514.140070] NVRM: Xid (0000:01:00): 8, Channel 00000002
[194516.140030] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[194518.141391] sched: RT throttling activated

michael@quad:~$ cat /proc/version_signature
Ubuntu 3.2.0-23.36-generic-pae 3.2.14

michael@quad:~$ lsb_release -rd
Description: Ubuntu 12.04 LTS
Release: 12.04

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-23-generic-pae 3.2.0-23.36
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic-pae 3.2.14
Uname: Linux 3.2.0-23-generic-pae i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu5
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC2: michael 9506 F.... pulseaudio
 /dev/snd/controlC0: michael 9506 F.... pulseaudio
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf6ff8000 irq 44'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,1043829f,00100002'
   Controls : 46
   Simple ctrls : 22
Card1.Amixer.info:
 Card hw:1 'UA101'/'EDIROL UA-101 (serial ZT82634), 192000 Hz at usb-0000:00:1a.7-3, high speed'
   Mixer name : ''
   Components : ''
   Controls : 1
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'MIDI Input Mode',0
   Capabilities: enum
   Items: 'High Load' 'Light Load'
   Item0: 'Light Load'
Card2.Amixer.info:
 Card hw:2 'CX8811'/'Conexant CX8811 at 0xfb000000'
   Mixer name : 'CX88'
   Components : ''
   Controls : 3
   Simple ctrls : 2
Date: Sun Apr 22 13:55:17 2012
HibernationDevice: RESUME=UUID=dd8becab-8d85-4a0f-9840-3cd90d202035
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
MachineType: System manufacturer P5K
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_US
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: root=UUID=4f6e10b1-9995-4249-a5e5-a9b20b72cace ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-23-generic-pae N/A
 linux-backports-modules-3.2.0-23-generic-pae N/A
 linux-firmware 1.79
RfKill:

SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2012-04-18 (3 days ago)
dmi.bios.date: 10/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1201
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5K
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd10/14/2008:svnSystemmanufacturer:pnP5K:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5K
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

[Joseph Salisbury (jsalisbury)]

These bugs occur typically in an interrupt context. Do you have a way to reproduce this bug? If so, there is a wiki page[0] that provides some information on gathering more data specific to these type of bugs. If possible can you review the wiki page and gather the additional data listed on that page?

[0] https://wiki.ubuntu.com/Kernel/DebuggingSchedulingWhileAtomic

[Michael Mess (michael-michaelmess)]

Thanks for the link.
Unfortunately I don't have a way to reproduce this bug, it just comes suddenly, but in the last time it seems that this issue didn't hit me again, maybe this has been fixed with one of the last kernel updates, maybe I didn't see it, because I didn't spend much time in front of the PC, most times I was using it remotely, maybe it could also be an issue with the nvidia driver?
Maybe it will hit me again, when I spend more time in front of the PC, then I will attach the logs.

[Michael Mess (michael-michaelmess)]

Today it hit me again when I was switching user.

I was logged in as one user, then pressed CTRL-ALT-L to lock the screen and then switch user.
After logging in as second user everything was OK.
Then I switched back to the first user and then back to the second user and the system was hanging for some time.
Also screen was garbled much, thus it is likely to be an nvidia-bug: See also https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1025693

Or is there anybody who is suffering from this without having an nvidia card? Then please leave a comment.

[596939.374062] NVRM: os_pci_init_handle: invalid context!
[596939.374067] NVRM: os_pci_init_handle: invalid context!
[596939.374076] NVRM: os_map_kernel_space: can't map 0xd0000000, invalid context!

[599206.972037] NVRM: Xid (0000:01:00): 8, Channel 00000003
[599208.972009] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[599249.000069] NVRM: Xid (0000:01:00): 8, Channel 00000003
[599251.000036] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[599281.028043] NVRM: Xid (0000:01:00): 8, Channel 00000003
[599283.028013] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[599285.029509] sched: RT throttling activated
[599303.060048] NVRM: Xid (0000:01:00): 8, Channel 00000003
[599305.060018] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[599457.092056] NVRM: Xid (0000:01:00): 8, Channel 00000003
[599459.092020] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
[599509.116045] NVRM: Xid (0000:01:00): 8, Channel 00000003
[599511.116017] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context

After that I have installed the latest update (including a linux kernel) and rebooted.

[Michael Mess (michael-michaelmess)]

After installing the current updates, I have enabled tracing and tried to reproduce the issue.
And the problem still exists.

I was able to reproduce the issue by switching users, this time the X11 system got completely unusable (hanging) and there also was a Segfault in compiz.
After switching users, the newly logged in second user just got a hanging session where the panels and background were drawn incompletely and it was hanging, while it was only possible to move the mouse.
It was neither possible to interact with the session nor to switch users nor switch to a text console.

Fortunately I was able to login via ssh to save the tracing and then reboot.

[Michael Mess (michael-michaelmess)]

When beeing logged in remotely I also vainly tried to regain access to the console by killing the user processes and the X11 process and later I found with top that there was a lightdm Zombie process which was using 98% CPU.

[Rocko (rockorequin)]

Did nvidia 304.37 fix this issue, as it seems to have done for some people in bug #973096? Unfortunately it doesn't fix my nvidia card from crashing when I use it to play 3d games under wine via bumblebee.

[Michael Mess (michael-michaelmess)]

I am still getting

[31161.506308] NVRM: os_pci_init_handle: invalid context!
[31161.506313] NVRM: os_pci_init_handle: invalid context!
[31161.506324] NVRM: os_map_kernel_space: can't map 0xd0000000, invalid context!
[31161.506328] NVRM: os_pci_init_handle: invalid context!
[33531.507648] NVRM: os_pci_init_handle: invalid context!
[33531.507652] NVRM: os_pci_init_handle: invalid context!
[33531.507660] NVRM: os_map_kernel_space: can't map 0xd0000000, invalid context!
[33531.507662] NVRM: os_pci_init_handle: invalid context!

in the dmesg log and the system sometimes freezes for some seconds or behaves strange.

This often happens when playing video with the flash plugin.
It may happen more likey when opening more browser tabs and playing video.

[MvW (2nv2u)]

I've got the same issue, completely locking up the computer sometimes, this seems to be same issue as this one:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/1132121

[MvW (2nv2u)]

Locking up again, this time running an OpenGL application, desktop did not recover, did manage to get to tty1 and after login the music still plays but returning to tty7 was not possible (black screen and music stopped, switching back took some time, almost unresponsive), restarted lightdm and found this in the log:

Jun 6 17:36:54 Machine kernel: [ 232.308483] NVRM: GPU at 0000:01:00: GPU-9e2ddf6e-47c2-4331-d30f-b7adedcd90fc
Jun 6 17:36:54 Machine kernel: [ 232.308489] NVRM: Xid (0000:01:00): 13, 0003 00000000 00000000 00000000 00000000 00000001
Jun 6 17:36:56 Machine kernel: [ 234.314519] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jun 6 17:38:20 Machine kernel: [ 317.783268] NVRM: Xid (0000:01:00): 13, 0002 00000000 00000000 00000000 00000000 00000001

[MvW (2nv2u)]

Still happening regularly:

Jun 24 15:51:30 Machine kernel: [ 424.863708] NVRM: GPU at 0000:01:00: GPU-9e2ddf6e-47c2-4331-d30f-b7adedcd90fc
Jun 24 15:51:30 Machine kernel: [ 424.863711] NVRM: Xid (0000:01:00): 8, Channel 00000003
Jun 24 15:51:32 Machine kernel: [ 426.861668] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jun 24 16:03:08 Machine kernel: [ 1122.660533] NVRM: Xid (0000:01:00): 8, Channel 00000001
Jun 24 16:03:10 Machine kernel: [ 1124.659529] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jun 24 16:58:19 Machine kernel: [ 4431.828940] NVRM: Xid (0000:01:00): 8, Channel 00000003
Jun 24 16:58:21 Machine kernel: [ 4433.827900] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jun 24 16:58:23 Machine kernel: [ 4435.833749] [sched_delayed] sched: RT throttling activated
Jun 24 16:58:54 Machine kernel: [ 4466.807760] gnome-shell[3408]: segfault at 48 ip 00007fd21d8fdc89 sp 00007fff75bca5b8 error 6 in libnvidia-glcore.so.319.23[7fd21c409000+1a47000]
Jun 24 17:24:38 Machine kernel: [ 6009.652278] NVRM: Xid (0000:01:00): 8, Channel 00000001
Jun 24 17:24:40 Machine kernel: [ 6011.651271] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jun 24 19:21:30 Machine kernel: [13017.648298] NVRM: Xid (0000:01:00): 8, Channel 00000006
Jun 24 19:21:32 Machine kernel: [13019.647294] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context

Anyone?

[Rocko (rockorequin)]

@2nv2u: fwiw, I suspect my Xid errors and crashes were being caused by poor quality nVidia hardware. I think the frequency of the errors did drop with later nvidia drivers, but I didn't stop getting them altogether until I tried a BIOS that reduced the voltage for 3d operations to the nvidia card (this is apparently a common problem with my nvidia 540M hardware when it's under stress). Having said that, I ran into the errors when I was running intensive 3d gaming applications, and it sounds like you are having problems with normal 2d operations, which shouldn't stress the card at all.

[MvW (2nv2u)]

@Rocko:
This could be the case, but it never happened to me before 12.10.
I'm using a Quadro FX 3800M and tried drivers 304.*, 310.*, 313.* and 319.* in 12.10 and 13.04 and this error happens quite frequently.
I did notice something that might be of interest. I'm using this laptop (Dell precision M6500) mostly in a docking station with 2 monitors attached. The other day I was working on it without the docking station (just the laptop screen) and it didn't happen at all in that session. Makes me wonder.
Another footnote is flash, this seems to trigger the behavior as well.

[MvW (2nv2u)]

Happened again, this time nothing but a terminal window and firefox showing a google search result.

Jul 24 14:44:07 Machine kernel: [ 3585.132265] NVRM: GPU at 0000:01:00: GPU-9e2ddf6e-47c2-4331-d30f-b7adedcd90fc
Jul 24 14:44:07 Machine kernel: [ 3585.132269] NVRM: Xid (0000:01:00): 8, Channel 00000003
Jul 24 14:44:07 Machine kernel: [ 3587.131233] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context

[Joshua Anhalt (jtree)]

lsb_release -rd
Description: Ubuntu 12.04.2 LTS

cat /proc/version_signature
Ubuntu 3.2.0-49.75-generic-pae 3.2.46

32-bit mode

GPU:Nvidia Quadro 4000M, nvidia-current 304.88-0ubuntu0.0.2

In addition to the above mentioned "NVRM: Xid ..." and "NVRM: os_schedule:..." messages, the following extra message had been appearing in dmesg, and syslog. Unfortunately, I don't see these messages in any of the other user's posted dmesgs, so my version of these symptoms, and current fix may be unrelated.

--- begin dmesg snippet
NVRM: Your system is not currently configured to drive a VGA console
NVRM: on the primary VGA device. The NVIDIA Linux graphics driver
NVRM: requires the use of a text-mode VGA console. Use of other console
NVRM: drivers including, but not limited to, vesafb, may result in
NVRM: corruption and stability problems, and is not supported.
--- end dmesg

So I decided to make sure that vesafb (and any fb stuff done by grub) were fully deactivated.

I added "blacklist vesafb" to a modprobe config file, should work by placing in /etc/modprobe.d/nvidia-blacklist.conf". The problems persisted, so I added "GRUB_GFXPAYLOAD_LINUX=text" to /etc/default/grub, ran update-grub, then rebooted.

Now the "NVRM: Xid ..." and "NVRM: os_schedule:..." messages have stopped, and the machine has run reliably for over a week. (The video would become corrupt, and machine would eventually hang once a day.)

Of course your mileage may vary.

[MvW (2nv2u)]

This is getting to a point which makes my computer unusable. It seems to happen more and more.
I started working on 12:00 today and it happened to me over 17 times already!

Tried jtree's solutions which unfortunately doesn't work for me. Anyone?

[Bruno Rocha Coutinho (bruno-r-coutinho)]

I'm using driver vestion 304.88 that comes with ubuntu 12.04 and
blacklisted all sensor modules.
On an old core 2 Q6600 with a Geforce GTX 480 this bugs dosn't appear more
and an i7-2600 with a Geforce GT 520 this bug appears once or twice a month.

2013/7/29 M. van Workum <[e-mail]>

> This is getting to a point which makes my computer unusable. It seems to
> happen more and more.
> I started working on 12:00 today and it happened to me over 17 times
> already!
>
> Tried jtree's solutions which unfortunately doesn't work for me. Anyone?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/986831
>
> Title:
> system freezes for some seconds: Attempted to yield the CPU while in
> atomic or interrupt context
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/986831/+subscriptions
>

[MvW (2nv2u)]

Just installed the latest beta 325.08, resulting in the same behavior, it happens to me once or twice every 20 minutes.
Detaching the laptop from the dock solves it though. Very strange...

[MvW (2nv2u)]

Unfortunately, working on the laptop detached from the bay didn't fix the issue, still happening, but less frequent (once every hour).
Tried the newest 325.15 driver to no avail.

[Brains (brains)]

@M. van Workum: "This is getting to a point which makes my computer unusable."

I know the feeling. Got similar instability problems with Ubuntu ever since 12.04, rendering the computer unusable.

12.10 and 13.04 did not fix it.

Tried to escalate within Canonical on a few occasions, but all they said was "repro steps are too vague". While they were right, these are not bugs to defer, since I was far from the only one.

Quite happy with Debian 7.1 now. Rock-solid, like I remember Ubuntu being before 12.04. I don't think I will easily come back here.

[penalvch (penalvch)]

Michael Mess, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[MvW (2nv2u)]

Tried running: Linux Machine 3.9.0-030900rc8-generic #201304211835 SMP Sun Apr 21 22:35:53 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux with the nVidia 325.15 driver.

Still causing the issue.

Aug 27 22:33:42 Machine kernel: [ 2530.339582] NVRM: GPU at 0000:01:00: GPU-9e2ddf6e-47c2-4331-d30f-b7adedcd90fc
Aug 27 22:33:42 Machine kernel: [ 2530.339587] NVRM: Xid (0000:01:00): 8, Channel 00000005
Aug 27 22:33:44 Machine kernel: [ 2532.338549] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context

Started an apport report.

[penalvch (penalvch)]

M. van Workum, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documention in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[MvW (2nv2u)]

Hi Christopher,

Why does it need a new bug report when the issue resembles this one exactly?

[MvW (2nv2u)]

Tested 13.10 beta 1 and this issue still happens quite frequently (325.15 driver), going to try Debian as suggested by Joris V.
I have used Ubuntu primarily since 8.04 but this is getting to much of a burden and it doesn't seemed to be fixed upstream..

[John Murray (johnmurrayvi)]

This occurs for me pretty much whenever I leave for awhile, come back, and within first 30 seconds of returning (starting to use my computer again), X will freeze. Only way to get out of it that I have found is using Alt + SysRq + REISUB. Checking syslog after it boots again, I always have "NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context".
I very recently upgraded from a GTX 560 Ti to a GTX 770, and that's when this started happening. I never had this issue with my GTX 560 Ti. However, I do remember having this problem on the first gen aluminum iMac, with a 9800 I believe. I could never use the Nvidia drivers on it because of this, though the Nouveau drivers worked fine.

Current setup:
Linux 3.10
Ubuntu 13.10
GTX 770
Version 325.15 of the Nvidia drivers

[penalvch (penalvch)]

John Murray, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[Brains (brains)]

no way... they even have standard messages now.

just create a new report and all will be fine! yeah...

Canonical seems to spread itself thin on various targeted markets, but are neglecting their core business at the moment.

Haven't I heard that from another software company having gone the exact same route?

[MvW (2nv2u)]

I agree with Joris V. they are starting to loose there reason for existence.
Please don't try to be what you despised in the first place!
Sadly I guess closing bug 1 unfortunately does reflect this new strategy...

But on the brighter side of things.
After investigating going to Debian I noticed after a couple of updates in the 13.10 beta, using the nVidia 325.15 driver, I haven't encountered this issues in a couple weeks now! Being cautiously optimistic! :)

[MvW (2nv2u)]

Still happened although less frequent, recently upgraded to 13.10 with nVidia 331.13 and it started to happen again in the same frequency as from the beginning.
Will contact Dell now since after some investigation this laptop seems to be prone to GPU failure and since non of my other PC's, who all have nVidia hardware, are affected, it has to be a hardware issue.

[David Anderson (davea42)]

Recently upgraded to 13.10. Replaced Nvidia 560TI with new GTX 760 SC. Replaced power supply.
x86_64. driver 319.32

Get the message after a few hours running boinc/seti calculations. system continues running
and calculating, only a reboot restores the monitor from being blank to showing something.
turning off boinc/seti calculations to see if that changes the situation.

[David Anderson (davea42)]

Here is the start of the messages, this from syslog. The first such messages

Nov 6 19:20:01 Dseti3 CRON[18475]: (root) CMD (if [ -x /etc/munin/plugins/apt_all ]; then munin-run apt_all update 7200 12 >/dev/null; elif [ -x /etc/munin/plugins/apt ]; then munin-run apt update 7200 12 >/dev/null; fi)
Nov 6 19:23:01 Dseti3 kernel: [129142.238696] [sched_delayed] sched: RT throttling activated
Nov 6 19:23:59 Dseti3 kernel: [129200.218913] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Nov 6 19:24:01 Dseti3 kernel: [129202.218438] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context

The day before I got (from syslog.3.gz) a
  " soft lockup - CPU#19 stuck for 23s! [swapper/19:0]"
in syslog. starting to look into this message now.

[penalvch (penalvch)]

M. van Workum / David Anderson, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

[MvW (2nv2u)]

Created a new report as suggested: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1258231

[MvW (2nv2u)]

Running quite well with kernel 3.2 for a week now and have switched to 3.4 2 days ago, still without any issues.
Perhaps all effecting should mark my bug happening to you as well, we should turn up the heat!

https://bugs.launchpad.net/ubuntu/+bug/1258231

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

[Temporal (joaoplim)]

I know this is old and probably nobody will look this, but I guess it is valid to put my experience here, once I can reproduce consistently and a almost at will the "NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context" problem:

Ubuntu: x64, 13.10, kernel 3.11.0-23-generic;
HD SSD OCZ octane 128GB.
Intel Q9400;
Motherboard: P5n-D;
Memory: 2x Macrovision 5-5-5-18; 2x2GB
                 2x Kingston 6-5-5-18; 2x2GB
--->running in successfull Dual Channel 8GB 6-5-5-18;
GPU 1: 9600 GT 512MB;
GPU 2: 9600 GT 512MB;
--->running in successful SLI;
--->running using nvidia drivers 319 proprietary.
PSU: Corsair CX600 (does not look like a problem).

How I reproduce the problem:

1)Run World of Warcraft (via Wine-any Wine that works WoW x32 will do, I tried with 1.4 and 1.5-), go to the latest levels (pandaria).
2)Open any browser and go to youtube, let it running videos from any playlist.
3)Soon after, the X server will start to stutter, and DMESG will show the "NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context" problem.
4)Usually, if I get to catch the problem, the kernel process that switches processes around (mostly the first of 4) called migration (in my case, migration/0) will appear running at 100%.

If I run just the game or just the browser, everything runs perfectly. SLI works randomly for WoW if running in full screen. SLI is always working while in Unity.

If I try to run GPU testers like furmark (for linux) under the same conditions I cannot reproduce the problem.

[penalvch (penalvch)]

Temporal, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs