2.6.10-mm2: swsusp problem with resuming on batteries (AMD64)
Hi,
On 2.6.10-mm2, if swsusp suspends my box on AC power and then it's resumed on batteries, the box reboots after (or while) suspending devices (ie before restoring the image). This is 100% reproducible, it appears.
The box is an Athlon 64 laptop on NForce 3.
Greets,
RJW
Signature · 3 lines
- Would you tell me, please, which way I ought to go from here? - That depends a good deal on where you want to get to. -- Lewis Carroll "Alice's Adventures in Wonderland"
Hi!
Quoted 5 lines
On 2.6.10-mm2, if swsusp suspends my box on AC power and then it's resumed on batteries, the box reboots after (or while) suspending devices (ie before restoring the image). This is 100% reproducible, it appears.
The box is an Athlon 64 laptop on NForce 3.
Can you try without cpufreq support? If we attempt to do 2GHz on AC power, machine may die ugly death.
Pavel
Signature · 2 lines
People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
Quoted 4 lines
Quoted 1 line
The box is an Athlon 64 laptop on NForce 3.
Can you try without cpufreq support? If we attempt to do 2GHz on AC power, machine may die ugly death.
Athlon 64 probably means it's running an x86_64 kernel. Wasn't there another thread on lkml about -mm2 swsusp and x86_64? I wonder if it's the same problem (or a related one).
-Barry K. Nathan <[email protected]>
Quoted 7 lines · Barry K. Nathan
Quoted 4 lines
Quoted 1 line
The box is an Athlon 64 laptop on NForce 3.
Can you try without cpufreq support? If we attempt to do 2GHz on AC power, machine may die ugly death.
Athlon 64 probably means it's running an
x86_64kernel. Wasn't there another thread on lkml about -mm2 swsusp andx86_64?
Yes, there was.
Quoted 1 line
I wonder if it's the same problem (or a related one).
The other thread was about the hang caused by the timer driver on suspend (which I'm still trying to understand, but it takes time ;-)).
That problem is rather not related to this one, because I'm currently using a slightly modified kernel in which the function timer_resume() (that caused the hang) is a noop.
Greets,
RJW
Signature · 3 lines
- Would you tell me, please, which way I ought to go from here? - That depends a good deal on where you want to get to. -- Lewis Carroll "Alice's Adventures in Wonderland"
Hi!
Quoted 5 lines
On 2.6.10-mm2, if swsusp suspends my box on AC power and then it's resumed on batteries, the box reboots after (or while) suspending devices (ie before restoring the image). This is 100% reproducible, it appears.
The box is an Athlon 64 laptop on NForce 3.
Forcing machine to 800MHz before suspend may do the trick, too.
Pavel
Signature · 2 lines
People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
Quoted 3 lines · Pavel Machek
Hi!
Quoted 1 line
On 2.6.10-mm2, if swsusp suspends my box on AC power and then it's resumed
on
Quoted 6 lines
Quoted 4 lines
batteries, the box reboots after (or while) suspending devices (ie before restoring the image). This is 100% reproducible, it appears.
The box is an Athlon 64 laptop on NForce 3.
Forcing machine to 800MHz before suspend may do the trick, too.
How can I do this?
RJW
Signature · 3 lines
- Would you tell me, please, which way I ought to go from here? - That depends a good deal on where you want to get to. -- Lewis Carroll "Alice's Adventures in Wonderland"
Hi!
Quoted 10 lines
Quoted 1 line
Quoted 1 line
On 2.6.10-mm2, if swsusp suspends my box on AC power and then it's resumed
on
Quoted 6 lines
Quoted 4 lines
batteries, the box reboots after (or while) suspending devices (ie before restoring the image). This is 100% reproducible, it appears.
The box is an Athlon 64 laptop on NForce 3.
Forcing machine to 800MHz before suspend may do the trick, too.
How can I do this?
echo "0%44%44%powersave" > /proc/cpufreq if you have that interface enabled. Or simply turn off CONFIG_CPUFREQ in config.
Pavel
Signature · 2 lines
People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
Quoted 3 lines · Pavel Machek
Hi!
Quoted 1 line
Quoted 1 line
Quoted 1 line
On 2.6.10-mm2, if swsusp suspends my box on AC power and then it's
resumed
Quoted 2 lines
Quoted 2 lines
on
Quoted 1 line
Quoted 1 line
batteries, the box reboots after (or while) suspending devices (ie
before
Quoted 10 lines
Quoted 7 lines
Quoted 5 lines
Quoted 3 lines
restoring the image). This is 100% reproducible, it appears.
The box is an Athlon 64 laptop on NForce 3.
Forcing machine to 800MHz before suspend may do the trick, too.
How can I do this?
echo "0%44%44%powersave" >
/proc/cpufreqif you have that interface enabled. Or simply turn offCONFIG_CPUFREQin config.
I turned off CONFIG_CPUFREQ and it helped. Still, cpufreq is a neat feature and I'd like to keep it in the kernel. :-)
Greets,
RJW
Signature · 3 lines
- Would you tell me, please, which way I ought to go from here? - That depends a good deal on where you want to get to. -- Lewis Carroll "Alice's Adventures in Wonderland"
Hi!
Quoted 9 lines
Quoted 6 lines
Quoted 3 lines
Quoted 1 line
Forcing machine to 800MHz before suspend may do the trick, too.
How can I do this?
echo "0%44%44%powersave" >
/proc/cpufreqif you have that interface enabled. Or simply turn offCONFIG_CPUFREQin config.I turned off
CONFIG_CPUFREQand it helped. Still, cpufreq is a neat feature and I'd like to keep it in the kernel. :-)
Yes, uh, what you have to do is add suspend/resume routines to cpufreq. Always force it to lowest frequency in device_suspend()... and force it to rescan AC/battery status before going to higher frequency.
Pavel
Signature · 2 lines
People were complaining that M$ turns users into beta-testers... ...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!