From owner-freebsd-stable@FreeBSD.ORG Wed Apr 5 03:20:45 2006 Return-Path: X-Original-To: freebsd-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 14A9716A422 for ; Wed, 5 Apr 2006 03:20:45 +0000 (UTC) (envelope-from ambrisko@ambrisko.com) Received: from mail2.ambrisko.com (mail2.ambrisko.com [64.174.51.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 81CEB43D53 for ; Wed, 5 Apr 2006 03:20:44 +0000 (GMT) (envelope-from ambrisko@ambrisko.com) Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2]) by mail2.ambrisko.com with ESMTP; 04 Apr 2006 20:20:07 -0700 Received: from ambrisko.com (localhost [127.0.0.1]) by www.ambrisko.com (8.12.11/8.12.11) with ESMTP id k353Kh7I068030; Tue, 4 Apr 2006 20:20:43 -0700 (PDT) (envelope-from ambrisko@ambrisko.com) Received: (from ambrisko@localhost) by ambrisko.com (8.12.11/8.12.11/Submit) id k353KhQP068029; Tue, 4 Apr 2006 20:20:43 -0700 (PDT) (envelope-from ambrisko) From: Doug Ambrisko Message-Id: <200604050320.k353KhQP068029@ambrisko.com> In-Reply-To: <4431A0A3.50604@servicefactory.se> To: =?ISO-8859-1?Q?Jonas_B=FClow?= Date: Tue, 4 Apr 2006 20:20:43 -0700 (PDT) X-Mailer: ELM [version 2.4ME+ PL94b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=unknown-8bit Cc: freebsd-stable@freebsd.org Subject: Re: Issues with nullconsole in FreeBSD 6.0-p6 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, 05 Apr 2006 03:20:45 -0000 Jonas Bülow writes: | I'm experiencing a really strange problem using nullconsole in FreeBSD | 6.0-p6. Briefly, what happens is that the use of nullconsole affects | the behavior of the OS negatively, very negatively. | | There are two different setups with different kernel | configurations. They both have console set to nullconsole in | loader.conf. | | In the first setup the machine reboots spontaneously somewhere during | boot without leaving a hint of the reason. | | In the other setup there is a fsck process (fsck_4.2bsd) crashing with | signal 8 (floating point exception) during boot. The fsck is run on an | auxiliary disk during startup. | | Both these problems goes away if console is set to either vidconsole | or comconsole in loader.conf. | | Adding DDB to the kernel configuration prevents to machine from | continuously rebooting in the first setup. Instead, it silently halts | somewhere in the boot process. Not easy telling where. It's seems to | be somewhere late in the process. Probably when running rc.d scripts | by observing the time before reboot compared to when using vidconsole | or comconsole. | | I've tried to debug the problem. I've not figured out how to remotely | debug a kernel when using nullconsole. The escape to debugger hot keys | (Ctrl+Alt+Esc or Ctrl+SysReq) does not work when using | nullconsole. Therefor it is not possible to switch to remote mode. Can | DDB be force to go directly into remote mode? | | I really understand it is impossible to give a simple answer or | solution to my problems described above. Well, if someone knows a | solution I wouldn't mind sharing it. What I really would like help | with is some input on how to debug this further. What to look for, | things to try etc. We don't seem to have that problem here with our enhanced consmute stuff. I noticed some implementation strangeness with the newer consmute implementation. Our major change is to put it into a function so if you break into the debugger or it panics you get that stuff. Now technically this wouldn't be a good idea with the original motivation but works for us. Bug me to remember to extract the patch for you to try. Doug A.