From owner-freebsd-bugs@FreeBSD.ORG Mon Dec 4 23:09:40 2006 Return-Path: X-Original-To: freebsd-bugs@FreeBSD.org Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2522616A47B for ; Mon, 4 Dec 2006 23:09:40 +0000 (UTC) (envelope-from jed@nersc.gov) Received: from mta2.lbl.gov (mta2.lbl.gov [128.3.41.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id A3F9043CAF for ; Mon, 4 Dec 2006 23:08:55 +0000 (GMT) (envelope-from jed@nersc.gov) Received: from mta2.lbl.gov (localhost [127.0.0.1]) by mta2.lbl.gov (8.13.8/8.13.8) with ESMTP id kB4N9Tro008998 for ; Mon, 4 Dec 2006 15:09:29 -0800 (PST) Received: from TWAIN.nersc.gov (groknow.nersc.gov [128.55.16.133]) by mta2.lbl.gov (8.13.8/8.13.8) with ESMTP id kB4N9SXE008994; Mon, 4 Dec 2006 15:09:29 -0800 (PST) Message-Id: <7.0.1.0.0.20061204092852.012d0d70@nersc.gov> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Mon, 04 Dec 2006 15:07:00 -0800 To: Kris Kennaway From: Jed Donnelley In-Reply-To: <7.0.1.0.0.20061204092804.035556a8@nersc.gov> References: <7.0.1.0.0.20061204092804.035556a8@nersc.gov> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: ClamAV 0.88.6/2277/Mon Dec 4 09:10:23 2006 on mta2 X-Virus-Status: Clean Cc: freebsd-bugs@FreeBSD.org Subject: Re: misc/106091: Keyboard disabled at mountroot> prompt X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Dec 2006 23:09:40 -0000 At 09:28 AM 12/4/2006, Kris Kennaway wrote: >On Fri, Dec 01, 2006 at 02:30:17AM +0000, Kris Kennaway > wrote: > > The following reply was made to PR misc/106091; it has been noted by GNATS. > > > > From: Jed Donnelley > > To: Ruslan Ermilov > > Cc: bug-followup@FreeBSD.org > > Subject: Re: misc/106091: Keyboard disabled at mountroot> prompt > > Date: Thu, 30 Nov 2006 18:23:39 -0800 > > > > At 06:17 PM 11/30/2006, Ruslan Ermilov wrote: > > >On Thu, Nov 30, 2006 at 08:42:48PM +0000, Jed Donnelley wrote: > > > > In the process of setting up a gmirror I messed up my fstab. > > > > When the boot process couldn't find a / to mount it dropped to the: > > > > > > > > mountroot> > > > > > > > > prompt. However, I found at that point that keyboard input was not > > > > accepted. I ended up having to start a system from a CD in "rescue" > > > > mode, mount the / file system from the hard drive and edit /etc/fstab > > > > that way. > > > > > >Was it observed over a serial console? > > > > No, KVM. Is there some reason that facility is only available over > > a serial console? The output displayed properly on the monitor > > and of course with a proper boot off a CD or HD the keyboard input > > worked properly. > > > > Thanks for considering this problem. > >No, but it's known that on a serial console input at the mountroot >prompt is mostly ignored (i.e. if you press the key enough times it >eventually does get accepted). This wouldn't apply to a KVM though. > >Does the keyboard work in the boot loader? i.e. if you tell the boot >menu to escape to the loader. If not, it's something about your KVM >that is the problem. The keyboard and display work fine in the boot loader - from the boot prompt (before the mountroot> prompt), from the CD (whether in rescue mode or when I was initially building the system) and of course from the running system both before and after I corrected the fstab problem. I believe testing this problem is as simple as building a system (or even using an existing system) and commenting out the / entry in the fstab. Then reboot. After the system fails to come back up and presumably waits in the mountroot> prompt, can you interact with it using the keyboard? I just did another test of such a change on another system with a distinct KVM configuration and different hardware. The behavior was the same. I did notice that if I booted in SafeMode then I was able to use the keyboard to mount the root file system (e.g. mountroot> ufs:/dev/mirror/gm0s1a ). That's a helpful work around. --Jed http://www.nersc.gov/~jed/