From: Soeren Sonnenburg <kernel@nn7.de>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] hci-usb bugfix
Date: Tue, 11 May 2004 09:30:39 +0200 [thread overview]
Message-ID: <1084260638.4599.20.camel@localhost> (raw)
In-Reply-To: <1084185635.4017.5.camel@pegasus>
On Mon, 2004-05-10 at 12:40, Marcel Holtmann wrote:
> Hi Soeren,
>
> > indeed it fixes this oops ... however I still get
>
> please try the attached patch. It should fix it, too.
well, at least I tried like 5 times plugin/out and it did not oops :)
hmhh why is the device address always incrementing ?
[...]
usb 1-1: USB disconnect, address 3
usb 1-1: new full speed USB device using address 4
usb 1-1: USB disconnect, address 4
usb 1-1: new full speed USB device using address 5
usb 1-1: USB disconnect, address 5
[...]
hmmhhh at least it works as far as I can tell now (the reproducable
oopses seem gone now)
> > usb 2-1: USB disconnect, address 4
> > usb 2-1: new full speed USB device using address 5
> > devfs_mk_dev: could not append to parent for bluetooth/rfcomm/0
> > devfs_remove: bluetooth/rfcomm/0 not found, cannot remove
> > Call trace:
> > [c00099c4] dump_stack+0x18/0x28
> > [c010af1c] devfs_remove+0xcc/0xd0
> > [c01e4a5c] tty_unregister_device+0x30/0x5c
> > [f2080b64] rfcomm_dev_destruct+0x50/0xd4 [rfcomm]
> > [f2081310] rfcomm_release_dev+0xf8/0x148 [rfcomm]
> > [f20807a8] rfcomm_sock_ioctl+0x34/0x58 [rfcomm]
> > [c02a8668] sock_ioctl+0xc0/0x2c0
> > [c00726e0] sys_ioctl+0x100/0x318
> > [c0005d60] ret_from_syscall+0x0/0x44
> > usb 2-1: USB disconnect, address 5
>
> Do you use DevFS? Does the same problem exists if you disable it and use
> udev instead?
ok, so I went to udev and also no oops so far...
Success!
Thanks!
Soeren.
next prev parent reply other threads:[~2004-05-11 7:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-09 19:47 [PATCH] hci-usb bugfix Sebastian Schmidt
2004-05-09 20:39 ` Marcel Holtmann
2004-05-10 16:13 ` Alan Stern
2004-05-10 16:19 ` Marcel Holtmann
2004-05-10 16:36 ` Oliver Neukum
2004-05-10 16:52 ` Marcel Holtmann
2004-05-10 19:15 ` Oliver Neukum
2004-05-10 19:39 ` Marcel Holtmann
2004-05-10 20:38 ` Oliver Neukum
2004-05-10 20:58 ` Marcel Holtmann
2004-05-10 17:19 ` Alan Stern
2004-05-10 17:27 ` Marcel Holtmann
2004-05-10 17:52 ` Alan Stern
2004-05-10 18:07 ` Marcel Holtmann
2004-05-11 14:59 ` Alan Stern
2004-05-12 13:13 ` Marcel Holtmann
2004-05-09 22:37 ` Soeren Sonnenburg
2004-05-10 10:40 ` Marcel Holtmann
2004-05-11 7:30 ` Soeren Sonnenburg [this message]
2004-05-12 13:15 ` Marcel Holtmann
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=1084260638.4599.20.camel@localhost \
--to=kernel@nn7.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox