From root@turing.morons.org  Tue Dec  6 21:10:12 2005
Return-Path: <root@turing.morons.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 7F90D16A41F
	for <FreeBSD-gnats-submit@freebsd.org>; Tue,  6 Dec 2005 21:10:12 +0000 (GMT)
	(envelope-from root@turing.morons.org)
Received: from turing.morons.org (morons.org [64.147.161.226])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E65D143D68
	for <FreeBSD-gnats-submit@freebsd.org>; Tue,  6 Dec 2005 21:10:11 +0000 (GMT)
	(envelope-from root@turing.morons.org)
Received: from localhost (localhost.morons.org [127.0.0.1])
	by turing.morons.org (Postfix) with ESMTP id 7D39F170DD
	for <FreeBSD-gnats-submit@freebsd.org>; Tue,  6 Dec 2005 13:10:11 -0800 (PST)
Received: from turing.morons.org ([127.0.0.1])
 by localhost (turing.morons.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 08615-03 for <FreeBSD-gnats-submit@freebsd.org>;
 Tue,  6 Dec 2005 13:10:03 -0800 (PST)
Received: by turing.morons.org (Postfix, from userid 0)
	id 3156E17061; Tue,  6 Dec 2005 13:10:03 -0800 (PST)
Message-Id: <20051206211003.3156E17061@turing.morons.org>
Date: Tue,  6 Dec 2005 13:10:03 -0800 (PST)
From: Nick Johnson <freebsd@spatula.net>
Reply-To: Nick Johnson <freebsd@spatula.net>
To: FreeBSD-gnats-submit@freebsd.org
Cc:
Subject: boot -s drops serial console at sh prompt 
X-Send-Pr-Version: 3.113
X-GNATS-Notify:

>Number:         90050
>Category:       kern
>Synopsis:       [boot] boot -s drops serial console at sh prompt
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Dec 06 21:20:01 GMT 2005
>Closed-Date:    Tue Jun 12 07:22:26 GMT 2007
>Last-Modified:  Tue Jun 12 07:22:26 GMT 2007
>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:

From: Kris Kennaway <kris@obsecurity.org>
To: Nick Johnson <freebsd@spatula.net>
Cc: FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: kern/90050: boot -s drops serial console at sh prompt
Date: Tue, 6 Dec 2005 16:32:57 -0500

 On Tue, Dec 06, 2005 at 01:10:03PM -0800, Nick Johnson wrote:
 
 > 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.
 
 Did the same thing work under 5.4?
 
 Kris

From: Nick Johnson <freebsd@spatula.net>
To: Kris Kennaway <kris@obsecurity.org>
Cc: FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: kern/90050: boot -s drops serial console at sh prompt
Date: Tue, 6 Dec 2005 13:35:54 -0800 (PST)

 On Tue, 6 Dec 2005, Kris Kennaway wrote:
 
 > Did the same thing work under 5.4?
 
 I'm afraid I honestly don't remember.  I'm not sure if I ever tried it, 
 because this box was born a 5.4 machine; I don't know if I ever booted it 
 single-user remotely.

From: Kris Kennaway <kris@obsecurity.org>
To: Nick Johnson <freebsd@spatula.net>
Cc: Kris Kennaway <kris@obsecurity.org>, FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: kern/90050: boot -s drops serial console at sh prompt
Date: Tue, 6 Dec 2005 17:05:25 -0500

 --DocE+STaALJfprDB
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 On Tue, Dec 06, 2005 at 01:35:54PM -0800, Nick Johnson wrote:
 > On Tue, 6 Dec 2005, Kris Kennaway wrote:
 >=20
 > >Did the same thing work under 5.4?
 >=20
 > I'm afraid I honestly don't remember.  I'm not sure if I ever tried it,=
 =20
 > because this box was born a 5.4 machine; I don't know if I ever booted it=
 =20
 > single-user remotely.
 
 So how do you know it's a 6.0 bug and not misconfiguration? :)
 
 Kris
 
 
 --DocE+STaALJfprDB
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.2 (FreeBSD)
 
 iD8DBQFDlgslWry0BWjoQKURAiP3AKDskyQ7sh/JEfAi0pwt2f2vLRf7QgCglxZP
 WVcxRz8iyZ2cPsZM675rvJU=
 =89cR
 -----END PGP SIGNATURE-----
 
 --DocE+STaALJfprDB--

From: Nick Johnson <freebsd@spatula.net>
To: Kris Kennaway <kris@obsecurity.org>
Cc: FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: kern/90050: boot -s drops serial console at sh prompt
Date: Tue, 6 Dec 2005 14:43:02 -0800 (PST)

 On Tue, 6 Dec 2005, Kris Kennaway wrote:
 
 > On Tue, Dec 06, 2005 at 01:35:54PM -0800, Nick Johnson wrote:
 >> On Tue, 6 Dec 2005, Kris Kennaway wrote:
 >>
 >>> Did the same thing work under 5.4?
 >>
 >> I'm afraid I honestly don't remember.  I'm not sure if I ever tried it,
 >> because this box was born a 5.4 machine; I don't know if I ever booted it
 >> single-user remotely.
 >
 > So how do you know it's a 6.0 bug and not misconfiguration? :)
 
 Are you suggesting that the behaviour is appropriate?  That dropping the 
 serial console once you get to a prompt somehow makes sense?
 
 I'm not going to get into a nerd-slapping fight / cock-size contest over 
 this.  Getting defensive and sanctimonious every time a bug is reported is 
 counterproductive.  It's just a bug report.  It's not a commentary on 
 anyone's worth as a developer or human being.  It's simply a problem that 
 should be fixed, because it doesn't make any sense the way it is now.
 
 Either this project is committed to quality or it isn't.  Frankly I don't 
 care which it is.  I'm not going to fight about it every time I file a PR.
 
     Nick

From: Kris Kennaway <kris@obsecurity.org>
To: Nick Johnson <freebsd@spatula.net>
Cc: Kris Kennaway <kris@obsecurity.org>, FreeBSD-gnats-submit@FreeBSD.org
Subject: Re: kern/90050: boot -s drops serial console at sh prompt
Date: Tue, 6 Dec 2005 18:11:38 -0500

 On Tue, Dec 06, 2005 at 02:43:02PM -0800, Nick Johnson wrote:
 > On Tue, 6 Dec 2005, Kris Kennaway wrote:
 > 
 > >On Tue, Dec 06, 2005 at 01:35:54PM -0800, Nick Johnson wrote:
 > >>On Tue, 6 Dec 2005, Kris Kennaway wrote:
 > >>
 > >>>Did the same thing work under 5.4?
 > >>
 > >>I'm afraid I honestly don't remember.  I'm not sure if I ever tried it,
 > >>because this box was born a 5.4 machine; I don't know if I ever booted it
 > >>single-user remotely.
 > >
 > >So how do you know it's a 6.0 bug and not misconfiguration? :)
 > 
 > Are you suggesting that the behaviour is appropriate?  That dropping the 
 > serial console once you get to a prompt somehow makes sense?
 
 In my experience, the serial console works if configured correctly
 (e.g. in /boot/loader.conf).  I asked the question to try and
 determine whether you're talking about a regression I have not seen,
 or if it's possible you just don't have it set up right.
 
 > I'm not going to get into a nerd-slapping fight / cock-size contest over 
 > this.  Getting defensive and sanctimonious every time a bug is reported is 
 > counterproductive.  It's just a bug report.  It's not a commentary on 
 > anyone's worth as a developer or human being.  It's simply a problem that 
 > should be fixed, because it doesn't make any sense the way it is now.
 
 You're the only one getting upset, buddy :-) Now, can we focus on
 discussing your bug report?
 
 Kris
State-Changed-From-To: open->feedback 
State-Changed-By: kris 
State-Changed-When: Tue Dec 6 23:54:15 GMT 2005 
State-Changed-Why:  
Feedback requested 

http://www.freebsd.org/cgi/query-pr.cgi?pr=90050 
State-Changed-From-To: feedback->closed 
State-Changed-By: linimon 
State-Changed-When: Tue Jun 12 07:21:09 UTC 2007 
State-Changed-Why:  
Feedback timeout (> 1 year). 

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