On Mon, 20 Sep 2010, Jiri Kosina wrote: > Thanks Matt and Phill for confirming the line that triggers the oops. As I > am not able to reproduce it myself, it's a bit tricky to track down what > went wrong. > > Could you please apply the patch below? It's printing the hid <-> hiddev > <-> usb_interface connections at various stages of probing and open. > Hopefully it'll reveal a little bit what goes wrong and where. Jiri: There's something very fishy going on here. Even more so than these bug reports suggest. The whole business about hiddev_driver in hiddev.c looks bogus. It doesn't get used for anything and it never binds to an interface. Which means that the usb_find_interface call in hiddev_open should never succeed. At the very least it would need to specify hid_driver instead of hiddev_driver. I have no idea what's really happening. Can you figure it out? Alan Stern -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
