View Single Post
Old 10-27-2017, 08:40 AM   #23
NullNix
Guru
NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.NullNix ought to be getting tired of karma fortunes by now.
 
Posts: 929
Karma: 15576314
Join Date: Jan 2013
Location: Ely, Cambridgeshire, UK
Device: Kindle Oasis 3, Kindle Oasis 1
Quote:
Originally Posted by AlanHK View Post
You seem to assume that the error is in the flash memory. How do you know that?
Quite. I had a problem with near-identical symptoms on my PW1 for many years: sometimes the light would not go off when you turned it off, and would then never turn off until you rebooted: sometimes the inverse problem occurred, with the light not turning on.

This obviously (to my mind) had nothing whatsoever to do with bad eMMC -- among other things, it happened for the first time the week I bought it, and flash doesn't wear out that fast. It was fairly clearly a counting-semaphore problem: perhaps "screen on" is denoted by a semaphore >=1 in a signed integer range, and there was, somewhere in the code, a screen off/screen on imbalance so that it ended up oscillating around 1/2 or something. Rebooting obviously fixes dynamic state problems like that.

To me this looks like exactly the same class of bug: purely software. I see no reason to assume anything relating to hardware here.
NullNix is offline   Reply With Quote