From owner-acpi-jp@jp.FreeBSD.org Sat Apr 17 02:23:55 2004
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) id i3GHNtB01610;
	Sat, 17 Apr 2004 02:23:55 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from root.org (root.org [67.118.192.226])
	by castle.jp.FreeBSD.org (8.11.6p2+3.4W/8.11.3) with SMTP/inet id i3GHNs901605
	for <acpi-jp@jp.FreeBSD.org>; Sat, 17 Apr 2004 02:23:55 +0900 (JST)
	(envelope-from nate@root.org)
Received: (qmail 98166 invoked by uid 1000); 16 Apr 2004 17:23:46 -0000
From: Nate Lawson <nate@root.org>
To: Yoshitaka Suetsugu <suetsugu@affrc.go.jp>
cc: acpi-jp@jp.FreeBSD.org, ducrot@poupinou.org, imp@bsdimp.com
In-Reply-To: <20040415.090118.74746160.suetsugu@affrc.go.jp>
Message-ID: <20040416102313.Y98071@root.org>
References: <20040316144529.U97064@root.org> <20040318161700.GA2551@portege.clkao.org>
 <20040319105328.GD28592@poupinou.org> <20040415.090118.74746160.suetsugu@affrc.go.jp>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=iso-2022-jp
Content-Transfer-Encoding: QUOTED-PRINTABLE
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Fri, 16 Apr 2004 10:23:46 -0700
X-Sequence: acpi-jp 3190
Subject: [acpi-jp 3190] Re: acpi FADT and throttle problems
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: nate@root.org
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+040413

On Thu, 15 Apr 2004, Yoshitaka Suetsugu wrote:
>   Bruno Ducrot <ducrot@poupinou.org>
> =A1=BF=A1=B1=A1=B1=A1=B1=A1=B1=A1=B1=A1=B1=A1=B1=A1=B1=A1=B1=A1=B1=A1=B1=
=A1=B1=A1=B1=A1=B1=A1=B1=A1=B1=A1=B1=A1=B1=A1=B1=A1=B1=A1=B1=A1=B1
> > 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 fin=
ished
> > > > and committed.  I had the driver written and then had to back off t=
o get
> > > > infrastructure working to allow it to work (acpi rman, cpu newbus
> > > > attachments -- and now I have to rework those#!#@$!#@$)  It's likel=
y SMM
> > > > code sets the Px state to the lowest before suspend and doesn't res=
et it
> > > > on resume, leaving that to the OS.  It's also possible our _PSx cod=
e 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.

Sorry, I can't read this.

-Nate
