wakeup problem from suspend bug report help request

[Derek Broughton]

Oguz Yarimtepe wrote:

> uswsusp didnt't work either. After reading Suse ACPI page
> (http://en.opensuse.org/S2ram) and debuging the suspend process
> (http://en.opensuse.org/ACPI_Suspend_debugging) i realised the problem
> can be related with BIOS or a kernel bug.
> 
> Here what they say:
> 
> If none of the methods described here seem to work, it is important to
> check if the machine is completely dead on resume or only the video is
> not resumed properly. A good way to check this is to start with a
> minimal system (init=/bin/bash), run s2ram -f, and after resume, when
> the display is still off, check if the "Caps Lock" key still works
> (you should see a reaction of the Caps Lock LED on the keyboard). If
> it does, it is most likely really a video initialization problem. If
> it doesn't, then it is most likely a BIOS problem or a bug in the
> Linux kernel.
> 
> After adding the init=/bin/bash to kernel parameters and suspending
> with echo mem > /sys/power/state, 

How on Earth can you read instructions like that, totally ignore them, and
then say you know what's happening?

It didn't say "echo mem > /sys/power/state", it said "s2ram -f".  They use
entirely different methods to suspend.

So now I can't imagine that you've bothered to follow the instructions I
gave you either.  What's the point in asking for help?

I'd also point out that you made a huge leap of faith by believing your
results mean "BIOS or a kernel bug".  Just because they said if it's not
POST it could be one or the other doesn't mean they think either is at all
likely.
-- 
derek