From owner-freebsd-hackers Mon Jan 20 21:50:23 2003 Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7049337B401; Mon, 20 Jan 2003 21:50:22 -0800 (PST) Received: from eagle.sharma-home.net (cpe-66-1-147-119.ca.sprintbbd.net [66.1.147.119]) by mx1.FreeBSD.org (Postfix) with ESMTP id 104EE43F18; Mon, 20 Jan 2003 21:50:22 -0800 (PST) (envelope-from adsharma@eagle.sharma-home.net) Received: by eagle.sharma-home.net (Postfix, from userid 500) id 4196E8115; Mon, 20 Jan 2003 21:53:19 -0800 (PST) Date: Mon, 20 Jan 2003 21:53:19 -0800 From: Arun Sharma To: FreeBSD-gnats-submit@freebsd.org Cc: hackers@freebsd.org Subject: device probing not verbose when using boot -v Message-ID: <20030121055319.GA13113@sharma-home.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG >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 majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message