View Single Post
Old 01-09-2021, 11:08 AM   #13
NiLuJe
BLAM!
NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.NiLuJe ought to be getting tired of karma fortunes by now.
 
NiLuJe's Avatar
 
Posts: 13,506
Karma: 26047202
Join Date: Jun 2010
Location: Paris, France
Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E
You won't find anything outside of kernel logs for an EPDC hang. At best iff KOReader was running in verbose debug mode, you might have seen the refresh request being logged, but since it doesn't actually hang in userspace, stuff would still be moving around, making the log not so terribly helpful.

But, FWIW, the device should still be alive and reachable over SSH (either over Wi-Fi or USBNet), and if subsequent refreshes are requested, you should see them all timeout after ~5s in the kernel logs.

See this InkVT thread for an example.

----

All that said, given that it only rebooted fine *after* being plugged for a bit, I'd vote for @davidfor's theory that the battery simply just died. (It's super-tiny on the Forma).

I mean, that's a *little* bit weird with a gauge at 86%, but, the battery gauge is reliably unreliable on Kobo devices, so, who knows ;p.

Last edited by NiLuJe; 01-09-2021 at 11:40 AM.
NiLuJe is offline   Reply With Quote