From owner-freebsd-bluetooth@FreeBSD.ORG Fri Sep 9 12:17:27 2005 Return-Path: X-Original-To: freebsd-bluetooth@freebsd.org Delivered-To: freebsd-bluetooth@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0ECD016A41F for ; Fri, 9 Sep 2005 12:17:26 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8D58F43D70 for ; Fri, 9 Sep 2005 12:17:19 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j89CHIOg096736 for ; Fri, 9 Sep 2005 07:17:18 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <43217D56.3050508@centtech.com> Date: Fri, 09 Sep 2005 07:17:26 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.11) Gecko/20050904 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-bluetooth@freebsd.org References: <431F388E.2010204@centtech.com> In-Reply-To: <431F388E.2010204@centtech.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/1071/Fri Sep 9 01:39:47 2005 on mh2.centtech.com X-Virus-Status: Clean Subject: Re: Bluetooth mouse breaks on -current X-BeenThere: freebsd-bluetooth@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Using Bluetooth in FreeBSD environments List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 09 Sep 2005 12:17:27 -0000 Eric Anderson wrote: > Ok, I wish I could provide better information, but as of the last couple > of weeks (2 weeks maybe?), I've had this weird problem with my bluetooth > mouse (which had been working flawlessly until now). Right in the > middle of use, my mouse will die. It will lose association (or whatever > it's called). Actually, the mouse seems to be ok, as I've tried it on > another computer and it works just fine with no changes. Once it dies, > I have to muck with the bthidcontrol forget, reboot, etc, so I'm not > sure what I do to fix it, but eventually it will be able to query the > mouse again and then bthidd will connect and everything will be fine. > > One thing I've noticed, is that now, when doing an l2ping, I get this: > # l2ping -a mouse > 44 bytes from mouse seq_no=0 time=59990.660 ms result=0x23 Resource > temporarily unavailable > 44 bytes from mouse seq_no=1 time=59990.834 ms result=0x23 Resource > temporarily unavailable > 44 bytes from mouse seq_no=2 time=59990.821 ms result=0x23 Resource > temporarily unavailable > 44 bytes from mouse seq_no=3 time=59990.885 ms result=0x23 Resource > temporarily unavailable > 44 bytes from mouse seq_no=4 time=59990.879 ms result=0x23 Resource > temporarily unavailable > > When my mouse is on or off. Also, pinging other devices, returns either > the same result, or sometimes it will return ~5000ms returns, as if it > can ping it, but it is slow - even when the device isn't powered on! > > What do I need to do to help diagnose? Seems that rebooting my FreeBSD laptop clears it up - so I'm thinking it has to do with the netgraph/bluetooth modules.. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology Anything that works is better than anything that doesn't. ------------------------------------------------------------------------