From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 16 00:58:10 2005 Return-Path: X-Original-To: freebsd-acpi@FreeBSD.org Delivered-To: freebsd-acpi@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A120B16A41C; Thu, 16 Jun 2005 00:58:10 +0000 (GMT) (envelope-from nate@root.org) Received: from www.cryptography.com (li-22.members.linode.com [64.5.53.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7329A43D53; Thu, 16 Jun 2005 00:58:10 +0000 (GMT) (envelope-from nate@root.org) Received: from [10.0.5.50] (adsl-64-171-184-89.dsl.snfc21.pacbell.net [64.171.184.89]) by www.cryptography.com (8.12.8/8.12.8) with ESMTP id j5G0w8Z6016826 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 15 Jun 2005 17:58:09 -0700 Message-ID: <42B0CDAD.6040806@root.org> Date: Wed, 15 Jun 2005 17:54:05 -0700 From: Nate Lawson User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Eric Anderson References: <200506032012.j53KCC5k077879@repoman.freebsd.org> <42B06B2D.4010600@centtech.com> <42B08B57.6010203@root.org> <200506151638.15687.jhb@FreeBSD.org> <42B0C40F.2050503@centtech.com> In-Reply-To: <42B0C40F.2050503@centtech.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-acpi@FreeBSD.org, John Baldwin Subject: Re: cvs commit: src/sys/dev/acpica acpi.c X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2005 00:58:10 -0000 Eric Anderson wrote: > John Baldwin wrote: >> >> Actually, we already reprogram all the APIC intpins on resume in >> ioapic_resume() from saved state. There's actually not anything for >> ioapic_suspend() to do, so I've mostly left this as a marker until the >> current resume code is tested. > > I now see that when it is trying to come out of resume, it panics. I > can't see it, and my serial access doesn't seem to work at that point (I > booted with boot -h, maybe I should have set some additional options) - > but if I type 'call doadump' on the keyboard, it dumps. However, I have > no idea what to do with it now that it's dumped :) That's getting somewhere. Use savecore(8) to get a copy of the dump image. Then run dmesg on it to get console messages and gdb /boot/kernel/kernel vmcore and type "bt" to get a backtrace and "print panicstr" to get the panic message. -- Nate