apm: busy: Unable to enter requested state

apm: busy: Unable to enter requested state

[jogi]

Hello,

I have a problem which I noticed recently. I have a DFI AK76SN + Athlon
1.2GHz. I use apm to get the system into suspend mode. This worked a
long time ago. But now all I get is:

apm: setting state busy
apm: busy: Unable to enter requested state
apm: setting state busy
apm: busy: Unable to enter requested state
apm: received normal resume notify

and then the cpu does not cool down (I guess it is not shut down like it
was before). Previously this worked fine and the cpu temperature at
resume was "room temperature" (20°C). But now it is almost always ~48°C.

Some changes which I remember:

- update bios (I reinstalled the previous bios but it did not help)
- updated kernel version (I actually don't remember which version I was
  using but I think 2.4.12 worked fine but does not work now)

Do I have to tweak the bios or is this a kernel issue or is there
something wrong with the bios?

What infos can I provide else? I tried 5 different bios versions,
changed most bios settings regarding power management, tried different
kernel versions, ... So I am running out of ideas ...

Regards,

   Jogi

-- 

Well, yeah ... I suppose there's no point in getting greedy, is there?

    << Calvin & Hobbes >>

Re: apm: busy: Unable to enter requested state

[Thomas Hood]

> 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.

Re: apm: busy: Unable to enter requested state

[jogi]

On Fri, Jan 25, 2002 at 08:02:13PM -0500, Thomas Hood wrote:
> > 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.

Firmware == bios?

> Is there a driver or userland process that is failing
> to process the suspend event quickly?

None that I know of ... But the system does kind of suspend
(hdd is spun down, monitor shuts down, ....) but when the system
resumes (press key, move mouse) the temperature of the cpu is
still the same it was before the suspend. Sometime ago the
cpu cooled down to roomtemperature (sys temp also). But this
does not happen any more :-(

> > 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?

When I press the suspend button the message appears
almost instantly (message appears several times). But
I checked 2.4.18-pre7 and there the message does not
appear but the cpu does not cool down either. The kernel
that generates this message was 2.4.17-rmap12a.

> > 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.

That is exactly what I would like it to do and which it
partly does. But the cpu does not cool down (it seems as
if it is not shut down - do I have to use a config option
for this?).

CONFIG_PM=y
# CONFIG_ACPI is not set
CONFIG_APM=y
# CONFIG_APM_IGNORE_USER_SUSPEND is not set
CONFIG_APM_DO_ENABLE=y
CONFIG_APM_CPU_IDLE=y
# CONFIG_APM_DISPLAY_BLANK is not set
CONFIG_APM_RTC_IS_GMT=y
# CONFIG_APM_ALLOW_INTS is not set
# CONFIG_APM_REAL_MODE_POWER_OFF is not set

Do I have to enable one of these?

Regards,

   Jogi


-- 

Well, yeah ... I suppose there's no point in getting greedy, is there?

    << Calvin & Hobbes >>