Date: Wed, 25 Jun 2008 08:20:03 GMT From: "Manuel Kasper" <mkasper@monzoon.net> To: freebsd-net@FreeBSD.org Subject: Re: kern/122295: [bge] bge Ierr rate increase (since 6.0R) [regression] Message-ID: <200806250820.m5P8K30M010556@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/122295; it has been noted by GNATS. From: "Manuel Kasper" <mkasper@monzoon.net> To: <bug-followup@FreeBSD.org> Cc: <r.gruyters@yirdis.nl> Subject: Re: kern/122295: [bge] bge Ierr rate increase (since 6.0R) [regression] Date: Wed, 25 Jun 2008 09:48:29 +0200 We've been experiencing the same issue with BCM5704 B0 in HP ProLiant DL360 G4 servers. The Ierrs are correlated with packet loss (which is why we noticed the problem in the first place); however for us, the patch in <http://marc.info/?l=3Dfreebsd-net&m=3D116838816601104&w=3D2>; completely fixes the problem and doesn't seem to introduce any problems with link state detection (cable disconnect/reconnect, changing link speed on remote end etc. all work fine). Also, OpenBSD already has essentially the same fix (with some dubious style changes) in its repository: <http://www.openbsd.org/cgi-bin/cvsweb/src/sys/dev/pci/if_bge.c#rev1.221 > The problem appears in both FreeBSD 6.3-RELEASE and 7.0-RELEASE. This is how things look without the fix (regardless of what link speed is used): ---- Router#ping 192.168.4.1 repeat 1000 size 1500 Type escape sequence to abort. Sending 1000, 1500-byte ICMP Echos to 192.168.4.1, timeout is 2 seconds: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!.!.!.!.!.!.!.!.!.!.!.!.!.!.!.!.!.!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!! Success rate is 98 percent (983/1000), round-trip min/avg/max =3D 1/1/4 = ms ---- -> Pings from Cisco routers are especially likely to show the issue, as apparently mii_tick() and the pings from the Cisco occur synchronously for a while. TCP throughput isn't affected very much. Related dmesg output: bge0: <Broadcom BCM5704 B0, ASIC rev. 0x2100> mem 0xfdd70000-0xfdd7ffff irq 25 at device 2.0 on pci2 miibus1: <MII bus> on bge0 brgphy0: <BCM5704 10/100/1000baseTX PHY> on miibus1 brgphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseTX, 1000baseTX-FDX, auto bge0: Ethernet address: 00:18:71:e4:xx:xx pciconf -lv: bge0@pci2:2:0: class=3D0x020000 card=3D0x00d00e11 chip=3D0x164814e4 = rev=3D0x10 hdr=3D0x00 vendor =3D 'Broadcom Corporation' device =3D 'BCM5704 NetXtreme Dual Gigabit Adapter' class =3D network subclass =3D ethernet
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200806250820.m5P8K30M010556>