View Single Post
Old 06-01-2018, 11:03 PM   #327
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
@7hir7een: It vaguely rung a bell, and, looking at the pre-FW 5.x version of USBNetwork, I indeed prevented toggling while plugged in because all kinds of weird-ass things might happen.

It's never been an issue on FW 5.x., though, but it was worth checking . I'd still recommend doing the toggle while unplugged because gremlins, but, still .

EDIT: Yeah, nothing in the full version either. It's quite possibly a side-effect of the crashes, though, since I'm seeing the mangled kernel logs replay during the reboot, but the system logs appear to even loop and/or go back in time at some points. It may also be lab126's dumping script going loopy, either in and of itself, either because of the crash, or an unfortunate log rotation.

EDITē: On the off-chance that leads to better result, you can also try, in a terminal over SSH:

Code:
showlog | ag kh_msg
Or digging into the archived logs manually:

Code:
for file in /var/local/log/messages_*.gz ; do [ -f "${file}" ] && zcat "${file}" | ag "kh_msg" ; done
That should leave you with only the bits from my stuff.

Last edited by NiLuJe; 06-01-2018 at 11:20 PM.
NiLuJe is offline   Reply With Quote