On Thu, Aug 9, 2012 at 12:41 PM, Rafael J. Wysocki [off-list ref] wrote:

On Thursday, August 09, 2012, Athlion wrote:

quoted

Thanks for the swift reply!

If I choose processors, I get (among other normal things) this:

What happens if you choose "core"?

Both core and processors always exhibit the same ACPI errors.

quoted

I do not get these ACPI Error and ACPI Exceptions in a normal run. Is
this normal?

No, it is not.

quoted

Does it indicate a problem?

A small one.  It indicates that P-states as defined in the BIOS aren't
usable to the ACPI cpufreq driver.  There also seems to be a problem with
the handling of the embedded controller, which may be more serious.

Should I report this to the ACPI list?

quoted

The dmesg of the pm-suspend after i have
# echo "processors" > /sys/power/pm_test
can be found here: https://dl.dropbox.com/u/63420/processors.txt

The dmesg of a full pm-suspend run is here
https://dl.dropbox.com/u/63420/full.txt

That seems to be a clean suspend/resume cycle.  What's the problem, then?

Yes, I'm sorry if it wasn't clear. Since that was a fresh reboot, the
suspend went OK. I posted it because I thought that these ACPI errors
were directly relevant to the problem I'm having. But I am keeping
track of all this info to have when this problem happens again but
since my computer hard locked (this hasn't happened before!) when I
opened the lid just 5 mins ago, and this happens about at 24 hours of
uptime, I will probably have all the info collected by tomorrow. Sorry
for the misunderstanding and thanks for the interest!