From: Martin Hermanowski <martin@mh57.de>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Soeren Sonnenburg <kernel@nn7.de>,
Marcel Holtmann <marcel@holtmann.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
USB development list <linux-usb-devel@lists.sourceforge.net>
Subject: Re: [linux-usb-devel] 2.6.6-rc3 still oops on unplugging usb bluetooth bcm203x dongle
Date: Thu, 29 Apr 2004 22:53:51 +0200 [thread overview]
Message-ID: <20040429205351.GJ11077@mh57.de> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0404291557550.1314-100000@ida.rowland.org>
[-- Attachment #1: Type: text/plain, Size: 1570 bytes --]
On Thu, Apr 29, 2004 at 03:59:36PM -0400, Alan Stern wrote:
> On Thu, 29 Apr 2004, Soeren Sonnenburg wrote:
>
> > 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]
>
> Marcel Holtman is working on this; some other people have reported the
> same problem. Have you been in touch with him? It appears to be a
> problem in the Bluetooth driver, not in the USB stack.
Are there any patches available? The most recent patch I could find is
for 2.6.5, and does not change this problem.
I would like to try the latest version of the bluez-patch, if this can
help to find the bug.
LLAP, Martin
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-29 21:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 6:05 2.6.6-rc3 still oops on unplugging usb bluetooth bcm203x dongle Soeren Sonnenburg
2004-04-29 9:59 ` Soeren Sonnenburg
2004-04-29 19:59 ` [linux-usb-devel] " Alan Stern
2004-04-29 20:53 ` Martin Hermanowski [this message]
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=20040429205351.GJ11077@mh57.de \
--to=martin@mh57.de \
--cc=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=marcel@holtmann.org \
--cc=stern@rowland.harvard.edu \
/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.