Re: g_ether broken on musb

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Fri, Oct 8, 2010 at 4:07 AM, Grazvydas Ignotas <notasas@xxxxxxxxx> wrote:
>>> Looks like the transfers get mixed somehow? Curiously after replugging
>>> the cable several times it starts working properly, however the
>>> problem comes back reliably after each reboot.
>>
>> Please apply the patch below against -next tree to see if
>> your issue can be fixed:
>>
>>       http://marc.info/?l=linux-usb&m=128576494214316&w=2
>>
>
> Doesn't seem to help:
> # ping pnd
> PING pnd (10.0.1.2) 56(84) bytes of data.
> 64 bytes from pnd (10.0.1.2): icmp_seq=3 ttl=64 time=3000 ms
> 64 bytes from pnd (10.0.1.2): icmp_seq=2 ttl=64 time=5000 ms
> 64 bytes from pnd (10.0.1.2): icmp_seq=1 ttl=64 time=7007 ms
> 64 bytes from pnd (10.0.1.2): icmp_seq=9 ttl=64 time=0.135 ms
> 64 bytes from pnd (10.0.1.2): icmp_seq=11 ttl=64 time=2000 ms
> 64 bytes from pnd (10.0.1.2): icmp_seq=10 ttl=64 time=4000 ms

Can you turn on CONFIG_USB_MUSB_DEBUG, and pass
musb_hdrc.debug=5 in the bootargs?

This should give sufficiently detailed debug messages in the
kernel logs (warning - it slows things down a lot, and could
make the original issue disappear). Maybe these logs
will help identify the problem.

- 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


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux