Date: Thu, 8 Jun 2000 07:42:45 +0200 From: Christoph Kukulies <kuku@gilberto.physik.RWTH-Aachen.DE> To: "Brech, Cary" <CBrech@kenan.com> Cc: "'freebsd-bugs@FreeBSD.org'" <freebsd-bugs@FreeBSD.ORG>, "Savio, Florie N" <fsavio@lucent.com>, "'mblott@lucent.com'" <mblott@lucent.com> Subject: Re: DEC Ethernet Chip Bug? Message-ID: <20000608074244.A61703@gil.physik.rwth-aachen.de> In-Reply-To: <2B493F87657DD211817300A0C99DD08405967B9E@camb-exch1.kenan.com>; from CBrech@kenan.com on Wed, Jun 07, 2000 at 01:52:04PM -0400 References: <2B493F87657DD211817300A0C99DD08405967B9E@camb-exch1.kenan.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Jun 07, 2000 at 01:52:04PM -0400, Brech, Cary wrote: > > We are currently encountering a problem with a 10/100 Ethernet Board based > on a DEC Chip. Traffic flows correctly for the first few minutes after a > reboot of the system. After a short period of time, 5 minutes, we can no > longer see TCP traffic. Rebooting restarts the interface. We are using > FreeBSD Version 3.4. > > Has anyone encountered this problem before? If it is the de0 driver I can agree that I had intermediate problems with this driver. But I believe it was before 3.4. Have you tried to shutdown the interface (ifconfig down)? Have you tried to specify the link# option when starting the interface? -- Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000608074244.A61703>