From owner-freebsd-usb@FreeBSD.ORG Fri Oct 3 21:17:34 2008 Return-Path: Delivered-To: usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 024EC1065688 for ; Fri, 3 Oct 2008 21:17:34 +0000 (UTC) (envelope-from vova@sw.ru) Received: from relay.sw.ru (mailhub.sw.ru [195.214.232.25]) by mx1.freebsd.org (Postfix) with ESMTP id 32E388FC12 for ; Fri, 3 Oct 2008 21:17:32 +0000 (UTC) (envelope-from vova@sw.ru) Received: from vbook.fbsd.ru ([77.232.23.6]) (authenticated bits=0) by relay.sw.ru (8.13.4/8.13.4) with ESMTP id m93KsItk016675 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 4 Oct 2008 00:54:20 +0400 (MSD) Received: from vova by vbook.fbsd.ru with local (Exim 4.69 (FreeBSD)) (envelope-from ) id 1KlrfG-0000jG-AN; Sat, 04 Oct 2008 00:54:18 +0400 From: Vladimir Grebenschikov To: Maksim Yevmenkin In-Reply-To: References: <3a386af20809261420j535680e8pf44453dbf6f84b20@mail.gmail.com> <1223034512.1842.111.camel@localhost> Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: SWsoft Date: Sat, 04 Oct 2008 00:54:17 +0400 Message-Id: <1223067257.2362.6.camel@localhost> Mime-Version: 1.0 X-Mailer: Evolution 2.22.3.1 FreeBSD GNOME Team Port Sender: Vladimir Grebenschikov Cc: freebsd-bluetooth@freebsd.org, usb@freebsd.org, Federico Lorenzi Subject: Re: Bluetooth audio - crash on USB bluetooth dongle disconnect X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vova@fbsd.ru List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 03 Oct 2008 21:17:34 -0000 On Fri, 2008-10-03 at 09:45 -0700, Maksim Yevmenkin wrote: > now you can connect your bluetooth device. kick tires and make sure > you can do inquiry etc. then simply pull the device out _without_ > stopping the stack first. at least on my system it often leads to > panic after a few seconds. First of all it crashes on disconnect with big probability even without btsock_sco. For me it crashes in uhci interrupt handler on NULL de-reference trace shows something like: usb_transfer_complete uhci_transfer_complete ... digging a bit shows that it crashes in uhci.c:2575 usbd_status uhci_device_isoc_start(usbd_xfer_handle xfer) { struct uhci_pipe *upipe = (struct uhci_pipe *)xfer->pipe; uhci_softc_t *sc = (uhci_softc_t *)upipe->pipe.device->bus; with upipe = NULL on interrupt Looks like it is result of locking changes in usb stack or like. Usb folks, can anybody give a hint what is the reason of such crash ? PS: I have SMP system. > thanks, > max -- Vladimir B. Grebenschikov vova@fbsd.ru