Skip to contentSkip to conversation

hangs on wakeup from s2ram

2.6.28-rc2 regression Soeren Sonnenburg 3 participants 4 messages Oct 27, 2008 – Nov 5, 2008

lore
Share & tools
lore
#0 lore raw

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

#1 lore raw
Quoted 8 lines · Soeren Sonnenburg

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?

#2 lore raw
In reply to Soeren Sonnenburg
Quoted 8 lines · Soeren Sonnenburg

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.

#3 lore raw
Quoted 10 lines · Carlos R. Mafra
Quoted 8 lines · Soeren Sonnenburg

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...

Quoted 8 lines

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