Re: Kernel OOPS in usb_submit_urb in drivers/usb/core/urb.c

2012-07-27 Thread Damjan
Maybe I read the kernel OOPS wrong. Was &ep->desc NULL or not? It's hard to tell from the information in the oops. You'd have to get an assembly listing of usb_submit_urb() and figure out what source code statement corresponds to offset 0x75 in the object code. Why did you originally think the

Re: Kernel OOPS in usb_submit_urb in drivers/usb/core/urb.c

2012-07-27 Thread Damjan
No, that's not right at all, for a couple of reasons. First, &ep->desc is the address of a member of a structure. Even if ep itself were null, &ep->desc would not be NULL unless desc happened to be the first member of the ep structure (it is now, but there's no guarantee that it always will be).

Re: Kernel OOPS in usb_submit_urb in drivers/usb/core/urb.c

2012-07-26 Thread Damjan
On чет, 26 јул 2012 23:32:48 CEST, Greg KH wrote: On Thu, Jul 26, 2012 at 11:25:44PM +0200, Damjan wrote: While playing with my custom made i2c-tiny-usb adapter I triggered this kernel OOPS in usb_submit_urb in the drivers/usb/core/urb.c file. From looking at the file, before line 329 it

Kernel OOPS in usb_submit_urb in drivers/usb/core/urb.c

2012-07-26 Thread Damjan
0f b6 d2 85 d2 89 54 24 04 74 [14428.092010] EIP: [] usb_submit_urb+0x75/0x310 [usbcore] SS:ESP 0068:c3bb5d34 [14428.092010] CR2: 0004 [14428.135104] ---[ end trace 9baf8f9c81bed80d ]--- >From adf870d98e60e4756cd49ed1f11c9c44b7f80477 Mon Sep 17 00:00:00 2001 From: Damjan Georgievski