Hi Frank, In this case, processor utilization is probably less of a concern than memory in terms of overall performance. The RIP2 is short to begin with for "normal" desktop activities. I believe the Pi2 B/(x) models came with ~1GB; even less on older versions. While you are watching HTOP, keep an eye on mem-usage, and when/how-much. You can set the sort order by memory or any number of filters using HTOP.
73's Greg, KI7MT -----Original Message----- From: FRANK DB5FP [mailto:db...@gmx.de] Sent: Tuesday, March 20, 2018 2:25 PM To: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] Monitoring stops suddenly in 1.80 and 1.90 RC2 Hi Joe, sorry first e-Mail did not pass my filter, so it went to spam...and I send a new one. At first, green Monitor light does NOT go out. Everything looks fine. But waterfall stops and no more messages are decoded. Sometimes it is possible to recover the program by pressing the Monitor buton twice. I tried 1.80 and 1.90 rc2only one instance. Both version have the same issue. I'm running FT8 on different bands and report the messages to pskreporter. I tried to get some more information by inspecting the processes with "htop" . It looks like the JT9 process is running but it's more or less idling 2.4% of CPU usage. During decode it's about 100% (1 core). During normal idle it's about 11%. If I shut down the JT9 process by kill-command and afterwards killing rest of the application, I can restart the application. By ending the program with ALT-F4 oder File-Exit I can not restart because of zombie processes on the message accrues that there would be a lock file. dmesg and /var/log/mesages don't show any problems. The problem is independent of any other program running beside wsjtx. But normally I use gpredict in the same time. Is there any error-loging possibility in wsjtx ? 73 Frank DB5FP > Hi Frank, > > On 3/17/2018 6:36 AM, FRANK DB5FP wrote: > > on my Raspberry Pi2 Monitoring Mode stopps suddenly. > > OS Version : Debian > > Kernel Linux version 4.14.18-v7+ > > > > Suddenly the Waterfall display stops and no messages are decoded BUT > > progressbar is still running. > > Rig controll ist still working. > > > > Any hints? > > You have reported this problem twice now. It might help to know what > WSJT-X (or possibly some other program running in your RasPi2 ??) is > doing when the green Monitor light goes out. What mode are you > running? What other processes are taking CPU time? > > Your system is, of course, in the "bare minimum" category for running > WSJT-X. Have you communicated with others who run WSJT-X on a > Raspberry Pi2 ? > > -- 73, Joe, K1JT > > ---------------------------------------------------------------------- > -------- Check out the vibrant tech community on one of the world's > most engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel ---------------------------------------------------------------------------- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
