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
[EMAIL PROTECTED]
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-bluetooth
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
