Re: [beagleboard] Re: BeagleBone ethernet VERY slow?

[fred basset]

I'm also seeing slow Ethernet on my custom board based off the BeagleBone.  I have TI looking into it.  I dumped some of the PHY registers and it indicated the link was running at 10MB/s and negotiation of 100MB/s failed.  I'll post here if I get a solution.

On Wed, May 8, 2013 at 11:45 AM, <flyingch...@gmail.com> wrote:

Anyone have any ideas or input?

On Tuesday, May 7, 2013 12:06:24 PM UTC-7, flyingch...@gmail.com wrote:

I just got a beaglebone Rev A6 and I have tried using the default Angstrom image it comes with and Also Ubuntu. Both OS's produce what I would consider an unusable ethernet. I am getting speeds on average of 5kbs for anything internet related.

Is there a known issue, that I am not finding on google? I have tried bring the interface down and up, releasing it and renewing, rebooting, different Cat5 cables. Nothing in the logs nor in configs stands out to me as the cause of this. Also I have tried the stock image that comes with it, as well as cloning that card and fully updating it with Angstrom which took almost all night to DL all the packages. No difference with Ubuntu.

Is there anything I can share that will be helpful in debugging this issue as I am at a loss. Thanks for any help and your time

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[randy rodes]

On Wednesday, May 8, 2013, fred basset <fredbas...@gmail.com> wrote:
> I'm also seeing slow Ethernet on my custom board based off the BeagleBone.  I have TI looking into it.  I dumped some of the PHY registers and it indicated the link was running at 10MB/s and negotiation of 100MB/s failed. 
I'll post here if I get a solution.
>

Is it the same case for Ubuntu images as well?

[evilwulfie]

check your ethernet cable for proper wiring if its not perfect it will fall back to 10-base t

http://www.zytrax.com/tech/layer_1/cables/tech_lan.htm#100s


On 5/9/2013 6:57 PM, flyingch...@gmail.com wrote:

Yes sir on Ubuntu Angstrom ArchArmLinux are the three I tried all with crippling slow ethernet speeds.

Still at a total loss for what is causing it and my project requires functional ethernet.

Could the board just have a bad ethernet port on it? Is this some known issue that I cant track down for its rev number?

Thanks for responding you guys, I am hoping this is something that can get solved or would be even happier if I am just being dense and forgetting something, but I honestly do not think its that.

[Gerald Coley]

What do you see when you run the IPERF test on it?

Gerald

On Thu, May 9, 2013 at 9:31 PM, <flyingch...@gmail.com> wrote:

Thanks but have tried many cables and even made new ones. The same cables can be used on other ethernet devices with no issues. Cable is always one of my first tries if I hit an issue with speed on ethernet.

--

Gerald

 

ger...@beagleboard.org

g-co...@ti.com

http://beagleboard.org/

http://circuitco.com/support/

[Gerald Coley]

If I read this correctly. something is definitely messed up here. Let me try a few things here and I will get back to you tomorrow. I am having the people at the factory pull some boards and run the test. I will let you know what they find.

Gerald

On Thu, May 9, 2013 at 10:32 PM, <flyingch...@gmail.com> wrote:

these tests normally work for me on other devices. Please state if this is a bad series to run.


Test 1:
iperf -c iperf.acd.net -P 10 -t 240 -w 130000                  
connect failed: Connection timed out                                           
connect failed: Connection timed out                                           
connect failed: Connection timed out                                           
connect failed: Connection timed out                                           
connect failed: Connection timed out                                           
connect failed: Connection timed out                                           
connect failed: Connection timed out                                           
connect failed: Connection timed out                                           
connect failed: Connection timed out                                           
connect failed: Connection timed out

Test 2:
iperf -c iperf.acd.net -P 10 -t 240 -w 130000 -r
------------------------------------------------------------
Server listening on TCP port 5001
TCP window size:  254 KByte (WARNING: requested  127 KByte)
------------------------------------------------------------
connect failed: Connection timed out
connect failed: Connection timed out                                           
connect failed: Connection timed out                                           
connect failed: Connection timed out                                           
connect failed: Connection timed out                                           
connect failed: Connection timed out                                           
connect failed: Connection timed out                                           
connect failed: Connection timed out                                           
connect failed: Connection timed out

Basically iperf borks trying to test. Using every mirror I can try as far as updating Angstrom and Ubuntu I get below 10kbs mostly in the 5kbs range.

[evilwulfie]

I get the exact same errors on my BBB

never used iperf before



On 5/9/2013 8:42 PM, flyingch...@gmail.com wrote:

Awesome thanks Gerald.

Let me know if you want any other info from my board. Tests on multiple OS's is fine as well.

Thanks!!

[evilwulfie]

OK some info iperf.acd.net seems to be the issue

i installed iperf on my server and use it to test the bone with via the internet and it works

install iperf on a known server preferably on the same subnet as the bone

and rerun your tests i think you will see it working

this is over my crappy wireless to lousy DSL to my uber fast linode


root@beaglebone:/etc# iperf -c wulfman.com -P 10 -t 240 -w 130000
------------------------------------------------------------
Client connecting to wulfman.com, TCP port 5001

TCP window size:   254 KByte (WARNING: requested   127 KByte)
------------------------------------------------------------

[  5] local 192.168.254.2 port 51822 connected with 64.62.190.245 port 5001
[  8] local 192.168.254.2 port 51814 connected with 64.62.190.245 port 5001
[ 10] local 192.168.254.2 port 51813 connected with 64.62.190.245 port 5001
[  4] local 192.168.254.2 port 51815 connected with 64.62.190.245 port 5001
[  6] local 192.168.254.2 port 51816 connected with 64.62.190.245 port 5001
[  7] local 192.168.254.2 port 51817 connected with 64.62.190.245 port 5001
[  9] local 192.168.254.2 port 51818 connected with 64.62.190.245 port 5001
[  3] local 192.168.254.2 port 51819 connected with 64.62.190.245 port 5001
[ 11] local 192.168.254.2 port 51820 connected with 64.62.190.245 port 5001
[ 12] local 192.168.254.2 port 51821 connected with 64.62.190.245 port 5001
[ ID] Interval       Transfer     Bandwidth
[ 12]  0.0-243.3 sec    456 KBytes  15.4 Kbits/sec
[  5]  0.0-244.9 sec    296 KBytes  9.90 Kbits/sec
[  9]  0.0-247.1 sec    528 KBytes  17.5 Kbits/sec
[  7]  0.0-251.8 sec    704 KBytes  22.9 Kbits/sec
[ 11]  0.0-253.7 sec    600 KBytes  19.4 Kbits/sec
[  3]  0.0-258.1 sec    408 KBytes  13.0 Kbits/sec
[  8]  0.0-259.5 sec    696 KBytes  22.0 Kbits/sec
[  4]  0.0-265.1 sec    512 KBytes  15.8 Kbits/sec
[ 10]  0.0-272.3 sec    400 KBytes  12.0 Kbits/sec
[  6]  0.0-289.1 sec    600 KBytes  17.0 Kbits/sec
[SUM]  0.0-289.1 sec  5.08 MBytes    147 Kbits/sec

On 5/9/2013 8:42 PM, flyingch...@gmail.com wrote:

Awesome thanks Gerald.

Let me know if you want any other info from my board. Tests on multiple OS's is fine as well.

Thanks!!



On Thursday, May 9, 2013 8:39:14 PM UTC-7, Gerald wrote:

[Gerald Coley]

You need something to download from of a known speed and performance. That is hard to do over the internet.

If you had two board, you could use them, back to back.

Gerald

On Thu, May 9, 2013 at 11:05 PM, <flyingch...@gmail.com> wrote:

weird works on my laptop.

Tried to do it to your domain but of course connection refused ;) .. But then I did to google.com and same thing connection timed out.

So I am guessing iperf may not be the most stable to use for testing something like this.

Is there some other tests I can run from the BB? Shouldnt downloading a package from the repo's be a decent through put idea?

[evilwulfie]

i stopped the server last night  i can re-enable it if you need it to test

On 5/9/2013 9:05 PM, flyingch...@gmail.com wrote:

weird works on my laptop.

Tried to do it to your domain but of course connection refused ;) .. But then I did to google.com and same thing connection timed out.

So I am guessing iperf may not be the most stable to use for testing something like this.

Is there some other tests I can run from the BB? Shouldnt downloading a package from the repo's be a decent through put idea?

[Gerald Coley]

Just give us some time to work on this and see. Whatever we find, if anything, won't be fixed in the next 24 hours. Let us do a little investigation.

Gerald

On Fri, May 10, 2013 at 11:28 AM, <flyingch...@gmail.com> wrote:

So what do you guys propose?

I hit my laptop with the test and seems to perform much better than if I am trying to update or download something with wget.

the BB is the server in the iperf test.
BB results:
perf -s -u -p 12345                                           
------------------------------------------------------------                   
Server listening on UDP port 12345                                             
Receiving 1470 byte datagrams                                                  
UDP buffer size:  160 KByte (default)                                          
------------------------------------------------------------                   
[  3] local 192.168.1.114 port 12345 connected with 192.168.1.107 port 60627   
[ ID] Interval       Transfer     Bandwidth        Jitter   Lost/Total Datagrams
[  3]  0.0-30.0 sec  3.75 MBytes  1.05 Mbits/sec   0.006 ms    0/ 2676 (0%)    
[  4] local 192.168.1.114 port 12345 connected with 192.168.1.107 port 37608   
[  4]  0.0-30.0 sec  3.75 MBytes  1.05 Mbits/sec   0.009 ms    0/ 2676 (0%)

Results from my laptop:
iperf -c 192.168.1.114 -u -p 12345 -t 30
------------------------------------------------------------
Client connecting to 192.168.1.114, UDP port 12345
Sending 1470 byte datagrams
UDP buffer size:  124 KByte (default)
------------------------------------------------------------
[  3] local 192.168.1.107 port 60627 connected with 192.168.1.114 port 12345
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-30.0 sec  3.75 MBytes  1.05 Mbits/sec
[  3] Sent 2676 datagrams
[  3] Server Report:
[  3]  0.0-30.0 sec  3.75 MBytes  1.05 Mbits/sec   0.005 ms    0/ 2676 (0%)
$ iperf -c 192.168.1.114 -u -p 12345 -t 30
------------------------------------------------------------
Client connecting to 192.168.1.114, UDP port 12345
Sending 1470 byte datagrams
UDP buffer size:  124 KByte (default)
------------------------------------------------------------
[  3] local 192.168.1.107 port 37608 connected with 192.168.1.114 port 12345
[ ID] Interval       Transfer     Bandwidth
[  3]  0.0-30.0 sec  3.75 MBytes  1.05 Mbits/sec
[  3] Sent 2676 datagrams
[  3] Server Report:
[  3]  0.0-30.0 sec  3.75 MBytes  1.05 Mbits/sec   0.008 ms    0/ 2676 (0%)

A wget test - DL'ing a .pdf from here https://github.com/MarkAYoder/BeagleBoard-exercises/blob/master/pptx/01-1%20Intro%20to%20Beagle.pdf
Saving to: ��‘01-1 Intro to Beagle.pdf��’                                      
                                                                               
100%[======================================>] 660,955     37.0KB/s   in 17s    
                                                                               
2013-05-10 11:21:41 (38.2 KB/s) - ��‘01-1 Intro to Beagle.pdf��’ saved [660955/]

Same test performed on my laptop on the same network and the same ethernet cable that the BB used:
Length: 21288 (21K) [text/html]
Saving to: ‘01-1 Intro to Beagle.pdf’

100%[======================================>] 21,288      --.-K/s   in 0.003s 

2013-05-10 09:27:01 (7.44 MB/s) - ‘01-1 Intro to Beagle.pdf’ saved [21288/21288]

The above should be close to what the BB gets.

But then if I try an update my Angstrom Image it just takes for ever, but can not show you average speed as it does not display this.

So what else can I do or try to get it to work normally with updating and using wget.

[Gerald Coley]

Can you register? That way I don't have to approve all your emails and they go through immediately, or shortly there after..

Gerald

On Fri, May 10, 2013 at 11:41 AM, <flyingch...@gmail.com> wrote:

OK thank you Gerlad.

[Gerald Coley]

No problem! You are now one of the many!

Thanks!

Gerald

On Fri, May 10, 2013 at 12:06 PM, <flyingch...@gmail.com> wrote:

Sorry thought I did when I signed up. Hopefully this solves that part for you.

Thanks for you endless support and hard work..

[Gerald Coley]

Here are the results of our testing:

Connecting Black directly to PC:

On BBB:

root@beaglebone:~# iperf -c 169.254.226.13

------------------------------------------------------------

Client connecting to 169.254.226.13, TCP port 5001

TCP window size: 21.0 KByte (default)

------------------------------------------------------------

[  3] local 169.254.206.196 port 32796 connected with 169.254.226.13 port 5001

[ ID] Interval       Transfer     Bandwidth

[  3]  0.0-10.0 sec    112 MBytes  94.2 Mbits/sec

 

On PC (server):

bin/iperf.exe -s -P 0 -i 1 -p 5001 -f k

------------------------------------------------------------

Server listening on TCP port 5001

TCP window size: 8.00 KByte (default)

------------------------------------------------------------

[1872] local 169.254.226.13 port 5001 connected with 169.254.206.196 port 32796

[ ID] Interval       Transfer     Bandwidth

[1872]  0.0- 1.0 sec  11623 KBytes  95214 Kbits/sec

[1872]  1.0- 2.0 sec  11492 KBytes  94143 Kbits/sec

[1872]  2.0- 3.0 sec  11492 KBytes  94141 Kbits/sec

[1872]  3.0- 4.0 sec  11476 KBytes  94008 Kbits/sec

[1872]  4.0- 5.0 sec  11490 KBytes  94124 Kbits/sec

[1872]  5.0- 6.0 sec  11492 KBytes  94141 Kbits/sec

[1872]  6.0- 7.0 sec  11489 KBytes  94115 Kbits/sec

[1872]  7.0- 8.0 sec  11494 KBytes  94157 Kbits/sec

[1872]  8.0- 9.0 sec  11489 KBytes  94119 Kbits/sec

[1872]  0.0-10.0 sec  115016 KBytes  94221 Kbits/sec

Gerald

[flyingch...@gmail.com]

Thanks Gerald,

Wonder why I can not get good results just updating my images then. Is it normal for the speed to be so low?

[Gerald Coley]

There are variables. As you saw, we got 94MB/s. But, that is on a clean connection which truly tests the capability of the board, which is what we are looking at. The first time we ran it on the network, it was much worse, like 500KB/S.

Gerald

[Stu Iliev]

Gerald,

The BeagleBone performs well on a "clean" network, but very bad on a "not clean" network.
Why would that be? How to fix it?

Stu

[Gerald Coley]

I guess it would depend on the definition of a "clean"  versus "not clean" network. There are a lot of settings inside the PHY that could be tweaked via a change in the SW driver.

Gerald

--