From owner-freebsd-bugs  Fri Mar 24  8:20: 5 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id ED97837B635
	for <freebsd-bugs@FreeBSD.org>; Fri, 24 Mar 2000 08:20:01 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id IAA90568;
	Fri, 24 Mar 2000 08:20:01 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: from web2.sea.nwserv.com (web2.sea.nwserv.com [216.145.16.2])
	by hub.freebsd.org (Postfix) with ESMTP id 61D6037B72E
	for <FreeBSD-gnats-submit@freebsd.org>; Fri, 24 Mar 2000 08:14:07 -0800 (PST)
	(envelope-from spatula@web2.sea.nwserv.com)
Received: (from spatula@localhost)
	by web2.sea.nwserv.com (8.9.3/8.9.3) id IAA07695;
	Fri, 24 Mar 2000 08:14:06 -0800 (PST)
	(envelope-from spatula)
Message-Id: <200003241614.IAA07695@web2.sea.nwserv.com>
Date: Fri, 24 Mar 2000 08:14:06 -0800 (PST)
From: freebsd@spatula.net
Reply-To: freebsd@spatula.net
To: FreeBSD-gnats-submit@freebsd.org
X-Send-Pr-Version: 3.2
Subject: kern/17581: devices silently fail
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         17581
>Category:       kern
>Synopsis:       devices failing probing do so silently
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Fri Mar 24 08:20:01 PST 2000
>Closed-Date:
>Last-Modified:
>Originator:     Nick Johnson
>Release:        FreeBSD 4.0-RELEASE i386
>Organization:
Spatula Systems
>Environment:
re-rolled 4.0-release
	

>Description:
Unlike previous versions of FreeBSD, when devices in 4.0-release fail to
probe, they do so silently (instead of reporting "xxx not found" or 
"xxx conflicts with zzz, not probed", etc).  This makes debugging more
difficult, and happens even with the -v flag given to the kernel.

If a new boot flag has been added to show these failures, it is not documented
in boot(8).
	

>How-To-Repeat:
Add any driver for a device not in your system to the kernel.
	

>Fix:
Add and/or document a boot flag to show probe failures, or show them with
greater verbosity by default.
	
	


>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message