Date: Fri, 24 Mar 2000 08:14:06 -0800 (PST) From: freebsd@spatula.net To: FreeBSD-gnats-submit@freebsd.org Subject: kern/17581: devices silently fail Message-ID: <200003241614.IAA07695@web2.sea.nwserv.com>
next in thread | raw e-mail | index | archive | help
>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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200003241614.IAA07695>