On Tue, Aug 4, 2009 at 1:02 AM, Rajaram R<rajaram.officemail@xxxxxxxxx> wrote: > On Sat, Aug 1, 2009 at 2:37 AM, Praveen G K<praveen.gk@xxxxxxxxx> wrote: >> Hello all, >> >> When I connect the device in mass storage mode using a bad USB cable, >> my device locks up completely. > > Why do you connect with a bad cable ? Is it a test ? If Yes , then > test of what It was just a test to see that the device does not lock up under any circumstances. Figured that the UI thread was freezing, only in the case of windows, which is a different problem altogether. Thanks for the help! > > Only a hard reset will help me get the >> device back to normal functioning. This happens when the device is >> connected to a windows box, but on a linux box, the device exits >> gracefully, when it realizes it is not able to enumerate properly. >> The linux host keeps sending the SET_ADDRESS command to the driver, >> while the windows box sends a series of Get_Descriptor requests and >> then enters the suspend state, and finally calls the unregister_driver >> function. >> >> I don't understand why it is locking up, because I collected the debug >> output from the fsg_unbind function in the file storage gadget file, >> and I see all the debug output in the function call. I connected a >> real view ICE debugger to see where it is locking up, and I notice >> that the code is executing in the default_idle function in >> arch/arm/kernel/process.c file. >> >> Please let me know if you have any suggestions. >> >> Thanks, >> Praveen Krishnan >> -- >> 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 >> > -- 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
