From owner-freebsd-current@FreeBSD.ORG Mon Nov 17 15:41:57 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 0B30016A4FA for ; Mon, 17 Nov 2003 15:41:57 -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 6C62943FE5 for ; Mon, 17 Nov 2003 15:41:43 -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 hAHNfful069354; Mon, 17 Nov 2003 16:41:41 -0700 (MST) (envelope-from durian@boogie.com) From: Mike Durian To: Doug White Date: Mon, 17 Nov 2003 16:41:40 -0700 User-Agent: KMail/1.5.4 References: <200311161028.48407.durian@boogie.com> <200311171338.03337.durian@boogie.com> <20031117130900.C22102@carver.gumbysoft.com> In-Reply-To: <20031117130900.C22102@carver.gumbysoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200311171641.41022.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: Mon, 17 Nov 2003 23:41:59 -0000 On Monday 17 November 2003 02:09 pm, Doug White wrote: > > Set flag 0x80 on sio1 and take it off of sio0. Thats what the kernel uses > to decide which port to use. The BOOT_COMCONSOLE_PORT is used by loader > only. I was finally able to get some partial success by setting flag 0x30 for sio1. When I'd boot, I'd get console messages on my remote tip session. However, I'd only receive those messages printed from user-level applications. I would not see any of the bold-face messages from the kernel. I tried dropping into the kernel debugger when the machine was not hung. The machine would immediately become unresponsive, as you'd expect if it was stopped in the debugger, but I never got any prompt on the serial console. I couldn't type another on the serial console to make anything happen either. Are there some hard-coded assumptions in the kernel that force a remote serial console to only work on sio0? Until I can get this working, I'm not going to be much help providing the trace backs needed to debug the tape write lock-up. mike