Hallo,
ich verwende die pm-utils für suspend to ram, welches problemlos funktioniert. Supend to disk bereitet mir allerdings Probleme. Wird das Notebook in den Tiefschlag geschickt, wird zwar die Netzwerkverbindung abgebrochen, der Rechner scheint sich auf den Tiefschlaf vorzubereiten, doch wenig später wird der Produktivzustand wiederhergestellt. Es scheint so, als würde der Vorgang abgebrochen werden.

Die /var/log/pm-suspend.log: 
enabled, not active

/usr/lib/pm-utils/sleep.d/01laptop-mode thaw hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub thaw hibernate:

/usr/lib/pm-utils/sleep.d/01grub thaw hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave thaw hibernate:

/usr/lib/pm-utils/sleep.d/00powersave thaw hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/00logging thaw hibernate:

/usr/lib/pm-utils/sleep.d/00logging thaw hibernate: success.
Son Okt 24 10:27:35 CEST 2010: Finished.
/var/log/messages: 
Oct 24 10:27:32 localhost kernel: ata1.00: configured for UDMA/133
Oct 24 10:27:32 localhost kernel: ata1: EH complete
Oct 24 10:27:32 localhost kernel: EXT4-fs (sda3): re-mounted. Opts: commit=0
Oct 24 10:27:32 localhost kernel: EXT4-fs (sda4): re-mounted. Opts: commit=0
Oct 24 10:27:32 localhost NetworkManager[3914]: <info> sleep requested (sleeping: no  enabled: yes)
Oct 24 10:27:32 localhost NetworkManager[3914]: <info> sleeping or disabling...
Oct 24 10:27:32 localhost NetworkManager[3914]: <info> (eth0): now unmanaged
Oct 24 10:27:32 localhost NetworkManager[3914]: <info> (eth0): device state change: 2 -> 1 (reason 37)
Oct 24 10:27:32 localhost NetworkManager[3914]: <info> (eth0): cleaning up...
Oct 24 10:27:32 localhost NetworkManager[3914]: <info> (eth0): taking down device.
Oct 24 10:27:32 localhost kernel: usb 3-1: USB disconnect, address 2
Oct 24 10:27:32 localhost bluetoothd[3953]: HCI dev 0 down
Oct 24 10:27:32 localhost bluetoothd[3953]: Adapter /org/bluez/3953/hci0 has been disabled
Oct 24 10:27:32 localhost bluetoothd[3953]: Stopping security manager 0
Oct 24 10:27:32 localhost NetworkManager[3914]: <info> (wlan0): now unmanaged
Oct 24 10:27:32 localhost NetworkManager[3914]: <info> (wlan0): device state change: 8 -> 1 (reason 37)
Oct 24 10:27:32 localhost NetworkManager[3914]: <info> (wlan0): deactivating device (reason: 37).
Oct 24 10:27:32 localhost dhcpcd[4070]: received SIGTERM, stopping
Oct 24 10:27:32 localhost dhcpcd[4070]: wlan0: removing interface
Oct 24 10:27:33 localhost NetworkManager[3914]: <info> (wlan0): canceled DHCP transaction, DHCP client pid 4070
Oct 24 10:27:33 localhost bluetoothd[3953]: HCI dev 0 unregistered
Oct 24 10:27:33 localhost bluetoothd[3953]: Unregister path: /org/bluez/3953/hci0
Oct 24 10:27:33 localhost NetworkManager[3914]: <info> (wlan0): cleaning up...
Oct 24 10:27:33 localhost NetworkManager[3914]: <info> (wlan0): taking down device.
Oct 24 10:27:33 localhost kernel: cfg80211: Calling CRDA to update world regulatory domain
Oct 24 10:27:33 localhost NetworkManager[3914]: <warn> (pid 4070) unhandled DHCP event for interface wlan0
Oct 24 10:27:33 localhost NetworkManager[3914]: <info> BT device 34:7E:39:31:07:41 removed
Oct 24 10:27:33 localhost NetworkManager[3914]: <info> BT device D4:88:90:57:0A:D2 removed
Oct 24 10:27:33 localhost NetworkManager[3914]: <info> wake requested (sleeping: yes  enabled: yes)
Oct 24 10:27:33 localhost NetworkManager[3914]: <info> waking up and re-enabling...
Oct 24 10:27:33 localhost NetworkManager[3914]: <info> (eth0): now managed
Oct 24 10:27:33 localhost NetworkManager[3914]: <info> (eth0): device state change: 1 -> 2 (reason 2)
Oct 24 10:27:33 localhost NetworkManager[3914]: <info> (eth0): bringing up device.
Oct 24 10:27:33 localhost laptop-mode: Laptop mode 
Oct 24 10:27:33 localhost laptop-mode: enabled, not active
Oct 24 10:27:33 localhost kernel: ADDRCONF(NETDEV_UP): eth0: link is not ready
Oct 24 10:27:33 localhost NetworkManager[3914]: <info> (eth0): preparing device.
Oct 24 10:27:33 localhost NetworkManager[3914]: <info> (eth0): deactivating device (reason: 2).
Oct 24 10:27:33 localhost NetworkManager[3914]: <info> (wlan0): now managed
Oct 24 10:27:33 localhost NetworkManager[3914]: <info> (wlan0): device state change: 1 -> 2 (reason 2)
Oct 24 10:27:33 localhost NetworkManager[3914]: <info> (wlan0): bringing up device.
Oct 24 10:27:34 localhost kernel: ADDRCONF(NETDEV_UP): wlan0: link is not ready
Oct 24 10:27:34 localhost NetworkManager[3914]: <info> (wlan0): preparing device.
Oct 24 10:27:34 localhost NetworkManager[3914]: <info> (wlan0): deactivating device (reason: 2).
Oct 24 10:27:34 localhost kernel: usb 3-1: new full speed USB device using uhci_hcd and address 3
Oct 24 10:27:34 localhost NetworkManager[3914]: <info> (wlan0): supplicant interface state:  starting -> ready
Oct 24 10:27:34 localhost NetworkManager[3914]: <info> (wlan0): device state change: 2 -> 3 (reason 42)
Oct 24 10:27:34 localhost bluetoothd[3953]: HCI dev 0 registered
Oct 24 10:27:34 localhost bluetoothd[3953]: HCI dev 0 up
Oct 24 10:27:34 localhost bluetoothd[3953]: Starting security manager 0
Oct 24 10:27:34 localhost bluetoothd[3953]: Adapter /org/bluez/3953/hci0 has been enabled
Oct 24 10:27:34 localhost kernel: ata1.00: configured for UDMA/133
Oct 24 10:27:34 localhost kernel: ata1: EH complete
Oct 24 10:27:34 localhost kernel: EXT4-fs (sda3): re-mounted. Opts: commit=0
Oct 24 10:27:35 localhost kernel: EXT4-fs (sda4): re-mounted. Opts: commit=0
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Activation (wlan0) starting connection 'Auto linksys'
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> (wlan0): device state change: 3 -> 4 (reason 0)
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Activation (wlan0/wireless): access point 'Auto xyz' has security, but secrets are required.
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> (wlan0): device state change: 5 -> 6 (reason 0)
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) started...
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> (wlan0): device state change: 6 -> 4 (reason 0)
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) scheduled...
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 1 of 5 (Device Prepare) complete.
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) starting...
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> (wlan0): device state change: 4 -> 5 (reason 0)
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Activation (wlan0/wireless): connection 'Auto xyz' has security, and secrets exist.  No new secrets needed.
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Config: added 'ssid' value 'xyz'
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Config: added 'scan_ssid' value '1'
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Config: added 'bssid' value 'XX:XX:XX:XX:XX:XX'
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Config: added 'key_mgmt' value 'NONE'
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Config: added 'auth_alg' value 'OPEN'
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Config: added 'wep_key0' value '<omitted>'
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Config: added 'wep_tx_keyidx' value '0'
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 2 of 5 (Device Configure) complete.
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> Config: set interface ap_scan to 1
Oct 24 10:27:36 localhost NetworkManager[3914]: <info> (wlan0): supplicant connection state:  inactive -> scanning
Oct 24 10:27:38 localhost NetworkManager[3914]: <info> (wlan0): supplicant connection state:  scanning -> associating
Oct 24 10:27:38 localhost kernel: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
Oct 24 10:27:38 localhost NetworkManager[3914]: <info> (wlan0): supplicant connection state:  associating -> associated
Oct 24 10:27:38 localhost NetworkManager[3914]: <info> (wlan0): supplicant connection state:  associated -> completed
Oct 24 10:27:38 localhost NetworkManager[3914]: <info> Activation (wlan0/wireless) Stage 2 of 5 (Device Configure) successful.  Connected to wireless network 'linksys'.
Oct 24 10:27:38 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) scheduled.
Oct 24 10:27:38 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) started...
Oct 24 10:27:38 localhost NetworkManager[3914]: <info> (wlan0): device state change: 5 -> 7 (reason 0)
Oct 24 10:27:38 localhost NetworkManager[3914]: <info> Activation (wlan0) Beginning DHCPv4 transaction (timeout in 45 seconds)
Oct 24 10:27:38 localhost NetworkManager[3914]: <info> dhcpcd started with pid 5386
Oct 24 10:27:38 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 3 of 5 (IP Configure Start) complete.
Oct 24 10:27:38 localhost dhcpcd[5386]: version 5.2.7 starting
Oct 24 10:27:38 localhost dhcpcd[5386]: wlan0: rebinding lease of 192.168.1.100
Oct 24 10:27:38 localhost NetworkManager[3914]: <info> (wlan0): DHCPv4 state changed nbi -> preinit
Oct 24 10:27:38 localhost dhcpcd[5386]: wlan0: acknowledged 192.168.1.100 from 192.168.1.1
Oct 24 10:27:38 localhost dhcpcd[5386]: wlan0: checking for 192.168.1.100
Oct 24 10:27:43 localhost dhcpcd[5386]: wlan0: leased 192.168.1.100 for 86400 seconds
Oct 24 10:27:43 localhost NetworkManager[3914]: <info> (wlan0): DHCPv4 state changed preinit -> bound
Oct 24 10:27:43 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) scheduled...
Oct 24 10:27:43 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) started...
Oct 24 10:27:43 localhost NetworkManager[3914]: <info>   address 192.168.1.100
Oct 24 10:27:43 localhost NetworkManager[3914]: <info>   prefix 24 (255.255.255.0)
Oct 24 10:27:43 localhost NetworkManager[3914]: <info>   gateway 192.168.1.1
Oct 24 10:27:43 localhost NetworkManager[3914]: <info>   nameserver '195.XX.XXX.XX'
Oct 24 10:27:43 localhost NetworkManager[3914]: <info>   nameserver '195.XX.XXX.XX'
Oct 24 10:27:43 localhost NetworkManager[3914]: <info>   domain name 'xyz.com'
Oct 24 10:27:43 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) scheduled...
Oct 24 10:27:43 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 4 of 5 (IP4 Configure Get) complete.
Oct 24 10:27:43 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) started...
Oct 24 10:27:44 localhost NetworkManager[3914]: <info> (wlan0): device state change: 7 -> 8 (reason 0)
Oct 24 10:27:44 localhost NetworkManager[3914]: <info> Policy set 'Auto linksys' (wlan0) as default for IPv4 routing and DNS.
Oct 24 10:27:44 localhost NetworkManager[3914]: <info> Activation (wlan0) successful, device activated.
Oct 24 10:27:44 localhost NetworkManager[3914]: <info> Activation (wlan0) Stage 5 of 5 (IP Configure Commit) complete.
meine fstab: 
# 
# /etc/fstab: static file system information
#
# <file system>        <dir>         <type>    <options>          <dump> <pass>
devpts                 /dev/pts      devpts    defaults            0      0
shm                    /dev/shm      tmpfs     nodev,nosuid        0      0

#/dev/cdrom             /media/cd   auto    ro,user,noauto,unhide   0      0
#/dev/dvd               /media/dvd  auto    ro,user,noauto,unhide   0      0
#/dev/fd0               /media/fl   auto    user,noauto             0      0

/dev/sda1 swap swap defaults 0 0
/dev/sda2 /boot ext2 defaults 0 1
/dev/sda3 / ext4 defaults 0 1
/dev/sda4 /home ext4 defaults 0 1
Der relevante Teil aus meiner menu.lst: 
# (0) Arch Linux
title  Arch Linux
root   (hd0,1)
kernel /vmlinuz26 root=/dev/sda3 resume=/dev/sda1 ro i915.modeset=1
initrd /kernel26.img
free -m 
             total       used       free     shared    buffers     cached
Mem:          1968        693       1274          0         45        274
-/+ buffers/cache:        374       1594
Swap:         3812          0       3812
Des weiteren wurde der Hook resume in die mkinitcpio.conf eingefügt und das image neu generiert.
Vielleicht könnt ihr das Verhalten nachvollziehen. Danke für alle Antworten!
Die einzig hilfreiche Datei pm-powersave.log ist total unvollständig. Ist das beim Posten verloren gegangen oder wird das vom letzten Hook den Laptop Mode Tools verursacht?
Es entspricht genau dem Inhalt der pm-suspend.log. Der Inhalt wird immer exakt gleich erstellt, wenn ich versuche den Rechner in den Tiefschlaf zu schicken. Die pm-powersave.log enthält: 
Running hook /usr/lib/pm-utils/power.d/disable_wol false:
Setting Wake On Lan for eth0 to enable...Done.

/usr/lib/pm-utils/power.d/disable_wol false: success.
Running hook /usr/lib/pm-utils/power.d/hal-cd-polling false:

/usr/lib/pm-utils/power.d/hal-cd-polling false: success.
Running hook /usr/lib/pm-utils/power.d/harddrive false:
Disabling hard drive power management for /dev/sda...Done.

/usr/lib/pm-utils/power.d/harddrive false: success.
Running hook /usr/lib/pm-utils/power.d/intel-audio-powersave false:

/usr/lib/pm-utils/power.d/intel-audio-powersave false: success.
Running hook /usr/lib/pm-utils/power.d/journal-commit false:
Setting journal commit time for / to 0...Done.
Setting journal commit time for /home to 0...Done.

/usr/lib/pm-utils/power.d/journal-commit false: success.
Running hook /usr/lib/pm-utils/power.d/laptop-mode false:
Laptop mode disabled.

/usr/lib/pm-utils/power.d/laptop-mode false: success.
Running hook /usr/lib/pm-utils/power.d/pcie_aspm false:

/usr/lib/pm-utils/power.d/pcie_aspm false: success.
Running hook /usr/lib/pm-utils/power.d/readahead false:
Setting readahead for /dev/sda3 to 256...Done.
Setting readahead for /dev/sda2 to 256...Done.
Setting readahead for /dev/sda4 to 256...Done.

/usr/lib/pm-utils/power.d/readahead false: success.
Running hook /usr/lib/pm-utils/power.d/sata_alpm false:
Setting SATA APLM on host2 to max_performance...Done.
Setting SATA APLM on host3 to max_performance...Done.
Setting SATA APLM on host4 to max_performance...Done.

/usr/lib/pm-utils/power.d/sata_alpm false: success.
Running hook /usr/lib/pm-utils/power.d/sched-powersave false:
**sched policy powersave OFF

/usr/lib/pm-utils/power.d/sched-powersave false: success.
Running hook /usr/lib/pm-utils/power.d/wireless false:
Turning powersave for wlan0 off...Error for wireless request "Set Power Management" (8B2C) :
    SET failed on device wlan0 ; Operation not supported.
Failed.

/usr/lib/pm-utils/power.d/wireless false: success.
Running hook /usr/lib/pm-utils/power.d/xfs_buffer false:

/usr/lib/pm-utils/power.d/xfs_buffer false: success.
Veflucht, vertippt! Ich meinte natürlich die pm-suspend.log, die andre ist ebenso nutzlos. Deinstalliere testweise mal die Laptop Mode Tools mach erneut einen Versuch für Hibernate und schau nochmal nach dem Log.
Die Meldungen sind nun ein wenig hilfreicher. 
Initial commandline parameters: 
Son Okt 24 20:11:12 CEST 2010: Running hooks for hibernate.
Running hook /usr/lib/pm-utils/sleep.d/00logging hibernate hibernate:
Linux Lambert 2.6.35-ARCH #1 SMP PREEMPT Wed Sep 29 08:45:18 CEST 2010 x86_64 Intel(R) Core(TM)2 Duo CPU T7300 @ 2.00GHz GenuineIntel GNU/Linux
Module                  Size  Used by
fuse                   62808  3 
rfcomm                 35171  4 
sco                     8700  2 
bnep                    8726  2 
l2cap                  40132  16 rfcomm,bnep
ext2                   64042  1 
btusb                  11353  3 
bluetooth              50581  11 rfcomm,sco,bnep,l2cap,btusb
snd_hda_codec_analog    72140  1 
arc4                    1378  2 
snd_seq_dummy           1463  0 
ecb                     2041  2 
snd_seq_oss            28792  0 
snd_seq_midi_event      5436  1 snd_seq_oss
snd_seq                50146  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device          5297  3 snd_seq_dummy,snd_seq_oss,snd_seq
iwlagn                294335  0 
uhci_hcd               22118  0 
snd_pcm_oss            39189  0 
snd_mixer_oss          17106  1 snd_pcm_oss
snd_hda_intel          22285  0 
snd_hda_codec          77223  2 snd_hda_codec_analog,snd_hda_intel
snd_hwdep               6110  1 snd_hda_codec
iwlcore               121988  1 iwlagn
snd_pcm                71445  3 snd_pcm_oss,snd_hda_intel,snd_hda_codec
snd_timer              19265  2 snd_seq,snd_pcm
tpm_tis                 8440  0 
tpm                    11181  1 tpm_tis
sdhci_pci               7090  0 
sdhci                  16478  1 sdhci_pci
mac80211              189302  2 iwlagn,iwlcore
snd_page_alloc          7249  2 snd_hda_intel,snd_pcm
tpm_bios                5505  1 tpm
ac                      3105  0 
battery                10103  0 
cfg80211              144231  3 iwlagn,iwlcore,mac80211
mmc_core               54202  1 sdhci
thinkpad_acpi          61936  0 
ehci_hcd               36992  0 
rfkill                 16010  4 bluetooth,cfg80211,thinkpad_acpi
iTCO_wdt               10669  0 
iTCO_vendor_support     1833  1 iTCO_wdt
usbcore               146481  4 btusb,uhci_hcd,ehci_hcd
e1000e                138147  0 
snd                    57626  12 snd_hda_codec_analog,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer,thinkpad_acpi
soundcore               6065  1 snd
led_class               2363  2 sdhci,thinkpad_acpi
tp_smapi               20873  0 
thinkpad_ec             4190  1 tp_smapi
i2c_i801                9062  0 
psmouse                54040  0 
nvram                   5837  1 thinkpad_acpi
evdev                   8775  13 
thermal                12338  0 
pcspkr                  1819  0 
sg                     25652  0 
cpufreq_ondemand        8439  2 
phc_intel               9847  1 
serio_raw               4486  0 
freq_table              2355  2 cpufreq_ondemand,phc_intel
processor              28966  3 phc_intel
mperf                   1243  1 phc_intel
rtc_cmos                9022  0 
rtc_core               14439  1 rtc_cmos
rtc_lib                 1898  1 rtc_core
ext4                  310908  2 
mbcache                 5746  2 ext2,ext4
jbd2                   69523  1 ext4
crc16                   1297  2 l2cap,ext4
sd_mod                 29536  5 
ahci                   20609  0 
ata_piix               21548  0 
libahci                19134  5 ahci
pata_acpi               3248  0 
libata                157227  4 ata_piix,ahci,libahci,pata_acpi
scsi_mod              124416  3 sg,sd_mod,libata
i915                  301815  2 
drm_kms_helper         24903  1 i915
drm                   164459  3 i915,drm_kms_helper
i2c_algo_bit            5231  1 i915
button                  4834  1 i915
i2c_core               18987  5 i2c_i801,i915,drm_kms_helper,drm,i2c_algo_bit
video                  19337  1 i915
output                  1972  1 video
intel_agp              30046  2 i915
             total       used       free     shared    buffers     cached
Mem:       2015460     337188    1678272          0      40524     121172
-/+ buffers/cache:     175492    1839968
Swap:      3903756          0    3903756

/usr/lib/pm-utils/sleep.d/00logging hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave hibernate hibernate:

/usr/lib/pm-utils/sleep.d/00powersave hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub hibernate hibernate:

/usr/lib/pm-utils/sleep.d/01grub hibernate hibernate: success.
Running hook /etc/pm/sleep.d/09tpfand hibernate hibernate:
:: Stopping ThinkPad fan control daemon    [BUSY]    [DONE] 

/etc/pm/sleep.d/09tpfand hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/11netcfg hibernate hibernate:

/usr/lib/pm-utils/sleep.d/11netcfg hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth hibernate hibernate:

/usr/lib/pm-utils/sleep.d/49bluetooth hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager hibernate hibernate:
Having NetworkManager put all interaces to sleep...Done.

/usr/lib/pm-utils/sleep.d/55NetworkManager hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules hibernate hibernate:

/usr/lib/pm-utils/sleep.d/75modules hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock hibernate hibernate:

/usr/lib/pm-utils/sleep.d/90clock hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq hibernate hibernate:

/usr/lib/pm-utils/sleep.d/94cpufreq hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/95led hibernate hibernate:

/usr/lib/pm-utils/sleep.d/95led hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler hibernate hibernate:
Kernel modesetting video driver detected, not using quirks.

/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler hibernate hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/99video hibernate hibernate:

/usr/lib/pm-utils/sleep.d/99video hibernate hibernate: success.
Son Okt 24 20:11:13 CEST 2010: performing hibernate
s2disk: Could not stat the resume device file. Reason: No such file or directory
Son Okt 24 20:11:14 CEST 2010: Awake.
Son Okt 24 20:11:14 CEST 2010: Running hooks for thaw
Running hook /usr/lib/pm-utils/sleep.d/99video thaw hibernate:

/usr/lib/pm-utils/sleep.d/99video thaw hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler thaw hibernate:

/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler thaw hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/95led thaw hibernate:

/usr/lib/pm-utils/sleep.d/95led thaw hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq thaw hibernate:

/usr/lib/pm-utils/sleep.d/94cpufreq thaw hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/90clock thaw hibernate:

/usr/lib/pm-utils/sleep.d/90clock thaw hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules thaw hibernate:
Reloaded unloaded modules.

/usr/lib/pm-utils/sleep.d/75modules thaw hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager thaw hibernate:
Having NetworkManager wake interfaces back up...Done.

/usr/lib/pm-utils/sleep.d/55NetworkManager thaw hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/49bluetooth thaw hibernate:

/usr/lib/pm-utils/sleep.d/49bluetooth thaw hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/11netcfg thaw hibernate:

/usr/lib/pm-utils/sleep.d/11netcfg thaw hibernate: success.
Running hook /etc/pm/sleep.d/09tpfand thaw hibernate:
:: Starting ThinkPad fan control daemon    [BUSY]    [DONE] 

/etc/pm/sleep.d/09tpfand thaw hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/01grub thaw hibernate:

/usr/lib/pm-utils/sleep.d/01grub thaw hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/00powersave thaw hibernate:

/usr/lib/pm-utils/sleep.d/00powersave thaw hibernate: success.
Running hook /usr/lib/pm-utils/sleep.d/00logging thaw hibernate:

/usr/lib/pm-utils/sleep.d/00logging thaw hibernate: success.
Son Okt 24 20:11:15 CEST 2010: Finished.
Das System scheint nach dem Fehler (s2disk: Could not stat the resume device file. Reason: No such file or directory) gleich wieder aufzuwachen. Seltsam, denn der Pfad in der menu.lst stimmt mit dem zur Swap-Partition überein.

EDIT: Das Anlegen einer config-Datei in /etc/pm/config.d mit dem Inhalt SLEEP_MODULE="kernel" hat mein Problem gelöst. Danke für deine Hilfe, fs4000. Welche Vor-/Nachteile bringt es denn, wenn ich statt dem kernel-Modul uswusp oder tuxonice verwende?
Tuxonice ist ja leider ein Kernelpatch, deshalb kann ich das weniger empfehlen. Uswsusp hat vll. den Vorteil, dass es wie Windows seit Vista "suspend to both" kann, also man kann sowohl vom RAM weitermachen und wenn der Strom ausgefallen ist von der Festplatte. Leider ist diese Funktion in keinem mir bekannten GUI implementiert.
Danke für die Information. Ich werde beim kernel Modul bleiben, bis jetzt funktioniert es problemlos.