Bug 23372

Summary: "boot 0:da(0,a)/boot/loader" does not configure lo0; "boot 0:da(0,a)/boot/loader /kernel" succeeds.
Product: Base System Reporter: Gary Aitken <garya>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.1-RELEASE   
Hardware: Any   
OS: Any   

Description Gary Aitken 2000-12-08 07:00:01 UTC 
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.

Fix: 

Beats me.  But I'd be interested in helping find the problem if
I can get some serious coaching...
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.
Comment 1 Gary Aitken 2000-12-15 22:28:34 UTC 
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"
Comment 2 Poul-Henning Kamp freebsd_committer freebsd_triage 2000-12-18 21:15:46 UTC 
State Changed
From-To: open->closed

Problem fixed my decrease in local murphy field.  Boffins baffled.