On Wed, 15 Aug 2001, Mark Hahn wrote:
> Date: Wed, 15 Aug 2001 15:28:54 +0000 (GMT)
> From: Mark Hahn <email@example.com>
> To: dlang <firstname.lastname@example.org>
> Subject: Re: lockup problem with 2.4.5,8 athlon
> > when they lock up I cannot ping the box, the screen is blank (does not
> > reapond to alt-sysrq), keyboard numlock does not respond, the reset button
> > does not work and the power switch needs to be held down for 4 sec to shut
> if the reset button doesn't work, you have broken hardware;
> the kernel isn't involved with it.
> > method 1: over the network.
> cause lots of sync logging.
> > method2: no network.
> cause lots of writes and closes.
> > On both machines I have gone into the BIOS and set 'failsafe defaults'.
> > this helped lengthen the time between crashes (before I could sometimes
> > get the machines to crash just by letting them sit idle for several
> > hours).
> all signs so far indicate bogus hardware. what is the reported temp
> of your CPU? have you scrutinized the hardware settings, checked for
> bios upgrades, etc?
> > please tell me what I can do to assist in debugging this problem.
> if you're running 2.4.8, you've already got everything the kernel
> can do to work around known via chipset bugs. there's no known kernel
> bug that would somehow cause this.
> not responding to alt-sysrq usually means the motherboard is hung,
> which is not a kernel issue. out of curiosity, though, do you have
> in your .config? there's some mutterings that the io/local apic
> stuff might not work on athlons.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/