From owner-freebsd-bugs@FreeBSD.ORG  Wed Feb 15 01:56:16 2006
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
X-Original-To: freebsd-bugs@freebsd.org
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2293216A420;
	Wed, 15 Feb 2006 01:56:16 +0000 (GMT)
	(envelope-from amesbury@umn.edu)
Received: from mtaout-m.tc.umn.edu (mtaout-m.tc.umn.edu [160.94.23.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A99BA43D45;
	Wed, 15 Feb 2006 01:56:13 +0000 (GMT)
	(envelope-from amesbury@umn.edu)
Received: from [160.94.247.212] (paulaner.oitsec.umn.edu [160.94.247.212]) by
	mtaout-m.tc.umn.edu with ESMTP; Tue, 14 Feb 2006 19:56:12 -0600 (CST)
X-Umn-Remote-Mta: [N] paulaner.oitsec.umn.edu [160.94.247.212] #+LO+TS+AU+HN
Message-ID: <43F28A3C.20905@umn.edu>
Date: Tue, 14 Feb 2006 19:56:12 -0600
From: Alan Amesbury <amesbury@umn.edu>
User-Agent: Thunderbird 1.5 (X11/20060119)
MIME-Version: 1.0
To: FreeBSD-gnats-submit@freebsd.org,
    freebsd-bugs@freebsd.org
References: <200602150150.k1F1o66Y077138@freefall.freebsd.org>
In-Reply-To: <200602150150.k1F1o66Y077138@freefall.freebsd.org>
X-Enigmail-Version: 0.94.0.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: 
Subject: Re: kern/93369: [PATCH] Fix failed detection of Nvidia NForce2
	chipset
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Feb 2006 01:56:16 -0000

Crap.  It's only *after* I submit this that I see PR78707. 
Unfortunately, we're not ready to rebuild/upgrade the host in question
to 6.0-STABLE, and hope that the support needed will get backported to
5.4 (as suggested in PR78707).


--
Alan Amesbury
University of Minnesota