From: Soeren Sonnenburg <kernel@nn7.de>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Cc: linux-usb-devel@lists.sourceforge.net
Subject: 2.6.6-rc3 still oops on unplugging usb bluetooth bcm203x dongle
Date: Thu, 29 Apr 2004 08:05:09 +0200 [thread overview]
Message-ID: <1083218706.3942.5.camel@localhost> (raw)
Hi...
I still get:
usb 2-1: USB disconnect, address 3
Oops: kernel access of bad area, sig: 11 [#1]
NIP: C02134B4 LR: F205D414 SP: EFE87DD0 REGS: efe87d20 TRAP: 0600 Not tainted
MSR: 00009032 EE: 1 PR: 0 FP: 0 ME: 1 IR/DR: 11
DAR: 6B6B6BB7, DSISR: 00000120
TASK = effa4030[5] 'khubd' THREAD: efe86000Last syscall: -1
GPR00: FFFF0001 EFE87DD0 EFFA4030 EE77C828 6B6B6B6B 00000000 EB8EE83C 00000000
GPR08: 00001388 EF0EE858 00010C00 C0213480 82008022 00000000 00000000 00000000
GPR16: 00000000 00000000 00000000 00000000 00000000 00220000 00230000 00000000
GPR24: 00000000 C0400000 00000001 6B6B6B6B 6B6B6BB7 EF07B8A0 EE77C828 EE77C6FC
NIP [c02134b4] class_device_del+0x34/0x140
LR [f205d414] hci_unregister_sysfs+0x14/0x24 [bluetooth]
Call trace:
[f205d414] hci_unregister_sysfs+0x14/0x24 [bluetooth]
[f205876c] hci_unregister_dev+0x18/0xb0 [bluetooth]
[f204cd94] hci_usb_disconnect+0x48/0x90 [hci_usb]
[c0277a24] usb_unbind_interface+0x88/0x8c
[c02125a4] device_release_driver+0x84/0x88
[c0212744] bus_remove_device+0x74/0xd0
[c0211120] device_del+0xa8/0x114
[c02111a4] device_unregister+0x18/0x30
[c027e248] usb_disable_device+0x9c/0xd8
[c0278768] usb_disconnect+0x9c/0x134
[c027ab14] hub_port_connect_change+0x294/0x298
[c027adec] hub_events+0x2d4/0x354
[c027aea8] hub_thread+0x3c/0xf0
[c00090b0] kernel_thread+0x44/0x60
Sometimes it helps to hciconfig hci0 down the bluetooth dongle + stop
all programs + rmmod them... However also the
rmmod hci_usb rfcomm bluetooth firmware_class bcm203x l2cap
is very likely to cause the same oops...
Yes, this is on powerpc but quite a number of people have the same issue
on x86 (with 2.6.5 at least... and thats around the time this oops on
unplugging appeared).
Any ideas ?
Soeren
next reply other threads:[~2004-04-29 6:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 6:05 Soeren Sonnenburg [this message]
2004-04-29 9:59 ` 2.6.6-rc3 still oops on unplugging usb bluetooth bcm203x dongle Soeren Sonnenburg
2004-04-29 19:59 ` [linux-usb-devel] " Alan Stern
2004-04-29 20:53 ` Martin Hermanowski
2004-04-29 20:59 ` Alan Stern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1083218706.3942.5.camel@localhost \
--to=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.