From time to time, X hangs - all I can do is move the mouse. From another machine, I ssh in, connect to that process with gdb, and get this: (gdb) bt #0 0x00007f886a6d66ad in ?? () from /usr/lib64/xorg/modules/drivers/nvidia_drv.so #1 0x00007f886a6d82e0 in ?? () from /usr/lib64/xorg/modules/drivers/nvidia_drv.so #2 0x00007f886a7505e8 in ?? () from /usr/lib64/xorg/modules/drivers/nvidia_drv.so #3 0x00007f886a6c0dff in ?? () from /usr/lib64/xorg/modules/drivers/nvidia_drv.so #4 0x00000000004ca191 in xf86SetCursor () #5 0x00000000004c7ca4 in xf86CursorSetCursor () #6 0x000000000058722e in miPointerUpdateSprite () #7 0x0000000000587521 in miPointerDisplayCursor () #8 0x00000000004daed9 in CursorDisplayCursor () #9 0x0000000000513107 in AnimCurDisplayCursor () #10 0x0000000000445815 in CheckMotion () #11 0x000000000051e5c9 in ProcessOtherEvent () #12 0x000000000054abea in ProcessPointerEvent () #13 0x000000000057bd7e in mieqProcessDeviceEvent () #14 0x000000000057bde5 in mieqProcessInputEvents () #15 0x000000000047e7b9 in ProcessInputEvents () #16 0x0000000000430833 in UpdateCurrentTime () #17 0x00000000004e4d55 in SyncSendAlarmNotifyEvents () #18 0x00000000004e5000 in SyncAlarmTriggerFired () #19 0x00000000004e5395 in IdleTimeWakeupHandler () #20 0x000000000043b41a in WakeupHandler () #21 0x000000000059aa08 in WaitForSomething () #22 0x0000000000436ee2 in Dispatch () #23 0x00000000004249ba in main () It seems pretty consistent that it's inside xf86SetCursor. This happens once or twice a day. I've tried both the 290.* versions of nvidia-drivers available, it doesn't seem to make much difference. KDE 4.7.90, Qt 4.7.4
Use nvidia-bug-report.sh and send the results to linux-bugs@nvidia.com and post the log here as well. Reference this ticket in your e-mail to nvidia.
Created attachment 296669 [details] output from nvidia-bug-report.sh Thanks, I've sent the email with the file attached. Adding it here, too, as per request.
Please retest with the latest X and latest nvidia-drivers.
I'm now running nvidia-drivers 302.17 + xorg-server 1.12.2, and am no longer getting this issue. Thanks for the follow-up.
Good to hear.