Bug 72901 - AMD A6: Since 3.12.8 machines no longer wake up from sleep
Summary: AMD A6: Since 3.12.8 machines no longer wake up from sleep
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: ACPI
Classification: Unclassified
Component: Power-Sleep-Wake (show other bugs)
Hardware: All Linux
: P1 blocking
Assignee: acpi_power-sleep-wake
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-24 19:11 UTC by infove
Modified: 2016-05-09 02:23 UTC (History)
4 users (show)

See Also:
Kernel Version: 3.12.9 and up
Subsystem:
Regression: No
Bisected commit-id:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description infove 2014-03-24 19:11:03 UTC 
Since v. 3.12.8 the machines no longer wake up from sleep in 50% cases.
No reaction to keyboard (Ctl-Alt-Del) and no USB power on mouse (all plugged into motherboard port directly).

Platform: AMD A6 APU, A75 chipset.

Kernel 3.12.8 is the last one which wakes up properly in 100%.
Tried 3.12.9 and 3.13 series - same behaviour.

Please revert wake from sleep code back, systems became useless.

Thank you
Comment 1 Aaron Lu 2014-03-27 09:01:43 UTC 
Looks like you will need to do a git bisect to find out the offending commit. There shouldn't be too many commits between v3.12.8 - v3.12.9. Also, you can try the document:
https://www.kernel.org/doc/Documentation/power/basic-pm-debugging.txt
To find out if it is caused by a driver module.
Comment 2 Zhang Rui 2014-06-03 06:39:51 UTC 
infove, any udpate on this?
Comment 3 infove 2014-06-05 00:00:33 UTC 
What update? Have you fixed the issue?
Comment 4 Zhang Rui 2014-06-05 01:43:30 UTC 
no, have you tried to do git bisect?
Comment 5 Lan Tianyu 2014-08-04 02:09:11 UTC 
Close this bug since no response for long time. Please reopen it if there are some updates.
Comment 6 infove 2014-08-04 02:42:53 UTC 
Why did you close this bug? What information do you need? You have not taken any action to triage this bug, apparently.

I could not figure out from your cryptic comments what the heck you needed from me. Please be verbose and use clearly spelled plain English language to convey your ideas instead of using the acronyms only you understand.
Comment 7 Lan Tianyu 2014-08-04 02:47:24 UTC 
From Aaron and Rui comments, git bisect is needed and please try do bisect between v3.12.8 and v3.12.9 to find out which commit breaks wakeup.
Comment 8 infove 2014-08-04 13:46:35 UTC 
I have no faintest idea what 'git bisect' is.

If that is something that you expect me to perform to figure out what is different between two consecutive minor versions, you are asking a wrong person and for too much.
Comment 9 Zhang Rui 2015-12-29 01:38:20 UTC 
Aaron, can you please share the link about how to do git bisect?
Comment 10 Zhang Rui 2016-03-15 08:37:54 UTC 
Please check this page and try git bisect to find out the offending commit, https://git-scm.com/docs/git-bisect
Comment 11 Zhang Rui 2016-05-09 02:23:26 UTC 
Bug closed as there is no response from the bug reporter.
Please feel free to reopen it if you can try git-bisect to find out the offending commit.
Note You need to log in before you can comment on or make changes to this bug.