From owner-freebsd-hackers  Mon Jul  7 18:37:14 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA20644
          for hackers-outgoing; Mon, 7 Jul 1997 18:37:14 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA20639
          for <FreeBSD-Hackers@FreeBSD.ORG>; Mon, 7 Jul 1997 18:37:12 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA02838;
	Mon, 7 Jul 1997 18:38:42 -0700 (PDT)
Message-Id: <199707080138.SAA02838@implode.root.com>
To: Simon Shapiro <Shimon@i-Connect.Net>
cc: FreeBSD-Hackers@FreeBSD.ORG
Subject: Re: PCI Bridge Question 
In-reply-to: Your message of "Mon, 07 Jul 1997 10:24:21 PDT."
             <XFMail.970707102421.Shimon@i-Connect.Net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Mon, 07 Jul 1997 18:38:42 -0700
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>>    Then what version was it failing under?
>
>RELENG_2_2 as of Saturday.  Are you maintaining this driver?  Is there a
>maintainer?  Should I dig into it?

   I wrote it; I maintain it.

>> an mbuf cluster had been freed onto the mclfree list. In any case, this
>> appears to be a much more generic problem - not specific to the fxp
>> device
>> driver.
>
>Most likely.  The fxp is where I see it on this system.

   I can't reproduce the problem here, but I haven't tried very hard. Is NFS
static in your kernel, or is it getting loaded as an LKM?

>BTW, what are your thoughts on my project using 3.0 kernel with 2.2 release?
>We really like the SMP kernel, even where it stands today (already better
>than
>NiceTry :-)

   Use -current kernel with -current userland sources; start with 2.2.2 and
upgrade to -current ("3.0") with a "make world" if necessary.

-DG

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