From owner-freebsd-advocacy@FreeBSD.ORG Fri Jun 4 11:50:37 2004 Return-Path: Delivered-To: freebsd-advocacy@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76C6B16A4CF for ; Fri, 4 Jun 2004 11:50:37 -0700 (PDT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5387043D41 for ; Fri, 4 Jun 2004 11:50:37 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) i54IoN0L087217 for ; Fri, 4 Jun 2004 11:50:23 -0700 (PDT) (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id i54IoNl2087211; Fri, 4 Jun 2004 11:50:23 -0700 (PDT) (envelope-from gnats) Resent-Date: Fri, 4 Jun 2004 11:50:23 -0700 (PDT) Resent-Message-Id: <200406041850.i54IoNl2087211@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-advocacy@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Vortechz Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AE3316A545 for ; 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 ; 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 ; 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 To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-2.3 Subject: advocacy/67580: Hints for boot failures. X-BeenThere: freebsd-advocacy@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: FreeBSD Evangelism List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jun 2004 18:50:37 -0000 >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: