From owner-freebsd-stable Wed May 10 23:10:41 2000 Delivered-To: freebsd-stable@freebsd.org Received: from jason.argos.org (a1-3b058.neo.rr.com [24.93.181.58]) by hub.freebsd.org (Postfix) with ESMTP id 0E29A37B7E4 for ; Wed, 10 May 2000 23:10:39 -0700 (PDT) (envelope-from mike@argos.org) Received: from localhost (mike@localhost) by jason.argos.org (8.9.1/8.9.1) with ESMTP id CAA00595; Thu, 11 May 2000 02:10:29 -0400 Date: Thu, 11 May 2000 02:10:29 -0400 (EDT) From: Mike Nowlin To: Kris Kirby Cc: David Miller , freebsd-stable@FreeBSD.ORG Subject: serial console buglet In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG (Taken from "Re: Server Farms?") > You mean you don't have a serial console? And yes, I can see where it may > be impractical (network access only, no serial ports, etc). Speaking of serial consoles, I keep getting bit by a little bug that is a descendant of the RS-232 specification (mother) and unterminated signals (father). On some of my machines that have serial consoles connected to (usually) Wyse 150 & Wyse 60 terminals, they have the annoying habit of not rebooting if the serial console is turned off... Turn the console on or pull the serial cable, and the machine proceeds to boot. (3-wire interface). Without digging into the source yet, I'm guessing there's something in there that keeps the boot process from starting if there's a constant mark/space (don't remember which one -- been a long day) on the console port. #1 - Is this correct? #2 - If so, what's the vote on putting a timeout in there -- if the port is blocked by this signal for more than 15 seconds (much longer than a "break" signal), go ahead and start booting anyway? --mike (Yes, I realize I could probably fix this with a resistor, but breaking kernel code is SO much more fun.) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message