From owner-freebsd-current@FreeBSD.ORG  Tue Dec 21 17:21:39 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 BF79616A4CE
	for <current@freebsd.org>; Tue, 21 Dec 2004 17:21:39 +0000 (GMT)
Received: from harmony.village.org (rover.village.org [168.103.84.182])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1C5D943D1D
	for <current@freebsd.org>; Tue, 21 Dec 2004 17:21:39 +0000 (GMT)
	(envelope-from imp@bsdimp.com)
Received: from localhost (warner@rover2.village.org [10.0.0.1])
	by harmony.village.org (8.13.1/8.13.1) with ESMTP id iBLHKNsT005636;
	Tue, 21 Dec 2004 10:20:32 -0700 (MST)
	(envelope-from imp@bsdimp.com)
Date: Tue, 21 Dec 2004 10:20:35 -0700 (MST)
Message-Id: <20041221.102035.11997056.imp@bsdimp.com>
To: sean@mcneil.com
From: "M. Warner Losh" <imp@bsdimp.com>
In-Reply-To: <1103489622.5226.6.camel@server.mcneil.com>
References: <1103434515.1158.10.camel@server.mcneil.com>
	<20041219150157.O19917@alpha.siliconlandmark.com>
	<1103489622.5226.6.camel@server.mcneil.com>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
cc: current@freebsd.org
Subject: Re: reboot without any info
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Dec 2004 17:21:39 -0000

In message: <1103489622.5226.6.camel@server.mcneil.com>
            Sean McNeil <sean@mcneil.com> writes:
: I think everyone has hardware fault on the brain right now.  Please note
: that the system works perfectly - even under extreme load - until the
: moment I run totem in the debugger.  Then it is instant.  I would never
: consider this behavior as hardware related.

In that case, you may be stuck with debugging the debugging process.
adding printfs to the perimeter (with a serial console), and gradually
worming your way in.  Not all printfs happen in some cases, so there
may be some abiguity that may drive you nuts...

Chances are the kernel/debugger is restoring state bogusly, and that
we're jumping to that bogus state, causing the reset (most likely in
kernel mode).

Warner