FC4 - IBM e326 - network problems.
Naoki
naoki at valuecommerce.com
Mon Aug 22 04:28:44 UTC 2005
When I do reinitialise I get this :
tg3: eth0: Link is down.
tg3: eth0: Link is up at 100 Mbps, full duplex.
tg3: eth0: Flow control is off for TX and off for RX.
On Mon, 2005-08-22 at 12:53 +0900, Naoki wrote:
> Hi all.
>
> I have a networking problem here I'd like to share.
>
> Cut down FC4 build on an IBM e326.
>
> I am attempting to SCP 2.4MB of data to this box ( from anywhere the
> results are the same ).
>
> It connects, asks for password, which I give. And then after a few
> packets I see it all go very ugly indeed. Throwing retransmissions and,
> segment losts, and DUP ACK messages.
> Which just kills the scp with a "Stalled" message. If I leave it then
> _eventaully_ the file will transfer.
>
> I've changed switches and have the same result. Starting to wonder if
> there is a problem with the Broadcom ethernet controller? One of the
> reasons I suspect the controller is performance jumps to normal (good)
> after I reinitialise the card.
>
>
> Server end :
>
> 4.913749 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
> len=144
> 4.916377 10.0.2.31 -> 10.0.2.27 SSHv2 Encrypted response packet
> len=32
> 4.916533 10.0.2.27 -> 10.0.2.31 TCP 60952 > ssh [ACK] Seq=1293
> Ack=1597 Win=8400 Len=0 TSV=2056922151 TSER=5310028
> 4.916828 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
> len=64
> 4.916965 10.0.2.31 -> 10.0.2.27 SSHv2 Encrypted response packet
> len=48
> 4.917276 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
> len=64
> 4.918916 10.0.2.31 -> 10.0.2.27 SSHv2 Encrypted response packet
> len=48
> 4.958139 10.0.2.27 -> 10.0.2.31 TCP 60952 > ssh [ACK] Seq=1421
> Ack=1693 Win=8400 Len=0 TSV=2056922193 TSER=5310031
> 4.958153 10.0.2.31 -> 10.0.2.27 SSHv2 Encrypted response packet
> len=48
> 4.958306 10.0.2.27 -> 10.0.2.31 TCP 60952 > ssh [ACK] Seq=1421
> Ack=1741 Win=8400 Len=0 TSV=2056922193 TSER=5310070
> 4.958609 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
> len=64
> 4.958762 10.0.2.31 -> 10.0.2.27 SSHv2 Encrypted response packet
> len=48
> 4.962323 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
> len=1448
> 4.962446 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
> len=1448
> 4.962451 10.0.2.31 -> 10.0.2.27 TCP ssh > 60952 [ACK] Seq=1789
> Ack=4381 Win=15424 Len=0 TSV=5310074 TSER=2056922196
> 4.962986 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
> len=1448
> 4.963239 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Previous segment
> lost] Encrypted request packet len=1448
> 4.963244 10.0.2.31 -> 10.0.2.27 TCP ssh > 60952 [ACK] Seq=1789
> Ack=5829 Win=18320 Len=0 TSV=5310075 TSER=2056922197 SLE=7277 SRE=8725
> 4.963780 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
> len=1448
> 4.963785 10.0.2.31 -> 10.0.2.27 TCP [TCP Dup ACK 46#1] ssh >
> 60952 [ACK] Seq=1789 Ack=5829 Win=18320 Len=0 TSV=5310076
> TSER=2056922197 SLE=7277 SRE=10173
> 5.178550 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Retransmission]
> Encrypted request packet len=1448
> 5.178557 10.0.2.31 -> 10.0.2.27 TCP ssh > 60952 [ACK] Seq=1789
> Ack=10173 Win=21216 Len=0 TSV=5310290 TSER=2056922413
> 5.179217 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Previous segment
> lost] Encrypted request packet len=1448
> 5.179221 10.0.2.31 -> 10.0.2.27 TCP [TCP Dup ACK 50#1] ssh >
> 60952 [ACK] Seq=1789 Ack=10173 Win=21216 Len=0 TSV=5310291
> TSER=2056922413 SLE=11621 SRE=13069
> 5.179741 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
> len=1448
> 5.179745 10.0.2.31 -> 10.0.2.27 TCP [TCP Dup ACK 50#2] ssh >
> 60952 [ACK] Seq=1789 Ack=10173 Win=21216 Len=0 TSV=5310292
> TSER=2056922413 SLE=11621 SRE=14517
> 5.180252 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
> len=1448
> 5.180255 10.0.2.31 -> 10.0.2.27 TCP [TCP Dup ACK 50#3] ssh >
> 60952 [ACK] Seq=1789 Ack=10173 Win=21216 Len=0 TSV=5310292
> TSER=2056922413 SLE=11621 SRE=15965
> 5.391515 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Retransmission]
> Encrypted request packet len=1448
> 5.391520 10.0.2.31 -> 10.0.2.27 TCP ssh > 60952 [ACK] Seq=1789
> Ack=15965 Win=24112 Len=0 TSV=5310503 TSER=2056922626
> 5.392043 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
> len=1448
> 5.392048 10.0.2.31 -> 10.0.2.27 TCP ssh > 60952 [ACK] Seq=1789
> Ack=17413 Win=27008 Len=0 TSV=5310504 TSER=2056922626
> 5.603540 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Out-Of-Order]
> Encrypted request packet len=1448
> 5.603546 10.0.2.31 -> 10.0.2.27 TCP [TCP Dup ACK 60#1] ssh >
> 60952 [ACK] Seq=1789 Ack=17413 Win=27008 Len=0 TSV=5310715
> TSER=2056922838 SLE=15965 SRE=17413
>
> Broadcom Corporation NetXtreme BCM5704 Gigabit Ethernet - tg3 driver.
> # ethtool eth0
> Settings for eth0:
> Supported ports: [ MII ]
> Supported link modes: 10baseT/Half 10baseT/Full
> 100baseT/Half 100baseT/Full
> 1000baseT/Half 1000baseT/Full
> Supports auto-negotiation: Yes
> Advertised link modes: Not reported
> Advertised auto-negotiation: No
> Speed: 100Mb/s
> Duplex: Full
> Port: Twisted Pair
> PHYAD: 1
> Transceiver: internal
> Auto-negotiation: off
> Supports Wake-on: g
> Wake-on: d
> Current message level: 0x000000ff (255)
> Link detected: yes
>
>
>
> Client end :
> 5.019926 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Retransmission]
> Encrypted request packet len=1448
> 5.020438 10.0.2.31 -> 10.0.2.27 TCP ssh > 35380 [ACK] Seq=1789
> Ack=7277 Win=21216 Len=0 TSV=6343633 TSER=2057955472 SLE=4381 SRE=5829
> 5.020513 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
> len=1448
> 5.020523 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
> len=1448
> 5.263902 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Retransmission]
> Encrypted request packet len=1448
> 5.264426 10.0.2.31 -> 10.0.2.27 TCP ssh > 35380 [ACK] Seq=1789
> Ack=10173 Win=24112 Len=0 TSV=6343877 TSER=2057955920
> 5.264464 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Retransmission]
> Encrypted request packet len=1448
> 5.264475 10.0.2.27 -> 10.0.2.31 SSHv2 Encrypted request packet
> len=1448
> 5.500935 10.0.2.27 -> 10.0.2.31 SSHv2 [TCP Retransmission]
> Encrypted request packet len=1448
>
> Client shows retransmissions but no DUP Ack or segment lost messages.
>
> Any ideas? I have other servers running with Broadcom BCM5703X chips and
> using the tg3 driver without problem.
More information about the fedora-list
mailing list