Hi,
Im using a built in re(4) card and it seems like its causes data-
corruption as soon as it gets some load (or after a few hours online)
The machine is running FreeBSD 7.0R:
FreeBSD ninja 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Wed Apr 16 22:49:15
CEST 2008 peter@ninja:/usr/obj/usr/src/sys/NINJA amd64
(using a RELENG_7 kernel updated today)
If I download alot of files with wget or something everything works
fine for a while until the download just stalls and tcpdump reports
"bad cksum"
13:04:25.839408 IP (tos 0x0, ttl 64, id 23912, offset 0, flags [DF],
proto TCP (6), length 1500, bad cksum 0 (->f40a)!) host1.http >
host2.53895: . 115065:116513(1448) ack 1421 win 8326
<nop,nop,timestamp 2316944721 2174233192>
and so on
again and again until the connection times out.
re0: <RealTek 8168/8111B PCIe Gigabit Ethernet> port 0xb800-0xb8ff mem
0xff9ff000-0xff9fffff irq 19 at device 0.0 on pci3
re0: Using 2 MSI messages
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S/8211B media interface> PHY 1 on miibus0
rgephy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT,
1000baseT-FDX, auto
re0: Ethernet address: 00:1d:60:74:be:e3
re0: [FILTER]
re0: [FILTER]
re0@pci0:3:0:0: class=0x020000 card=0x81aa1043 chip=0x816810ec
rev=0x01 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8168/8111 PCI-E Gigabit Ethernet NIC'
class = network
subclass = ethernet
A strange thing is that encrypted data seems to work better than
plaintext. https works for a longer time (after boot) then http for
example.
On Tue, Apr 29, 2008 at 01:18:10PM +0200, Peter Ankerst?l wrote:> Im using a built in re(4) card and it seems like its causes data-corruption > as soon as it gets some load (or after a few hours online) > > The machine is running FreeBSD 7.0R: > > FreeBSD ninja 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Wed Apr 16 22:49:15 CEST > 2008 peter@ninja:/usr/obj/usr/src/sys/NINJA amd64 > > (using a RELENG_7 kernel updated today) > > > If I download alot of files with wget or something everything works fine > for a while until the download just stalls and tcpdump reports "bad cksum" > > 13:04:25.839408 IP (tos 0x0, ttl 64, id 23912, offset 0, flags [DF], proto > TCP (6), length 1500, bad cksum 0 (->f40a)!) host1.http > host2.53895: . > 115065:116513(1448) ack 1421 win 8326 <nop,nop,timestamp 2316944721 > 2174233192> > and so on > again and again until the connection times out.tcpdump reporting "bad cksum" can occur due to TX/RX checksum offloading. Do you not see this message normally, but only when the problem begins? Have you tried turning off TX/RX offloading to see if the erroneous behaviour goes away? Have you tried disabling RFC1323 to see if that's actually what's responsible for the stalls you're seeing? sysctl net.inet.tcp.rfc1323=0 I'd recommend staying away from Realtek NICs. Pick up an Intel Pro/1000 GT or PT. Realtek has a well-known history of issues. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB |
On Tue, 29 Apr 2008 13:18:10 +0200 Peter Ankerst?l <peter@pean.org> wrote:> Hi, > > Im using a built in re(4) card and it seems like its causes data- > corruption as soon as it gets some load (or after a few hours online)IIRC, this is a known issue with if_re and 7.0-R. It is fixed in 7.0-stable, but I don't remember the date. You can find patches here: http://people.freebsd.org/~yongari/re/ In my case, the problem raised its ugly head after some (unknown) amount of data had been transferred. HTH -- Regards, Torfinn Ingolfsen
On Apr 29, 2008, at 2:08 PM, Jeremy Chadwick wrote:>> > > > I'd recommend staying away from Realtek NICs. Pick up an Intel Pro/ > 1000 > GT or PT. Realtek has a well-known history of issues. > >Just wanted to tell you guys that so far a em(4) seems to have fixed the problem. -- Peter Ankerst?l peter@pean.org