From owner-freebsd-current@FreeBSD.ORG  Sat May  8 20:58:08 2010
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: current@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id D9413106566B
	for <current@freebsd.org>; Sat,  8 May 2010 20:58:08 +0000 (UTC)
	(envelope-from bw@exodus.desync.com)
Received: from exodus.desync.com (exodus.desync.com [208.83.20.164])
	by mx1.freebsd.org (Postfix) with ESMTP id 3B2618FC0C
	for <current@freebsd.org>; Sat,  8 May 2010 20:58:07 +0000 (UTC)
Received: from exodus.desync.com (localhost [127.0.0.1])
	by exodus.desync.com (8.14.4/8.14.4) with ESMTP id o48KZo9x008923
	(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
	Sat, 8 May 2010 16:35:50 -0400 (EDT)
	(envelope-from bw@exodus.desync.com)
Received: (from bw@localhost)
	by exodus.desync.com (8.14.4/8.14.4/Submit) id o48KZn8Y008922;
	Sat, 8 May 2010 16:35:49 -0400 (EDT) (envelope-from bw)
Date: Sat, 8 May 2010 16:35:49 -0400
From: ben wilber <ben@desync.com>
To: Benjamin Kaduk <kaduk@MIT.EDU>
Message-ID: <20100508203549.GA8088@exodus.desync.com>
References: <20100508200032.GB31100@weongyo>
	<alpine.GSO.1.10.1005081605200.29136@multics.mit.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <alpine.GSO.1.10.1005081605200.29136@multics.mit.edu>
X-Angst-Level: High
Cc: current@freebsd.org
Subject: Re: a panic on uart_z8530_class?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.5
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: Sat, 08 May 2010 20:58:08 -0000

On Sat, May 08, 2010 at 04:11:49PM -0400, Benjamin Kaduk wrote:
> > [root@test ~]# kgdb /boot/kernel/kernel /var/crash/vmcore.1
> > GNU gdb 6.1.1 [FreeBSD]
> > Copyright 2004 Free Software Foundation, Inc.
> > GDB is free software, covered by the GNU General Public License, and you are
> > welcome to change it and/or distribute copies of it under certain conditions.
> > Type "show copying" to see the conditions.
> > There is absolutely no warranty for GDB.  Type "show warranty" for details.
> > This GDB was configured as "amd64-marcel-freebsd"...
> > Cannot access memory at address 0xffffff0127ffffe0
> > (kgdb) bt
> > #0  0x0000000000000000 in ?? ()
> > Cannot access memory at address 0x0
> > (kgdb) q
> 
> 
> I have seen this behavior from kgdb --- it doesn't seem to be able to 
> handle coredumps I've made recently.  At first I thought that I managed to 
> trash either my kernel image or kgdb binary with all the unclean 
> shutdowns I've been having, but if you're seeing kgdb failures, maybe it's 
> not just my local system.
> 
> Yet I am assuming that this is not broken for *everyone*, or we would have 
> heard more noise about it.
> 
> I'm running a current snapshot from April 4th; maybe I will try updating 
> to a new snapshot tonight and see if kgdb behaves better after everything 
> is rebuilt.

Same here, for the last couple months maybe.