[ltp] Is it just me or is ACPId way, way too verbose?
Michael Karcher
linux-thinkpad@linux-thinkpad.org
Thu, 21 Feb 2008 12:14:13 +0100
--=-SnP123K+M/02N2eR+lXN
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable
Am Mittwoch, den 20.02.2008, 23:22 -0800 schrieb Ryan Turner:
> Just to clarify, this is the message that makes up about 95% of
> /var/log/messages. In this case it's repeated (alternating from CPU0 to
> CPU1) around 55 times a second for sometimes hours at a time.
>=20
> Feb 18 10:12:13 ferret acpid: received event "processor CPU0 00000080
> 00000000"
> Feb 18 10:12:13 ferret acpid: notifying client 2745[0:0]
> Feb 18 10:12:13 ferret acpid: notifying client 2939[104:1004]
> Feb 18 10:12:13 ferret acpid: notifying client 4035[0:0]
> Feb 18 10:12:13 ferret acpid: completed event "processor CPU0 00000080
> 00000000"
I don't know about any way to make acpid not log such events, I am
sorry; however, this is strange, probably your ACPI BIOS (mainly DSDT)
does really strange things. A CPU 0x00000080 notification should be
issued by the ACPI hardware to the operating system not when the
frequency of the processor has been changed, but only when the list of
available frequencies to choose from has changed (See ACPI Specification
3.0a, page 144). This usually happens on some laptops when
plugging/unplugging the power supply, as on battery the highest
frequencies might be unavailable. It might also be an attempt to tell
the operating system about thermal issues detected by the ACPI hardware,
that caused the ACPI firmware to limit processor speed, although the
regular way to do that is to have a thermal zone device that is
connected to a processor device instead of changing the P state
(frequency) table.
Did you check whether your BIOS is up-to-date? Do you have unusually
high core temperatures? (Use the coretemp module to directly access the
thermal monitor included in Intel's Core processors).
Regards,
Michael Karcher
--=-SnP123K+M/02N2eR+lXN
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Dies ist ein digital signierter Nachrichtenteil
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
iD8DBQBHvV0Ezhek2R7EicoRArBgAJ9Y0K4tVh5Wk1rIc7XY3qe8fzRAJQCgj2UT
ycrHze04R9QeEtVO2BZCSmU=
=6uOd
-----END PGP SIGNATURE-----
--=-SnP123K+M/02N2eR+lXN--