On Mon, Jul 10, 2006 at 10:04:57AM +0200, Dominique Dumont wrote: > Andrew Sackville-West <andrew@farwestbilliards.com> writes: > > > If transcode jobs run well, I think your CPU is ok, even though i > think 56C is quite hot (my barton XP 3200 is about 42 C now, 48C when > transcoding). huh. well, I'll look into that some more, though the temp is quite stable. i am using the stock fan/cooler which may be an issue. This machine is probably 4-5 years old and I suspect the temperature issues where not well in hand at that point. like I said, its quite stable, rising no more than a couple degrees C when under a heavy load. So, I don't think that's the problem. > > In my case, the culprit was revealed by par2 (See the end of > bug #296387 [1] ). This program always failed on big jobs (~ 10GB). Once I > removed the suspect RAM, everything worked smoothly again: > - no kernel locks or oops > - par2 ran fine. interesting. I"ve run memtest pretty extensivley with no issues, but I won't rule out the ram. I wouldn't mind putting another stick in there anyway. My problem seems to have vanished. As I said in another post, I found I had acpid running, left over from some investigating I had done some months back. I've disabled it and my problem seems to have gone away. Its been over 3 days of uptime with no issues now. we'll see, and thanks to all for their assistance. A
Attachment:
signature.asc
Description: Digital signature