From: kernel <kernel@crazytrain.com>
To: Giuseppe Bilotta <bilotta78@hotpop.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dell Inspiron sensors (was: Re: Huge unreliability - does Linux have something to do with it?)
Date: Sun, 06 Feb 2005 11:58:37 -0500 [thread overview]
Message-ID: <1107709117.3828.6.camel@crazytrain> (raw)
In-Reply-To: <MPG.1c7035d63901d496989710@news.gmane.org>
On Sun, 2005-02-06 at 10:58, Giuseppe Bilotta wrote:
> I have a Dell Inspiron 8200, from March 2002. Since end of
> December 2004 I've started having system lockups which at first
> I couldn't identify, although they seemed to be overheating
> related. So I started monitoring the temperatures on all the
> components in my system (I can monitor CPU, GPU and HD temp;
> more on this later), and noticed that the lockups happen when
> the HD temp gets around 40 C. Indeed, they are 99% of the time
> preceded by a loud "click" coming from the HD wereabouts ...
> haven't lost any data yet but I've started backing up
> everything and getting ready to get a replacement HD.
You might want to try this;
Remove the keyboard, remove the cover beneath. Take a can of air dust
(or equivalent) and *carefully* blow out the inside of the laptop.
-then-
Look at the back side and the right side of the laptop. You'll see the
intake for air and the A/C unit. Take that air dust and blow in such
that the plastic fan whirls away. Take a snapshot of the dust bunnies
and send them to Dell.
I have a 5150 Inspiron. In less than 1 year this thing started powering
off (hard) on its own, no matter the OS installed (multi-boot). I dug
around the 'net and found similar issues, all relating to OVERHEATING.
Poorly designed was the culprit, but Dell has not yet admitted to this
(but look at the Dell Linux forum or just Dell laptop forum and see
Dell's techs replies) - think of the numbers sold and it makes sense.
Anyways, aside from that, I had a dust bunny the size of a U.S. quarter
fly out. Since then I make certain to rest it on a flat surface (I cut
some steel and carry it with me) and every couple of months take it
apart as described and blow out the dust.
-fd
next prev parent reply other threads:[~2005-02-06 17:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 9:03 Huge unreliability - does Linux have something to do with it? jerome lacoste
2005-02-04 9:20 ` Julien Banchet
2005-02-04 10:31 ` Jim Nelson
2005-02-04 10:45 ` Bernd Eckenfels
2005-02-04 11:28 ` jerome lacoste
2005-02-04 17:13 ` Horst von Brand
2005-02-04 11:27 ` Andre Tomt
2005-02-04 11:51 ` DervishD
2005-02-04 12:18 ` Wakko Warner
2005-02-04 14:44 ` Dmitry Torokhov
2005-02-06 15:58 ` Dell Inspiron sensors (was: Re: Huge unreliability - does Linux have something to do with it?) Giuseppe Bilotta
2005-02-06 16:58 ` kernel [this message]
2005-02-06 21:58 ` Giuseppe Bilotta
2005-02-05 10:38 ` Huge unreliability - does Linux have something to do with it? jerome lacoste
2005-02-05 12:27 ` Willy Tarreau
2005-02-05 15:11 ` Wakko Warner
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=1107709117.3828.6.camel@crazytrain \
--to=kernel@crazytrain.com \
--cc=bilotta78@hotpop.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;
as well as URLs for NNTP newsgroup(s).