From owner-freebsd-current@FreeBSD.ORG Thu Nov 20 08:59:50 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 00F0516A4CE for ; Thu, 20 Nov 2003 08:59:50 -0800 (PST) Received: from fever.boogie.com (cpe-66-87-52-132.co.sprintbbd.net [66.87.52.132]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6E44443FFD for ; Thu, 20 Nov 2003 08:59:46 -0800 (PST) (envelope-from durian@boogie.com) Received: from man.boogie.com (man.boogie.com [192.168.1.3]) by fever.boogie.com (8.12.9/8.12.9) with ESMTP id hAKGxgul017352; Thu, 20 Nov 2003 09:59:43 -0700 (MST) (envelope-from durian@boogie.com) From: Mike Durian To: Bruce Evans Date: Thu, 20 Nov 2003 09:59:42 -0700 User-Agent: KMail/1.5.4 References: <200311161028.48407.durian@boogie.com> <200311191120.26575.durian@boogie.com> <20031120080442.H9178@gamplex.bde.org> In-Reply-To: <20031120080442.H9178@gamplex.bde.org> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311200959.42152.durian@boogie.com> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60 X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on fever.boogie.com cc: current@freebsd.org Subject: Re: hard lock-up writing to tape X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Nov 2003 16:59:50 -0000 On Wednesday 19 November 2003 02:15 pm, Bruce Evans wrote: > > Anyway, the stuff to the left of the slash in the above is the list > of active consoles and the stuff to the right of the slash is the > list of possible consoles. You have to move stuff from one list to > the other. I vaguely remember that this is done using '-' to delete > things from the left hand list and something more direct to add them. You remember correctly. Thanks for the info. However, I think I'm going to have to throw in the towel on this. When I swap the console output using the kern.console sysctl, I can get user application console output to appear on the remote machine - just nothing from the kernel. For example, if I 'echo hello > /dev/console', hello will appear on the remote machine. But I never see any of the bold face messages, such as the very frequent: checking stopevent 2 with the following non-sleepable locks held: exclusive sleep mutex sigacts r = 0 (0xc6b6faa8) locked @ /disk2/src/sys/kern/ subr_trap.c:260 When I tried to generate a break using ~# from tip to drop into the debugger, nothing happens, so I don't think the serial console is fully connected in the kernel, even though the bold-face output disappeared from the syscons console. I do have an extra bit of information on my original tape lock-up problem. At one point, when I thought I had the remote console working and was reproducing the problem, the tape backup worked fine until I pinged the machine. I think the machine responded to the ping and then that was it. It locked up solid. mike