From owner-freebsd-stable@FreeBSD.ORG Wed Nov 16 03:18:39 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 204B716A41F for ; Wed, 16 Nov 2005 03:18:39 +0000 (GMT) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (adsl-63-193-123-122.dsl.snfc21.pacbell.net [63.193.123.122]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC0F143D45 for ; Wed, 16 Nov 2005 03:18:36 +0000 (GMT) (envelope-from david@catwhisker.org) Received: from bunrab.catwhisker.org (localhost [127.0.0.1]) by bunrab.catwhisker.org (8.13.3/8.13.3) with ESMTP id jAG3Ia8q007456 for ; Tue, 15 Nov 2005 19:18:36 -0800 (PST) (envelope-from david@bunrab.catwhisker.org) Received: (from david@localhost) by bunrab.catwhisker.org (8.13.3/8.13.1/Submit) id jAG3IaTM007455 for stable@freebsd.org; Tue, 15 Nov 2005 19:18:36 -0800 (PST) (envelope-from david) Date: Tue, 15 Nov 2005 19:18:35 -0800 From: David Wolfskill To: stable@freebsd.org Message-ID: <20051116031835.GS69015@bunrab.catwhisker.org> Mail-Followup-To: David Wolfskill , stable@freebsd.org References: <20051115103821.GJ39882@cirb503493.alcatel.com.au> <20051116020933.72951.qmail@web36209.mail.mud.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051116020933.72951.qmail@web36209.mail.mud.yahoo.com> User-Agent: Mutt/1.4.2.1i Cc: Subject: Re: Swapfile problem in 6? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Nov 2005 03:18:39 -0000 On Tue, Nov 15, 2005 at 06:09:33PM -0800, Rob wrote: > ... > > Yes. See above URL. The advantage is that you can > > (hopefully) capture a log of your debug session. > > Send a serial BREAK and you should get a DDB> > > prompt. > > What is this "serial BREAK"? > How do I "send a serial BREAK" at the serial > console? Is this some magic key combination? I'm probably saying something about my age by doing this.... :-} A "BREAK" (in serial communications) is an absence of start or stop bits for more than a character's worth of bits, is handled as a "framing error," and is distinct from any character. Now, to generate one, you would normally hit the BREAK key of your terminal (Control-BREAK on some; I think Hazeltine had this feature of dubious merit). If you are using a serial communications program (such as "tip") instead of an ASCII terminal, it depends on the program you're using. In the case of tip, the sequence "~#" at the beginning of a line will generate tip's best approximation of a framing error. In the case of kermit, Control-\B does it. > And, eh, at the moment of deadlock, there is no > response at all from the serial console; will the > "serial BREAK" not be bothered by that? The serial BREAK won't be bothered at all. :-} The issue is (if I understand properly) whether or not there's enough of the system to be able to have the tty driver recognize the framing error and do something appropriate as a result. Peace, david -- David H. Wolfskill david@catwhisker.org Prediction is difficult, especially if it involves the future. -- Niels Bohr See http://www.catwhisker.org/~david/publickey.gpg for public key.