>Submitter-Id: current-users
>Originator: Arun Sharma
>Organization:
>Confidential: no
>Synopsis: device probing not verbose when using boot -v
>Severity:
>Priority:
>Category: kern
>Class: sw-bug
>Release: FreeBSD 5.0 i386
>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.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message