From owner-freebsd-hackers Tue Mar 30 0:37:13 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from ewok.creative.net.au (ewok.creative.net.au [203.30.44.41]) by hub.freebsd.org (Postfix) with SMTP id 2AD4614E7E for ; Tue, 30 Mar 1999 00:37:07 -0800 (PST) (envelope-from adrian@freebsd.org) Received: (qmail 28565 invoked by uid 1008); 30 Mar 1999 08:22:08 -0000 Message-ID: <19990330082208.28563.qmail@ewok.creative.net.au> From: adrian@freebsd.org To: freebsd-hackers@freebsd.org Subject: Re: fxp driver causing lockup In-reply-to: Your message of "Mon, 29 Mar 1999 16:21:47 PST." <19990329162147.D45807@TelcoSucks.org> Date: Tue, 30 Mar 1999 16:22:07 +0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Ulf Zimmermann writes: >On Thu, Mar 18, 1999 at 10:29:35PM -0600, 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-RELEAS >E >> 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-3 >50. >> Interestingly, it happened with my machine, but not with a cow-orkers which >> is exactly the same. (By actual inspection, not by model.) > >Had the same problem just now on a Compaq EN, I went into the Bios and >enabled under Advance Options the "PCI Bus Mastering" and that fixed >the problem with the fxp card. > Ditto here. I found the loop, then found DG had commited a patch to the if_fxp.c driver to fix it. The problem exists in 3.1-RELEASE too - apply the patch, and it will work fine. Adrian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message