Quote:
Originally Posted by Lucas Malor
Please, try. Do a stupid script that append to a file the current date every X seconds, put Kobo in sleep mode, resume it after a while and see in the file if there's a gap in data. If so, you have to use /etc/pm/sleep.d, if the dir exists.
|
That happens to look something like this:
Code:
02/01/11-12:22:29 INFO Kobo WiFi: disabling WiFi
02/01/11-12:22:45 INFO Kobo suspend: going to sleep . . .
02/01/11-12:22:45 INFO Kobo suspend: asked the kernel to put subsystems to sleep, ret: true
02/01/11-12:22:47 INFO Kobo suspend: waited for 2s because of reasons...
02/01/11-12:22:47 INFO Kobo suspend: synced FS
02/01/11-12:22:47 INFO Kobo suspend: asking for a suspend to RAM . . .
02/01/11-12:22:47 INFO Kobo suspend: ZzZ ZzZ ZzZ? Write syscall returned: true
02/01/11-12:26:54 INFO Kobo suspend: woke up!
02/01/11-12:27:09 ERROR Kobo suspend: putting device back to sleep, unexpected wakeups: 1
02/01/11-12:27:09 INFO Kobo suspend: going to sleep . . .
02/01/11-12:27:09 INFO Kobo suspend: asked the kernel to put subsystems to sleep, ret: true
02/01/11-12:27:11 INFO Kobo suspend: waited for 2s because of reasons...
02/01/11-12:27:11 INFO Kobo suspend: synced FS
02/01/11-12:27:11 INFO Kobo suspend: asking for a suspend to RAM . . .
02/01/11-12:27:11 INFO Kobo suspend: ZzZ ZzZ ZzZ? Write syscall returned: true
02/01/11-12:29:36 INFO Kobo suspend: woke up!
02/01/11-12:29:36 INFO Kobo resume: clean up after wakeup
02/01/11-12:29:36 INFO Kobo resume: unflagged kernel subsystems for resume, ret: true
The "unexpected wakeup" is the RTC_WKALM_SET I purposefully scheduled before suspending.