Kernel Bug Tracker – Bug 42929
GMA500: Regression: 3.3.0-rc7 - Display remains black after S3 (vga console)
Last modified: 2013-04-09 06:23:26 UTC
It was last working in 3.2.1, in 3.3.0-rc7+ it's no longer working.
I will attach a dmesg and lspci. Let me know what else I can do to debug the issue.
PS. Responses might be a bit slow this time, sorry. Also, if I had time for a bisect, I wouldn't post this.
Important: The display stays off after trying to suspend. The system doesn't suspend, though. At least not noticeably. It is still responsive after suspend, though.
Created attachment 72582 [details]
dmesg after suspend
Created attachment 72583 [details]
Possibly related in some way to:
Where I loaded the gma500_gfx graphics driver module before suspend and suspend fails.
IMO, it seems there are two issues here
1) S3 resumes immediately after suspend
2) black screen after suspend
issue 2) is probably caused by the broken gma500_gfx driver.
And issue 1) is probably caused by EHCI?
> [ 17.524804] ehci_hcd 0000:00:1d.7: wake-up capability enabled by ACPI
could you please try to run
"echo disabled > /sys/bus/pci/devices/0000:00:1d.0/power/wakeup" to disable the EHCI wakeup and see if the problem still exists?
Oh, yes, it's true. Sorry! I forgot the LID > /proc/acpi/wakeup.
So issue 1) is gone.
re: LID > /proc/acpi/wakeup
Hmm, so the LID was causing an immediate wakeup?
Has this always been an issue and you've always used this workaround,
or is this a new problem?
re: black screen
ACPI is not responsible for resuming the screen -- the graphics driver is.
So this would be an issue with your graphics driver.
Can you describe the version that works and the version that fails?
No, this is an old problem. Since 2.6.34. See here:
Having black screen issue also/still with released 3.3.0 kernel.
gma500_gfx is the gpu driver there (for the cedartrail gma3600).
Underneath / besides display not powering up all seems to work.
So to me this really could be related to #4291.
Please test 3.5, that should have fixed most of these cases
It's fixed! Works great! Thanks!!!
Now the X display area is moved up about 20 pixels... opening another bug fot that. ;)