Date: Mon, 20 Jan 2003 21:53:19 -0800 From: Arun Sharma <arun@sharma-home.net> To: FreeBSD-gnats-submit@FreeBSD.org Cc: hackers@FreeBSD.org Subject: kern/47286: device probing not verbose when using boot -v Message-ID: <20030121055319.GA13113@sharma-home.net>
next in thread | raw e-mail | index | archive | help
>Number: 47286 >Category: kern >Synopsis: device probing not verbose when using boot -v >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jan 20 22:00:14 PST 2003 >Closed-Date: >Last-Modified: >Originator: Arun Sharma >Release: FreeBSD 5.0 i386 >Organization: >Environment: When FreeBSD has trouble booting on some hardware, the lockup is silent and leaves no clues about where the hang is happening, even if the user is using boot -v. This makes it very hard for a tester to report meaningful bugs. Specific case in question: kern/44619. The hang was in eisa_probe, but the kernel messages don't provide a clue. So the proposal is to print the name of the device being probed and attached before attempting to do it in kern/subr_bus.c:device_probe_and_attach() if (bootverbose) is set. >Description: >How-To-Repeat: >Fix: >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?20030121055319.GA13113>