Hi, 2010/10/9 Grazvydas Ignotas <notasas@xxxxxxxxx>: >> Also, you may take Gadiyar's suggestion to post your musb debug info. > > Thanks for ideas, I've found why it happens for me. It's because my > network setup script looks like this: > ifconfig usb0 10.0.1.2 down > ifconfig usb0 10.0.1.2 up > > So to reproduce, just load up g_ether, and run: > # ifconfig usb0 10.0.1.2 down > (must be with IP, it somehow affects things) Reproduce the test with your setup script, no your 'ping' issue happened on my beagle B5. > Then I get: > [ 21.253662] musb_gadget_queue 1211: <== to ep1out request=c193ed00 > [ 21.260192] musb_ep_restart 1179: <== RX/OUT request c193ed00 len > 1536 on hw_ep1 > [ 21.267974] musb_gadget_queue 1211: <== to ep1out request=c193ed40 > ... > [ 21.319854] musb_gadget_queue 1211: <== to ep1out request=c193ef40 > [ 21.326751] musb_gadget_disable 1129: ep1in > [ 21.331115] musb_g_giveback 186: ep1out request c193ed00, 0/1536 fault -108 > [ 21.338409] musb_g_giveback 186: ep1out request c193ed40, 0/1536 fault -108 > [ 21.345672] musb_g_giveback 18ut request c193ed80, 0/1536 fault -108 > [ 21.352966] musb_g_giveback 186: ep1out request c193edc0, 0/1536 fault -108 > [ 21.360229] musb_g_giveback 186: ep1out request c193ee00, 0/1536 fault -108 > [ 21.367523] musb_g_giveback 186: ep1out request c193ee40, 0/1536 fault -108 > [ 21.374786] musb_g_giveback 186: ep1out request c193ee80, 0/1536 fault -108 > [ 21.382049] musb_g_giveback 186: ep1out request c193eec0, 0/1536 fault -108 > [ 21.389343] musb_g_giveback 186: ep1out request c193ef00, 0/1536 fault -108 > [ 21.396606] musb_g_giveback 186: ep1out request c193ef40, 0/1536 fault -108 > [ 21.403869] musb_gadget_disable 1129: ep1out > [ 21.408355] musb_hdrc periph: enabled ep1in for bulk IN, dma, maxpacket 512 > [ 21.415618] musb_hdrc periph: enabled ep1out for bulk OUT, dma, maxpacket 512 The log info above is very normal and caused by 'ifconfig usb0 down', so it is useless. > (my serial is dropping some output, it's due to my hardware) > > At this point musb begins acting up, but seems to recover after some > cable replugs. > We need the musb log info when the ping packet is out of order or lost, instead of the log info triggered by 'ifconfig usb0 down' only. Also I suggest you capture the ethernet interface traffic first, then enable musg debug switch and post musb debug message out if the ethernet traffic is OK but 'ping' is still not OK since your issue may be related network instead of musb driver. thanks, -- Lei Ming -- 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
