https://bugzilla.novell.com/show_bug.cgi?id=306983#c40
--- Comment #40 from Jens Nixdorf 2007-11-22 09:11:47 MST ---
sorry for the delay. Today i found time to check this with init=/bin/bash:
s2ram without options -> failed completely
s2ram -f -> failed completely
s2ram -f -p -> resumes, keyboard is working, but display is staying blank
s2ram -f -p -s -> resumes, keyboard is working, but display is staying blank
s2ram -f -p -m -> resumes, keyboard is working, but display is staying blank
s2ram -f -p -m -s -> works!
with init=/bin/bash and nohz=off highres=off NOTHING works.
When it works only with "-f -p -m -s" in this small environment
(init=/bin/bash), why it is working approx. 5 of 10 times in the standard
environment, even though there are no options in /etc/pm/...?
Normally i would say that i take these options for a config-file in
/etc/pm/..., but i have to fear that with the next kernel-update the same
procedure starts again like its happen at least three times since 10.3 Beta 2.
Which pm-suspend.log do you want to have? Like it is at the moment, without any
option in /etc/pm/...? After a failed resume? After a working resume?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.