Date
1 - 2 of 2
WD 3.0.4 checkins which may fix 100% CPU problems
|
Rob, After doing a 'git pull' I rebooted the TC. After immediately starting the SSH connection and running btop - wsprdaemon works normally. Upon shutting down the SSH session, then re-opening it again - the TC goes into the familiar100% cpu condition with connections to the KIWIs continually starting and then dropping every few seconds. Rebooting and immediately starting the SSH connection and running btop - and leaving it that way - wsprdaemon works normally. 73 / Rick KK6PR On Thu, Oct 6, 2022 at 9:21 AM Rob Robinett <rob@...> wrote: In the last few hours I have been checking in WD code which protects it against some error conditions I encountered at KFS which had stimulated a 100% CPU usage condition. That error state was produced on WD systems configured with MERGed receivers when there was a failure to communicate with one or more of the real receivers in a MERGed group. |
|
|
|
Rob Robinett
In the last few hours I have been checking in WD code which protects it against some error conditions I encountered at KFS which had stimulated a 100% CPU usage condition. That error state was produced on WD systems configured with MERGed receivers when there was a failure to communicate with one or more of the real receivers in a MERGed group.
I'm not sure this fixes the 100% CPU problems reported by Rick KK6PR and Holgar OE9GHV, but there was a significant unhandled error condition in the posting daemon of WD which has now been corrected. I will be making a few additional changes to WD 3.0.4 to correct the 0.1 Hz spot frequency error and to enhance FST4W spots to 0.1 Hz frequency resolution and 0.1 dB SNR resolution. Those are the last significant changes on the 3.0.4 TODO list. As always, you can get the latest code with a 'git pull' |
|
|