From owner-freebsd-current@FreeBSD.ORG  Fri Mar 19 12:09:53 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2569516A4CE
	for <current@freebsd.org>; Fri, 19 Mar 2004 12:09:53 -0800 (PST)
Received: from rwcrmhc12.comcast.net (rwcrmhc12.comcast.net [216.148.227.85])
	by mx1.FreeBSD.org (Postfix) with ESMTP id F008A43D2D
	for <current@freebsd.org>; Fri, 19 Mar 2004 12:09:52 -0800 (PST)
	(envelope-from freebsd-current-local@be-well.ilk.org)
Received: from be-well.no-ip.com ([66.30.196.44])
          by comcast.net (rwcrmhc12) with ESMTP
          id <2004031920095201400es6ese>; Fri, 19 Mar 2004 20:09:52 +0000
Received: by be-well.no-ip.com (Postfix, from userid 1147)
	id EA5AFE; Fri, 19 Mar 2004 15:09:51 -0500 (EST)
Sender: lowell@be-well.ilk.org
To: current@freebsd.org
References: <20040318132321.F9436@root.org>
From: Lowell Gilbert <freebsd-current-local@be-well.ilk.org>
Date: 19 Mar 2004 15:09:51 -0500
In-Reply-To: <20040318132321.F9436@root.org>
Message-ID: <44ekromwds.fsf@be-well.ilk.org>
Lines: 6
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Subject: Re: agp0 hang in 5.2.1-RELEASE
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Mar 2004 20:09:53 -0000

Nate Lawson <nate@root.org> writes:

> It can't be disabled at the loader prompt?

I don't think so; there doesn't seem to be any way to avoid the
probe.