From owner-freebsd-hackers Thu Mar 18 20:30:14 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from smtp.enteract.com (thor.enteract.com [207.229.143.11]) by hub.freebsd.org (Postfix) with SMTP id A9B9C14E78 for ; Thu, 18 Mar 1999 20:30:12 -0800 (PST) (envelope-from dscheidt@enteract.com) Received: (qmail 14056 invoked from network); 19 Mar 1999 04:29:53 -0000 Received: from nathan.enteract.com (dscheidt@207.229.143.6) by thor.enteract.com with SMTP; 19 Mar 1999 04:29:53 -0000 Date: Thu, 18 Mar 1999 22:29:35 -0600 (CST) From: David Scheidt To: hackers@FreeBSD.org Subject: Re: fxp driver causing lockup In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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.) David Scheidt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message