Hi,
2010/10/11 Grazvydas Ignotas nota...@gmail.com:
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
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
2010/10/11 Grazvydas Ignotas nota...@gmail.com:
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
On Mon, Oct 11, 2010 at 1:53 PM, Ming Lei tom.leim...@gmail.com wrote:
2010/10/11 Grazvydas Ignotas nota...@gmail.com:
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
2010/10/11 Grazvydas Ignotas nota...@gmail.com:
On Mon, Oct 11, 2010 at 1:53 PM, Ming Lei tom.leim...@gmail.com wrote:
2010/10/11 Grazvydas Ignotas nota...@gmail.com:
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
So maybe it's ep2in issue after all?
Yes, it is really with ep2in, and musb ep2in always return more data to
host so cause overflow in host.
I see what triggered your issue, please try the patch in the link below:
http://marc.info/?l=linux-usbm=128576496614332w=2
This has fixed my
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:
Hi,
2010/10/9 Grazvydas Ignotas nota...@gmail.com:
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
I have tried patch-v2.6.36-rc6-next-20101006 on my beagle B5, seems
no such problem.
Did you try booting with the cable attached? The problem only shows up
if I boot the board with cable attached, no such problem after replug.
I also have g_ether compiled into kernel, maybe that makes a
2010/10/8 Grazvydas Ignotas nota...@gmail.com:
I have tried patch-v2.6.36-rc6-next-20101006 on my beagle B5, seems
no such problem.
Did you try booting with the cable attached? The problem only shows up
Yes, my beagle is powered by usb cable connected with PC.
if I boot the board with cable
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
On Wed, Oct 06, 2010 at 06:33:23PM -0500, Grazvydas Ignotas wrote:
Hi,
pulled today's linux-next and g_ether is acting strange on my pandora board:
# ping pnd
PING pnd (10.0.1.2) 56(84) bytes of data.
64 bytes from pnd (10.0.1.2): icmp_seq=2 ttl=64 time=2018 ms
64 bytes from pnd (10.0.1.2):
2010/10/7 Grazvydas Ignotas nota...@gmail.com:
Hi,
pulled today's linux-next and g_ether is acting strange on my pandora board:
# ping pnd
PING pnd (10.0.1.2) 56(84) bytes of data.
64 bytes from pnd (10.0.1.2): icmp_seq=2 ttl=64 time=2018 ms
64 bytes from pnd (10.0.1.2): icmp_seq=1 ttl=64
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:
On Fri, Oct 8, 2010 at 4:07 AM, Grazvydas Ignotas nota...@gmail.com 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
2010/10/8 Grazvydas Ignotas nota...@gmail.com:
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
Hi,
pulled today's linux-next and g_ether is acting strange on my pandora board:
# ping pnd
PING pnd (10.0.1.2) 56(84) bytes of data.
64 bytes from pnd (10.0.1.2): icmp_seq=2 ttl=64 time=2018 ms
64 bytes from pnd (10.0.1.2): icmp_seq=1 ttl=64 time=5036 ms
64 bytes from pnd (10.0.1.2): icmp_seq=8
17 matches
Mail list logo
