<snip> > > > > > > So far I have tried many versions of the linux-omap and linux-omap-pm > > > kernel, from about 2.6.30 to the latest git version. They all exhibit > > > the USB OTG death bug. > > > I've used kernels with openembedded patches and without, currently > > > without. Yesterday I discovered the musb_hdrc.fifo_mode parameter and > > > played around with it. I also modified the given configurations. Result: > > > - FIFO configurations including .mode = BUF_DOUBLE don't work at all - no > > > devices work. > > > - the USB death bug is not fixed by: > > > - using only one endpoint > > > - using no TXRX entries but only separate RX and TX > > > (every endpoint gets a TX and an RX entry though) > > > - using a large number of endpoints with same maxpacket value > > > ... still no solution. > > > > > > Enabling debug output of the musb_hdrc driver (yes I've also compiled in > > > debug messages) is not very practical due to the high volume of > > > messages; also, when the bug occurs nothing special is printed. The > > > first error usually comes from the memory manager / filesystem > > > complaining that it can't do "IO to offline device", i.e. the > > > disappeared external harddisk (which contains the swapfile). > > > > > > I would *really* appreciate somebody looking into this because this > > > currently makes the hardware as useful as a brick for me. I can supply > > > debug output and test patches. Would you care to try these two patches please? http://marc.info/?l=linux-usb&m=125957336716915&w=2 And The dependency patch: http://marc.info/?l=linux-usb&m=125879861004131&w=2 Let me know if these fix the bug for you. - Anand -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
