Debian Bug report logs - #689368
linux-image-3.5-trunk-amd64: Mouse and keyboard freeze on Ivy Bridge platform

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Sébastien Dinot <sebastien.dinot@free.fr>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: linux-image-3.5-trunk-amd64: Mouse and keyboard freeze on Ivy Bridge platform

Date: Tue, 02 Oct 2012 00:38:41 +0200

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/pci0000:00/0000: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-0000: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 0000:01:00.0: acceleration disabled by default, pass noaccel=0 to force enable
[    1.363243] [drm] nouveau 0000: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 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[    1.367457] kvm: disabled by bios
[    1.438427] [drm] nouveau 0000:01:00.0: ... appears to be valid
[    1.438429] [drm] nouveau 0000:01:00.0: Using VBIOS from PRAMIN
[    1.438430] [drm] nouveau 0000:01:00.0: BIT BIOS found
[    1.438432] [drm] nouveau 0000:01:00.0: Bios version 75.19.36.00
[    1.438433] [drm] nouveau 0000:01:00.0: TMDS table version 2.0
[    1.438593] [drm] nouveau 0000:01:00.0: MXM: no VBIOS data, nothing to do
[    1.438594] [drm] nouveau 0000:01:00.0: DCB version 4.0
[    1.438596] [drm] nouveau 0000:01:00.0: DCB outp 00: 02000300 00000000
[    1.438597] [drm] nouveau 0000:01:00.0: DCB outp 01: 01000302 00020030
[    1.438598] [drm] nouveau 0000:01:00.0: DCB outp 02: 02011362 00020010
[    1.438607] [drm] nouveau 0000:01:00.0: DCB outp 03: 04022310 00000000
[    1.438608] [drm] nouveau 0000:01:00.0: DCB conn 00: 00001030
[    1.438609] [drm] nouveau 0000:01:00.0: DCB conn 01: 00002161
[    1.438610] [drm] nouveau 0000:01:00.0: DCB conn 02: 00000200
[    1.438613] [drm] nouveau 0000: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 0000:01:00.0: 0x799B: Condition still not met after 20ms, skipping following opcodes
[    1.488348] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 1 at offset 0x7A04
[    1.495182] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 2 at offset 0x89B4
[    1.495183] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 3 at offset 0x89B5
[    1.495226] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table 4 at offset 0x8AA6
[    1.495227] [drm] nouveau 0000:01:00.0: Parsing VBIOS init table at offset 0x8B0B
[    1.515053] [drm] nouveau 0000:01:00.0: 0x7330: Condition still not met after 20ms, skipping following opcodes
[    1.516843] [TTM] Zone  kernel: Available graphics memory: 4076256 kiB
[    1.516845] [TTM] Zone   dma32: Available graphics memory: 2097152 kiB
[    1.516854] [TTM] Initializing pool allocator
[    1.516856] [TTM] Initializing DMA pool allocator
[    1.516864] [drm] nouveau 0000:01:00.0: Detected 1024MiB VRAM (DDR3)
[    1.516868] mtrr: type mismatch for e8000000,8000000 old: write-back new: write-combining
[    1.516876] [drm] nouveau 0000:01:00.0: 512 MiB GART (aperture)
[    1.519840] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010).
[    1.519840] [drm] No driver support for vblank timestamp query.
[    1.525502] [drm] nouveau 0000:01:00.0: 2 available performance level(s)
[    1.525504] [drm] nouveau 0000:01:00.0: 1: core 270MHz shader 540MHz memory 405MHz voltage 900mV
[    1.525505] [drm] nouveau 0000:01:00.0: 3: core 810MHz shader 1620MHz memory 667MHz voltage 1040mV
[    1.525507] [drm] nouveau 0000:01:00.0: c: core 270MHz shader 540MHz memory 405MHz voltage 900mV
[    1.575711] [drm] nouveau 0000:01:00.0: allocated 1680x1050 fb: 0xe0000, bo ffff880213215c00
[    1.575784] fbcon: nouveaufb (fb0) is primary device
[    1.586778] usb 2-1.5: new low-speed USB device number 3 using ehci_hcd
[    1.641320] Console: switching to colour frame buffer device 210x65
[    1.646338] fb0: nouveaufb frame buffer device
[    1.646339] drm: registered panic notifier
[    1.646341] [drm] Initialized nouveau 1.0.0 20120316 for 0000:01:00.0 on minor 0
[    1.684577] usb 2-1.5: New USB device found, idVendor=045e, idProduct=00a4
[    1.684581] usb 2-1.5: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.684584] usb 2-1.5: Product: Microsoft(R) Compact Optical Mouse
[    1.684586] usb 2-1.5: Manufacturer: Microsoft
[    1.701726] usbcore: registered new interface driver usbhid
[    1.701728] usbhid: USB HID core driver
[    1.704380] input: Microsoft Microsoft(R) Compact Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.5/2-1.5:1.0/input/input4
[    1.704592] hid-generic 0003:045E:00A4.0001: input,hidraw0: USB HID v1.10 Mouse [Microsoft Microsoft(R) Compact Optical Mouse] on usb-0000:00:1d.0-1.5/input0
[    1.758756] usb 2-1.6: new low-speed USB device number 4 using ehci_hcd
[    1.857281] usb 2-1.6: New USB device found, idVendor=046d, idProduct=c315
[    1.857286] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[    1.857289] usb 2-1.6: Product: Logitech USB Keyboard
[    1.857291] usb 2-1.6: Manufacturer: Logitech
[    1.861235] input: Logitech Logitech USB Keyboard as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/input/input5
[    1.861474] hid-generic 0003:046D:C315.0002: input,hidraw1: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on usb-0000:00:1d.0-1.6/input0
[    2.411075] input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
[    2.411228] input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
[    2.411378] input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
[    2.411528] input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
[    2.411678] input: HDA Intel PCH Line Out as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
[    2.412327] hda_intel: Disabling MSI
[    2.412339] hda-intel: 0000:01:00.1: Handle VGA-switcheroo audio client
[    2.869559] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input11
[    2.869709] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input12
[    3.090832] Adding 5858292k swap on /dev/sda1.  Priority:-1 extents:1 across:5858292k SS
[    3.106022] EXT4-fs (sda2): re-mounted. Opts: (null)
[    3.135620] EXT4-fs (sda2): re-mounted. Opts: errors=remount-ro
[    3.246760] fuse init (API version 7.19)
[    3.256232] loop: module loaded
[    3.966351] kjournald starting.  Commit interval 5 seconds
[    3.967017] EXT3-fs (dm-2): using internal journal
[    3.967021] EXT3-fs (dm-2): mounted filesystem with ordered data mode
[    4.583816] Bluetooth: Core ver 2.16
[    4.583828] NET: Registered protocol family 31
[    4.583829] Bluetooth: HCI device and connection manager initialized
[    4.583830] Bluetooth: HCI socket layer initialized
[    4.583830] Bluetooth: L2CAP socket layer initialized
[    4.583833] Bluetooth: SCO socket layer initialized
[    4.589378] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.589380] Bluetooth: BNEP filters: protocol multicast
[    4.590015] Bluetooth: RFCOMM TTY layer initialized
[    4.590017] Bluetooth: RFCOMM socket layer initialized
[    4.590017] Bluetooth: RFCOMM ver 1.11
[    4.609024] lp: driver loaded but no devices found
[    4.613700] ppdev: user-space parallel port driver
[    4.752574] r8169 0000:03:00.0: eth1: link down
[    4.752598] r8169 0000:03:00.0: eth1: link down
[    4.752975] IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready
[    6.340954] r8169 0000:03:00.0: eth1: link up
[    6.341273] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready

** Model information
sys_vendor: System manufacturer
product_name: System Product Name
product_version: System Version
chassis_vendor: Chassis Manufacture
chassis_version: Chassis Version
bios_vendor: American Megatrends Inc.
bios_version: 1201
board_vendor: ASUSTeK COMPUTER INC.
board_name: P8Z77-V LX
board_version: Rev X.0x

** Loaded modules:
parport_pc
ppdev
lp
parport
rfcomm
bnep
bluetooth
cpufreq_stats
cpufreq_conservative
cpufreq_userspace
cpufreq_powersave
ext3
jbd
loop
fuse
dm_crypt
snd_hda_codec_hdmi
hid_generic
usbhid
hid
snd_hda_codec_realtek
coretemp
snd_hda_intel
nouveau
snd_hda_codec
eeepc_wmi
asus_wmi
sparse_keymap
rfkill
snd_hwdep
snd_pcm
snd_page_alloc
mxm_wmi
kvm
snd_seq
snd_seq_device
acpi_cpufreq
evdev
snd_timer
mperf
snd
i2c_i801
microcode
ttm
drm_kms_helper
psmouse
drm
pcspkr
serio_raw
i2c_algo_bit
i2c_core
soundcore
wmi
lpc_ich
mfd_core
video
button
processor
ext4
crc16
jbd2
mbcache
dm_mod
sg
sd_mod
sr_mod
cdrom
crc_t10dif
crc32c_intel
ghash_clmulni_intel
ahci
libahci
xhci_hcd
aesni_intel
aes_x86_64
libata
scsi_mod
aes_generic
cryptd
ehci_hcd
thermal
fan
thermal_sys
r8169
mii
usbcore
usb_common

** PCI devices:
00:00.0 Host bridge [0600]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor DRAM Controller [8086:0150] (rev 09)
	Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: <access denied>

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor PCI Express Root Port [8086:0151] (rev 09) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
	I/O behind bridge: 0000e000-0000efff
	Memory behind bridge: f6000000-f70fffff
	Prefetchable memory behind bridge: 00000000e8000000-00000000f1ffffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA+ MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:14.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB xHCI Host Controller [8086:1e31] (rev 04) (prog-if 30 [XHCI])
	Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 42
	Region 0: Memory at f7100000 (64-bit, non-prefetchable) [size=64K]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd

00:16.0 Communication controller [0780]: Intel Corporation 7 Series/C210 Series Chipset Family MEI Controller #1 [8086:1e3a] (rev 04)
	Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 5
	Region 0: Memory at f711a000 (64-bit, non-prefetchable) [size=16]
	Capabilities: <access denied>

00:1a.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #2 [8086:1e2d] (rev 04) (prog-if 20 [EHCI])
	Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 23
	Region 0: Memory at f7118000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: <access denied>
	Kernel driver in use: ehci_hcd

00:1b.0 Audio device [0403]: Intel Corporation 7 Series/C210 Series Chipset Family High Definition Audio Controller [8086:1e20] (rev 04)
	Subsystem: ASUSTeK Computer Inc. Device [1043:8445]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 44
	Region 0: Memory at f7110000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel

00:1c.0 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 1 [8086:1e10] (rev c4) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=02, subordinate=02, sec-latency=0
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1c.4 PCI bridge [0604]: Intel Corporation 7 Series/C210 Series Chipset Family PCI Express Root Port 5 [8086:1e18] (rev c4) (prog-if 00 [Normal decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: 0000d000-0000dfff
	Prefetchable memory behind bridge: 00000000f2100000-00000000f21fffff
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:1c.5 PCI bridge [0604]: Intel Corporation 82801 PCI Bridge [8086:244e] (rev c4) (prog-if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=00, secondary=04, subordinate=05, sec-latency=0
	Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>

00:1d.0 USB controller [0c03]: Intel Corporation 7 Series/C210 Series Chipset Family USB Enhanced Host Controller #1 [8086:1e26] (rev 04) (prog-if 20 [EHCI])
	Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin A routed to IRQ 23
	Region 0: Memory at f7117000 (32-bit, non-prefetchable) [size=1K]
	Capabilities: <access denied>
	Kernel driver in use: ehci_hcd

00:1f.0 ISA bridge [0601]: Intel Corporation Z77 Express Chipset LPC Controller [8086:1e44] (rev 04)
	Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Capabilities: <access denied>

00:1f.2 SATA controller [0106]: Intel Corporation 7 Series/C210 Series Chipset Family 6-port SATA Controller [AHCI mode] [8086:1e02] (rev 04) (prog-if 01 [AHCI 1.0])
	Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin B routed to IRQ 43
	Region 0: I/O ports at f070 [size=8]
	Region 1: I/O ports at f060 [size=4]
	Region 2: I/O ports at f050 [size=8]
	Region 3: I/O ports at f040 [size=4]
	Region 4: I/O ports at f020 [size=32]
	Region 5: Memory at f7116000 (32-bit, non-prefetchable) [size=2K]
	Capabilities: <access denied>
	Kernel driver in use: ahci

00:1f.3 SMBus [0c05]: Intel Corporation 7 Series/C210 Series Chipset Family SMBus Controller [8086:1e22] (rev 04)
	Subsystem: ASUSTeK Computer Inc. Device [1043:84ca]
	Control: I/O+ Mem+ BusMaster- SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap- 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Interrupt: pin C routed to IRQ 18
	Region 0: Memory at f7115000 (64-bit, non-prefetchable) [size=256]
	Region 4: I/O ports at f000 [size=32]

01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [GeForce GT 520] [10de:1040] (rev a1) (prog-if 00 [VGA controller])
	Subsystem: Micro-Star International Co., Ltd. Device [1462:2630]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 16
	Region 0: Memory at f6000000 (32-bit, non-prefetchable) [size=16M]
	Region 1: Memory at e8000000 (64-bit, prefetchable) [size=128M]
	Region 3: Memory at f0000000 (64-bit, prefetchable) [size=32M]
	Region 5: I/O ports at e000 [size=128]
	Expansion ROM at f7000000 [disabled] [size=512K]
	Capabilities: <access denied>
	Kernel driver in use: nouveau

01:00.1 Audio device [0403]: NVIDIA Corporation GF119 HDMI Audio Controller [10de:0e08] (rev a1)
	Subsystem: Micro-Star International Co., Ltd. Device [1462:2630]
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin B routed to IRQ 17
	Region 0: Memory at f7080000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel

03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller [10ec:8168] (rev 06)
	Subsystem: ASUSTeK Computer Inc. P8P67 and other motherboards [1043:8432]
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Interrupt: pin A routed to IRQ 41
	Region 0: I/O ports at d000 [size=256]
	Region 2: Memory at f2104000 (64-bit, prefetchable) [size=4K]
	Region 4: Memory at f2100000 (64-bit, prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: r8169

04:00.0 PCI bridge [0604]: ASMedia Technology Inc. ASM1083/1085 PCIe to PCI Bridge [1b21:1080] (rev 03) (prog-if 01 [Subtractive decode])
	Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
	Latency: 0, Cache Line Size: 64 bytes
	Bus: primary=04, secondary=05, subordinate=05, sec-latency=32
	Secondary status: 66MHz+ FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort+ <SERR- <PERR-
	BridgeCtl: Parity- SERR- NoISA- VGA- MAbort- >Reset- FastB2B-
		PriDiscTmr- SecDiscTmr- DiscTmrStat- DiscTmrSERREn-
	Capabilities: <access denied>


** USB devices:
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 003: ID 045e:00a4 Microsoft Corp. 
Bus 002 Device 004: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages linux-image-3.5-trunk-amd64 depends on:
ii  debconf [debconf-2.0]                   1.5.46
ii  initramfs-tools [linux-initramfs-tool]  0.108
ii  kmod                                    9-2
ii  linux-base                              3.5
ii  module-init-tools                       9-2

Versions of packages linux-image-3.5-trunk-amd64 recommends:
ii  firmware-linux-free  3.1

Versions of packages linux-image-3.5-trunk-amd64 suggests:
pn  debian-kernel-handbook  <none>
ii  grub-pc                 1.99-23
pn  linux-doc-3.5           <none>

Versions of packages linux-image-3.5-trunk-amd64 is related to:
pn  firmware-atheros        <none>
pn  firmware-bnx2           <none>
pn  firmware-bnx2x          <none>
pn  firmware-brcm80211      <none>
pn  firmware-intelwimax     <none>
pn  firmware-ipw2x00        <none>
pn  firmware-ivtv           <none>
pn  firmware-iwlwifi        <none>
pn  firmware-libertas       <none>
pn  firmware-linux          <none>
pn  firmware-linux-nonfree  <none>
pn  firmware-myricom        <none>
pn  firmware-netxen         <none>
pn  firmware-qlogic         <none>
pn  firmware-ralink         <none>
ii  firmware-realtek        0.36
pn  xen-hypervisor          <none>

-- debconf information:
* linux-image-3.5-trunk-amd64/postinst/missing-firmware-3.5-trunk-amd64:
  linux-image-3.5-trunk-amd64/postinst/ignoring-ramdisk:
  linux-image-3.5-trunk-amd64/prerm/removing-running-kernel-3.5-trunk-amd64: true
  linux-image-3.5-trunk-amd64/postinst/depmod-error-initrd-3.5-trunk-amd64: false

Message #14 received at 689368@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Sébastien Dinot <sebastien.dinot@free.fr>

Cc: 689368@bugs.debian.org

Subject: Re: Mouse and keyboard freeze on Ivy Bridge platform

Date: Mon, 1 Oct 2012 18:19:37 -0700

Hi Sébastien,

Sébastien Dinot wrote:

> 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).

Thanks for a clear report.  Presumably removing and replugging the
mouse doesn't help.  Does unloading and reloading the USB driver
("modprobe -r ehci_hcd && modprobe ehci_hcd") have any effect?

Did these machines always behave this way, or is this a regression?
Is the 2.6.32.y kernel from squeeze also affected?

(For my own reference: kernel log at [1].)

Jonathan

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=35;bug=689268

Message #19 received at 689368@bugs.debian.org (full text, mbox, reply):

From: Sébastien Dinot <sebastien.dinot@free.fr>

To: 689368@bugs.debian.org

Subject: Re: Mouse and keyboard freeze on Ivy Bridge platform

Date: Tue, 2 Oct 2012 23:32:40 +0200

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.dinot@free.fr
http://sebastien.dinot.free.fr/
Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer !

Message #24 received at 689368@bugs.debian.org (full text, mbox, reply):

From: Sébastien Dinot <sebastien.dinot@free.fr>

To: 689368@bugs.debian.org

Subject: Re: Mouse and keyboard freeze on Ivy Bridge platform

Date: Wed, 3 Oct 2012 01:32:36 +0200

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/pci0000:00/0000: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-0000: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.dinot@free.fr
http://sebastien.dinot.free.fr/
Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer !

Message #29 received at 689368@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Sébastien Dinot <sebastien.dinot@free.fr>

Cc: 689368@bugs.debian.org

Subject: Re: Mouse and keyboard freeze on Ivy Bridge platform

Date: Tue, 2 Oct 2012 17:24:07 -0700

Sébastien Dinot wrote:

> Good point! Keyboard and mouse work again after these commands.

Yay.

Ok, one more test and then we should take this upstream: if you set
the usbcore.autosuspend parameter to -1, does that change anything?

	# modprobe -r ehci_hcd; # or unplug mouse
	# echo -1 >/sys/module/usbcore/parameters/autosuspend
	# modprobe ehci_hcd; # or replace mouse

Either way, please send a summary to linux-usb@vger.kernel.org, cc-ing
Alan Stern <stern@rowland.harvard.edu>, linux-input@vger.kernel.org,
and either me or this bug log so we can track it.  Be sure to mention:

 - steps to reproduce, expected result, actual result, and how the
   difference indicates a bug (should be simple enough)

 - which kernels you have tested and what happened with each

 - how reproducible it is and how long it takes (e.g., within a couple
   of hours 80% of the time?)

 - full "dmesg" output from booting and reproducing it, as an
   attachment or link

 - a link to http://bugs.debian.org/689368 for the backstory

 - any other weird symptoms or observations

If we're lucky, someone upstream will have ideas for commands or
patches to try to further track down the cause.

Thanks again for your help and patience.

Good luck,
Jonathan

Message #34 received at 689368@bugs.debian.org (full text, mbox, reply):

From: sebastien.dinot@free.fr

To: linux-usb@vger.kernel.org

Cc: Alan Stern <stern@rowland.harvard.edu>, linux-input@vger.kernel.org, 689368@bugs.debian.org

Subject: Mouse and keyboard freeze on Ivy Bridge platform

Date: Wed, 3 Oct 2012 09:40:48 +0200 (CEST)

Hi,

I am encountering random keyboard and mouse freezes which can only be resolved by a hard reset (by pushing the power switch of 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 use Debian on these platforms and I tried several Linux kernels:
  
  * linux-image-3.2.0-3-amd64   (package from Debian testing)
  * linux-image-3.4-trunk-amd64 (package from Debian experimental)
  * linux-image-3.5-trunk-amd64 (package from Debian experimental)

I pointed out this bug to the Debian kernel team:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689368

The mouse and keyboard are both USB devices and it seems that the bug is coming from the echci-hcd module:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689368#24

I attached the dmesg output and the kern.log file to my first message to Debian:

* http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=35;filename=dmesg.20121001-231244;att=1;bug=689268
* http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=35;filename=kern.log.20121001-232320.gz;att=2;bug=689268

As mentioned to the Debian maintainers, this bug is very frequent (I had up to four freezes in an hour) and my PC are really unusable!

Can I run additional tests or give you additional informations to help you resolve this painful bug?

Sebastien

-- 
Sébastien Dinot, sebastien.dinot@free.fr
http://sebastien.dinot.free.fr/
Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer !

Message #39 received at 689368@bugs.debian.org (full text, mbox, reply):

From: Alan Stern <stern@rowland.harvard.edu>

To: sebastien.dinot@free.fr

Cc: linux-usb@vger.kernel.org, <linux-input@vger.kernel.org>, <689368@bugs.debian.org>

Subject: Re: Mouse and keyboard freeze on Ivy Bridge platform

Date: Wed, 3 Oct 2012 10:40:36 -0400 (EDT)

On Wed, 3 Oct 2012 sebastien.dinot@free.fr wrote:

> Hi,
> 
> I am encountering random keyboard and mouse freezes which can only be
> resolved by a hard reset (by pushing the power switch of the computer
> case).

> The mouse and keyboard are both USB devices and it seems that the bug
> is coming from the echci-hcd module:

> Can I run additional tests or give you additional informations to
> help you resolve this painful bug?

Please build a kernel with CONFIG_USB_DEBUG enabled.  When a hang
occurs, get a list of hang tasks (Alt-SysRq-w probably won't work, but
"echo w >/proc/sysrq-trigger" from a network login should).  Then send
the dmesg output

Alan Stern

Message #44 received at 689368@bugs.debian.org (full text, mbox, reply):

From: Sébastien Dinot <sebastien.dinot@free.fr>

To: Alan Stern <stern@rowland.harvard.edu>

Cc: linux-usb@vger.kernel.org, linux-input@vger.kernel.org, 689368@bugs.debian.org

Subject: Re: Mouse and keyboard freeze on Ivy Bridge platform

Date: Thu, 4 Oct 2012 21:43:47 +0200

[Message part 1 (text/plain, inline)]

Hi,

Alan Stern a écrit :
> Please build a kernel with CONFIG_USB_DEBUG enabled.

Done (3.6.0+ kernel)

> When a hang occurs, get a list of hang tasks (Alt-SysRq-w probably
> won't work, but "echo w >/proc/sysrq-trigger" from a network login
> should). Then send the dmesg output

The mouse and the keyboard froze four times tonight in half an hour :

- at 20:42:05
- at 20:53:44
- at 20:58:21
- at 21:15:19

But the SysRq command (executed through a remote SSH connection)
displayed nothing. :(

In attachment, you will find the kern.log file.

Sebastien

-- 
Sébastien Dinot, sebastien.dinot@free.fr
http://sebastien.dinot.free.fr/
Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer !

[kern.log.20121004-2123.gz (application/octet-stream, attachment)]

Message #49 received at 689368@bugs.debian.org (full text, mbox, reply):

From: Alan Stern <stern@rowland.harvard.edu>

To: Sébastien Dinot <sebastien.dinot@free.fr>

Cc: linux-usb@vger.kernel.org, <linux-input@vger.kernel.org>, <689368@bugs.debian.org>

Subject: Re: Mouse and keyboard freeze on Ivy Bridge platform

Date: Thu, 4 Oct 2012 16:59:42 -0400 (EDT)

On Thu, 4 Oct 2012, Sébastien Dinot wrote:

> Hi,
> 
> Alan Stern a écrit :
> > Please build a kernel with CONFIG_USB_DEBUG enabled.
> 
> Done (3.6.0+ kernel)
> 
> > When a hang occurs, get a list of hang tasks (Alt-SysRq-w probably
> > won't work, but "echo w >/proc/sysrq-trigger" from a network login
> > should). Then send the dmesg output
> 
> The mouse and the keyboard froze four times tonight in half an hour :
> 
> - at 20:42:05
> - at 20:53:44
> - at 20:58:21
> - at 21:15:19
> 
> But the SysRq command (executed through a remote SSH connection)
> displayed nothing. :(

No tasks were hung.  That's okay.

> In attachment, you will find the kern.log file.
 
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.
 
You could try getting a USB-2 hub and attaching your mouse and
keyboard through the hub.  That might help ... or it might not.

Alan Stern

Message #54 received at 689368@bugs.debian.org (full text, mbox, reply):

From: Sébastien Dinot <sebastien.dinot@free.fr>

To: Alan Stern <stern@rowland.harvard.edu>

Cc: linux-usb@vger.kernel.org, linux-input@vger.kernel.org, 689368@bugs.debian.org

Subject: Re: Mouse and keyboard freeze on Ivy Bridge platform

Date: Thu, 4 Oct 2012 23:36:06 +0200

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.dinot@free.fr
http://sebastien.dinot.free.fr/
Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer !

Message #59 received at 689368@bugs.debian.org (full text, mbox, reply):

From: Sarah Sharp <sarah.a.sharp@linux.intel.com>

To: Sébastien Dinot <sebastien.dinot@free.fr>

Cc: Alan Stern <stern@rowland.harvard.edu>, linux-usb@vger.kernel.org, linux-input@vger.kernel.org, 689368@bugs.debian.org

Subject: Re: Mouse and keyboard freeze on Ivy Bridge platform

Date: Thu, 4 Oct 2012 15:59:21 -0700

On Thu, Oct 04, 2012 at 11:36:06PM +0200, Sébastien Dinot wrote:
> 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?

Sometimes USB 2.0 hubs can handle more electrical noise from the host
controller, especially if they are externally powered by a wall-wort.
So introducing a USB 2.0 hub may fix the transfer errors caused by the
host.

BTW, do these Ivy Bridge systems have any (blue) USB 3.0 ports?  If so,
does your mouse and keyboard work under those ports?

Sarah Sharp

Message #64 received at 689368@bugs.debian.org (full text, mbox, reply):

From: Alan Stern <stern@rowland.harvard.edu>

To: Sébastien Dinot <sebastien.dinot@free.fr>

Cc: linux-usb@vger.kernel.org, <linux-input@vger.kernel.org>, <689368@bugs.debian.org>

Subject: Re: Mouse and keyboard freeze on Ivy Bridge platform

Date: Fri, 5 Oct 2012 10:23:02 -0400 (EDT)

On Thu, 4 Oct 2012, Sébastien Dinot wrote:

> 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.

Maybe they have something in common.  I don't know.  All I can do is
explain to you what your kernel log indicates -- and it strongly
indicates a hardware error.  Didn't you notice all those "detected 
XactErr" lines in the log?  There were more than 70000 of them!

> 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.

That's a good point, and a cable failure indeed seems less likely than
some of the other possibilities (such as a failure of the internal
"rate-matching" hub).

One possible explanation is that an occasional noisy signal (caused by
a slightly faulty cable) triggers a bug in the internal hub, and that
bug causes all communication to fail until the hub is reset when you
reload the module.

> > 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?

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.

Alan Stern

Message #69 received at 689368@bugs.debian.org (full text, mbox, reply):

From: Sébastien Dinot <sebastien.dinot@free.fr>

To: Alan Stern <stern@rowland.harvard.edu>

Cc: linux-usb@vger.kernel.org, linux-input@vger.kernel.org, 689368@bugs.debian.org

Subject: Re: Mouse and keyboard freeze on Ivy Bridge platform

Date: Wed, 17 Oct 2012 22:13:12 +0200

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.dinot@free.fr
http://sebastien.dinot.free.fr/
Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer !

Message #74 received at 689368@bugs.debian.org (full text, mbox, reply):

From: Jonathan Nieder <jrnieder@gmail.com>

To: Sébastien Dinot <sebastien.dinot@free.fr>

Cc: 689368@bugs.debian.org, Alan Stern <stern@rowland.harvard.edu>, linux-usb@vger.kernel.org, linux-input@vger.kernel.org

Subject: Re: Mouse and keyboard freeze on Ivy Bridge platform

Date: Wed, 17 Oct 2012 13:54:01 -0700

Hi Sébastien,

Sébastien Dinot wrote:
> 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...

Thanks, that's interesting.  If you have time to test connecting the
old keyboard and mouse through a hub, that would still be useful.

Jonathan

Message #79 received at 689368@bugs.debian.org (full text, mbox, reply):

From: Sébastien Dinot <sebastien.dinot@free.fr>

To: Jonathan Nieder <jrnieder@gmail.com>

Cc: 689368@bugs.debian.org, Alan Stern <stern@rowland.harvard.edu>, linux-usb@vger.kernel.org, linux-input@vger.kernel.org

Subject: Re: Mouse and keyboard freeze on Ivy Bridge platform

Date: Wed, 17 Oct 2012 23:12:02 +0200

Jonathan Nieder a écrit :
> Thanks, that's interesting.  If you have time to test connecting the
> old keyboard and mouse through a hub, that would still be useful.

Ok, I am going to ask for a hub to my friends and to test my hardware
through it.

Sebastien

-- 
Sébastien Dinot, sebastien.dinot@free.fr
http://sebastien.dinot.free.fr/
Ne goûtez pas au logiciel libre, vous ne pourriez plus vous en passer !

Send a report that this bug log contains spam.