From owner-freebsd-amd64@FreeBSD.ORG  Fri Apr  1 16:18:50 2005
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 2953616A4CE
	for <freebsd-amd64@freebsd.org>; Fri,  1 Apr 2005 16:18:50 +0000 (GMT)
Received: from yertle.kcilink.com (yertle.kcilink.com [65.205.34.180])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E5D0243D39
	for <freebsd-amd64@freebsd.org>; Fri,  1 Apr 2005 16:18:49 +0000 (GMT)
	(envelope-from vivek@khera.org)
Received: from [192.168.7.149] (host-149.int.kcilink.com [192.168.7.149])
	by yertle.kcilink.com (Postfix) with ESMTP id 7C0DFB80C
	for <freebsd-amd64@freebsd.org>; Fri,  1 Apr 2005 11:18:49 -0500 (EST)
Mime-Version: 1.0 (Apple Message framework v619.2)
In-Reply-To: <424D58F7.1010005@infotechfl.com>
References: <f0111a98c01333b3c306c81d10294de4@khera.org>
	<Pine.SOC.4.61.0503300229560.3181@tea.blinkenlights.nl>
	<3f9aa5aef19c41837cce1563e2c97a21@khera.org> <424C215E.5080201@infotechfl.com>
	<b6c7cfb181756fdfa3593f64223cb08a@khera.org> <424C4EED.5070601@infotechfl.com>
	<1112312243.6323.10.camel@lanshark.dmv.com> <424D58F7.1010005@infotechfl.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <cab069d57aee4d9ba99d5ed9ef6b94c1@khera.org>
Content-Transfer-Encoding: 7bit
From: Vivek Khera <vivek@khera.org>
Date: Fri, 1 Apr 2005 11:18:47 -0500
To: freebsd-amd64@freebsd.org
X-Mailer: Apple Mail (2.619.2)
Subject: Re: Tyan k8sr lockups
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Apr 2005 16:18:50 -0000

On Apr 1, 2005, at 9:21 AM, Gary Mu1der wrote:

> Is there a way to force a crash dump? I heard mention of a key combo 
> on the console to force a crash dump, but I suspect the console 
> keyboard is totally hung as well.
>
> Does anyone have a doc on how to run the kernel under gdb or something 
> and log what is happening to a serial console?
>

when I get my lockups (had another this A.M.) the serial console line 
is non-responsive as well.  I cannot break into the kernel debugger at 
all.  There is no evidence of *anything* going bad other than the 
machine is totally unresponsive to network and console.  nothing is 
logged anywhere, including the BIOS.

when it happens it is during time of heavy I/O + network load.  I'm now 
running with debug.mpsafenet=0 to see if i'm tickling a bug in the 
network stack, given that I saw some bge0 timeouts earlier.