From nobody@FreeBSD.org  Fri Jun  4 11:48:45 2004
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3AE3316A545
	for <freebsd-gnats-submit@FreeBSD.org>; Fri,  4 Jun 2004 11:48:45 -0700 (PDT)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3499043D49
	for <freebsd-gnats-submit@FreeBSD.org>; Fri,  4 Jun 2004 11:48:45 -0700 (PDT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.12.11/8.12.11) with ESMTP id i54Imd8P014296
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 4 Jun 2004 11:48:39 -0700 (PDT)
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.12.11/8.12.11/Submit) id i54ImdSN014295;
	Fri, 4 Jun 2004 11:48:39 -0700 (PDT)
	(envelope-from nobody)
Message-Id: <200406041848.i54ImdSN014295@www.freebsd.org>
Date: Fri, 4 Jun 2004 11:48:39 -0700 (PDT)
From: Vortechz <vortechz@lysator.liu.se>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Hints for boot failures.
X-Send-Pr-Version: www-2.3

>Number:         67580
>Category:       kern
>Synopsis:       [request] add hints for boot failures
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          suspended
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          change-request
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jun 04 11:50:23 PDT 2004
>Closed-Date:    
>Last-Modified:  Mon Jan 28 09:04:47 UTC 2008
>Originator:     Vortechz
>Release:        4.10
>Organization:
>Environment:
Unfortunately no such information can be provided.
>Description:
There are problems leading to instant boot panic on some machines.
FreeBSD suffers from this problem whereas OpenBSD and Linux kernels
does not. I would like to see a possibility to se a text either in the
bootloader, the CLI or the visualconfig about such problems and how they
might be worked around using proper "set" directives.
(A better alternative would be to make the proper change in the
kernel and make the problem go away.)

For example: use: "set hw.pcic.intr_path=1" if your laptop hangs
with a kernel panic due to hard-routed irq.

>How-To-Repeat:
Boot the FreeBSD-4.10 CD on my laptop, a "BEST8950".

>Fix:

>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-advocacy->freebsd-bugs 
Responsible-Changed-By: trhodes 
Responsible-Changed-When: Tue Jul 6 06:15:46 GMT 2004 
Responsible-Changed-Why:  
Move to bugs. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=67580 
State-Changed-From-To: open->suspended 
State-Changed-By: linimon 
State-Changed-When: Mon Jan 28 09:04:39 UTC 2008 
State-Changed-Why:  
Mark suspended awaiting patches. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=67580 
>Unformatted:
