Andrew Sackville-West <[EMAIL PROTECTED]> writes: > yeah, another good idea. unfortunately, that's a no go either. I'm > running at a pretty steady 132 F/ 56 C right now with it climbing to > about 140F, but no more when I'm pushing it. Also, it seems more > common when I'm NOT working. Also, doesn't crop up when I leave some > crunching job running overnight (like a big transcode job or something). > > I ran memtest all night with no problems at all. Also ran stesscpu for > a while with no probs. I'm beginning to think, as i crawl through my > memory, that it might be related to some acpi stuff I was fooling > with. we'll see.
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). 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. HTH [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=296387 -- Dominique Dumont "Delivering successful solutions requires giving people what they need, not what they want." Kurt Bittner -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
