From owner-freebsd-current@FreeBSD.ORG Wed Jan 14 09:51:58 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 967CB16A4CE for ; Wed, 14 Jan 2004 09:51:58 -0800 (PST) Received: from ran.psg.com (ip166.usw253.dsl-acs2.sea.iinet.com [209.20.253.166]) by mx1.FreeBSD.org (Postfix) with ESMTP id 121C843D2D for ; Wed, 14 Jan 2004 09:51:57 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost ([127.0.0.1] helo=ran.psg.com) by ran.psg.com with esmtp (Exim 4.24; FreeBSD) id 1AgpBM-000FBZ-La; Wed, 14 Jan 2004 09:51:56 -0800 From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Maksim Yevmenkin References: <20040114173501.96095.qmail@web40306.mail.yahoo.com> Message-Id: Date: Wed, 14 Jan 2004 09:51:56 -0800 cc: FreeBSD Current Subject: Re: bluetooth blues X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 14 Jan 2004 17:51:58 -0000 > 1) reboot your laptop > 2) attach bluetooth device and execute rc.bluetooth start > 3) verify that bluetooth works, i.e. try inquiry, l2ping etc. > 4) stop the stack, i.e. execute rc.bluetooth stop > 5) suspend > 6) resume > 7) look into /var/log/messages (just to see if you got something > related to the bluetooth device) Jan 14 09:44:29 roam kernel: pcib0: slot 29 INTA is routed to irq 11 Jan 14 09:44:29 roam kernel: pcib0: slot 29 INTB is routed to irq 11 Jan 14 09:44:29 roam kernel: pcib0: slot 29 INTC is routed to irq 11 Jan 14 09:44:31 roam kernel: pcib0: slot 29 INTD is routed to irq 11 Jan 14 09:44:31 roam kernel: pcib0: slot 31 INTB is routed to irq 11 Jan 14 09:44:31 roam last message repeated 2 times Jan 14 09:44:31 roam kernel: pcib1: slot 0 INTA is routed to irq 11 Jan 14 09:44:31 roam kernel: usb0: controller did not reset Jan 14 09:44:31 roam kernel: usb0: cannot start Jan 14 09:44:31 roam kernel: usb1: controller did not reset Jan 14 09:44:31 roam kernel: usb1: cannot start Jan 14 09:44:31 roam kernel: usb2: controller did not reset Jan 14 09:44:31 roam kernel: usb2: cannot start Jan 14 09:44:31 roam kernel: pcib2: slot 0 INTA is routed to irq 11 Jan 14 09:44:31 roam kernel: pcib2: slot 0 INTB is routed to irq 11 Jan 14 09:44:31 roam kernel: pcib2: slot 1 INTA is routed to irq 11 Jan 14 09:44:31 roam kernel: pcib2: slot 2 INTA is routed to irq 11 Jan 14 09:44:31 roam kernel: wakeup from sleeping state (slept 00:00:29) Jan 14 09:44:31 roam kernel: uhub0: illegal enable change, port 1 Jan 14 09:44:31 roam kernel: uhub1: illegal enable change, port 1 Jan 14 09:44:31 roam kernel: uhub2: illegal enable change, port 1 Jan 14 09:44:31 roam kernel: ubt0: at uhub2 port 1 (addr 2) disconnected Jan 14 09:44:31 roam kernel: ubt0: detached Jan 14 09:44:31 roam kernel: em0: Link is up 1000 Mbps Full Duplex Jan 14 09:44:31 roam kernel: usb0: host system error Jan 14 09:44:31 roam kernel: usb0: host controller process error Jan 14 09:44:31 roam kernel: usb0: host controller halted Jan 14 09:44:31 roam kernel: usb1: host system error Jan 14 09:44:31 roam kernel: usb1: host controller process error Jan 14 09:44:31 roam kernel: usb1: host controller halted Jan 14 09:44:31 roam kernel: usb2: host system error Jan 14 09:44:31 roam kernel: usb2: host controller process error Jan 14 09:44:31 roam kernel: usb2: host controller halted Jan 14 09:44:32 roam kernel: uhub0: port 1 reset failed Jan 14 09:44:32 roam kernel: uhub1: port 1 reset failed Jan 14 09:44:32 roam kernel: uhub2: port 1 reset failed > 8) start the stack, i.e. execute rc.bluetooth start # l2ping -a rb66 l2ping: Could not connect socket, dst bdaddr=00:60:57:af:7a:8e: Network is down > if this does not crash then i would assume that it is my problem > and not usb fault. that sure is a lot of whining about usb in the resume log randy