On Tue, 20 Dec 2011, zhangst wrote: > I Had the same problem. > > this is my oops: > ops len 882 > [<41217299>] usb_hcd_unlink_urb+0x34/0x73 > Oops: 0000 [#2] PREEMPT SMP > <0>Call Trace: > [<412179fe>] ? usb_kill_urb+0x3e/0xa1 > [<41028e74>] ? get_parent_ip+0xb/0x36 > [<41028f0d>] ? sub_preempt_count+0x6e/0x9d > [<412173ac>] ? usb_hcd_flush_endpoinusb_hcd_unlink_urbt+0xd4/0xea > [<4121920d>] ? usb_disable_endpoint+0x40/0x64 > [<412192a8>] ? usb_disable_device+0x2f/0xe4 > [<41213a44>] ? usb_disconnect+0x9e/0x106 > [<41214dde>] ? hub_thread+0x972/0xda3 > [<412e3d41>] ? _raw_spin_unlock_irq+0x2d/0x44 > [<41023762>] ? finish_task_switch+0x6b/0xab > [<4102000a>] ? aes_dec_blk+0x7ee/0xb6c > [<41028f0d>] ? sub_preempt_count+0x6e/0x9d > [<41041bcc>] ? autoremove_wake_function+0x0/0x36 > [<4102109c>] ? complete+0x43/0x4b > [<4121446c>] ? hub_thread+0x0/0xda3 > [<41041909>] ? kthread+0x65/0x67 > [<410418a4>] ? kthread+0x0/0x67 > [<41002eba>] ? kernel_thread_helper+0x6/0x1c > EIP: [<41217299>] SS:ESP 0068:bf8d3e54 > > use the oops, i can analysis that urb->dev is NULL, and this case oops. > this problem is solved? There's no way to know what you're talking about unless you provide a lot more information. The output from dmesg would be a good start. Also, an oops is a lot easier to debug if you build your kernel with CONFIG_FRAME_POINTER enabled. For USB problems, it also helps to enable CONFIG_USB_DEBUG. Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
