From owner-freebsd-acpi@FreeBSD.ORG Wed Dec 29 18:34:10 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 9897516A4CE for ; Wed, 29 Dec 2004 18:34:10 +0000 (GMT) Received: from mail3.speakeasy.net (mail3.speakeasy.net [216.254.0.203]) by mx1.FreeBSD.org (Postfix) with ESMTP id 63FE343D64 for ; Wed, 29 Dec 2004 18:34:10 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 27052 invoked from network); 29 Dec 2004 18:34:10 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 29 Dec 2004 18:34:09 -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 iBTIY009003706; Wed, 29 Dec 2004 13:34:06 -0500 (EST) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-acpi@FreeBSD.org Date: Wed, 29 Dec 2004 11:27:43 -0500 User-Agent: KMail/1.6.2 References: <20041223145047.GA1064@webcom.it> <200412281027.58052.jhb@FreeBSD.org> <20041228232009.GC90171@webcom.it> In-Reply-To: <20041228232009.GC90171@webcom.it> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200412291127.43943.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx 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: Wed, 29 Dec 2004 18:34:10 -0000 On Tuesday 28 December 2004 06:20 pm, Andrea Campi wrote: > On Tue, Dec 28, 2004 at 10:27:57AM -0500, John Baldwin wrote: > > > > 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. > > OK, thanks. Just for completeness, I'll check and report what > happens with a different value of HZ (100, for instance ;-)), just in > case this makes any difference--as I would expect if this is a case > of resuming to some hardcoded value. Actually, device pmtimer will ensure that the clocks are reprogrammed correctly. You didn't leave that out of your kernel config did you? (I think we should just make that standard like it is in 4.x rather than optional.) -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org