Dear all,
my macbook pro 1,1 suspends nicely (s2ram) but on wakeup I see a black
screen...
Does anyone else observe this? As this was from within X (and it still
works in .27) I cannot give more details without further investigations
from the cmdline...
SOeren
On 10/27/2008 12:28 PM, Soeren Sonnenburg wrote:
> Dear all,
>
> my macbook pro 1,1 suspends nicely (s2ram) but on wakeup I see a black
> screen...
>
> Does anyone else observe this? As this was from within X (and it still
> works in .27) I cannot give more details without further investigations
> from the cmdline...
Most distros switch to a console and even after that do suspend (if not, just
try it from console). Do you see any traces when you add no_console_suspend to
the kernel command line?
On Mon 27.Oct'08 at 12:28:17 +0100, Soeren Sonnenburg wrote:
> Dear all,
>
> my macbook pro 1,1 suspends nicely (s2ram) but on wakeup I see a black
> screen...
>
> Does anyone else observe this? As this was from within X (and it still
> works in .27) I cannot give more details without further investigations
> from the cmdline...
This is also happening with my Vaio, and 2.6.27 works fine suspending
to RAM from inside X.
I was silent about this issue (it happened before -rc1) because I really
did not have the time to bisect it, which I think is the best way to
solve this issues quickly.
I will try to bisect it in the next days, but I can't promiss anything.
On Mon, 2008-10-27 at 15:10 +0100, Carlos R. Mafra wrote:
> On Mon 27.Oct'08 at 12:28:17 +0100, Soeren Sonnenburg wrote:
> > Dear all,
> >
> > my macbook pro 1,1 suspends nicely (s2ram) but on wakeup I see a black
> > screen...
> >
> > Does anyone else observe this? As this was from within X (and it still
> > works in .27) I cannot give more details without further investigations
> > from the cmdline...
>
> This is also happening with my Vaio, and 2.6.27 works fine suspending
> to RAM from inside X.
>
> I was silent about this issue (it happened before -rc1) because I really
> did not have the time to bisect it, which I think is the best way to
> solve this issues quickly.
>
> I will try to bisect it in the next days, but I can't promiss anything.
I still have this hang in resume -rc3+git current, but I don't have the
time to dig into this for the next 3 weeks :(
Soeren