From owner-freebsd-bugs  Sun Sep  2 12:55:58 2001
Delivered-To: freebsd-bugs@freebsd.org
Received: from tomts8-srv.bellnexxia.net (tomts8.bellnexxia.net [209.226.175.52])
	by hub.freebsd.org (Postfix) with ESMTP
	id BBC8F37B406; Sun,  2 Sep 2001 12:55:49 -0700 (PDT)
Received: from xena.gsicomp.on.ca ([64.228.155.124])
          by tomts8-srv.bellnexxia.net
          (InterMail vM.4.01.03.16 201-229-121-116-20010115) with ESMTP
          id <20010902195548.SJL27547.tomts8-srv.bellnexxia.net@xena.gsicomp.on.ca>;
          Sun, 2 Sep 2001 15:55:48 -0400
Received: from hermes (hermes.gsicomp.on.ca [192.168.0.18])
	by xena.gsicomp.on.ca (8.11.1/8.11.1) with SMTP id f82Jn2u09282;
	Sun, 2 Sep 2001 15:49:03 -0400 (EDT)
	(envelope-from matt@gsicomp.on.ca)
Message-ID: <014501c133e8$2f83ca80$1200a8c0@gsicomp.on.ca>
From: "Matthew Emmerton" <matt@gsicomp.on.ca>
To: "Daniel Zuck" <daniel@dan-up.de>, <net@freebsd.org>,
	<bugs@freebsd.org>
References: <69558AC19D6@dan-net.dan-up.de>
Subject: Re: Possibly Bug Report with Kernel ep (3com 5xx ISA and others) driver
Date: Sun, 2 Sep 2001 15:48:06 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4807.1700
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

> >> The machine has 2 interfaces (obviously ep0 and ep1), and
> >> after about 24 hours uptime, ep1 was somehow broken:
> >>
> >> If trying to ping: sendto: no bufferspace available
> >>
> >> ifconfig ep1 down, ifconfig ep1 up was a work-around, but no
> >> solution...
> >>
> >> Netstat showed nothing 'extraordinary' like high ammount of
> >> collissions, late collisions, fragmentations, carrier losses
> >> even the net work load was almost a little above nothing.
>
> >All of these are typical of media problems - bad cables or
> >ports on your hub or switch.

> I can exclude this:
>  - The statistics do not show any 'loss of carrier' (mentioned
> above)
>  - On the same hub's, there are some highly available financial
> applications and web-servers. If there would be that sort of
> problem, I'd surely noticed.
>  - For some other reason, we changed the hub and cabeling, and
> the problem still exists...

Ack!  My error - I didn't notice the "nothing".

> >> I remember to have the same problem with another box running
> 3.3
> >> generic (other hardware...) - so I am wondering if the driver
> >> might be somehow broken.
> >
> >But if it was a driver problem, the problem would show up on
> >both interfaces, right?
>
> Yes, and inbetween I can confirm: The problem occurs on both
> interfaces; the chance that the problem occurs is slightly
> higher on the interface with the higher network load.
>
> To sum up: As the very same problem occurs with pretty different
> hardware, I really think there's something wrong with the
> cooperation of the ep-driver and 3com 509 - maybe the driver,
> maybe some design error on the network cards...
>
> So if sb says: 'No probs with ep driver and ne2000 cards', then
> I think we have to ask 3com... ;)

Aren't the 509s ISA-based?  My thought would be just to replace them with a
newer, more stable NIC.

--
Matt Emmerton


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message