Hi, 2010/10/11 Grazvydas Ignotas <notasas@xxxxxxxxx>: > hello, > >> Reproduce the test with your setup script, no your 'ping' issue >> happened on my beagle B5. > > ok I've updated to next-20101008 (from next-20101006) and the network > no longer works at all on fresh boot, it starts working only after > replugging the cable. I think it's because patch "usb: musb: gadget: > Unmapping the dma buffer when switching to PIO mode" was dropped, If the patch is not dropped, DMA will not be used to unload fifo for out ep, otherwise DMA will be used for out ep. > which effectively disables DMA due to a bug in it, so it's probably > DMA problems on my board. Here is my log: Yes, your issue may be related with ep1out Rx DMA, but I am not sure since the very important message between timestamp 39.256011 and 85.210693 is not provided by you, why not post all messages? So we can't know if there are any rx interrupts after requests are queued into ep1out queue, then don't know anything about the dma handling after rx interrupt comes. If possible, please provide all the debug message instead of just selecting part of them. Except for above, no other abnormal things wrt. musb are found from your log. > > http://notaz.gp2x.de/misc/pnd/linux_next_20101008_musb > > There is some lock backtrace in the log, but I don't think it's It is lockdep warning, which touches me too, nothing to do with your issue. > related, as with "Unmapping the dma buffer when switching to PIO mode" > patch network works, but I guess I lose DMA. > I'm using omap2plus_defconfig with OMAP2 and OMAP4 disabled (otherwise > did not boot for some reason), and musb, g_ether and earlyprintk > enabled. > thanks, -- Lei Ming -- 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
