From owner-freebsd-hackers  Sun Oct 12 09:43:27 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id JAA01863
          for hackers-outgoing; Sun, 12 Oct 1997 09:43:27 -0700 (PDT)
          (envelope-from owner-freebsd-hackers)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA01842
          for <hackers@freefall.freebsd.org>; Sun, 12 Oct 1997 09:43:21 -0700 (PDT)
          (envelope-from root@implode.root.com)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id JAA03820;
	Sun, 12 Oct 1997 09:44:31 -0700 (PDT)
Message-Id: <199710121644.JAA03820@implode.root.com>
To: "Greg Rowe" <greg@uswest.net>
cc: "'hackers@freefall.freebsd.org'" <hackers@freefall.freebsd.org>
Subject: Re: fxp0 lost connectivity! 
In-reply-to: Your message of "Sun, 12 Oct 1997 16:15:25 -0000."
             <9710121615.ZM6374@psv.oss.uswest.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Sun, 12 Oct 1997 09:44:31 -0700
Sender: owner-freebsd-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>Will this fix be part of 2.2.5 Release ?

   Anything that is in 2.2-stable up until 2.2.5 is tagged will be in the
release. ...so, yes.

>> >How do I fix it ?
>>
>>    There is a fix in both -current and -stable that works around the hardware
>> bug.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project