APMD-List:
Archives

  From: Craig Markwardt <craigm@pcasun3.gsfc.nasa.gov>
  To  : Jont Allen <jba@research.att.com>
  Date: Thu, 5 Aug 1999 17:45:35 -0400 (EDT)

minor bug in apmd-3.0beta9

Jont Allen writes:
 > Avery and Craig,
 > 
 > I found a small bug. I have an IBM560X. F3 maps to standby and F4 to
 > suspend. When I hit F4, it calls
 > apmd_proxy standby system
 > rather than
 > apmd_proxy suspend system
 > 
 > apm -s and apm -S call suspend and standby as user, which seems correct.
 > 
 > Thus it looks like the system suspend (F4) is mapped wrong in the software
 > some how.
 > 
 > Version 3.0 beta 8 worked fine. When I upgraded to 3.0 beta 9, the problem
 > appeared.
 > 

I don't think anything as major as you describe has changed in 3.0
beta 9.

One way to find out if the APM kernel driver is flakey is to compile
it with debugging.  Edit your kernel file arch/i386/kernel/apm.c,
changing to "#define APM_DEBUG".  On of the things this does is logs
every APM event received directly from the BIOS.  I think this would
be the easiest way to tell if apmd, apmd_proxy, or the kernel driver,
are screwing up. 

I don't recommend the debugging for general usage, since it chews up
log space, but it may help sort things out now.

Craig