Date: Thu, 7 Dec 2000 23:52:57 -0700 (MST) From: Gary Aitken <garya@nightmare.dreamchaser.org> To: FreeBSD-gnats-submit@freebsd.org Subject: kern/23372: booting default kernel fails to configure lo0 device Message-ID: <200012080652.XAA07396@nightmare.dreamchaser.org> Resent-Message-ID: <200012080700.eB8702n81425@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>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: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-Id: current-users
>Arrival-Date: Thu Dec 07 23:00:01 PST 2000
>Closed-Date:
>Last-Modified:
>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:
>Unformatted:
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012080652.XAA07396>