advocacy/67580: Hints for boot failures.

Vortechz vortechz at lysator.liu.se
Fri Jun 4 18:50:37 GMT 2004


>Number:         67580
>Category:       advocacy
>Synopsis:       Hints for boot failures.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-advocacy
>State:          open
>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:
>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:
>Unformatted:


More information about the freebsd-advocacy mailing list