> apm: setting state busy
> apm: busy: Unable to enter requested state
> apm: setting state busy
> apm: busy: Unable to enter requested state
While the suspend request is being processed, the apm
driver attempts to set the power state to "busy", as
required by the APM spec. The attempt fails, presumably
because of shortcomings in your firmware.
Is there a driver or userland process that is failing
to process the suspend event quickly?
> apm: received normal resume notify
The APM firmware appears to generate this event.
Perhaps it is timing out waiting for the OS to respond
to the suspend event with a set-power-state operation.
How long does it take for this to happen?
> and then the cpu does not cool down (I guess it is
> not shut down like it was before).
A suspended machine does more than cool down. It does
not operate at all.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Thu Jan 31 2002 - 21:00:38 EST