From: Bjoern Schmidt <lucky21@uni-paderborn.de>
To: Len Brown <len.brown@intel.com>
Cc: linux-kernel@vger.kernel.org, Bjoern Schmidt <lucky21@uni-paderborn.de>
Subject: [BUG] Re: fsb of older cpu
Date: Sun, 14 Mar 2004 16:11:00 +0100 [thread overview]
Message-ID: <40547604.7020504@uni-paderborn.de> (raw)
In-Reply-To: <1078892273.2347.551.camel@dhcppc4>
Hello Len,
i think that the fadt of my laptop is buggy, but i am not
sure. The fadt tells a C2 latency of 100 and a C3 latency
of 300. C3 is disabled in drivers/acpi/processor.c because
type-f DMA is set.
C2 is enabled and seems to be used, but has no effects on pm.
Thottling seems to have no effects too. The temperature of
the cpu rises fast until one of the active or S-state
trip-points is reached, in the worst case the systems
goes to S5.
Now i have set the C2 valid flag statically to "0" in the
sources (driver/acpi/processor.c).
cat /proc/acpi/processor/.../info tells that pm is not supported
anymore, and throttling seems to work now. The temperature
of the cpu settled down to the aimed trip-point of 58 dC.
Can you comfirm that this behaviour is a result of a buggy
fadt, or could it be that there is a bug in the kernels acpi?
Do you know if a PII Deschutes is C2 capable? In the acpi
specification i can see that the programming model for c2
state is "Fixed Hardware Control Logic" which is integrated
into the external chipset. Is the chipset the only
dependency for c2-state, or is the processor a dependency too?
I think so, of course, but its not clearly enough for me...
Greetings
Bjoern Schmidt
prev parent reply other threads:[~2004-03-14 15:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A6974D8E5F98D511BB910002A50A6647615F47CB@hdsmsx402.hd.intel.com>
2004-03-09 6:58 ` fsb of older cpu Len Brown
2004-03-09 11:16 ` Bjoern Schmidt
2004-03-09 11:35 ` Stefan Smietanowski
2004-03-09 12:07 ` Bjoern Schmidt
2004-03-10 4:17 ` Len Brown
2004-03-11 13:53 ` [BUG] " Bjoern Schmidt
2004-03-14 15:11 ` Bjoern Schmidt [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40547604.7020504@uni-paderborn.de \
--to=lucky21@uni-paderborn.de \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox