A structured approach to fixing this bug would be to first learn how apmd and suspend/resume works on Linux, then trying to track the code path in kernel and userland, inserting printk() respectively printf() statements to see where exactly things differ from the way they're supposed to work.
Sorry if this is not detailed enough for you, but I'm not a kernel developer.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=79626\"][{POST_SNAPBACK}][/a][/div]
It's hard to tell if you're begin sarcastic or not , but I do understand. I may not be a Z or kernel developer, but I am a developer, so I do understand what you mean. It just requires some basic troubleshooting, which requires someone to be able to devote some time to it. Not an easy thing, I know.
So it's possibly a (mis)interaction between the kernel & apm? That makes sense. Are there any other known issues with apm right now? I've noticed that opie's been locking up on me quite a bit in the last day or so. I can ssh in & restart it, but if I'm not next to a pc, then I have to hard boot. Trying to figure out what changes I may have made to cause it. At first I thought it might have been the opie-networkapplet, I seem to remember some issue with that, but I removed it & no fix.
I wish I had the time to set up a development environment, grab the kernel sources & play around. Maybe one day. thanks Mickey.