Acpi suspend to ram on Acer Aspire 5672
Hi list,
I don't know what the correct approach to this is, but I need some help :-)
I have been trying to get my Acer Aspire 5672 to suspend to ram, using kernel version 2.6.22 patched by Gentoo (r8). The ACPI functions work for shutting down the machine, and (but I'm not sure of this) for suspend to disk. When I set /sys/power/state to "disk" the power-led switches to orange (which it also does when switching to suspend in Windows).
Quoted 1 line
From the above I think that ACPI is working as it should, but when I try
to suspend to ram the machine switches to the correct state (orange power-led) but is unable to resume. When resuming the machine hangs, disk spins up but it's not reacting to for example the num-lock key.
I've read a lot about how suspend to ram is supposed to work, and if I understand it correctly the ACPI functions from the BIOS are supposed to jump to kernel code when resuming and the kernel should initialize all hardware correct? Is there some way to check whether it is actually reaching kernel-code, and thus if this might be fixable in kernel?
I have already tried to patch the DSDT, but to no avail. The errors:
Some reserved symbols being used and some methods that didn't return a value for all controlpaths (notably _WAK which I changed to return 0x00,0x00 on the last line).
Is there anything else I can try?
Regards,
Tomas
P.S. I'm not a native English speaker, so sorry for some weird grammar choices.
Hi Tomas,
I have this problem on ACER Extensa 5220.
The "save to disk" is OK,but after "save to RAM" the notebook hangs and seems (for example when i press CapsLock key - nothing) one is dead.
Roman.
Quoted 40 lines · Tomas Salfischberger
Hi list,
I don't know what the correct approach to this is, but I need some help :-)
I have been trying to get my Acer Aspire 5672 to suspend to ram, using kernel version 2.6.22 patched by Gentoo (r8). The ACPI functions work for shutting down the machine, and (but I'm not sure of this) for suspend to disk. When I set
/sys/power/stateto "disk" the power-led switches to orange (which it also does when switching to suspend in Windows).From the above I think that ACPI is working as it should, but when I try to suspend to ram the machine switches to the correct state (orange power-led) but is unable to resume. When resuming the machine hangs, disk spins up but it's not reacting to for example the num-lock key.
I've read a lot about how suspend to ram is supposed to work, and if I understand it correctly the ACPI functions from the BIOS are supposed to jump to kernel code when resuming and the kernel should initialize all hardware correct? Is there some way to check whether it is actually reaching kernel-code, and thus if this might be fixable in kernel?
I have already tried to patch the DSDT, but to no avail. The errors:
Some reserved symbols being used and some methods that didn't return a value for all controlpaths (notably_WAKwhich I changed to return 0x00,0x00 on the last line).Is there anything else I can try?
Regards,
Tomas
P.S. I'm not a native English speaker, so sorry for some weird grammar choices.-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Hi,
Quoted 4 lines · Roman Rumisek
I have this problem on ACER Extensa 5220.
The "save to disk" is OK,but after "save to RAM" the notebook hangs and seems (for example when i press CapsLock key - nothing) one is dead.
I also received an off-list reply from Peter Pregler about his Acer TM 3200 having the same issues.
What we need to debug this is some method of first finding out whether the kernel-code is actually reached during the resume process. If it is actually executing kernel-code, we need to debug at which point in hardware initialization it gets stuck.
Peter mentioned we need serial-port access (or a special firewire-cable) to debug. Do you have a docking-station?
An other approach would be to patch the kernel to use the system-speaker to output some debug beeps. I'll look into that the next moment I have a few spare hours, probably Thursday.
Just to get more details: Is the "Acer Extensa 5220" a dual core model?
Thanks for your reply,
Tomas
Hi,
Quoted 11 lines · Tomas Salfischberger
Hi,
Quoted 4 lines · Roman Rumisek
I have this problem on ACER Extensa 5220.
The "save to disk" is OK,but after "save to RAM" the notebook hangs and seems (for example when i press CapsLock key - nothing) one is dead.I also received an off-list reply from Peter Pregler about his Acer TM 3200 having the same issues.
Quoted 7 lines
What we need to debug this is some method of first finding out whether the kernel-code is actually reached during the resume process. If it is actually executing kernel-code, we need to debug at which point in hardware initialization it gets stuck.
Peter mentioned we need serial-port access (or a special firewire-cable) to debug. Do you have a docking-station?
No, only notebook.
Quoted 6 lines
An other approach would be to patch the kernel to use the system-speaker to output some debug beeps. I'll look into that the next moment I have a few spare hours, probably Thursday.
Just to get more details: Is the "Acer Extensa 5220" a dual core model?
May be, but I have notebook with D530 Celeron.
Roman
Quoted 8 lines
Thanks for your reply,
Tomas
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html