From owner-freebsd-current@FreeBSD.ORG Fri Jul 13 13:30:26 2012 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C8524106566B for ; Fri, 13 Jul 2012 13:30:26 +0000 (UTC) (envelope-from erichfreebsdlist@ovitrap.com) Received: from alogreentechnologies.com (alogreentechnologies.com [67.212.224.110]) by mx1.freebsd.org (Postfix) with ESMTP id 72CD08FC08 for ; Fri, 13 Jul 2012 13:30:26 +0000 (UTC) Received: from x220.ovitrap.com ([122.129.201.10]) (authenticated bits=0) by alogreentechnologies.com (8.13.1/8.13.1) with ESMTP id q6DC4Pbt005643 for ; Fri, 13 Jul 2012 06:04:26 -0600 From: Erich Dollansky To: freebsd-current@freebsd.org Date: Fri, 13 Jul 2012 19:04:24 +0700 User-Agent: KMail/1.13.7 (FreeBSD/10.0-CURRENT; KDE/4.8.3; amd64; ; ) MIME-Version: 1.0 Content-Type: Text/Plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201207131904.24490.erichfreebsdlist@ovitrap.com> Subject: Erratic USB mouse behaviour when wireless is down and USB hard disk connected X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jul 2012 13:30:26 -0000 Hi, I know that this is not a very helpful information. I have an Lenovo X220 running 10 from some 2 weeks ago. I just noticed that the USB mouse (a wireless Logitech Trackman) becomes unusable when the wireless (iwn) is not able to connect to the access point and a USB hard disk is plugged in. Even when no data are transferred the USB mouse is unusable. The built-in track-point behaves just normal. When I turn off the wireless network via the hardware switch, the system stays usable as expected even under heavy hard disk access. If it was not something else I have missed, the only difference was the access point which went down when I noticed the problem. Please understand this just as a hint to the developers of the sub-systems which could cause the problem. As this network here is not mine, I am not able to do any tests with it. If somebody has an idea what could be tested, tell me please. I will have access to 'my' network the coming week again. Erich