Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 30 Mar 1999 00:42:56 -0800
From:      Ulf Zimmermann <ulf@Alameda.net>
To:        adrian@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
Subject:   Re: fxp driver causing lockup
Message-ID:  <19990330004256.A52430@TelcoSucks.org>
In-Reply-To: <19990330082208.28563.qmail@ewok.creative.net.au>; from adrian@FreeBSD.ORG on Tue, Mar 30, 1999 at 04:22:07PM %2B0800
References:  <19990329162147.D45807@TelcoSucks.org> <19990330082208.28563.qmail@ewok.creative.net.au>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Mar 30, 1999 at 04:22:07PM +0800, adrian@FreeBSD.ORG wrote:
> 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 <wes@softweyr.com> 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.

It is not in the SNAP from yesterday yet, so I looked around. Found
the BIOS setting, worked like a charm then.

> 
> 
> 
> Adrian
> 
> 
> To Unsubscribe: send mail to majordomo@FreeBSD.org
> with "unsubscribe freebsd-hackers" in the body of the message

-- 
Regards, Ulf.

---------------------------------------------------------------------
Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936
Alameda Networks, Inc. | http://www.Alameda.net  | Fax#: 510-521-5073


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990330004256.A52430>