From: Martin Hermanowski <lkml@martin.mh57.de>
To: Greg KH <greg@kroah.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.5-mm4 (hci_usb module unloading oops)
Date: Mon, 19 Apr 2004 22:29:43 +0200 [thread overview]
Message-ID: <20040419202943.GA5557@mh57.de> (raw)
In-Reply-To: <20040412220353.GC23692@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]
On Mon, Apr 12, 2004 at 03:03:53PM -0700, Greg KH wrote:
> On Mon, Apr 12, 2004 at 12:19:11PM +0200, Martin Hermanowski wrote:
> > I get an oops when I try to unload the hci_usb module.
>
> {sigh} I'm hating that driver right now...
>
> There are a number of pending bluetooth patches for that driver that fix
> a number of different bugs, so I'm leary of trying to see if this is a
> different one or not at this point in time. Care to apply all of the
> bluetooth patches and if this still happens, can you report it to the
> linux-usb-devel and bluez-devel mailing lists?
I can try these patches in the next days, can you point me to an url?
> > What other useful information can I provide?
>
> CONFIG_DEBUG_DRIVER might be good to set, and then we can see if we are
> not trying to remove the same device twice for some odd reason. If you
> do duplicate this, please include all of the debug log entries that
> happen from when you unplug the device.
>
> Also CONFIG_USB_DEBUG might help out.
I just tried 2.6.6-rc1-mm1 (patched with mppe and iscsi), same problem.
I compiled with CONFIG_DEBUG_DRIVER and CONFIG_USB_DEBUG, after booting,
I activate the usb-dongle (Fn+F5 on the IBM T41p), then I run `hciconfig
down' and `rmmod hci_usb', which triggers the problem
I uploaded both the config and the whole syslog file from the boot until
shutting down:
http://mh57.de/~martin/config-2.6.6-rc1-mm1
http://mh57.de/~martin/syslog-2.6.6-rc1-mm1
> > Apr 12 12:07:48 localhost udev[22216]: removing device node '/dev/hci0'
>
> Nice, glad to see udev is working for you :)
I'm using udev 0.024-2 from debian, and it is working quite well :-)
LLAP, Martin
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-04-19 20:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-11 3:05 2.6.5-mm4 Andrew Morton
2004-04-12 6:46 ` 2.6.5-mm4 Paul P Komkoff Jr
2004-04-12 7:42 ` 2.6.5-mm4 Andrew Morton
2004-04-12 8:22 ` 2.6.5-mm4 Paul P Komkoff Jr
2004-04-12 8:28 ` 2.6.5-mm4 Andrew Morton
2004-04-12 9:10 ` 2.6.5-mm4 Paul P Komkoff Jr
2004-04-12 9:44 ` fix must_not_trace_exec() test (was: 2.6.5-mm4) Olaf Dietsche
2004-04-12 14:18 ` fix must_not_trace_exec() test Andy Lutomirski
2004-04-12 22:02 ` Chris Wright
2004-04-12 10:19 ` 2.6.5-mm4 (hci_usb module unloading oops) Martin Hermanowski
2004-04-12 22:03 ` Greg KH
2004-04-12 22:36 ` Marcel Holtmann
2004-04-12 22:42 ` Greg KH
2004-04-12 22:57 ` Marcel Holtmann
2004-04-19 20:29 ` Martin Hermanowski [this message]
2004-04-12 12:24 ` [PATCH] change audit_log_format() -> printk() (was: 2.6.5-mm4) Olaf Dietsche
2004-04-12 17:06 ` 2.6.5-mm4 (compile stats) John Cherry
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=20040419202943.GA5557@mh57.de \
--to=lkml@martin.mh57.de \
--cc=akpm@osdl.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/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.