Date: Mon, 29 Dec 2003 20:46:06 +0100 From: Dejan Lesjak <dejan.lesjak@ijs.si> To: "Kevin Oberman" <oberman@es.net> Cc: freebsd-current@freebsd.org Subject: Re: 5.2-RC oerrs and collisions on dc0 Message-ID: <200312292046.06501.dejan.lesjak@ijs.si> In-Reply-To: <20031228233331.1F3F05D04@ptavv.es.net> References: <20031228233331.1F3F05D04@ptavv.es.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 29 of December 2003 00:33, Kevin Oberman wrote:
> > From: Dejan Lesjak <dejan.lesjak@ijs.si>
> > Date: Sun, 28 Dec 2003 00:49:50 +0100
> > Sender: owner-freebsd-current@freebsd.org
> >
> >
> > --Boundary-00=_eqh7/a7oNAgo+1o
> > Content-Type: text/plain;
> > charset="us-ascii"
> > Content-Transfer-Encoding: 7bit
> > Content-Disposition: inline
> >
> > Hello,
> >
> > I tried 5.2-RC2 on alpha and netstat -i keeps showing oerrs and
> > collisions on dc card (DEC DE500-BA):
> >
> > Name Mtu Network Address Ipkts Ierrs Opkts Oerrs
> > Coll
> > nge0* 1500 <Link#1> 00:04:5a:71:d2:e0 0 0 0 0
> > 0
> > dc0 1500 <Link#2> 00:00:f8:10:52:47 1478 0 737 335
> > 5695
> > dc0 1500 193.2.4 ewok 1103 - 733 -
> > -
> > lo0 16384 <Link#3> 14 0 14 0
> > 0
> > lo0 16384 your-net localhost 0 - 0
>
> -
>
> This looks very much like an auto-negotiation problem. Can you check
> ifconfig dc0?
Yes of course, I knew I would forget to send something:
dc0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
inet 193.2.4.17 netmask 0xffffff00 broadcast 193.2.4.255
ether 00:00:f8:10:52:47
media: Ethernet autoselect (100baseTX <full-duplex>)
status: active
>
> To have collisions, it must be running half-duplex. (By definition
> collision detection is disabled in FDX.) The additional errors further
> support this.
>
> The other question is what the other end of this link sees. Is it
> running full or half duplex? If full duplex, is it seeing input errors?
>
> If the far end is running FDX, can you set this end explicitly to FDX?
The other end is a switch and it is on FDX, that is why these collisions are
so curious. Switch doesn't see input errors, it does however see out errors.
I tried explicitly setting dc0 to 100baseTX, full-duplex and collisions are
still there. Also I tried setting this explicitly in SRM, but no change.
Anything else I can try?
--
Behind every great computer sits a skinny little geek.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200312292046.06501.dejan.lesjak>