linux-kernel - Re: USB Mouse Disconnect Kernel-3.7/3.8

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20130319123157.48edba0feba48bcb2b5c30c9@comcast.net>
Date:	Tue, 19 Mar 2013 12:31:57 -0400
From:	Frank Peters <frank.peters@...cast.net>
To:	Jiri Kosina <jkosina@...e.cz>
Cc:	linux-kernel@...r.kernel.org, linux-usb@...r.kernel.org
Subject: Re: USB Mouse Disconnect Kernel-3.7/3.8

This message is a repost.  I did not include the complete original message
in my initial reply, and I am doing so now.

> On Mon, 11 Mar 2013, Frank Peters wrote:
> 
> > When I boot my x64 Linux system to the console a continuous series
> > of "USB disconnect/reconnect" messages appears in the kernel log.
> > The disconnect/reconnect messages concern the USB mouse:
> > 
> > usb 1-1.3: USB disconnect, device number N
> > usb 1-1.3: new low-speed USB device number N+1 using ehci-pci
> > input: Microsoft  Microsoft Basic Optical Mouse v2.0  as /devices/pci0000:00/0000:00:1a.0 usb1/1-1/1-1.3/1-1.3:1.0/input/input5
> > hid-generic 0003:045E:00CB.0006: input: USB HID v1.11 Mouse [Microsoft  Microsoft Basic Optical Mouse v2.0 ] on usb-0000:00:1a.0-1.3/input0
> > ....
> > 
> > These "USB disconnect/reconnect" messages will repeat roughly every 40 seconds
> > with the device number "N" increasing to "N+1" each time.
> > 
> > The interesting thing about this behavior is that I can stop the messages,
> > and presumably the disconnects, by starting the General Purpose Mouse (gpm)
> > server:
> > 
> > gpm -m /dev/input/mice -t imps2
> > 
> > If I then terminate the gpm server, the USB disconnect/reconnect messages
> > will start to occur once again.
> > 
> > The USB disconnects also stop when I start the graphical X server.
> > 
> > It would seem that if nothing is "grabbing" the USB mouse (i.e. gpm or X)
> > then the kernel somehow automatically disconnects it.
> > 
> > My system has the USB built in to the kernel (no modules).
> > 
> > The motherboard I use is Intel DP55KG which has the P55 Express
> > chipset to control the USB.
> > 
> > I've seen this behavior on the current kernel-3.8.x and also
> > on the previous kernel-3.7.  I have not tested anything earlier.
> > 
> > Please CC to frank.peters@...cast.net as I am not subscribed to
> > the list.
> 
> [ adding linux-usb@ to CC ]
> 
> Do you have USB autosuspend enabled on that device?
> 

The CONFIG_USB_SUSPEND, which controls USB autosuspend, is not available
to me during kernel configuration because I do not enable "Run-time PM core
functionality" (PM_RUNTIME).

Based on this, I would assume that USB autosuspend is not enabled.

Frank Peters
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/