From owner-freebsd-current@FreeBSD.ORG Sun May 9 19:29:33 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id B5C8C1065680 for ; Sun, 9 May 2010 19:29:33 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-6.mit.edu (DMZ-MAILSEC-SCANNER-6.MIT.EDU [18.7.68.35]) by mx1.freebsd.org (Postfix) with ESMTP id 6E9E58FC1E for ; Sun, 9 May 2010 19:29:33 +0000 (UTC) X-AuditID: 12074423-b7c0bae0000030f0-09-4be70d1c54fd Received: from mailhub-auth-1.mit.edu (MAILHUB-AUTH-1.MIT.EDU [18.9.21.35]) by dmz-mailsec-scanner-6.mit.edu (Symantec Brightmail Gateway) with SMTP id AE.29.12528.C1D07EB4; Sun, 9 May 2010 15:29:32 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id o49JTWpY021864 for ; Sun, 9 May 2010 15:29:32 -0400 Received: from multics.mit.edu (MULTICS.MIT.EDU [18.187.1.73]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id o49JTUU5010639 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 9 May 2010 15:29:32 -0400 (EDT) Received: (from kaduk@localhost) by multics.mit.edu (8.12.9.20060308) id o49JTUoT017985; Sun, 9 May 2010 15:29:30 -0400 (EDT) Date: Sun, 9 May 2010 15:29:30 -0400 (EDT) From: Benjamin Kaduk To: freebsd-current@freebsd.org In-Reply-To: <20100509032756.GA90127@darklight.org.ru> Message-ID: References: <20100508200032.GB31100@weongyo> <20100508203549.GA8088@exodus.desync.com> <20100509032756.GA90127@darklight.org.ru> User-Agent: Alpine 1.10 (GSO 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII X-Brightmail-Tracker: AAAAAA== 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 09 May 2010 19:29:33 -0000 On Sun, 9 May 2010, Yuri Pankov wrote: > On Sat, May 08, 2010 at 09:59:23PM -0500, Brandon Gooch wrote: >> 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... My cores are not *completely* unuseable -- I can (e.g.) walk the process tree starting at allproc, and things look sane, but kgdb's 'proc' command claims that all PIDs are invalid, and doesn't give me backtraces. >> >> -Brandon > > Just another "me too". May be we have something common in our setup? > (I'm dumping to /dev/gpt/swap 8Gb GPT partition, using ahci(4) on a ATI > IXP700 AHCI SATA controller). > > Another issue - dump is written extremely slow (1.5Gb in ~5 minutes). I am more inclined to believe that this is a kgdb bug than a problem with the dump itself, but I am running on atapci0: AHCI v1.20 (Intel ICH9 family). (Old-ish) dmesg and pciconf may be found in http://stuff.mit.edu/afs/sipb.mit.edu/user/kaduk/freebsd/glossolalia/ -Ben