ExecutorElassus
Veteran
Joined: 11 Mar 2004
Posts: 1435
Location: Berlin, Germany
|
 Posted: Tue Aug 07, 2012 12:37 am Post subject: NVRM Lockups on Xorg |
 |
|
So, I've been having serious stability issues with my setup ever since I tried to fix the blue-people problem with adobe flash (namely, that the latest and last version of flash has color layers swapped unless you enable hardware acceleration and export "VDPAU_NVIDIA_NO_OVERLAY=1"). Ever since, I have consistent problems with EQ overflow: the screen starts flickering, then the X server hits 100% CPU, and the system freezes (or X is nice and spares me a hard reboot by just crashing). My /var/log/Xorg.0.log is full of stuff like this:
| Code: | [306171.113] [mi] EQ overflowing. Additional events will be discarded until existing events are processed.
[306171.138]
[306171.138] Backtrace:
[306171.182] 0: /usr/bin/X (xorg_backtrace+0x34) [0x565d74]
[306171.182] 1: /usr/bin/X (mieqEnqueue+0x263) [0x546d53]
[306171.182] 2: /usr/bin/X (0x400000+0x4a95c) [0x44a95c]
[306171.182] 3: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f332483e000+0x6130) [0x7f3324844130]
[306171.182] 4: /usr/bin/X (0x400000+0x72047) [0x472047]
[306171.182] 5: /usr/bin/X (0x400000+0x966ca) [0x4966ca]
[306171.182] 6: /lib64/libc.so.6 (0x7f332a1c0000+0x37720) [0x7f332a1f7720]
[306171.182] 7: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f3325387000+0x8edcd) [0x7f3325415dcd]
[306171.182] 8: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f3325387000+0x90985) [0x7f3325417985]
[306171.182] 9: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f3325387000+0x
fa449) [0x7f3325481449]
[306171.182] 10: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f3325387000+0xfeb73) [0x7f3325485b73]
[306171.182] 11: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f3325387000+0xeafd5) [0x7f3325471fd5]
[306171.182] 12: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f3325387000+0x523608) [0x7f33258aa608]
[306171.182] 13: /usr/bin/X (0x400000+0xf6536) [0x4f6536]
[306171.182] 14: /usr/lib64/xorg/modules/drivers/nvidia_drv.so (0x7f3325387000+0x5273d1) [0x7f33258ae3d1]
[306171.182] 15: /usr/bin/X (0x400000+0xef644) [0x4ef644]
[306171.182] 16: /usr/bin/X (0x400000+0x37019) [0x437019]
[306171.182] 17: /usr/bin/X (0x400000+0x2658a) [0x42658a]
[306171.182] 18: /lib64/libc.so.6 (__libc_start_main+0xed) [0x7f332a1e460d]
[306171.182] 19: /usr/bin/X (0x400000+0x2687d) [0x42687d]
[306171.182]
[306171.182] [mi] These backtraces from mieqEnqueue may point to a culprit higher up the stack.
[306171.182] [mi] mieq is *NOT* the cause. It is a victim.
[306172.638] [mi] Increasing EQ size to 1024 to prevent dropped events.
[306172.638] [mi] EQ processing has resumed after 51 dropped events.
[306172.638] [mi] This may be caused my a misbehaving driver monopolizing the server's resources.
|
Also, dmesg is full of stuff like this:
| Code: | INFO: task kworker/0:5:7085 blocked for more than 120 seconds.
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
kworker/0:5 D 0000000000000001 0 7085 2 0x00000000
ffff8800130aa6d0 0000000000000046 ffff88012a865390 0000000000011d40
0000000000004000 ffff8800cf8d3fd8 0000000000000002 0000000000000000
ffff88012fffc680 0000000000000246 0000000000000001 00000000000003e8
Call Trace:
[<ffffffff811d06c0>] ? cpumask_next_and+0x28/0x34
[<ffffffff814b30ba>] ? schedule_timeout+0x23/0x217
[<ffffffff810a2390>] ? __alloc_pages_nodemask+0x112/0x79a
[<ffffffff814b3c17>] ? __down+0x66/0x93
[<ffffffff8104732a>] ? down+0x25/0x34
[<ffffffffa1eb418e>] ? os_acquire_mutex+0x32/0x36 [nvidia]
[<ffffffffa1e83425>] ? _nv014474rm+0x1b/0x20 [nvidia]
[<ffffffffa17dcf4e>] ? _nv016064rm+0xe7/0x17f [nvidia]
[<ffffffffa1d559fa>] ? _nv015041rm+0x28a/0x3bc [nvidia]
[<ffffffffa1e8975f>] ? _nv001074rm+0x310/0xc1b [nvidia]
[<ffffffffa1e8e020>] ? rm_execute_work_item+0x51/0x138 [nvidia]
[<ffffffffa1eb47f9>] ? nv_printf+0x7f/0x7f [nvidia]
[<ffffffffa1eb4836>] ? os_execute_work_item+0x3d/0x6e [nvidia]
[<ffffffff8103f582>] ? process_one_work+0x1cd/0x339
[<ffffffff8103fb32>] ? worker_thread+0x157/0x211
[<ffffffff8103f9db>] ? manage_workers.isra.23+0x158/0x158
[<ffffffff810434b8>] ? kthread+0x7d/0x85
[<ffffffff814bc254>] ? kernel_thread_helper+0x4/0x10
[<ffffffff8104343b>] ? kthread_freezable_should_stop+0x4d/0x4d
[<ffffffff814bc250>] ? gs_change+0xb/0xb
NVRM: Xid (0000:01:00): 8, Channel 00000001
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: Xid (0000:01:00): 8, Channel 00000001
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context
NVRM: os_schedule: Attempted to yield the CPU while in atomic or interrupt context |
kernel is 3.5.0-gentoo, nvidia-drivers is 290.59-r1. I cannot use the 3xx nvidia-drivers: the X server lasts maybe five minutes before crashing out.
Are any of these problems familiar? Is there any way to stop having the nvidia driver be so unstable? Are there workarounds?
Cheers,
EE |
|
Multimedia
