From: "Gnea" <gnea@rochester.rr.com>
To: Buddha Buck <bmbuck@14850.com>, linux-kernel@vger.kernel.org
Subject: Re: HOW-DO-I: Diagnosing hardware problems
Date: 02 Dec 2000 11:34:15 EST [thread overview]
Message-ID: <20001202162932.AAA12198@mail2.nyroc.rr.com@celery> (raw)
In-Reply-To: <5.0.0.25.0.20001130095146.00c3aae0@armstrong.cse.buffalo.edu>
In-Reply-To: <5.0.0.25.0.20001130095146.00c3aae0@armstrong.cse.buffalo.edu>
On Thu, 30 Nov 2000 10:12:34 -0500, Buddha Buck blurted forth:
> Hi,
[snip]
> When this first started (under 2.4.0pre10), I was getting oopses, showing
> the system was dying in wake_up, while trying to schedule during an
> interrupt (I think that's what the oops said). Some oopses would be
> logged, and not kill the system, others would kill the system, and not be
> logged. When I downgraded to 2.2.17+ide, I stopped getting oopses, and the
> lockups stopped, for a while. Now the system (under both 2.2.18 and
> 2.4.0pre11) lockups but doesn't oops, not even to the console.
[snip]
sounds like a bad CPU fan, take the cover off of the computer and start
it up, observe how fast the fan on the CPU is running. if it's not
running at all, that's your problem. turn the computer off and do not
start it again until you've replaced it, you can seriously burn stuff
out if it continues to run like that. also, is there a lot of clutter
in the case? wires everywhere? u may want to consider getting some
twist-ties or rubber bands or whatever and using them to clean up the
mess to allow proper ventilation of the system and get heat out of
there... this sounds like the most logical problem/solution to me, but
of course i could be wrong.. give this a go and see what happens.
--
.oO gnea at rochester dot rr dot com Oo.
.oO url: http://garson.org/~gnea Oo.
"You can tune a filesystem, but you can't tuna fish" -unknown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-02 17:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-30 15:12 HOW-DO-I: Diagnosing hardware problems Buddha Buck
2000-12-02 16:34 ` Gnea [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20001202162932.AAA12198@mail2.nyroc.rr.com@celery \
--to=gnea@rochester.rr.com \
--cc=bmbuck@14850.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox