From owner-freebsd-hackers Thu Mar 18 22:38: 5 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from obie.softweyr.com (unknown [204.68.178.33]) by hub.freebsd.org (Postfix) with ESMTP id 6099F14EDC for ; Thu, 18 Mar 1999 22:38:01 -0800 (PST) (envelope-from wes@softweyr.com) Received: from softweyr.com (wes@zaphod.softweyr.com [204.68.178.35]) by obie.softweyr.com (8.8.8/8.8.8) with ESMTP id XAA21524; Thu, 18 Mar 1999 23:37:36 -0700 (MST) (envelope-from wes@softweyr.com) Message-ID: <36F1F0B0.F8F79F22@softweyr.com> Date: Thu, 18 Mar 1999 23:37:36 -0700 From: Wes Peters Organization: Softweyr llc X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 3.1-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: David Scheidt Cc: hackers@FreeBSD.ORG Subject: Re: fxp driver causing lockup References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG David Scheidt wrote: > > On 19 Mar 1999, Dag-Erling Smorgrav wrote: > > : > :Wes Peters writes: > :> I haven't seen any freezes while *probing* the fxp, but they may not > :> really know the difference. The hang happened in the *attach*, when > :> the user (or system) ifconfig's the interface up. Do you have any > :> details, or a contact I can email? > : > :No, I've never had trouble with the fxp driver. It's something I saw > :mentioned on one of the lists - either -advocacy or -chat. > > The machine on my desk at work had this problem trying to install 3.0-RELEASE > via NFS. The hang occurred at ifconfig up time, not boot time. I was > worried that I wouldn't be able to use FreeBSD because of it. Not getting > my constant unix fix would be a bad thing. The machine is a Compaq EN PII-350. > Interestingly, it happened with my machine, but not with a cow-orkers which > is exactly the same. (By actual inspection, not by model.) Booting it under Windows, disabling the interface, then booting to FreeBSD will probably bring it up. On the other hand, if you have kernel sources on-line, applying the patch will fix the problem so it'll work under FreeBSD without the intervention of MS-Virus. I'll send the patch in a separate message, it's already been posted to several of the mailing lists. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC http://www.softweyr.com/~softweyr wes@softweyr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message