Date: Tue, 6 Dec 2005 13:10:03 -0800 (PST) From: Nick Johnson <freebsd@spatula.net> To: FreeBSD-gnats-submit@FreeBSD.org Subject: kern/90050: boot -s drops serial console at sh prompt Message-ID: <20051206211003.3156E17061@turing.morons.org> Resent-Message-ID: <200512062120.jB6LK2lG059456@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 90050 >Category: kern >Synopsis: boot -s drops serial console at sh prompt >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Tue Dec 06 21:20:01 GMT 2005 >Closed-Date: >Last-Modified: >Originator: Nick Johnson >Release: FreeBSD 6.0-STABLE i386 >Organization: morons.org >Environment: System: FreeBSD turing.morons.org 6.0-STABLE FreeBSD 6.0-STABLE #2: Tue Dec 6 08:53:05 PST 2005 root@turing.morons.org:/usr/obj/usr/src/sys/TURING i386 >Description: When rebooting into FreeBSD 6.0 single-user mode for the first time from FreeBSD 5.4, the serial console appeared to hang after mounting root. Gaining physical access to the machine revealed that the system had not hung, but was displaying the "Enter path to sh" prompt, which had not been echoed to the serial console. Input from the serial console was not recognized. Sending a break from the serial console did not cause the debugger to start. /boot.config contains the flags -Dv It is unknown whether this happens any time FreeBSD 6.0 is rebooted into single user mode or if it only happens when following the instructions in /usr/src/UPGRADING for upgrading from 5.4 to 6.0. >How-To-Repeat: Reboot FreeBSD 6.0 into single user mode from a serial console. >Fix: Unknown. >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051206211003.3156E17061>