From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id F3E2213877A for ; Thu, 14 Aug 2014 01:52:15 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6EA11E0D2E; Thu, 14 Aug 2014 01:52:07 +0000 (UTC) Received: from cdptpa-oedge-vip.email.rr.com (cdptpa-outbound-snat.email.rr.com [107.14.166.230]) by pigeon.gentoo.org (Postfix) with ESMTP id 59E3DE0B9A for ; Thu, 14 Aug 2014 01:52:06 +0000 (UTC) Received: from [142.196.222.217] ([142.196.222.217:49479] helo=basement.kutulu.org) by cdptpa-oedge03 (envelope-from ) (ecelerity 3.5.0.35861 r(Momo-dev:tip)) with ESMTP id 43/49-18475-5461CE35; Thu, 14 Aug 2014 01:52:05 +0000 Received: from localhost (basement.kutulu.org [127.0.0.1]) by basement.kutulu.org (Postfix) with ESMTP id 1EB80112008 for ; Wed, 13 Aug 2014 21:52:05 -0400 (EDT) X-Virus-Scanned: amavisd-new at kutulu.org Received: from basement.kutulu.org ([127.0.0.1]) by localhost (basement.kutulu.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1UlQGMjwIaOV for ; Wed, 13 Aug 2014 21:51:55 -0400 (EDT) Received: from PORPOISE (PORPOISE.kutulu.org [192.168.69.91]) by basement.kutulu.org (Postfix) with ESMTPSA id 06539112007 for ; Wed, 13 Aug 2014 21:51:54 -0400 (EDT) From: "Mike Edenfield" To: Subject: [gentoo-user] Intermittent USB device failures Date: Wed, 13 Aug 2014 21:52:00 -0400 Message-ID: <005d01cfb762$56aadcf0$040096d0$@kutulu.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 15.0 Content-Language: en-us Thread-Index: Ac+3YP0DsN/28N3gQwKsm8ma7I8Adw== X-RR-Connecting-IP: 107.14.168.142:25 X-Cloudmark-Score: 0 X-Archives-Salt: 6ca74c82-c6c9-49c9-9bed-89028e908f4f X-Archives-Hash: f43b1c212764f666eb2dde6db14f03b5 I've recently taken an old Windows XP system and rebuilt it to run Gentoo. Since then, I've been having issues using any type of USB input device (which is particularly bad, since it has no PS/2 input ports). After some indeterminate period of time, the input device simply stops responding. Typically, I can use the console for a few days at a time before the keyboard dies, but if I load up a GUI and start using the mouse it takes less than a few hours. I'm fairly sure this problem is USB-related, since I believe I've eliminated everything downstream of that: I've tried using both evdev and legacy mouse and keyboard drivers in both the kernel and X and all of them work the same way. evtest shows no activity from the device once it breaks, nor do the legacy /dev driver files. Most notably, removing and re-plugging the device doesn't register as a device attachment. If, for example, I take a working USB mouse and swap USB ports, I get this: [ 1219.418050] usb 2-8: USB disconnect, device number 3 [ 1225.258011] usb 2-7: new low-speed USB device number 4 using ohci-pci [ 1225.449627] usb 2-7: New USB device found, idVendor=046d, idProduct=c044 [ 1225.449946] usb 2-7: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1225.450240] usb 2-7: Product: USB-PS/2 Optical Mouse [ 1225.450740] usb 2-7: Manufacturer: Logitech [ 1225.464165] input: Logitech USB-PS/2 Optical Mouse as /devices/pci0000:00/0000:00:0b.0/usb2/2-7/2-7:1.0/input/input6 [ 1225.464666] hid-generic 0003:046D:C044.0003: input,hidraw1: USB HID v1.10 Mouse [Logitech USB-PS/2 Optical Mouse] on usb-0000:00:0b.0-7/input0 If I do the same thing after the device has stopped functioning, I get the disconnect message but that's it: [199729.451060] i2c i2c-3: sendbytes: NAK bailout. [199733.215303] usb 2-7: USB disconnect, device number 4 [199814.495204] type=1006 audit(1394381639.494:3): pid=5861 uid=0 old auid=4294967295 new auid=1000 old ses=4294967295 new ses=2 res=1 (the i2c errors, I believe, are unrelated; they seem to be caused by the nouveau driver I'm using). I've gone through at least 6 different kernel versions and they all exhibit this same behavior. At this point I'm not even sure what else I can do to troubleshoot this problem, so any advice would be appreciated! Thanks, --Mike