From owner-freebsd-questions Fri Sep 1 19: 6:25 2000 Delivered-To: freebsd-questions@freebsd.org Received: from stout.hampshire.edu (stout.hampshire.edu [192.33.12.80]) by hub.freebsd.org (Postfix) with ESMTP id F2FDB37B422 for ; Fri, 1 Sep 2000 19:06:21 -0700 (PDT) Received: from localhost (tdk98@localhost) by stout.hampshire.edu (8.9.3+Sun/8.9.1) with ESMTP id WAA19430 for ; Fri, 1 Sep 2000 22:02:20 -0400 (EDT) X-Authentication-Warning: stout.hampshire.edu: tdk98 owned process doing -bs Date: Fri, 1 Sep 2000 22:02:20 -0400 (EDT) From: Trevor Daniel Kramer X-Sender: tdk98@stout To: FreeBSD Mailing List Subject: Re: [Urgent] 3Com 3C90X Cards not Compatible? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have also seen this problem with a 3Com90X. I am running 4.1 STABLE. Trevor On Fri, 1 Sep 2000, Kenneth Wayne Culver wrote: > What version of FreeBSD is this? > > > ================================================================= > | Kenneth Culver | FreeBSD: The best NT upgrade | > | Unix Systems Administrator | ICQ #: 24767726 | > | and student at The | AIM: muythaibxr | > | The University of Maryland, | Website: (Under Construction) | > | College Park. | http://www.wam.umd.edu/~culverk/| > ================================================================= > > On Fri, 1 Sep 2000 freebsd@alcatraz.wolfpaw.net wrote: > > > Greetings, > > > > Recently I changed the ethernet cards in our gateway from 2 D-Link > > 538TX's to 2 3Com 3C90X's don't remember which one, the 100BaseTX full > > duplex ones (509b maybe?). Anyway, when we had the D-Link cards in the > > machine, all was good - no problems. Yesterday I added the 2 3Com cards > > and now it will just reboot - with no notice - spontainiosly. Its not a > > huge issue, but it causes intermittant 2 minute network failures, which is > > just really teally annoying. There are no system logs to show the reboot, > > and it doesn't even stop to dismount the drives, which is > > worrisome. Anyone have any ideas on why this might be occuring? or > > how I can find out? Ive tried fstat (as we had another FreeBSD server > > crash from a crond prog that left open files everywhere) and it doesn't > > seem to show any problems. > > > > Thanks in Advance :) > > Dale > > Sysadmin, Wolfpaw.net > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-questions" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message