From garya@nightmare.dreamchaser.org  Thu Dec  7 22:53:15 2000
Return-Path: <garya@nightmare.dreamchaser.org>
Received: from nightmare.dreamchaser.org (unknown [12.32.42.198])
	by hub.freebsd.org (Postfix) with ESMTP id 8919537B402
	for <FreeBSD-gnats-submit@freebsd.org>; Thu,  7 Dec 2000 22:53:14 -0800 (PST)
Received: (from root@localhost)
	by nightmare.dreamchaser.org (8.9.3/8.9.3) id XAA07396;
	Thu, 7 Dec 2000 23:52:57 -0700 (MST)
	(envelope-from garya)
Message-Id: <200012080652.XAA07396@nightmare.dreamchaser.org>
Date: Thu, 7 Dec 2000 23:52:57 -0700 (MST)
From: Gary Aitken <garya@nightmare.dreamchaser.org>
Reply-To: garya@nightmare.dreamchaser.org
To: FreeBSD-gnats-submit@freebsd.org
Subject: booting default kernel fails to configure lo0 device
X-Send-Pr-Version: 3.2

>Number:         23372
>Category:       kern
>Synopsis:       "boot 0:da(0,a)/boot/loader" does not configure lo0; "boot 0:da(0,a)/boot/loader /kernel" succeeds.
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Dec 07 23:00:01 PST 2000
>Closed-Date:    Mon Dec 18 13:15:46 PST 2000
>Last-Modified:  Mon Dec 18 13:16:29 PST 2000
>Originator:     Gary Aitken
>Release:        FreeBSD 4.1-RELEASE i386
>Organization:
individual
>Environment:
Micron pc
  Intel pentium i586, 16Meg
  bt0 scsi controller (BT946C0
    1 Conner CFP 1080S disk
    Wangtek 5150ES tape
    Plextor PX-4X-CS CD
  de0 ethernet (21041)
  eth0 Emerging Technologies ET5025 sync serial
>Description:
If the system boots automatically or manually by hitting cr,
it comes up with no lo0 device.  If booted by explicitly naming
the kernel:
  boot: 0:da(0,a)/boot/loader /kernel
it boots with the lo0 device present.

This behavior is exhibited by the originally installed generic kernel,
by a GENERIC kernel built on the system, and by a custom kernel built
on the system.  The GENERIC and custom kernels were installed using
make install.

Explicitly naming the lo0 device in the network_interfaces argument in
/etc/rc.conf results in a message about the lo0 device not being present.

This would not be a big deal except it makes power-fail recovery
impossible...

Reboots on this hardware used to work fine under 2.1.
Two modifications have been made:
  A USR modem card was removed.
  The etinc ET5025 serial interface card was added.
>How-To-Repeat:
Unfortunately, all I have to do is reboot.  I don't know if it
is repeatable on any other system; I suspect not.
>Fix:
Beats me.  But I'd be interested in helping find the problem if
I can get some serious coaching...

>Release-Note:
>Audit-Trail:

From: Gary Aitken <garya@dreamchaser.org>
To: freebsd-gnats-submit@FreeBSD.org
Cc:  
Subject: Re: kern/23372: "boot 0:da(0,a)/boot/loader" does not configure lo0; 
 "boot 0:da(0,a)/boot/loader /kernel" succeeds.
Date: Fri, 15 Dec 2000 15:28:34 -0700

 This problem appears to have automatically fixed itself as a
 result of a power failure and subsequent reboot.  Apparently
 the fsck fixed up the problem, although I did not see any
 interesting messages in the log other than the expected
 "warning, / was not properly dismounted"
 
State-Changed-From-To: open->closed 
State-Changed-By: phk 
State-Changed-When: Mon Dec 18 13:15:46 PST 2000 
State-Changed-Why:  
Problem fixed my decrease in local murphy field.  Boffins baffled. 

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