MobileRead Forums - View Single Post - Kindle 3.1 software for Kindle 2, 2i, & DX (under construction)

pmul · 10-14-2012, 05:58 PM

Damn it.

I should learn how to read log files properly. 'cmd' is the process that crashes, 'pmond' (process monitor daemon) catches this and restarts 'cmd'. This is most of the delay.
The 'orientationFaceUp' was a red herring.
BTW the state of the accelerometer is stored in '/proc/accelerometer' in plain text.
Anyway, this:

Code:

121005:181147 cvm[3427]: E lipc:dbuserr:name=org.freedesktop.DBus.Error.NoReply:Receive Dbus error message (DBUS_MESSAGE_TYPE_ERROR): Message did not receive a reply (timeout by message bus)
121005:181152 pmond[2060]: I def:exit:proc=cmd, exitcode=139:cmd (19772) exited
121005:181152 pmond[2060]: I def:rst:proc=cmd:Restarting cmd
121005:181152 cmd[20111]: I def:starting::Starting Connection Manager

is where the story really starts. After the dbus error, in cvm (java) pmond restarts cmd, which then does lots of stuff, including starting the "Connection Manager" (another red herring, I think I'll open a fish shop....)

Now, is the dbus error timeout a cause or a symptom?
And why:

Does it wake up rapidly if it hasn't been asleep for too long (<80 seconds or so)?
Does it wake up rapidly if I ssh into it before operating the power slider?

10-14-2012, 05:58 PM	#572
pmul Enthusiast Posts: 36 Karma: 11764 Join Date: Jul 2009 Device: K-1, K-2-3G, K-3-3G, K4PC, K4iPhone, K4iPad, K-Touch-Wifi, K-Fire, DXG	Damn it. I should learn how to read log files properly. 'cmd' is the process that crashes, 'pmond' (process monitor daemon) catches this and restarts 'cmd'. This is most of the delay. The 'orientationFaceUp' was a red herring. BTW the state of the accelerometer is stored in '/proc/accelerometer' in plain text. Anyway, this: Code: 121005:181147 cvm[3427]: E lipc:dbuserr:name=org.freedesktop.DBus.Error.NoReply:Receive Dbus error message (DBUS_MESSAGE_TYPE_ERROR): Message did not receive a reply (timeout by message bus) 121005:181152 pmond[2060]: I def:exit:proc=cmd, exitcode=139:cmd (19772) exited 121005:181152 pmond[2060]: I def:rst:proc=cmd:Restarting cmd 121005:181152 cmd[20111]: I def:starting::Starting Connection Manager is where the story really starts. After the dbus error, in cvm (java) pmond restarts cmd, which then does lots of stuff, including starting the "Connection Manager" (another red herring, I think I'll open a fish shop....) Now, is the dbus error timeout a cause or a symptom? And why: Does it wake up rapidly if it hasn't been asleep for too long (<80 seconds or so)? Does it wake up rapidly if I ssh into it before operating the power slider?