From owner-freebsd-current@FreeBSD.ORG Mon Oct 11 16:16:42 2004 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 13D2116A4CE; Mon, 11 Oct 2004 16:16:42 +0000 (GMT) Received: from mail.vtec.ipme.de (Ad6ac.a.pppool.de [213.6.214.172]) by mx1.FreeBSD.org (Postfix) with ESMTP id 868BE43D2D; Mon, 11 Oct 2004 16:16:39 +0000 (GMT) (envelope-from volker@vwsoft.com) Received: from [192.168.16.24] (unknown [192.168.16.24]) by bellona.sz.vwsoft.com (Postfix) with ESMTP id 24C755C66; Mon, 11 Oct 2004 18:16:34 +0200 (CEST) Message-ID: <416AB1E1.9060108@vwsoft.com> Date: Mon, 11 Oct 2004 18:16:33 +0200 From: Volker User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040822 Thunderbird/0.7+ Mnenhy/0.6.0.101 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson , freebsd-current@freebsd.org References: In-Reply-To: X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: beta6/7 machine freeze 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, 11 Oct 2004 16:16:42 -0000 Robert, thanks for all your information. The machine has been prepared for using a serial console and already has the kernel debugger enabled. WITNESS has been disabled but I'll enable it and rebuild the kernel (this evening). I haven't been able to send a break signal over the serial line to get into the debugger, but that might be a problem of my terminal emulation. I'll try to set debug.mpsafenet=0, bring the machine up again and see if I can than recreate the machine freeze and enter the debugger. Using the syscon I've been unable to enter the debugger because the machine doesn't process any keystrokes while freezed. I'll keep you posted as soon as I've got something new. Thanks, Volker On 2004-10-11 17:44, Robert Watson wrote: > In fact, this is almost certainly part of the problem. I'd try setting > debug.mpsafenet=0 in /boot/loader.conf and reboot as a first step t see if > the problem goes away. > > Robert N M Watson FreeBSD Core Team, TrustedBSD Projects > robert@fledge.watson.org Principal Research Scientist, McAfee Research > > On Mon, 11 Oct 2004, Robert Watson wrote: > > >>BTW, since it sounds like this might be a networking related problem, you >>might try setting debug.mpsafenet=0 in loader.conf to see if the problem >>goes away -- that will put the Giant lock back over the network stack and >>might close races. i4b might not be MPSAFE, I'll go take a look. >> >>Robert N M Watson FreeBSD Core Team, TrustedBSD Projects >>robert@fledge.watson.org Principal Research Scientist, McAfee Research >> >> > > -- GPG/PGP fingerprint: FF93 13A1 2477 B631 E953 06DF 4C49 ADD9 E4BF 79B1