[ltp] Suspend to Disk - Kenrel 2.6.4 vs. r50p

[Niel Lambrechts]

On Thu, 2004-04-29 at 08:07, hamish wrote:
> I have an r50p and runnign debian unstable with kernel 2.6.4, compiled 

> What is the story on suspend to disk anyway? Should we use the kernel 
> code? swsusp patches & resume2? pmdisk patches?  Damnit I just want it 
> to work... I'd even use straight FN-F4 except my video won't wake up 
> afterwards... Currently I have to reboot several times a day (i.e. 
> whenever I want to move my thinkpad from one place to another). very 
> frustrating...
> 
> TIA
>   hamish.

I also have a R50P. I am running SuSE 9.0 Pro (like we all should :) )
and 2.6.6-rc2-mm1 / ACPI / swsusp. The only alteration I make is to use
my own dsdt, since IBM's is borked. Let me know if you're interested.

USB modules dont load under ACPI suspend-to-RAM for a couple of kernels
now on this type of Thinkpad. I understand from a linux.kernel message
from Len Brown that this is really a pci config space problem, and not
usb... Anyhow, after a suspend to ram, modprobe ehci-hcd hangs and cpu =
busy. If I dont use USB afterwards, I can successfully use S3.

My most stable solution is to use swsusp. I can suspend/resume ok under
X (not accelerated), and all other things I use (usb, wifi, samba etc.)
still works after resuming. All I did was a mkswap, and add
resume=/dev/hda2 (swap partition) to make things work.


-Niel 

PS: funny, have you ever checked the date of doing a ps -ef|grep grep
after resuming (any method, acpi/apm)? It does not match current/hwclock
date!