On 4/28/06, Teresa and Dale <[EMAIL PROTECTED]> wrote: > Richard Fish wrote: > > > On 4/28/06, Fernando Antunes <[EMAIL PROTECTED]> wrote: > > > >> I've already run memtest86, no problem report. > > > > > > memtest86 is nearly useless on modern computers. > > > > Try this one instead: > > http://people.redhat.com/dledford/memtest.html > > > > -Richard > > > > I ran into this with a family member recently, the CPU was running hot > and the mobo was cutting the CPU off. The only way to get it back up > again was to reboot. She kept doing this though, thinking it was > windoze, until the CPU burned out. > > If you are using Gentoo and it does this during a compile, check the CPU > heatsink for dust and make sure the fan is spinning as it should. May > also want to check those temps if you can. Most newer mobos have that. > > It could also be something else getting hot, drive, memory, one of the > chips on the mobo, northbridge comes to mind. > > Don't wait until something burns out to find out what it is. :\ > > Dale > :-) :-) > > -- > gentoo-user@gentoo.org mailing list > >
I completely agree with Dale, Pentium 4 is known for heat problems, I have to use cpufreqd and write rules to let the CPU cool down by lowering the frequency while compiling/playing. If you have thermal zone option checked with ACPI in your kernel, it would reboot at around 73C, if not, it would just go up and eventually lock up. Hard drives and memory also heat a lot, check them too. And Thomas, I have a pavilion, it runs flawless for a LONG time now, so, don't say that kinda stuff about it, my notebook have feelings, you know... -- Daniel da Veiga Computer Operator - RS - Brazil -----BEGIN GEEK CODE BLOCK----- Version: 3.1 GCM/IT/P/O d-? s:- a? C++$ UBLA++ P+ L++ E--- W+++$ N o+ K- w O M- V- PS PE Y PGP- t+ 5 X+++ R+* tv b+ DI+++ D+ G+ e h+ r+ y++ ------END GEEK CODE BLOCK------ -- gentoo-user@gentoo.org mailing list
