On Sunday 10 September 2006 16:26, Mikus Grinbergs wrote:
Running SuSE 10.1 64-bit on an opteron system which is mostly unattended. Happened to notice that 'zmd' was running, and taking up a significant CPU percentage. I had done *nothing* to explicitly start zmd. I might have been using YaST2 at the time in question (don't remember clearly) - but I think not.
My reason for posting is that an idle priority program, heavily floating-point intensive, reported a computational glitch (from which it was able to recover) just about the time 'zmd' started. I'm posting this to alert the SuSE developers to check that 'zmd' is not happening to affect the hardware involved with floating point.
I find this extremely hard to believe. zmd doesn't use any particular kernel drivers, so it shouldn't have any influence on any hardware at all
I think it suspicious that as 'zmd' started using up CPU cycles, that seemed to coincide with a computational glitch in another program on my system. [I have seen no other glitches with that program, before or since.]
As John said, what is a 'glitch'? I guess if your system was running at 110% with both your program and zmd going at it, it could be exposing some problem with the hardware. Perhaps it was on the virge of overheating? Perhaps there is a problem with a memory cell that you happened to expose?