I've had a problem with X in f12 or some time that sees the mouse pointer freezing. I'm now having the same issue in f11.
I'm happy to file a bug in bugzilla, but I'm hoping someone mught be able to point me in the right direction.
After some time after running X the mouse pointer will freeze. Switching to a VT doesn't help, but I can use the keyboard to close apps and do a little navigation. Also pushing the power button will see a dialog to allow me to shutdown, suspend, etc. I can suspend and resume and this fixes the problem.
I'm not however convinced that it's an X bug. I think it might be related to bluetooth (I believe that my mouse and keyboard have something to do with bluetooth on this laptop) and that the suspend resume cycle restarts bluetooth and fixes the problem.
Could this be right. Or should I just file against X.
Rodd
[rodd@moose ~]$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.3 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 4 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB Controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB Controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation ICH9M/M-E SATA AHCI Controller (rev 03) 00:1f.3 SMBus: Intel Corporation 82801I (ICH9 Family) SMBus Controller (rev 03) 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility HD 3670 01:00.1 Audio device: ATI Technologies Inc RV635 Audio device [Radeon HD 3600 Series] 04:00.0 Network controller: Intel Corporation PRO/Wireless 5300 AGN [Shiloh] Network Connection 08:00.0 Ethernet controller: Broadcom Corporation NetLink BCM5784M Gigabit Ethernet PCIe (rev 10) 09:01.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05) 09:01.1 SD Host controller: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22) 09:01.2 System peripheral: Ricoh Co Ltd R5C843 MMC Host Controller (rev 12) 09:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12) 09:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff) [rodd@moose ~]$ lsusb Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 004: ID 05ca:18a1 Ricoh Co., Ltd Bus 001 Device 003: ID 2040:1801 Hauppauge Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 003: ID 413c:8157 Dell Computer Corp. Bus 003 Device 004: ID 413c:8158 Dell Computer Corp. Bus 003 Device 002: ID 0a5c:4500 Broadcom Corp. Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
On Thu, 2009-09-10 at 19:29 +1000, Rodd Clarkson wrote:
I've had a problem with X in f12 or some time that sees the mouse pointer freezing. I'm now having the same issue in f11.
I'm happy to file a bug in bugzilla, but I'm hoping someone mught be able to point me in the right direction.
After some time after running X the mouse pointer will freeze. Switching to a VT doesn't help, but I can use the keyboard to close apps and do a little navigation. Also pushing the power button will see a dialog to allow me to shutdown, suspend, etc. I can suspend and resume and this fixes the problem.
I'm not however convinced that it's an X bug. I think it might be related to bluetooth (I believe that my mouse and keyboard have something to do with bluetooth on this laptop) and that the suspend resume cycle restarts bluetooth and fixes the problem.
You could verify this with "DISPLAY=:0 xinput list" when the mouse pointer stops. If you don't see the bluetooth mouse in the list, then the kernel is refusing to re-plug it right. If you _do_ see the mouse in the list, then X is confused somewhere.
Does keyboard navigation still work when this happens? Does alt-tab switch windows, etc.
- ajax
On Tue, 2009-09-15 at 09:42 -0400, Adam Jackson wrote:
On Thu, 2009-09-10 at 19:29 +1000, Rodd Clarkson wrote:
I've had a problem with X in f12 or some time that sees the mouse pointer freezing. I'm now having the same issue in f11.
I'm happy to file a bug in bugzilla, but I'm hoping someone mught be able to point me in the right direction.
After some time after running X the mouse pointer will freeze. Switching to a VT doesn't help, but I can use the keyboard to close apps and do a little navigation. Also pushing the power button will see a dialog to allow me to shutdown, suspend, etc. I can suspend and resume and this fixes the problem.
I'm not however convinced that it's an X bug. I think it might be related to bluetooth (I believe that my mouse and keyboard have something to do with bluetooth on this laptop) and that the suspend resume cycle restarts bluetooth and fixes the problem.
You could verify this with "DISPLAY=:0 xinput list" when the mouse pointer stops. If you don't see the bluetooth mouse in the list, then the kernel is refusing to re-plug it right. If you _do_ see the mouse in the list, then X is confused somewhere.
Does keyboard navigation still work when this happens? Does alt-tab switch windows, etc.
I'll give this a try when I next have a lock-up.
I'm pretty sure that this problem only occurs before I've cycled through a suspend-resume.
I suspect bluetooth issues because the bluetooth icon appears until I do the suspend-resume cycle and then the icon doesn't appear and bluetooth doesn't work (but the mouse does).
Keyboard navigation still works, and I can switch to a VT too.
R.
On Wed, 2009-09-16 at 21:15 +1000, Rodd Clarkson wrote:
You could verify this with "DISPLAY=:0 xinput list" when the mouse pointer stops. If you don't see the bluetooth mouse in the list, then the kernel is refusing to re-plug it right. If you _do_ see the mouse in the list, then X is confused somewhere.
Does keyboard navigation still work when this happens? Does alt-tab switch windows, etc.
I'll give this a try when I next have a lock-up.
I'm pretty sure that this problem only occurs before I've cycled through a suspend-resume.
I suspect bluetooth issues because the bluetooth icon appears until I do the suspend-resume cycle and then the icon doesn't appear and bluetooth doesn't work (but the mouse does).
Keyboard navigation still works, and I can switch to a VT too.
Ajax
Alright, I've had this happen after a suspend-resume cycle, and it appears that it's not bluetooth related as the output of xinput is the same before as after.
Do you want me to file a bug on this and then work from there?
Rodd
On Fri, 2009-09-18 at 15:11 +1000, Rodd Clarkson wrote:
On Wed, 2009-09-16 at 21:15 +1000, Rodd Clarkson wrote:
I'm pretty sure that this problem only occurs before I've cycled through a suspend-resume.
I suspect bluetooth issues because the bluetooth icon appears until I do the suspend-resume cycle and then the icon doesn't appear and bluetooth doesn't work (but the mouse does).
Keyboard navigation still works, and I can switch to a VT too.
Alright, I've had this happen after a suspend-resume cycle, and it appears that it's not bluetooth related as the output of xinput is the same before as after.
Do you want me to file a bug on this and then work from there?
Yeah. Likely a kernel bug. Try running something like evtest on the pointer device after resume and see if you get events at all:
http://people.freedesktop.org/~ajax/evtest.c
If you get events that way, then X is confused; if you don't, then the kernel driver is confused.
- ajax
On Fri, Sep 18, 2009 at 11:01:25AM -0400, Adam Jackson wrote:
On Fri, 2009-09-18 at 15:11 +1000, Rodd Clarkson wrote:
On Wed, 2009-09-16 at 21:15 +1000, Rodd Clarkson wrote:
I'm pretty sure that this problem only occurs before I've cycled through a suspend-resume.
I suspect bluetooth issues because the bluetooth icon appears until I do the suspend-resume cycle and then the icon doesn't appear and bluetooth doesn't work (but the mouse does).
Keyboard navigation still works, and I can switch to a VT too.
Alright, I've had this happen after a suspend-resume cycle, and it appears that it's not bluetooth related as the output of xinput is the same before as after.
Do you want me to file a bug on this and then work from there?
Yeah. Likely a kernel bug. Try running something like evtest on the pointer device after resume and see if you get events at all:
http://people.freedesktop.org/~ajax/evtest.c
If you get events that way, then X is confused; if you don't, then the kernel driver is confused.
I saw it happen a few days ago too. Same circumstance. Back from resume, keyboard worked, but no mouse. Flipping to tty2, and then back to X made the mouse work again. Didn't happen again when I tried to repeat it.
Dave