Maybe, maybe not . . . .
There is a definite pattern here:
Code:
[root@kindle root]# dmesg
[ 101.048759] KERNEL: I pmic: PWRON1 event:
[ 101.246992] cyttsp: I cyttsp_proc_write::command=unlock:
[ 164.429048] cyttsp: I cyttsp_proc_write::command=lock:
[ 69.146976] KERNEL: I aplite_charger: Restart charging:
[ 345.405187] KERNEL: I aplite_charger: Battery full Stop charging:
[ 184.179650] KERNEL: I aplite_charger: Restart charging:
[ 460.437894] KERNEL: I aplite_charger: Battery full Stop charging:
[ 269.212394] KERNEL: I aplite_charger: Restart charging:
[ 8.599683] KERNEL: I aplite_charger: Battery full Stop charging:
[ 354.245148] KERNEL: I aplite_charger: Restart charging:
[ 63.632433] KERNEL: I aplite_charger: Battery full Stop charging:
[ 439.277848] KERNEL: I aplite_charger: Restart charging:
[ 148.665061] KERNEL: I aplite_charger: Battery full Stop charging:
[ 524.350571] KERNEL: I aplite_charger: Restart charging:
[ 233.737835] KERNEL: I aplite_charger: Battery full Stop charging:
[ 42.512368] KERNEL: I aplite_charger: Restart charging:
[ 318.770530] KERNEL: I aplite_charger: Battery full Stop charging:
[ 127.545076] KERNEL: I aplite_charger: Restart charging:
[ 245.636135] aplite_charger: I pmic:faulti:sense_0=0x200:battery dies/charger times out.
[ 339.794269] PM: Syncing filesystems ... done.
[ 339.862853] Freezing user space processes ... (elapsed 0.00 seconds) done.
[ 339.866307] Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
[ 339.867194] Suspending console(s) (use no_console_suspend to debug)
[ 339.868346] cyttsp_suspend: Enter
[ 339.888562] WiFi chip powered down
[ 339.889415] PM: suspend of devices complete after 21.077 msecs
[ 339.889478] kernel: I PM:suspend:duration=21.077:
[ 339.890472] PM: late suspend of devices complete after 0.925 msecs
[ 339.890530] kernel: I PM:latesuspend:duration=0.925:
[ 339.935129] PM: early resume of devices complete after 0.270 msecs
[ 339.935206] kernel: I PM:earlyresume:duration=0.270:
[ 339.988619] WiFi chip powered on
[ 340.123421] mmc0: queuing CIS tuple 0x01 length 3
[ 340.130823] mmc0: queuing CIS tuple 0x1a length 5
[ 340.134048] mmc0: queuing CIS tuple 0x1b length 8
[ 340.134704] mmc0: queuing CIS tuple 0x14 length 0
[ 340.296101] PM: resume of devices complete after 360.528 msecs
[ 340.296117] kernel: I PM:resume:duration=360.528:
[ 340.296276] Restarting tasks ... done.
[ 340.701503] g_ether gadget: high speed config #1: CDC Ethernet (ECM)
[ 342.290615] Battery: Resume - TimeSuspended(secs)=41841, NAC=0x1d3c, RSOC=96, capacity=96%
[ 342.369272] Battery: Resume - PostUpdate NAC=0x1d08, RSOC=96
It looks like the kernel's internally generated messages have proper time stamps.
The messages sent into the kernel's buffer by the lab126 scripting certainly looks like it has problems. Almost as if they where using random numbers for the time stamps.
Groan -
I may have to set this little "corruption detection" project aside until I have enough time to read through whatever it is lab126 is doing with its message logging.