nV News Forums

 
 

nV News Forums (http://www.nvnews.net/vbulletin/index.php)
-   NVIDIA Linux (http://www.nvnews.net/vbulletin/forumdisplay.php?f=14)
-   -   BUG: os_schedule: Attempted to yield the CPU while in atomic or interrupt context (http://www.nvnews.net/vbulletin/showthread.php?t=163468)

rockob 06-14-11 06:04 AM

BUG: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
 
1 Attachment(s)
I get the error "NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context" reasonably frequently while running wine 3d apps in the linux 3.0-rc3 kernel. It causes the application to hang and shortly afterwards the entire desktop hangs and the intel interrupt driver reports missing PM interrupts. The crash appears to be random but I find it likely to occur in less than five minutes of running a 3d-intensive app like a game in wine.

It happens with both the 275.09.04 and the 270.41.09 drivers (with the latter suitably patched to compile for kernel 3.0-rc3).

Note though that it doesn't happen with the stock 2.6.38-10-generic Ubuntu kernel (ie I haven't been able to reproduce it).

rockob 06-17-11 01:13 AM

Re: BUG: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
 
It still happens with the 275.09.07 driver.

ididthefopp 06-24-11 12:04 AM

Re: BUG: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
 
1 Attachment(s)
The same goes for my desktop. It's very annoying.
gentoo ~x86
xorg-server 1.10.2
nvidia-drivers 275.09.07
wine 1.3.17
kde 4.6.3

rockob 07-09-11 01:54 PM

Re: BUG: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
 
It is still happening with the 280.04 nvidia driver and 3.0-rc6 kernel. The 'Attempted to yield the CPU while in atomic or interrupt context' messages aren't appearing any more, but under heavy load on the nvidia driver, the kernel will still crash along with a 'GPU at 01:00.0 fell off the bus' message in the syslog.

rockob 07-23-11 04:34 AM

Re: BUG: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
 
I've run into this crash several times today with the 3.0-generic kernel and 275.19.

I also got a slightly different message just before an 'attempted to yield' error message:

Jul 23 15:34:31 hercules kernel: [ 2195.898158] NVRM: Xid (0000:01:00): 13, 0006 00000000 00009197 00002490 00000030 00000000
Jul 23 15:34:35 hercules kernel: [ 2197.900997] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context

rockob 07-23-11 07:57 AM

Re: BUG: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
 
I even experienced the freeze earlier today in Ubuntu's 2.6.38-10-generic kernel (not 3.0 for a change):

Code:

Jul 23 18:33:30 hercules kernel: [ 9321.694429] NVRM: Xid (0000:01:00): 13, 0006 00000000 00009197 00002490 00000030 00000000
Jul 23 18:33:30 hercules kernel: [ 9321.698052] NVRM: Xid (0000:01:00): 39, CCMDs 00000005 000090b5
Jul 23 18:33:32 hercules kernel: [ 9323.697393] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jul 23 18:33:36 hercules kernel: [ 9327.696157] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jul 23 18:33:59 hercules rtkit-daemon[1217]: The canary thread is apparently starving. Taking action.
Jul 23 18:33:59 hercules rtkit-daemon[1217]: Demoting known real-time threads.
Jul 23 18:33:59 hercules rtkit-daemon[1217]: Successfully demoted thread 1889 of process 1847 (n/a).
Jul 23 18:33:59 hercules rtkit-daemon[1217]: Successfully demoted thread 1888 of process 1847 (n/a).
Jul 23 18:33:59 hercules rtkit-daemon[1217]: Successfully demoted thread 1847 of process 1847 (n/a).
Jul 23 18:33:59 hercules rtkit-daemon[1217]: Demoted 3 threads.

and later on, this appeared several times:

Code:

Jul 23 18:42:08 hercules kernel: [ 9838.933046] INFO: task kworker/7:2:7007 blocked for more than 120 seconds.
Jul 23 18:42:08 hercules kernel: [ 9838.933050] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jul 23 18:42:08 hercules kernel: [ 9838.933053] kworker/7:2    D 0000000000000007    0  7007      2 0x00000000
Jul 23 18:42:08 hercules kernel: [ 9838.933059]  ffff880036de9be0 0000000000000046 ffff880036de9fd8 ffff880036de8000
Jul 23 18:42:08 hercules kernel: [ 9838.933064]  0000000000013d00 ffff88021198df38 ffff880036de9fd8 0000000000013d00
Jul 23 18:42:08 hercules kernel: [ 9838.933068]  ffff8800afc4db80 ffff88021198db80 00000000000052d0 7fffffffffffffff
Jul 23 18:42:08 hercules kernel: [ 9838.933072] Call Trace:
Jul 23 18:42:08 hercules kernel: [ 9838.933081]  [<ffffffff815c14dd>] schedule_timeout+0x26d/0x2e0
Jul 23 18:42:08 hercules kernel: [ 9838.933088]  [<ffffffff8105e316>] ? load_balance_fair+0xf6/0x140
Jul 23 18:42:08 hercules kernel: [ 9838.933093]  [<ffffffff815c0f99>] wait_for_common+0xd9/0x180
Jul 23 18:42:08 hercules kernel: [ 9838.933097]  [<ffffffff8105f600>] ? default_wake_function+0x0/0x20
Jul 23 18:42:08 hercules kernel: [ 9838.933303]  [<ffffffffa170ed90>] ? os_execute_work_item+0x0/0xa0 [nvidia]
Jul 23 18:42:08 hercules kernel: [ 9838.933309]  [<ffffffff815c111d>] wait_for_completion+0x1d/0x20
Jul 23 18:42:08 hercules kernel: [ 9838.933486]  [<ffffffffa170e24a>] os_acquire_sema+0x7a/0x90 [nvidia]
Jul 23 18:42:08 hercules kernel: [ 9838.933594]  [<ffffffffa10d830e>] ? _nv023034rm+0x9/0xb [nvidia]
Jul 23 18:42:08 hercules kernel: [ 9838.933771]  [<ffffffffa16dc384>] _nv023245rm+0x6/0x1f [nvidia]
Jul 23 18:42:08 hercules kernel: [ 9838.933970]  [<ffffffffa15cd3ee>] ? _nv003531rm+0x38/0x131 [nvidia]
Jul 23 18:42:08 hercules kernel: [ 9838.934149]  [<ffffffffa16e8088>] ? _nv002385rm+0xd/0x27 [nvidia]
Jul 23 18:42:08 hercules kernel: [ 9838.934323]  [<ffffffffa16ec474>] ? rm_execute_work_item+0x1c/0xe4 [nvidia]
Jul 23 18:42:08 hercules kernel: [ 9838.934498]  [<ffffffffa170ede0>] ? os_execute_work_item+0x50/0xa0 [nvidia]
Jul 23 18:42:08 hercules kernel: [ 9838.934505]  [<ffffffff8108284d>] ? process_one_work+0x11d/0x420
Jul 23 18:42:08 hercules kernel: [ 9838.934510]  [<ffffffff810832e9>] ? worker_thread+0x169/0x360
Jul 23 18:42:08 hercules kernel: [ 9838.934514]  [<ffffffff81083180>] ? worker_thread+0x0/0x360
Jul 23 18:42:08 hercules kernel: [ 9838.934518]  [<ffffffff81087866>] ? kthread+0x96/0xa0
Jul 23 18:42:08 hercules kernel: [ 9838.934523]  [<ffffffff8100ce24>] ? kernel_thread_helper+0x4/0x10
Jul 23 18:42:08 hercules kernel: [ 9838.934527]  [<ffffffff810877d0>] ? kthread+0x0/0xa0
Jul 23 18:42:08 hercules kernel: [ 9838.934531]  [<ffffffff8100ce20>] ? kernel_thread_helper+0x0/0x10


V|r 06-23-12 05:38 AM

Re: BUG: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
 
Hi!

I got this hang today:
Code:

Jun 23 12:06:53 Trigati kernel: [ 8634.758581] NVRM: Xid (0000:01:00): 13, 0001 00000000 00008597 000015e0 00000000 00000100
Jun 23 12:07:12 Trigati kernel: [ 8653.742732] NVRM: Xid (0000:01:00): 8, Channel 00000007
Jun 23 12:07:14 Trigati kernel: [ 8655.739333] NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
Jun 23 12:07:28 Trigati kernel: [ 8668.874359] NVRM: Xid (0000:01:00): 13, 0001 00000000 00008597 00000100 0fffea00 00000100

This is with driver version 295.49 on Ubuntu 12.04 LTS (GNU/Linux 3.2.0-25-generic x86_64).
The hang occured when I started playing a 3D game in wine.


All times are GMT -5. The time now is 06:25 PM.

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