I saw one of those (cdc_bind oops) recently too; not clear what misbehaved since no relevant usb code changed recently.
Try the next batch of USB changes, which does change that function. (They're in Greg's queue, Linus doesn't have them yet. [1]) I've not seen this mysterious oops with that version, with an SL-5500 (OZ 3.2) or the device which did the oops for me.
- Dave
[1] bk://kernel.bkbits.net/gregkh/linux/linus-2.6
From: Petr Baudis <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: USB not working correctly in 2.6.0-test4-mm4 Date: Sun, 31 Aug 2003 13:59:03 +0200
EIP is at cdc_bind+0x116/0x2b0 [usbnet] eax: 000000c4 ebx: c73efab2 ecx: c2c12124 edx: 10783236 esi: 00000005 edi: c226989c ebp: c2945ec8 esp: c2945ea4 ds: 007b es: 007b ss: 0068 Process modprobe (pid: 2215, threadinfo=c2944000 task=c30c0080) Stack: c1c4b400 c99b716e c99b6ee0 c226989c c1c4b400 c2945ecc c99b716e c1c4b406 c2945efc c2945efc c99b6a4f c2269800 c2c12060 c99b81d8 c99b81c0 c99b71e8 c2269800 c22690d0 fffffff4 c2269000 c99b6ee0 c29b4d20 c2945f24 c987107b Call Trace: [<c99b6a4f>] usbnet_probe+0x1eb/0x3dc [usbnet] [<c987107b>] usb_probe_interface+0x6b/0x98 [usbcore] [<c01cfac6>] bus_match+0x32/0x58 [<c01cfbc4>] driver_attach+0x44/0x80 [<c01cfe4d>] bus_add_driver+0x85/0xa0 [<c01d01e2>] driver_register+0x36/0x38 [<c98711a7>] usb_register+0x6f/0xa4 [usbcore] [<c983d027>] usbnet_init+0x27/0x37 [usbnet] [<c012f4ea>] sys_init_module+0x11e/0x250 [<c0293757>] syscall_call+0x7/0xb
------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
