On Thu, Feb 03, 2005 at 08:55:08PM -0800, DJA wrote: > [EMAIL PROTECTED] wrote: > > > >The CPU fan was replaced, correcting the angry buzzing sound. > >The old fan seems to spin more easily in one direction than > >the other when I blow air into it. I suspect the bearing is > >bad, but not letting the blades bump the casing. > >I don't know if the oops message will recur without a bad fan, > >but even if it doesn't recur I'm guessing there is some > >incompatibility. Hints on investigating the incompatibility > >might be helpful; a first lock at Google wasn't very > >helpful. Thanks very much. > > > >Stewart Strait > > If a fan's blade(s) hit(s) the fan casing, then the fan will stop[1], at > least momentarily. Does the fan ever stop completely (pause) when it > makes the loudest noises - those noises which lead you to surmise blades > contacting case? > > Failing fan -> increased heat -> higher resistance -> lower power > efficiency + faster break-down of components. Yes, a failing fan could > ultimately cause oops messages. Don't believe me? Try unplugging the fan > from an Athlon or P4 for a while and wait for the fun. Trust me, it > won't be a long wait.
Let me add a note of caution from personal experience. I used to think that a cooked CPU was all or nothing -- if it booted, you could trust it. Not so, I have learned. I had an AMD K7 (Duron?) that booted but was the cause of kernel panics and other hilarity, seemingly at random. My point being, if you have reason to believe that a (modern, delicate) CPU has run at too-high temps for any time at all, be afraid -- be very afraid. I would not rule out the appearance of failing HDs and other HW being a bad CPU instead. The Allens may correct this, which I would defer to gracefully. -- Lan Barnes [EMAIL PROTECTED] Linux Guy, SCM Specialist 858-354-0616 -- KPLUG-List mailing list [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
