durn, but that looks familar.
Since my posting, it has occured to me that perhaps that dumpstack utility is the only thing that got mis-built (and its output is meaningless).
I have also been digging around in /etc/upstart and reading the scripts.
There are quite a few debugging related things mentioned - I wish I knew which one would provide the answer.
You can enter the following command without any options and it will report on what options it accepts.
But cvm continues to hog the cpu (and the SoC still is drawing almost the max. current it can) -
Which means one of these services is broke:
Code:
[root@kindle upstart]# lipc-probe -l
com.lab126.todo
com.lab126.amazonRegistrationService
com.lab126.otav1
com.lab126.kindleStatusService
com.lab126.winmgr.ligl
com.lab126.booklet
com.lab126.powerd
com.lab126.kaf
com.lab126.winmgr
com.lab126.deviced
com.lab126.grokservice
com.amazon.ebook.util.net.certmanutilities
com.lab126.booklet.home
com.lab126.odot
com.lab126.freetime
com.lab126.transferService
com.lab126.JournalingService
com.lab126.adManager
com.lab126.LocalizationServices
com.lab126.pmond
com.lab126.DeviceAuthenticationService
com.lab126.reader.readingtimer
com.lab126.blanket
com.lab126.archive
com.lab126.system
com.lab126.certmand
com.amazon.kindle.inputMethod
com.lab126.dsus
com.lab126.indexer
com.lab126.extractor.java
com.lab126.scanner
com.lab126.transfer
com.lab126.dynconfig
com.lab126.cmd
com.lab126.todo.kaf
com.lab126.refreshCache
com.lab126.keyboard
com.lab126.readingstreams
com.lab126.IdentityService
com.lab126.stored
com.lab126.pillow
com.lab126.demoservice
com.lab126.dpm.apps
com.lab126.wifid
com.lab126.mobi8
com.lab126.lxinit
com.lab126.appmgrd
com.lab126.devicemetrics
com.lab126.phd
com.lab126.adRotationManager
com.lab126.sph
com.lab126.volumd
com.lab126.bookcacher
com.lab126.tphv3
com.lab126.instantSearch
com.lab126.coverArtService
com.lab126.ccat
com.lab126.contentpackd
com.lab126.store
com.lab126.linux.arm.connectionutilities
com.lab126.reader.languagelayer
com.lab126.household
com.lab126.dpmManager
com.lab126.KindleIdentity
com.lab126.ota
com.lab126.sharing
com.lab126.reader.qa
com.lab126.cvm
com.lab126.merchant
org.freedesktop.DBus
the Kindle is a busy little thing, even when it isn't broke.
Another example of the command:
Code:
[root@kindle upstart]# lipc-probe -v com.lab126.cvm
rw Str logMask [0x0fff0000]
rw Str logLevel [Current log level=info
(Possible transient levels: all, perf, debug[9-0], info, warn, error, crit, non)
(Possible persistent levels: p_all, p_perf, p_debug[0-9], p_info, p_warn, p_err]
And this one has possibilities for the next generation of backdoor lock:
Code:
[root@kindle upstart]# lipc-probe -v com.lab126.ota
w Str refreshCache
r Int isFirstBootAfterUpdate [0]
r Str getUpdateVersion [0]
r Int isUpdateAvailable [0]
w Int startUpdate
rw Str logLevel [Current log level=info
(Possible transient levels: all, perf, debug[9-0], info, warn, error, crit, non)
(Possible persistent levels: p_all, p_perf, p_debug[0-9], p_info, p_warn, p_err]
w Int scanUserstoreForUpdates
rw Str logMask [0x0fff0000]
r Str isUpdatePending []
rw Has transferProgressNotification [*NOT SHOWN*]
But the only way to learn about how to use these things is by reading how they are used in the existing scripts, and hope someone left in some comments.