From owner-freebsd-acpi@FreeBSD.ORG Thu Jun 16 00:13:37 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 EDB0116A41C; Thu, 16 Jun 2005 00:13:37 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh1.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id A8FB943D1D; Thu, 16 Jun 2005 00:13:35 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [192.168.42.23] (andersonbox3.centtech.com [192.168.42.23]) by mh1.centtech.com (8.13.1/8.13.1) with ESMTP id j5G0DXFY011268; Wed, 15 Jun 2005 19:13:34 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <42B0C40F.2050503@centtech.com> Date: Wed, 15 Jun 2005 19:13:03 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050603 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: <200506032012.j53KCC5k077879@repoman.freebsd.org> <42B06B2D.4010600@centtech.com> <42B08B57.6010203@root.org> <200506151638.15687.jhb@FreeBSD.org> In-Reply-To: <200506151638.15687.jhb@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.82/941/Wed Jun 15 13:13:38 2005 on mh1.centtech.com X-Virus-Status: Clean Cc: freebsd-acpi@FreeBSD.org 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:13:38 -0000 John Baldwin wrote: > On Wednesday 15 June 2005 04:11 pm, Nate Lawson wrote: > >>Eric Anderson wrote: >> >>>>>>Ok - I've narrowed it down. A GENERIC kernel will go into S3 just >>>>>>fine on this laptop. Removing apic from the kernel will break that. >> >>It is interesting that the suspend path without the apic support causes >>a hang for you. This should be investigated. Does it work if you have >>apic compiled in but boot with hint.apic.0.disabled="1" ? Any ideas >>where to look John? > > > Not for the !APIC case, no. It would probably be good to get that working > first before trying to work on the APIC case. Perhaps the ioapic resume code > is using locks when it shouldn't though. Is it not safe to grab a spin lock > when intr_resume() is called? > > >>>>>ioapic_suspend: not implemented! >>>>>ioapic_suspend: not implemented! >> >>I still think this needs to be implemented although it's not likely to >>be your problem. > > > 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 :) Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------