Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 24 Jan 2007 06:17:37 -0800
From:      Jeremy Chadwick <koitsu@FreeBSD.org>
To:        Robin Gruyters <r.gruyters@yirdis.nl>
Cc:        freebsd-stable@freebsd.org
Subject:   Re: bge Ierr rate increase from 5.3R -> 6.1R
Message-ID:  <20070124141737.GA7772@icarus.home.lan>
In-Reply-To: <20070124105741.cj2htvoxcs4gg8wk@server.yirdis.net>
References:  <20070124105741.cj2htvoxcs4gg8wk@server.yirdis.net>

next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jan 24, 2007 at 10:57:41AM +0100, Robin Gruyters wrote:
> I have the same problem here. At the moment I only have two servers  
> upgraded from FreeBSD 5.4R to FreeBSD 6.1R and one to FreeBSD 6.2R.
> 
> And here is the netstat -ni output from our development server:
> 
> [netstat -ni]
> Name    Mtu     Ipkts   Ierrs   Opkts   Oerrs   Coll
> ste0*   1500    0       0       0       0       0
> ste1*   1500    0       0       0       0       0
> ste2*   1500    0       0       0       0       0
> ste3*   1500    0       0       0       0       0
> bge0    1500    9866912 2114443 18835209        0       0
> bge0    1500    2004841 -       18833483        -       -
> bge0    1500    1723393 -       1719554 -       -
> bge0    1500    82      -       66      -       -
> bge0    1500    19036813        -       14796159        -       -
> bge0    1500    38709278        -       35167554        -       -
> bge0    1500    0       -       0       -       -
> bge0    1500    621     -       0       -       -
> bge0    1500    1716    -       0       -       -
> bge0    1500    184     -       0       -       -
> bge0    1500    52881   -       2336    -       -
> bge1*   1500    0       0       0       0       0
> pflog   33208   0       0       0       0
> lo0     16384   0       51692624        0       0
> lo0     16384   6611    -       6611    -       -
> [...]
> 
> Is there a fix for it already, or maybe a workaround?

The problem was that the driver code was not properly obtaining
error statistics from the Broadcom chip, thus errors _were_
(before the fix) not being calculated/accounted for.  Now (after
the fix) errors are being accounted for correctly.

So the errors you see in your netstat output are probably real/
ccurate.  I'll vote for a duplex-related problem or some naughty
cabling.

-- 
| 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 |




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070124141737.GA7772>