Bug 61691 - AMD A4-1200 APU with Radeon(TM) HD Graphics fails to resume
Summary: AMD A4-1200 APU with Radeon(TM) HD Graphics fails to resume
Status: RESOLVED PATCH_ALREADY_AVAILABLE
Alias: None
Product: Drivers
Classification: Unclassified
Component: Console/Framebuffers (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: James Simmons
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-09-19 20:42 UTC by Stefan de Konink
Modified: 2014-02-02 13:09 UTC (History)
2 users (show)

See Also:
Kernel Version: 3.12.0-rc1+
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Stefan de Konink 2013-09-19 20:42:13 UTC
Currently I am running the latest master. In its minimal configuration I have efi-fb compiled in. The current master suspends the efi-fb driver including a full backlight off. A few days ago that would have been a blinking cursor on the left top with the backlight on. Suspending in essence works, but resume doesn't result in restoring the backlight.

When inserting radeon.ko over an ssh connection after resuming the efi-fb minimal configuration, it switches the backlight on. But results in a screen of tiles then the screen slowly becomes fully white.


When having radeon.ko loading at boot, the results are worse. Unlike the bug below describes the screen is blank but the processes in the kernel do not unsuspend. So echo "mem" > /sys/power/state does eventually suspends the device, but when pressing a key the computer doesn't go beyond a running ventilator. Interesting: ping to the systems IP address does work, ctrl-alt-del doesn't.

https://bugs.freedesktop.org/show_bug.cgi?id=43829

So in my perception there are two bugs here:
 - in the minimal configuration using the EFI framebuffer the backlight should be restored
 - in the preferenced configuration using the radeon framebuffer the processes should continue
Comment 1 Alan 2013-11-04 11:39:42 UTC
radeon or radeonfb ?
Comment 2 Stefan de Konink 2013-11-04 11:54:00 UTC
radeon
Comment 3 Dennis Jansen 2014-01-28 14:14:59 UTC
May be related to: https://bugzilla.kernel.org/show_bug.cgi?id=65141, see my comments there for possible hibernation fix.
Comment 4 Dennis Jansen 2014-01-28 14:15:48 UTC
Sorry, wrong bug entry. probably not related.
Comment 5 Stefan de Konink 2014-01-28 16:06:54 UTC
On the bright side kernel 3.13 does fix my blank screen. Sadly keyboard/mouse does not resume yet.
Comment 6 Dennis Jansen 2014-02-02 12:59:16 UTC
Don't you see only a different issue then, now? I think it might make sense to close this bug as fixed and open another one for the keyboard issue. At least it should be assigned to different developers, because it no longer sounds like a graphics issue to me.
Comment 7 Stefan de Konink 2014-02-02 13:09:42 UTC
Actually it is currently the 'sometimes' component for the keyboard/mouse. When I set up to test everything now, it just resumes including mousen/keyboard support. So I am happy to mark this report as fixed, but need to figure out how to reproduce resume the problem before going forward with opening a new issue.

On the other hand, since the system does start now making an 'expert' trace of the resume probably does work.

Note You need to log in before you can comment on or make changes to this bug.