Bug 11522
Summary: | S2ram is broken on laptops | ||
---|---|---|---|
Product: | Power Management | Reporter: | Clark Tompsett (clarkt) |
Component: | Hibernation/Suspend | Assignee: | power-management_other |
Status: | REJECTED INSUFFICIENT_DATA | ||
Severity: | normal | CC: | rjw, rui.zhang |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 2.6.27-rc5 | Subsystem: | |
Regression: | Yes | Bisected commit-id: | |
Bug Depends on: | |||
Bug Blocks: | 7216, 10492 | ||
Attachments: |
dmesg output from successful s2ram
pm-suspend log correct log from 6772 showing good s2ram with 2.6.25 kernel dmesg log 6772 good suspend pm-suspend log 6772 2.6.27-rc5 bad lspci output git show output output from bisect module list |
Description
Clark Tompsett
2008-09-08 13:03:41 UTC
Created attachment 17682 [details]
dmesg output from successful s2ram
dmesg output from dv6772 showing successful recovery from s2ram on 2.6.25 kernel with patch from 11368.
Created attachment 17683 [details]
pm-suspend log
pm-suspend log from dv6772 that goes with the dmesg log.
logs attached are from the wrong machine. Please delete them. Created attachment 17684 [details]
correct log from 6772 showing good s2ram with 2.6.25 kernel
correct log from 6772 (amd tl-64) showing good s2ram with the 2.6.25 kernel
Created attachment 17685 [details]
dmesg log 6772 good suspend
dmesg log 6772 2.6.25 good suspend.
Created attachment 17686 [details]
pm-suspend log 6772 2.6.27-rc5 bad
pm suspend log showing system did not restore from s2ram 6772 2.6.27-rc5 kernel. No binary blobs used in this test system.
The fastest way to determine what broke suspend/resume on your boxes would be to carry out bisection of kernels between 2.6.25 and 2.6.26 using git-bisect. Can you please do that? >+ /usr/sbin/s2ram -fa3 --vbe_post
does the problem still exist without using these parameters?
please attach the lspci output.
Created attachment 17739 [details]
lspci output
lspci output that you asked for.
bisect results -- 2.6.26-rc8 to rc9: 821b03ffac8851d6bc1d5530183d2eb25adae35d this broke s2ram # git show 821b03ffac8851d6bc1d5530183d2eb25adae35d fatal: bad object 821b03ffac8851d6bc1d5530183d2eb25adae35d weird. :( (In reply to comment #10) > bisect results -- 2.6.26-rc8 to rc9: > 821b03ffac8851d6bc1d5530183d2eb25adae35d > > this broke s2ram There's no such commit in the Linus' tree. Are you sure you're testing an unmodified kernel.org kernel? command used to get the git tree: $ git clone \ git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git linux-2.6 i don't see this commit either. Clark, what do you see from: $ git show 821b03ffac8851d6bc1d5530183d2eb25adae35d Created attachment 17980 [details]
git show output
output from get show as requested.
clark, you are probably running the linux-next tree. please run "cat .git/config" to make sure. If you're not using linus's git tree, please run the command in comment #13 again to get the latest mainline kernel and test again. :) [core] repositoryformatversion = 0 filemode = true bare = false logallrefupdates = true [remote "origin"] url = git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git fetch = +refs/heads/*:refs/remotes/origin/* [branch "master"] remote = origin merge = refs/heads/master This commit is in the mainline and it is a merge with the networking tree. Clark, please verify that commit 3d25802e3ba7c82457b5c12bbfeefe391d8a333e works for you. If it does, please try bisection between commits 2fe195cfe3e53c144d247b2768e37732e8eae4d8 and 88a6f4ad76be425f47df7f892baf913bcd466fb3 . I need information on how to do test specific commits. $ git bisect start $ git bisect good 88a6f4ad76be425f47df7f892baf913bcd466fb3 $ git bisect bad 2fe195cfe3e53c144d247b2768e37732e8eae4d8 but first please verify that 88a6f4ad76be425f47df7f892baf913bcd466fb3 works for you and 2fe195cfe3e53c144d247b2768e37732e8eae4d8 fails. If 2fe195cfe3e53c144d247b2768e37732e8eae4d8 works, then the merge itself has cause the problem to appear, so if you find that this is the case, please let me know. Created attachment 18101 [details]
output from bisect
output from the bisect and this is what failed. But, that driver is not used by my system(s).
Created attachment 18102 [details]
module list
This is a list of the modules used on the hp system I'm using for testing.
does the problem still exist in the latest kernel release? I'll have to get the current 2.6.28 kernel to test. Currently with OpenSuSE 11.1 RC1, the gateway ml3109 (intel celeron 520) will suspend to ram but the hp dv6772 (amd tl84) does not. clark, any update? does 2.6.28 work for you on hp dv6772? if not, please 1. set CONFIG_PM_DEBUG and rebuild your kernel 2. echo {freezer, devices, platform, processors, core} > /sys/power/pm_test 3. echo mem > /sys/power/state 4. does the system come back in a few seconds? Tried the 2.6.29 kernel and it still will not return from s2ram mode. so you mean the test in comment #25 still failed? If not, please do the test in comment #25. note that you need to try "freezer/devices/platform/processor/core" one by one and see if all of them work, or which one fails. close this bug as there is no response from the bug reporter. please reopen the bug if the problem still exists in the latest upstream kernel and you can provide the info requested in comment #27. |