[bigwoof]

Originally Posted by NiLuJe

ssh/telnet slowing down to a crawl while you're saturating the Wi-Fi with... Wi-Fi transfers makes perfect sense, FWIW.

Hi, I thought of this as well but no books are being transferred. it's possible metadata is so maybe. but the feel (on my side) seems like intense memory pressure causing the slugginess. that would explain why htop refuses to even start.

Originally Posted by NiLuJe

It'd also be consistent with a system going OOM, which makes this a bit tricky to diagnose...

yeah, I've tried replicating this so many times now and can't get it to crash while I'm monitoring the syslog. it's quite a fun puzzle.

ku crashes in so many different ways (inluding one where the Kobo printed out in big lettering KOBO DISCONNECTED on the ku "before connecting to calibre mostly blank page) and then the ku "disconnected" message appeared.

Originally Posted by NiLuJe

Enter USBNet! That way you'd get rid of the "is it Wi-Fi?" factor .

I'll try this but it really does not feel like the WiFi is being saturated at all..

Originally Posted by NiLuJe

EDIT: Re-reading the message, a reboot would imply either nickel hangs because the system is OOM, tries to swap, but can't because there's no swap, and that makes nickel so slow that it trips sickel's watchdog and forces a reboot. (Or nickel gets OOM-killed, sickel detects that, and reboots).

So what does the kernel say, exactly? Running klogd first means you get a timestamped kernel log in your syslog: an OOM-kill would be visible there.

There is nothing interesting in the syslog except for WiFi messages.. every now and then the kernel heat watchdog goes off. nothing interesting as far as I can tell. nothing that says that memory pressure is reaching dangerous levels. will keep trying

Originally Posted by NiLuJe

EDIT²: It's 4AM, so I'm a bit slow ;p. Is nickel still alive and responsive and how's the RAM usage when you happen to check the syslog and stuff just breaks at the first book?

4 a.m???? oof!! yeah, nickel is alive after ku dies. once it rebooted in nickel by itself and I had syslog running. but there was *nothing* in the syslog to say why it rebooted. just normal messages and ku was not running.. so a very wierd system instability reboot..

in htop when I start it with -s PERCENT_KERNEL, it appears that ku has a VIRT of ~830+M and a RES of ~200M but in all these cases, ku just disconnects before the first file was sent in calibre. these are not the case (that I first found) where files are being transferred, the memory usage explodes, htop and other operations crawl or just don't start, and kobo reboots.

also, the same memory and cpu usage was also shown for the nickel process as well btw. which makes sense as ku is spawned by nickel right?

and yeah, the libra has just 512M of which htop says ~480M is available