Messages in this thread | | | Subject | Re: [PATCH] hci-usb bugfix | From | Soeren Sonnenburg <> | Date | Tue, 11 May 2004 09:30:39 +0200 |
| |
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.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |