And if it's heat or bad memory, why have no problems shown up in the two days (of 110%!) since what I described. [Though I did halt 'zmd' after it had been wasting CPU cycles for 24+ hours, before I noticed that it was running. (I could tell from the drop in logged output by the idle priority program, which went back to full output once I halted zmd.) ] I can sure believe the correlation. Since I am running a desktop at home, I power off every night. I have uninstalled zmd, rug, and zen-updater (just now again) probably 10 times since I installed 10.1. It by itself will almost double the temp of my cpu (AMD64-3200) when it runs. I keep trying it every few weeks to see if it has improved, but do not like watching my cpu stressed at every boot for so long. I have reduced my installation sources to the dvd, inst-source and non-oss-inst-source, and update, but still it hammers the cpu for a significant amount of time every boot. For my needs, I can just run smart every few days to get the updates and save the wear and tear on
Mikus Grinbergs wrote: the cpu. Anyway, I have ksensors running in the tray with the cpu temp shown, and have seen the effects of zmd, and would guess it indeed may have overheated your cpu or at least pushed it to its limits. Interesting to me, the latest versions seemed quite a bit better as measured by top, but with the various processes (i.e. gpg, update-status, etc.) switching and not maxing out the cpu at all, the cpu temp still climbs to "reportedly" 66 C. HTH. -- Joe Morris Registered Linux user 231871