Thread: [KUALette] Hardware Report
View Single Post
Old 08-06-2013, 01:40 PM   #8
knc1
Going Viral
knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.knc1 ought to be getting tired of karma fortunes by now.
 
knc1's Avatar
 
Posts: 17,212
Karma: 18210809
Join Date: Feb 2012
Location: Central Texas
Device: No K1, PW2, KV, KOA
Quote:
Originally Posted by knc1 View Post
This seems to be occurring more often than it should.

Well, in point of fact, it should **never** happen but in the Kindle kernels it is a known problem (according to lab126's own comments in the log writer functions).

Today's challenge -
Script a corruption detector for this hardware reporter.

This problem was fixed back in the days of the version 2.5.x kernel, but it seems to have gotten "un-fixed" in the Amazon kernel build.
Sorry folks, that isn't going to happen.

The date/time stamps on kernel events have been turned off in 5.3.3 and 5.3.4 (at least, maybe others).
knc1 is offline   Reply With Quote