From owner-freebsd-hackers Thu Mar 18 20: 5:44 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (Postfix) with ESMTP id 09A5B15561; Thu, 18 Mar 1999 20:05:40 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id FAA81789; Fri, 19 Mar 1999 05:05:16 +0100 (CET) (envelope-from des) To: Wes Peters Cc: Dag-Erling Smorgrav , hackers@FreeBSD.ORG, jkh@FreeBSD.ORG Subject: Re: fxp driver causing lockup References: <199903172356.RAA14113@us.networkcs.com> <36F04CD0.B0D46F3B@softweyr.com> <36F1C9B9.257D9269@softweyr.com> From: Dag-Erling Smorgrav Date: 19 Mar 1999 05:05:15 +0100 In-Reply-To: Wes Peters's message of "Thu, 18 Mar 1999 20:51:21 -0700" Message-ID: Lines: 19 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Wes Peters writes: > Dag-Erling Smorgrav wrote: > > Wes Peters writes: > > > It did, it's working fine now. Here's the diff vs. 3.1-RELEASE: > > > [...] > > Hmm, I wonder if this will fix the "freeze while probing fxp0" bug as > > well. ISTR that's what's keeping FreeBSD out of IBM's list of > > recommended operating systems for the Netfinity. > 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. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message