ale(4): Problems with tso, rxcsum and/or txcsum
Ulrich Spörlein
uqs at spoerlein.net
Mon Jun 15 12:16:33 UTC 2009
Hello Pyun,
I have connection problems with the onboard GigE of an Asus P5Q board, using a recent 8-CURRENT
ale0: <Atheros AR8121/AR8113/AR8114 PCIe Ethernet> port 0xdc00-0xdc7f mem 0xfe9c0000-0xfe9fffff irq 17 at device 0.0 on pci2
ale0: 960 Tx FIFO, 1024 Rx FIFO
ale0: Using 1 MSI messages.
ale0: 4GB boundary crossed, switching to 32bit DMA addressing mode.
miibus0: <MII bus> on ale0
ale0: Ethernet address: 00:24:8c:36:3e:10
ale0: [FILTER]
ale0: link state changed to UP
ale0 at pci0:2:0:0: class=0x020000 card=0x82261043 chip=0x10261969 rev=0xb0 hdr=0x00
vendor = 'Attansic (Now owned by Atheros)'
device = 'PCI-E ETHERNET CONTROLLER (AR8121/AR8113 )'
class = network
subclass = ethernet
ale0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=311b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING,TSO4,WOL_MCAST,WOL_MAGIC>
ether 00:24:8c:36:3e:10
inet 192.168.0.146 netmask 0xffffff00 broadcast 192.168.0.255
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
When transferring data to the machine at ~10MB/s (100Mbit network only) the ssh
connection will die after a couple of minutes with
Disconnecting: Bad packet length 1592360521.
After disabling tso, txcsum and rxcsum the connection seems to be
stable, though. I fail to figure out a pattern, though. Do I need to
down/up the interface for changes to tso or {tr}xcsum to have any
effect?
Right now I'm rsyncing several GB to the machine and the connection
seems stable even though I re-activated tso, rxcum and txcsum. This is
rather weird ... Are problems with this chip revision known?
Cheers,
Ulrich Spörlein
--
http://www.dubistterrorist.de/
More information about the freebsd-current
mailing list