|
Description
|
This problem actually stems from ppm returning an errno if there is an attempt to set a state that is already in that state. And then gets compounded by the 'autopm disable' returning EINVAL, and 'autopm enable' returning EBUSY.
The code in handlers.c allows for the suppression of acceptable error messages, such as an EBUSY if turning on the feature, but has no way of dealing with more than one suppression. Specifically, for autopm the 'default' action can be different for various platforms (i.e. the Ultra 20 will now enable autopm, whereas others will disable autopm if 'autopm default' is in power.conf), and it is quite possible that either EBUSY or EINVAL will legitimately be returned. If the EBUSY is suppressed (which is the default action introduced by Suspend to RAM on x86), the code cryptically displays: 'autopm default failed, Invalid argument'. Though the underlying architecture needs updating, this bug should work out the suppression of the 'disable' message.
|
