Colin Laurie wrote:
> Hello there you may/may not be interested in this:
>
>
> Aug 15 16:18:48 linux-gidt kernel: Clocksource tsc unstable (delta = -124697887 ns)
> Aug 15 16:18:48 linux-gidt kernel: nf_conntrack version 0.5.0 (16384 buckets, 65536 max)
> Aug 15 16:18:50 linux-gidt kernel: ACPI Exception (thermal-0458): AE_ERROR, ACPI thermal trip point
> state changed
> Aug 15 16:18:50 linux-gidt kernel: Please send acpidump to linux-acpi@xxxxxxxxxxxxxxx
> Aug 15 16:18:50 linux-gidt kernel: [20070126]
> Aug 15 16:18:50 linux-gidt powersaved[2326]: WARNING (continueEvent:250) Could not execute program
> /usr/lib/powersave/scripts for event daemon.scheme.change: No such file or directory
> Aug 15 16:19:06 linux-gidt nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/autofs'
> exited with error status 1.
> Aug 15 16:19:07 linux-gidt ntpd[2492]: unable to bind to wildcard socket address 0.0.0.0 - another
> process may be running - EXITING
> Aug 15 16:19:07 linux-gidt nm-dispatcher.action: Script '/etc/NetworkManager/dispatcher.d/nfs'
> exited with error status 2.
> Aug 15 16:19:49 linux-gidt python: hp-systray(init)[2691]: warning: No hp: or hpfax: devices found
> in any installed CUPS queue. Exiting.
> Aug 15 16:22:03 linux-gidt smartd[3144]: Problem creating device name scan list
> Aug 15 17:52:28 linux-gidt kernel: hub 6-0:1.0: unable to enumerate USB device on port 5
> Aug 15 17:52:29 linux-gidt hp: io/hpmud/pp.c 627: unable to read device-id ret=-1
>
As a quick answer to your subject:
Previously spelled acpidmp, acpidump it is now included in many
Linux distributions. If not, you can get the latest version from the
latest pmtools package on this page.
<http://www.lesswatts.org/projects/acpi/utilities.php>
It's a pity Google doesn't know about this page. (It finds individual
tarballs, distribution specific packages, man pages etc.). I submitted
the URL on their feedback form on the off-chance they actually read it :-).
Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
