* Bluetooth USB oopses on unplug (2.6.1) @ 2004-01-26 10:20 Pavel Machek 2004-01-26 13:45 ` Marcel Holtmann 0 siblings, 1 reply; 5+ messages in thread From: Pavel Machek @ 2004-01-26 10:20 UTC (permalink / raw) To: kernel list, maxk Hi! In 2.6.1, bluetooth-over-usb (hci_usb) works very well... As long as I do not unplug it. When I do, it oopses. Is there newer version of bluetooth that I should try? Pavel -- When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bluetooth USB oopses on unplug (2.6.1) 2004-01-26 10:20 Bluetooth USB oopses on unplug (2.6.1) Pavel Machek @ 2004-01-26 13:45 ` Marcel Holtmann 2004-01-26 16:16 ` Pavel Machek 0 siblings, 1 reply; 5+ messages in thread From: Marcel Holtmann @ 2004-01-26 13:45 UTC (permalink / raw) To: Pavel Machek; +Cc: Linux Kernel Mailing List, Max Krasnyansky Hi Pavel, > In 2.6.1, bluetooth-over-usb (hci_usb) works very well... As long as I > do not unplug it. When I do, it oopses. Is there newer version of > bluetooth that I should try? try to disable the SCO audio option for the driver itself. It should work then, because the driver no longer uses ISOC transfers. However show us the oops (through ksymoops) and show us your USB hardware on your motherboard (lspci). Regards Marcel ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bluetooth USB oopses on unplug (2.6.1) 2004-01-26 13:45 ` Marcel Holtmann @ 2004-01-26 16:16 ` Pavel Machek 2004-01-26 17:09 ` Marcel Holtmann 0 siblings, 1 reply; 5+ messages in thread From: Pavel Machek @ 2004-01-26 16:16 UTC (permalink / raw) To: Marcel Holtmann; +Cc: Linux Kernel Mailing List, Max Krasnyansky Hi! > > In 2.6.1, bluetooth-over-usb (hci_usb) works very well... As long as I > > do not unplug it. When I do, it oopses. Is there newer version of > > bluetooth that I should try? > > try to disable the SCO audio option for the driver itself. It should > work then, because the driver no longer uses ISOC transfers. Will try. > However show us the oops (through ksymoops) and show us your USB > hardware on your motherboard (lspci). pavel@amd:~$ lspci 00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 3188 (rev 01) 00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device b188 00:0a.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller 00:0c.0 Network controller: Broadcom Corporation BCM94306 802.11g (rev 02) 00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Controller (rev 50) 00:11.6 Communication controller: VIA Technologies, Inc. Intel 537 [AC97 Modem] (rev 80) 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) 00:13.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf [Radeon Mobility 9000 M9] (rev 02) pavel@amd:~$ I'll have to hand-copy the oops, as machine dies after unplug. Here it is: Oops: 2 EIP is at uhci_remov_pending_qhs Call trace: uhci_irq usb_hcd_irq handle_irq_event do_IRQ common_interrupt_1 Pavel -- When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bluetooth USB oopses on unplug (2.6.1) 2004-01-26 16:16 ` Pavel Machek @ 2004-01-26 17:09 ` Marcel Holtmann 2004-01-26 17:39 ` Pavel Machek 0 siblings, 1 reply; 5+ messages in thread From: Marcel Holtmann @ 2004-01-26 17:09 UTC (permalink / raw) To: Pavel Machek; +Cc: Linux Kernel Mailing List, Max Krasnyansky Hi Pavel, > > However show us the oops (through ksymoops) and show us your USB > > hardware on your motherboard (lspci). > > pavel@amd:~$ lspci > 00:00.0 Host bridge: VIA Technologies, Inc.: Unknown device 3188 (rev 01) > 00:01.0 PCI bridge: VIA Technologies, Inc.: Unknown device b188 > 00:0a.0 CardBus bridge: ENE Technology Inc CB1410 Cardbus Controller > 00:0c.0 Network controller: Broadcom Corporation BCM94306 802.11g (rev 02) > 00:10.0 USB Controller: VIA Technologies, Inc. USB (rev 80) > 00:10.1 USB Controller: VIA Technologies, Inc. USB (rev 80) > 00:10.2 USB Controller: VIA Technologies, Inc. USB (rev 80) > 00:10.3 USB Controller: VIA Technologies, Inc. USB 2.0 (rev 82) > 00:11.0 ISA bridge: VIA Technologies, Inc. VT8235 ISA Bridge > 00:11.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT8233/A/C/VT8235 PIPC Bus Master IDE (rev 06) > 00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235 AC97 Audio Controller (rev 50) > 00:11.6 Communication controller: VIA Technologies, Inc. Intel 537 [AC97 Modem] (rev 80) > 00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 74) > 00:13.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 80) > 00:18.0 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > 00:18.1 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > 00:18.2 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > 00:18.3 Host bridge: Advanced Micro Devices [AMD] K8 NorthBridge > 01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf [Radeon Mobility 9000 M9] (rev 02) > pavel@amd:~$ > > I'll have to hand-copy the oops, as machine dies after unplug. Here it > is: > > Oops: 2 > EIP is at uhci_remov_pending_qhs > Call trace: > uhci_irq > usb_hcd_irq > handle_irq_event > do_IRQ > common_interrupt_1 as I expected. It is an UHCI host adapter and it looks like the uhci_hcd driver has problems to unlink the ISOC URB's. Look at the LKML and USB mailing lists for similiar post. At the moment I don't know of any patch for it. Sorry. Regards Marcel ^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bluetooth USB oopses on unplug (2.6.1) 2004-01-26 17:09 ` Marcel Holtmann @ 2004-01-26 17:39 ` Pavel Machek 0 siblings, 0 replies; 5+ messages in thread From: Pavel Machek @ 2004-01-26 17:39 UTC (permalink / raw) To: Marcel Holtmann; +Cc: Linux Kernel Mailing List, Max Krasnyansky Hi! > > I'll have to hand-copy the oops, as machine dies after unplug. Here it > > is: > > > > Oops: 2 > > EIP is at uhci_remov_pending_qhs > > Call trace: > > uhci_irq > > usb_hcd_irq > > handle_irq_event > > do_IRQ > > common_interrupt_1 > > as I expected. It is an UHCI host adapter and it looks like the uhci_hcd > driver has problems to unlink the ISOC URB's. Look at the LKML and USB > mailing lists for similiar post. At the moment I don't know of any patch > for it. Sorry. No problem. For the record, it works okay without SCO. Thanks for that. Pavel -- When do you have a heart between your knees? [Johanka's followup: and *two* hearts?] ^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2004-01-26 17:40 UTC | newest] Thread overview: 5+ messages (download: mbox.gz follow: Atom feed -- links below jump to the message on this page -- 2004-01-26 10:20 Bluetooth USB oopses on unplug (2.6.1) Pavel Machek 2004-01-26 13:45 ` Marcel Holtmann 2004-01-26 16:16 ` Pavel Machek 2004-01-26 17:09 ` Marcel Holtmann 2004-01-26 17:39 ` Pavel Machek
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox