I'll second this email...
My computer had been stable all winter (with setiathome runnning full
time) but suddenly come the Australian summer it started freezing.
Not panicing, just totally freezing under load.
I could reproduce it by trying to build the whole of KDE and each time
it was a freeze, never a panic.
Windows 98 was freezing too but I didn't think that was abormal ;/
It turned out to be heat related as the machine is now stable after I
installed a case fan (before I only had the power supply fan and CPU
fan).
I see that the internal case temperature still gets up to about 50 or 51
degrees celcius whereas it was getting to 52 degrees before.
Note that I AM overclocking a Celeron 300a to 450 MHz by running with
a 100 MHz FSB instead of 66 MHz so I suppose I shouldn't be surprised at
the need for better cooling.
As I'd prefer better CPU cooling to the case fan on the grounds of noise,
can people recommend good CPU fans (over the standard Intel retail version
Celeron 300a fan) ? How about these Peltier (sp ?) cooling devices I have
heard about ?
On Sun, 5 Mar 2000, Dan Papasian wrote:
> 1. Is your computer overclocked?
>
> 2. Is the computer totally frozen? (i.e. scroll lock doesn't turn the light on)
>
> 3. Does similar load crash the box as well? (try make -j2 world)
>
> 4. Does it freeze in the same spot?
>
> 5. Is the computer not responding to pings?
>
> If you've answered yes to a good amount of these questions, there is a good
> chance that your processor(s) are overheating. Try improving the airflow to the
> case (But using a household fan isn't recommended due to EMI)
>
> -Dan Papasian
> <[EMAIL PROTECTED]>
>
> On Sat, Mar 04, 2000 at 11:50:10PM -0800, Arun Sharma wrote:
> > Compiling Mozilla with make -j 2 got -current to lock up, twice in
> > succession. I'm running a fairly recent snapshot (a week or two old)
> > on a Dual celeron box (BP6) with UDMA66 enabled.
> >
> > The kernel had DDB enabled. I was running X, but I didn't see any
> > signs of the kernel attempting to get into the debugger.
> >
> > Has this been fixed ? Is anyone interested in investigating ?
> > I'll post more info if I find anything.
> >
> > -Arun
> >
> >
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
>
>
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
