Ticket #930 (closed defect: fixed)
suspend/resume broken in SHR-testing
| Reported by: | texoft2 | Owned by: | daniel |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | Frameworkd / FSO | Version: | SHR-testing |
| Keywords: | Cc: |
Description
After last upgrade I got this error in /var/log/fsousaged.log:
UsageController [WARNING] <0 resources>: Can't find plugin for lowlevel_type = 'openmoko'; suspend/resume will NOT be available!
Suspending quits immediately.
Change History
comment:1 follow-up: ↓ 2 Changed 2 years ago by texoft2
- Status changed from new to closed
- Resolution set to fixed
comment:2 in reply to: ↑ 1 Changed 2 years ago by nahumba
- Status changed from closed to reopened
- Resolution fixed deleted
Replying to texoft2:
After about a day of searching I found solution (modify /etc/frameworkd.conf):
#fsousage.lowlevel_openmoko needs to appear before fsousage.dbus_service [fsousage.lowlevel_openmoko] [fsousage.dbus_service]for some reason this is not done in distribution's default frameworkd.conf.
tried this , didn't work.
the auto suspend is on even after changing in the
settings -> power-> suspend | "off".
log:
root@om-gta02 /etc $ cat /var/log/fsousaged.log
2000-01-01T08:18:10.562784Z fsousaged [INFO] : fsousaged starting up...
2000-01-01T08:18:11.135390Z LowLevelOpenmoko? [INFO] <>: Registering openmoko low level suspend/resume handling
2000-01-01T08:18:11.136744Z UsageController? [INFO] <0 resources>: Ready. Using lowlevel plugin 'openmoko' to handle suspend/resume
2000-01-01T08:18:11.137382Z fsousaged [INFO] : loaded 2 plugins
2000-01-01T08:18:11.137793Z fsousaged [INFO] : fsousaged => mainloop
2000-01-01T08:19:12.042888Z UsageController? [INFO] <8 resources>: >>>>>>> KERNEL SUSPEND
2000-01-01T08:25:39.964199Z UsageController? [INFO] <8 resources>: <<<<<<< KERNEL RESUME
2000-01-01T08:25:39.967903Z UsageController? [INFO] <8 resources>: Resume reason seems to be FSO_USAGE_RESUME_REASON_GSM
2000-01-01T08:25:40.003020Z UsageController? [ERROR] <8 resources>: Resource GSM can't be enabled: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.. Trying to disable instead
comment:3 Changed 2 years ago by texoft2
nahumba your issue is different and you should create separate ticket for it. This:
2000-01-01T08:18:11.136744Z UsageController? [INFO] <0 resources>: Ready. Using lowlevel plugin 'openmoko' to handle suspend/resume
indicates, that the lowlevel suspend plugin is loaded and other logs imply that it suspends your freerunner.
The issue in this ticket is, that the lowlevel plugin won't load and therefore freerunner won't even try to suspend.

After about a day of searching I found solution (modify /etc/frameworkd.conf):
for some reason this is not done in distribution's default frameworkd.conf.