From owner-freebsd-current@FreeBSD.ORG Mon Jul 16 13:15:51 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 F37AF106564A; Mon, 16 Jul 2012 13:15:50 +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 9355C8FC12; Mon, 16 Jul 2012 13:15:50 +0000 (UTC) Received: from amd620.ovitrap.com ([49.128.188.2]) (authenticated bits=0) by alogreentechnologies.com (8.13.1/8.13.1) with ESMTP id q6GDFdas026453; Mon, 16 Jul 2012 07:15:43 -0600 From: Erich Dollansky To: Hans Petter Selasky Date: Mon, 16 Jul 2012 20:17:58 +0700 User-Agent: KMail/1.13.7 (FreeBSD/8.3-STABLE; KDE/4.7.4; amd64; ; ) References: <201207131904.24490.erichfreebsdlist@ovitrap.com> <201207161947.04557.erichfreebsdlist@ovitrap.com> <201207161507.27481.hselasky@c2i.net> In-Reply-To: <201207161507.27481.hselasky@c2i.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201207162017.58849.erichfreebsdlist@ovitrap.com> Cc: Adrian Chadd , freebsd-current@freebsd.org Subject: Re: 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: Mon, 16 Jul 2012 13:15:51 -0000 Hi, On Monday 16 July 2012 20:07:27 Hans Petter Selasky wrote: > On Monday 16 July 2012 14:47:04 Erich Dollansky wrote: > > Hi, > > > > On Sunday 15 July 2012 15:25:10 Adrian Chadd wrote: > > > Sounds like bluetooth coexistence? > > > > the problem are only there when the network goes down while being used. > > When the network is down when I start the machine and when the network is > > up and running, the problem is not there. > > > > This makes it so weird for me. > > > > Ok, after a restart the problem was solved. But, are we really used to > > restart FreeBSD because of things like this? > > > > What does "top" and "vmstat -i" say. I think this is more a hardware problem > than software problem, like lost/shared interrupts. Maybe the IRQ is not > properly masked when downing the network interface. I did not think of vmstat at that moment of time. Top did not show me anything which was completely out. Do not worry too much. I hoped to give a hint here for a programmer who might has noticed something like this. I hope to do some testing soon. Erich