Per Jessen wrote:
John Andersen wrote:
Also, switch to Console 10 and just watch it while your machine is working hard. You might see some messages come shooting thru when something triggers a protective shutdown.
I've had a serial console hooked up all the time to see if I could catch anything kernel-related - nothing. If only it was a kernel-issue, then I'd have _something_.
You can make some settings to eliminate overly protective shutdown sequences, some in KDE, and some in BIOS.
I've got the CUP-temp warning set at 70C. No other limits that I can see anywhere. The Phenom manual does talk about a TEMPTRIP setting which would make the machine go straight into some down state, from which only a hard reset would bring it out. Doesn't sound like my situation though.
I believe that's a thermal-hibernation state. Intel introduced this with the last 32-bit processors, and AMD introduced it in the later models of the 32-bit Athlon line. The important thing to remember in this scenario is that the machine is NOT crashed...it has merely throttling CPU operation (to 0 Hz) until it's cool enough to resume processing. No registers are lost. As you can imagine, this sort of thing has a very negative impact on time-keeping, but at least the machine isn't crashed.
(Oh, check the manufacturer to see if there is later bios available).
Yep, already spoke to Gigabyte and got their latest beta-BIOS.
What was the procedure on that? I just bought a new Gigabyte board (AM2+ socket so I can use an Athlon-64 dual core now, and put in a Phemon quad core later), and anticipate that any BIOS upgrade could be difficult. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org