Date: Sat, 8 May 2010 21:59:23 -0500 From: Brandon Gooch <jamesbrandongooch@gmail.com> To: ben wilber <ben@desync.com> Cc: Benjamin Kaduk <kaduk@mit.edu>, current@freebsd.org Subject: Re: a panic on uart_z8530_class? Message-ID: <v2w179b97fb1005081959v17e093e1j978ad7aeec2d4c79@mail.gmail.com> In-Reply-To: <20100508203549.GA8088@exodus.desync.com> References: <20100508200032.GB31100@weongyo> <alpine.GSO.1.10.1005081605200.29136@multics.mit.edu> <20100508203549.GA8088@exodus.desync.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 8, 2010 at 3:35 PM, ben wilber <ben@desync.com> wrote: > 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 y= ou are >> > welcome to change it and/or distribute copies of it under certain cond= itions. >> > Type "show copying" to see the conditions. >> > There is absolutely no warranty for GDB. =A0Type "show warranty" for d= etails. >> > This GDB was configured as "amd64-marcel-freebsd"... >> > Cannot access memory at address 0xffffff0127ffffe0 >> > (kgdb) bt >> > #0 =A00x0000000000000000 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. =A0At first I thought that I manage= d 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 ha= ve >> 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 everythin= g >> is rebuilt. > > Same here, for the last couple months maybe. I'll chime in here with a "me too". Since at early April, I've been trying to figure out why my laptop locks up overnight (something about the CPUs going into C3). I can nearly always get it to coredump, but the vmcore files I generate are unusable... -Brandon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?v2w179b97fb1005081959v17e093e1j978ad7aeec2d4c79>