Date: Tue, 4 May 2004 18:49:52 +1000 (EST) From: Bruce Evans <bde@zeta.org.au> To: Doug Ambrisko <ambrisko@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 Message-ID: <20040504180010.E9274@gamplex.bde.org> In-Reply-To: <200405032235.i43MZSpH052701@repoman.freebsd.org> References: <200405032235.i43MZSpH052701@repoman.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040504180010.E9274>