From owner-acpi-jp@jp.FreeBSD.org Fri Mar 19 19:53:38 2004
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) id i2JArcF59851;
	Fri, 19 Mar 2004 19:53:38 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from poup.poupinou.org (poup.poupinou.org [195.101.94.96])
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) with ESMTP/inet id i2JArb759846
	for <acpi-jp@jp.freebsd.org>; Fri, 19 Mar 2004 19:53:37 +0900 (JST)
	(envelope-from ducrot@poupinou.org)
Received: from ducrot by poup.poupinou.org with local (Exim)
	id 1B4Hd2-0000Xw-00; Fri, 19 Mar 2004 11:53:28 +0100
To: acpi-jp@jp.FreeBSD.org
Cc: Nate Lawson <nate@root.org>, "M. Warner Losh" <imp@bsdimp.com>
Message-ID: <20040319105328.GD28592@poupinou.org>
References: <20040316143411.GA4468@portege.clkao.org> <20040316100826.S95770@root.org> <20040317.050943.101593525.imp@bsdimp.com> <20040316144529.U97064@root.org> <20040318161700.GA2551@portege.clkao.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20040318161700.GA2551@portege.clkao.org>
User-Agent: Mutt/1.5.4i
From: Bruno Ducrot <ducrot@poupinou.org>
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Fri, 19 Mar 2004 11:53:28 +0100
X-Sequence: acpi-jp 3119
Subject: [acpi-jp 3119] Re: acpi FADT and throttle problems
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: ducrot@poupinou.org
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+040307

On Fri, Mar 19, 2004 at 12:17:00AM +0800, Chia-liang Kao wrote:
> On Tue, Mar 16, 2004 at 02:48:39PM -0800, Nate Lawson wrote:
> > Merely loading the driver won't help unless he uses the sysctls.
> > 
> > One thing that might help ACPI Px states when I have the driver finished
> > and committed.  I had the driver written and then had to back off to get
> > infrastructure working to allow it to work (acpi rman, cpu newbus
> > attachments -- and now I have to rework those#!#@$!#@$)  It's likely SMM
> > code sets the Px state to the lowest before suspend and doesn't reset it
> > on resume, leaving that to the OS.  It's also possible our _PSx code in
> > the power branch will help.

I doubt ACPI Px states will help.  It is a PIII at 500MHz and even if
that one support SpeedStep, there is no support at all for
P-states from ACPI point-of-view.

> Ok, I just discovered hw.acpi.toshiba.cpu_speed being contrary to
> acpi_toshiba(4) - the higher number of the sysctl makes the cpu
> slower.
> 
> However after resuming the cpu_speed is set to 0 but it's really slow
> as if i set it to 7 before, and setting it to any value later wouldn't
> change the speed at all.

Are you sure that after resuming it is a problem with throttling?  This
may be an interrupt storm, for example.

-- 
Bruno Ducrot

--  Which is worse:  ignorance or apathy?
--  Don't know.  Don't care.
