nefunkcni ACPI events po suspend2 a probuzeni

Pri suspend-to-ram a naslednem probuzeni je vse v poradku, ale pri suspendovani pomoci suspend2 a naslednem probuzeni prestanou fungovat ACPI events.

Jedna se o IBM/Thinkpad R52, debian etch/sid, verze jadra 2.6.16 (debiani zdroj + suspend2 patch 2.2.4).

K suspendovani pouzivam hibernate skript, relevantni pasaze jsou tyto:

### suspend2 (for Software Suspend 2)
UseSuspend2 yes
Reboot no
EnableEscape yes
DefaultConsoleLevel 1
Compressor lzf
Encryptor none

## useful for initrd usage:
SuspendDevice swap:/dev/sda2
## Powerdown method - 3 for suspend-to-RAM, 4 for ACPI S4 sleep, 5 for poweroff
PowerdownMethod 5

### clock
SaveClock restore-only

### hardware_tweaks
IbmAcpi yes

### modules
# UnloadModules snd_via82cxxx usb-ohci
# UnloadAllModules yes
UnloadBlacklistedModules yes
LoadModules auto
# LoadModulesFromFile /etc/modules

### vbetool
EnableVbetool yes

### xhacks
SwitchToTextMode yes
UseDummyXServer yes

Zkousel jsem pouzivat jak primo acpi button/sleep, button/power, tak i pres ibm-acpi ibm/hotkey, oboji funguje do te doby, nez se pouzije suspend2.

Zahadne na tom je, ze cca mesic to fungovalo (nez jsem zkusil zprovoznit ibm-acpi hotkeys, ale i pri uvedeni vsech nastaveni a skriptu do puvodniho tvaru problem zustava, reload modulu button ani celeho ibm-acpi nefunguje.

Jediny relevantni podobny pripad jsem nasel zde. "Suspend-to-disk (using swsusp) still has some issues. Suspend/Resume works, but from time to time after Resume ACPI events aren’t issued anymore." Ac jiny notebook (a jinou metodu pro suspend-to-disk), jedna se o stejny chipset a stejny problem.

Otazkou tedy je, zda se jedna o problem jadra, suspend2, nebo nejake spatne restartovane sluzby/moduly?

† + ♥ ⇒ ☼

Dotaz: nefunkcni ACPI events po suspend2 a probuzeni