Re: [linux-usb-devel] Re: [OOPS] reproducible oops with 2.6.5-rc2-bk3

From: Colin Leroy
Date: Thu Mar 25 2004 - 10:24:45 EST


> That's right. However, the oops you saw shouldn't happen so long as
> intf->cur_altsetting points to something valid. I got the impression
> in the cdc-acm probe routine maybe it was a null pointer.

Yes, i think so too.

> Can you insert
> a statement in the cdc-acm probe function to print out the values of
> and ifdata, to check that they aren't NULL?

Already done, that's what helped me find this was related to altsettings
stuff. I didn't check to see if cur_altsetting was null, but a dev_dbg()
at the beginnning of the function was appearing, and not the dev_dbg() I
had put after this block.

> > I'm not sure the change in cdc-acm (which no longer uses index 0
> > altsetting) is correct. Or is this another bug in my phone (motorola
> > which should be handled differently than other cdc-acm devices ?
> It's hard to say without more information. The contents of
> /proc/bus/usb/devices or the output of lsusb with the phone plugged in
> would help.

Ok, I'll try to do that tonight.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at