Bug#689368: Mouse and keyboard freeze on Ivy Bridge platform
Hi, Alan Stern a écrit : In addition to what Sarah said, it's possible that your problem is related to the fact that the keyboard and mouse operate at low speed. If you connected them through a hub then that hub would communicate with the internal hub at high speed, not low speed. I had no freeze since I bought wireless keyboard and mouse ten days ago. Obviously, I am satisfied by this happy end but I am surprised too because my previous keyboard and mouse still work fine with older hardware... Jonathan, as far as I am concerned, you can close this bug! A big thanks to all of you. Sebastien -- Sébastien Dinot, sebastien.di...@free.fr http://sebastien.dinot.free.fr/ Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer ! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121017201312.ga17...@dinot.net
Bug#689368: Mouse and keyboard freeze on Ivy Bridge platform
Alan Stern a écrit : The log file shows lots and lots of low-level communication errors. They could be caused by bad cabling or by bad USB hardware in your computer. It's unlikely that they were caused by the mouse or keyboard, because the log shows errors for both of them starting at exactly the same times. In my humble opinion, this issue is not caused by a bad USB hardware because I am encountering it with two different motherboards (MSI Z77A-G43 and ASUS P8Z77-V LX), both with an uptodate BIOS. May be it is caused by a bad cabling but my mouse and my keyboard worked fine with my previous PC. They are connected to USB2 ports in both cases. But to clear up this point, I will try new mouse and keyboard. A last question: if it is a cable failure, why does it disappear temporarily when I unload then reload the module? I do not have deep experience and knowledge of hardware, may be there is a rational explanation to it. You could try getting a USB-2 hub and attaching your mouse and keyboard through the hub. That might help ... or it might not. Sorry, I do not understand the aim of this operation. Could you explain me it? Thanks for your help, Sébastien -- Sébastien Dinot, sebastien.di...@free.fr http://sebastien.dinot.free.fr/ Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer ! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121004213606.ga8...@dinot.net
Bug#689368: Mouse and keyboard freeze on Ivy Bridge platform
Jonathan Nieder a écrit : Presumably removing and replugging the mouse doesn't help. No. Does unloading and reloading the USB driver (modprobe -r ehci_hcd modprobe ehci_hcd) have any effect? I never tried it. I will test it the next time. Did these machines always behave this way, or is this a regression? Is the 2.6.32.y kernel from squeeze also affected? It is not a regression, I encountered this bug from the first day. If I am not mistaken, I can not try 2.6 Linux kernel because the Ivy Bridge chipset is supported starting from 3.2 Linux kernel. Sébastien -- Sébastien Dinot, sebastien.di...@free.fr http://sebastien.dinot.free.fr/ Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer ! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121002213239.ga9...@dinot.net
Bug#689368: Mouse and keyboard freeze on Ivy Bridge platform
Jonathan Nieder a écrit : Does unloading and reloading the USB driver (modprobe -r ehci_hcd modprobe ehci_hcd) have any effect? Good point! Keyboard and mouse work again after these commands. Once again, I found the following event in the kern.log file: Oct 3 01:11:33 hector kernel: [ 4016.352234] usb 2-1.5: USB disconnect, device number 10 Oct 3 01:11:33 hector kernel: [ 4016.558658] usb 2-1.5: new low-speed USB device number 11 using ehci_hcd Oct 3 01:11:33 hector kernel: [ 4016.657061] usb 2-1.5: New USB device found, idVendor=045e, idProduct=00a4 Oct 3 01:11:33 hector kernel: [ 4016.657066] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Oct 3 01:11:33 hector kernel: [ 4016.657069] usb 2-1.5: Product: Microsoft(R) Compact Optical Mouse Oct 3 01:11:33 hector kernel: [ 4016.657071] usb 2-1.5: Manufacturer: Microsoft Oct 3 01:11:33 hector kernel: [ 4016.662142] input: Microsoft Microsoft(R) Compact Optical Mouse as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input19 Oct 3 01:11:33 hector kernel: [ 4016.662536] hid-generic 0003:045E:00A4.0009: input,hidraw0: USB HID v1.10 Mouse [Microsoft Microsoft(R) Compact Optical Mouse] on usb-:00:1d.0-1.5/input0 And the freeze occured at 01:11:33 (more or less few seconds by my watch). Sébastien -- Sébastien Dinot, sebastien.di...@free.fr http://sebastien.dinot.free.fr/ Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer ! -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121002233236.ga5...@dinot.net
Bug#689368: linux-image-3.5-trunk-amd64: Mouse and keyboard freeze on Ivy Bridge platform
Package: src:linux Version: 3.5.2-1~experimental.1 Severity: critical Justification: breaks the whole system Hi, I am encountering random keyboard and mouse freezes which can only be resolved by a hard reset (push the power button on the computer case). I have this frequent and irritating issue with two differents Ivy Bridge platforms: 1. Processor: Intel Core i5 3450 (IGP HD 2500) Motherboard: MSI Z77A-G43 (with uptodate BIOS) 2. Processor: Intel Core i5 3570K (IGP HD 4000) Motherboard: ASUS P8Z77-V LX (with uptodate BIOS) I tried these platforms: - with both the IGP and a discrete graphic card (MSI N520GT) using free drivers (Intel and Nouveau) - with several Linux kernels: * linux-image-3.2.0-3-amd64 (testing) * linux-image-3.4-trunk-amd64 (experimental) * linux-image-3.5-trunk-amd64 (experimental) - with both testing and unstable uptodate Debian distributions. I can't work two hours without keyboard and mouse freeze. Sometimes, these systems freeze three or four times an hour! :( Except in rare cases, the system is alive. I can open a remote SSH session and if I push the power button (on the computer case), the logout dialog appears. I can not relate these freezes to a special software, task or action but they always happen when I move the mouse and I never encountered such issue throughout a remote SSH connection. In attachment, you will find the dmesg output dumped (through a remote SSH connection) after the latest freeze and the kernel log file. The last log before a freeze is always like this: [ 8276.625165] usb 2-1.5: USB disconnect, device number 8 [ 8276.830839] usb 2-1.5: new low-speed USB device number 9 using ehci_hcd [ 8276.928992] usb 2-1.5: New USB device found, idVendor=045e, idProduct=00a4 [ 8276.928997] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 8276.928999] usb 2-1.5: Product: Microsoft(R) Compact Optical Mouse [ 8276.929001] usb 2-1.5: Manufacturer: Microsoft [ 8276.934076] input: Microsoft Microsoft(R) Compact Optical Mouse as /devices/pci:00/:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input17 [ 8276.934434] hid-generic 0003:045E:00A4.0007: input,hidraw0: USB HID v1.10 Mouse [Microsoft Microsoft(R) Compact Optical Mouse] on usb-:00:1d.0-1.5/input0 Of course, I did not disconnect the mouse or shake its USB cable. :( Sebastien -- Package-specific info: ** Version: Linux version 3.5-trunk-amd64 (Debian 3.5.2-1~experimental.1) (debian-kernel@lists.debian.org) (gcc version 4.6.3 (Debian 4.6.3-1) ) #1 SMP Mon Aug 20 04:17:46 UTC 2012 ** Command line: BOOT_IMAGE=/boot/vmlinuz-3.5-trunk-amd64 root=UUID=103f96e1-a3b8-42ab-9424-d4ba3e58f256 ro quiet ** Not tainted ** Kernel log: [1.361691] [drm] nouveau :01:00.0: acceleration disabled by default, pass noaccel=0 to force enable [1.363243] [drm] nouveau :01:00.0: Checking PRAMIN for VBIOS [1.364647] microcode: CPU2 sig=0x306a9, pf=0x2, revision=0x12 [1.365822] microcode: CPU3 sig=0x306a9, pf=0x2, revision=0x12 [1.366992] microcode: Microcode Update Driver: v2.00 tig...@aivazian.fsnet.co.uk, Peter Oruba [1.367457] kvm: disabled by bios [1.438427] [drm] nouveau :01:00.0: ... appears to be valid [1.438429] [drm] nouveau :01:00.0: Using VBIOS from PRAMIN [1.438430] [drm] nouveau :01:00.0: BIT BIOS found [1.438432] [drm] nouveau :01:00.0: Bios version 75.19.36.00 [1.438433] [drm] nouveau :01:00.0: TMDS table version 2.0 [1.438593] [drm] nouveau :01:00.0: MXM: no VBIOS data, nothing to do [1.438594] [drm] nouveau :01:00.0: DCB version 4.0 [1.438596] [drm] nouveau :01:00.0: DCB outp 00: 02000300 [1.438597] [drm] nouveau :01:00.0: DCB outp 01: 01000302 00020030 [1.438598] [drm] nouveau :01:00.0: DCB outp 02: 02011362 00020010 [1.438607] [drm] nouveau :01:00.0: DCB outp 03: 04022310 [1.438608] [drm] nouveau :01:00.0: DCB conn 00: 1030 [1.438609] [drm] nouveau :01:00.0: DCB conn 01: 2161 [1.438610] [drm] nouveau :01:00.0: DCB conn 02: 0200 [1.438613] [drm] nouveau :01:00.0: Parsing VBIOS init table 0 at offset 0x7383 [1.442855] Refined TSC clocksource calibration: 3410.013 MHz. [1.442859] Switching to clocksource tsc [1.488337] [drm] nouveau :01:00.0: 0x799B: Condition still not met after 20ms, skipping following opcodes [1.488348] [drm] nouveau :01:00.0: Parsing VBIOS init table 1 at offset 0x7A04 [1.495182] [drm] nouveau :01:00.0: Parsing VBIOS init table 2 at offset 0x89B4 [1.495183] [drm] nouveau :01:00.0: Parsing VBIOS init table 3 at offset 0x89B5 [1.495226] [drm] nouveau :01:00.0: Parsing VBIOS init table 4 at offset 0x8AA6 [
