From owner-freebsd-questions  Fri Aug  9 08:02:22 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id IAA17797
          for questions-outgoing; Fri, 9 Aug 1996 08:02:22 -0700 (PDT)
Received: from alpha.pair.com (pair.com [207.86.128.11])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id IAA17786
          for <freebsd-questions@freebsd.org>; Fri, 9 Aug 1996 08:02:18 -0700 (PDT)
Received: (from sigma@localhost) by alpha.pair.com (8.7.5/8.6.12) id LAA20397 for freebsd-questions@freebsd.org; Fri, 9 Aug 1996 11:02:20 -0400 (EDT)
From: Kevin Martin <sigma@pair.com>
Message-Id: <199608091502.LAA20397@alpha.pair.com>
Subject: SMC 10/100 network lockup problem
To: freebsd-questions@freebsd.org
Date: Fri, 9 Aug 1996 11:02:20 -0400 (EDT)
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I've occasionally seen strange behavior from a couple of FreeBSD 2.1.0
machines using SMC 10/100 EtherPower cards on a 10baseT network.

About one in every dozen reboots, when the network card is enabled and
ifconfig'ed, it creates a packet storm and locks up - you can only clean
things up by turning off the misbehaving machine.

I've noticed that this does not happen with the plain 10mbps cards, and I
don't think I've seen it happen on FreeBSD 2.1.5.  Before I make the
upgrade on these machines (they're not too important, except when they
misbehave), I wanted to see if anyone had seen this kind of behavior and
either knew that 2.1.5 is the fix, or that I need some special ifconfig
command (ie, "link2"?).

Thanks,
Kevin Martin
sigma@pair.com