From owner-cvs-src@FreeBSD.ORG Tue May 4 01:49:58 2004 Return-Path: Delivered-To: cvs-src@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5EDBA16A4CE; Tue, 4 May 2004 01:49:58 -0700 (PDT) Received: from mailout1.pacific.net.au (mailout1.pacific.net.au [61.8.0.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6BFAE43D4C; Tue, 4 May 2004 01:49:57 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from mailproxy1.pacific.net.au (mailproxy1.pacific.net.au [61.8.0.86])i448nu4u010035; Tue, 4 May 2004 18:49:56 +1000 Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) i448nrI2024612; Tue, 4 May 2004 18:49:54 +1000 Date: Tue, 4 May 2004 18:49:52 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Doug Ambrisko In-Reply-To: <200405032235.i43MZSpH052701@repoman.freebsd.org> Message-ID: <20040504180010.E9274@gamplex.bde.org> References: <200405032235.i43MZSpH052701@repoman.freebsd.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: cvs-src@freebsd.org cc: src-committers@freebsd.org cc: cvs-all@freebsd.org Subject: Re: cvs commit: src/sys/conf NOTES options src/share/man/man4 sio.4 src/sys/dev/sio sio.c X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 May 2004 08:49:58 -0000 On Mon, 3 May 2004, Doug Ambrisko wrote: > ambrisko 2004/05/03 15:35:28 PDT > > FreeBSD src repository > > Modified files: > sys/conf NOTES options > share/man/man4 sio.4 > sys/dev/sio sio.c > Log: > Remove new options and my prevention of system freeze when the sio probe > returns okay when HW probe fails. This happens when comconsole flag is > set but VGA console is used instead. > > Back out requested by: bde (He will be looking at other solutions from scratch) Thanks. I think you mean that the freeze happens when the comconsole flag is set but the VGA console is _not_ used instead despite there being no usable serial console. Neither the boot blocks not sio check whether the configured console port exists before using it, but this is less fatal in the boot blocks since they have a timeout in their output routine. In particular, dual consoles may appear to work, just a little slowly, with VGA output working and serial output going nowhere but not being observed. Network and/or nonstandard boot blocks apparently set the comconsole flag without initializing a serial console (because they don't support using one and don't know that they are supposed to initialize one for the kernel?). This can cause garbled i/o. There are also problems with multiple enabled console or debugger ports... See PR 65278 for the main one. Bruce