From owner-freebsd-questions Sat Jun 26 17: 2:36 1999 Delivered-To: freebsd-questions@freebsd.org Received: from reiters.org (kewanee.net [208.29.66.222]) by hub.freebsd.org (Postfix) with ESMTP id 06F9B14CE0 for ; Sat, 26 Jun 1999 17:02:33 -0700 (PDT) (envelope-from denny@reiters.org) Received: (from denny@localhost) by reiters.org (8.9.3/8.9.2) id TAA85528; Sat, 26 Jun 1999 19:02:24 -0500 (CDT) (envelope-from denny) Date: Sat, 26 Jun 1999 19:02:24 -0500 From: Dennis Reiter To: Doug White Cc: "Potter, Jeff" , "'freebsd-questions@FreeBSD.ORG'" Subject: Re: FreeBSD 3.1 locks when using fxp0 ... Message-ID: <19990626190224.B82345@reiters.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Doug White on Fri, Jun 25, 1999 at 03:11:52PM -0700 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Quoting Doug White (dwhite@resnet.uoregon.edu): > On Tue, 22 Jun 1999, Potter, Jeff wrote: > > > FreeBSD 3.1 locks when using fxp0 (Intel Pro100B) during installation. When > > the installation script attempts to bind ip address & netmask the unit locks > > hard. The unit must be power cycled to recover. > > > > Hardware: > > > > Compaq Deskpro EN (DPENS P400/6) > > 400MHZ PII CPU > > 128MB RAM > > ATI Rage Turbo AGP (Embedded) > > Compaq Intel 10/100 Network Controller (Embedded Intel 82558B) > > Sounds like an interrupt problem. > Pretty sure it is an interrupt conflict. Try disabling the USB ports if they're enabled. This sounds similar to a problem I had w/ a machine. -- Denny Reiter | denny@reiters.org FreeBSD: The Power to Serve | www.freebsd.org Linux Users Group Galesburg Area | www.productivity.org/groups/lugga The best things in life are free, but the expensive ones are still worth a look. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message