From owner-freebsd-acpi@FreeBSD.ORG Tue Dec 28 23:02:19 2004 Return-Path: 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 8198F16A4CE for ; Tue, 28 Dec 2004 23:02:19 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4FFB143D1F for ; Tue, 28 Dec 2004 23:02:19 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 17330 invoked from network); 28 Dec 2004 23:02:19 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 28 Dec 2004 23:02:18 -0000 Received: from [10.50.41.243] (gw1.twc.weather.com [216.133.140.1]) (authenticated bits=0) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id iBSLoQg6095856; Tue, 28 Dec 2004 16:50:31 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: Nate Lawson Date: Tue, 28 Dec 2004 10:27:57 -0500 User-Agent: KMail/1.6.2 References: <20041223145047.GA1064@webcom.it> <41D0931F.2010200@root.org> In-Reply-To: <41D0931F.2010200@root.org> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200412281027.58052.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: freebsd-acpi@FreeBSD.org Subject: Re: S3 experience on Thinkpad 570E X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 28 Dec 2004 23:02:19 -0000 On Monday 27 December 2004 05:56 pm, Nate Lawson wrote: > Andrea Campi wrote: > > Hi, > > > > I've tried using S3 on -CURRENT, more in response to Nate's request than > > out of need, since S4BIOS is working great on this PC. > > > > In a nutshell, acpiconf -s3 powers down; on powerup however the machine > > is deadly slow. I replicated this with a stripped down kernel; the only > > thing that was evidently wrong is that the clock slowed down from 1000 to > > around 250 interrupts per second. > > It sounds like the clock interrupt source is not getting saved/restored > properly if it slows after a resume. I am not sure how to solve this. > Perhaps John has something to add. Currently on i386 the clocks are not real new-bus devices and I'm not sure if they have proper resume support. I think we do have some sort of hardcoded call to the clock code on i386 to resume the clocks but I'm not sure. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org