Date: Sat, 8 May 2010 16:35:49 -0400 From: ben wilber <ben@desync.com> To: Benjamin Kaduk <kaduk@MIT.EDU> Cc: current@freebsd.org Subject: Re: a panic on uart_z8530_class? Message-ID: <20100508203549.GA8088@exodus.desync.com> In-Reply-To: <alpine.GSO.1.10.1005081605200.29136@multics.mit.edu> References: <20100508200032.GB31100@weongyo> <alpine.GSO.1.10.1005081605200.29136@multics.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100508203549.GA8088>