PW4 w/jailbreak: restart takes 3 minutes

[knc1]

Originally Posted by NiLuJe

@makue: I'd first take a look at a *full* log dumped via showlog and not ;dm, because Amazon's logging facilities sometime do funny things when coalescing logs...

(i.e., here, I'm only seeing the replay of dmesg's backlog done once the system logger boots up, which doesn't tell us much about when exactly it hung, besides "before syslog-ng appeared to have been brought up").

Could we automate that?


Consider; the first (the only) program the kernel runs after it finishes start-up is "init".
Perhaps jam a "dmesg" and/or "showlog" call very early into the list of things "init" starts?


If such a modification never gets called, then we know the system crashed before reaching "init".


The root fs is mounted when "init" is started ...
But if we are having file system errors, then writing our extra log output could be a "bad idea" ...
But if we set-up a ram disk to write (or re-direct) our special logging too...
Also, if required, we could net-cat it off of the machine somewhat later.




Whatever, it is going to be hard to debug.
(Note: I think debugfs is mounted, but I am not sure when in the process it gets mounted. Early, with /proc and /sys ??)

[makue]

Waiting for the replacement kindle I've made some final experiments.

First I've deleted all content from the documents folder, that might/should have stopped the indexer but the restart times kept the same.

Then I've made a "reset" and even that made no change to the reboot time.

Finally I'v reinstalled all the "hacks" and books and even then no change. Ok this was more than expectable. So, yes this device is really broken.

The only thing that puzzles me is that the support was so motivated to declare to me that a restart time up to several hours is very normal and no indication of any problems. Finally he offered me a another kindle as replacement but they were never so reluctant to do so in the past. Maybe a problem related to Germany but it was too observable to me.

[NiLuJe]

Kindles *do* take a shitload of time to boot up, so, who knows, they might have been reluctant to believe your timing .

[makue]

Yeah, right u are. Just checked my older kindles and they dare to take just up to 90 seconds to restart. This is simply unacceptable how can I expect a decent boot in such a hurry. Guess they are also broken and need to be returned.

[NiLuJe]

Inconceivable!

[knc1]

Originally Posted by makue

Yeah, right u are. Just checked my older kindles and they dare to take just up to 90 seconds to restart. This is simply unacceptable how can I expect a decent boot in such a hurry. Guess they are also broken and need to be returned.

For a Kindle, a restart is a very rare event, so its timing is insignificant.

They are designed to suspend / resume, not stop and restart.

[makue]

The replacement Kindle PW4 has arrived. Fortunately it's been sent with firmware 5.10.0.2. After applying the jailbreak and installing all the needfull gems from NiLuJe it is as good as new

A final question, before I send the other broken device back, is a reset sufficient to clean it up or is more to be done?

[knc1]

Originally Posted by makue

The replacement Kindle PW4 has arrived. Fortunately it's been sent with firmware 5.10.0.2. After applying the jailbreak and installing all the needfull gems from NiLuJe it is as good as new

A final question, before I send the other broken device back, is a reset sufficient to clean it up or is more to be done?

Reset + Install an Amazon image file.
Specifically in that order without anything else in-between.