mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Alan" <alan@clueserver.org>
To: "Pavel Machek" <pavel@ucw.cz>
Cc: "Len Brown" <lenb@kernel.org>,
	"Gabriel C" <nix.or.die@googlemail.com>,
	"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
	linux-pm@lists.linux-foundation.org,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Re: Some sort corruption of my Thermal Subsystem after suspend to  ram
Date: Thu, 1 May 2008 09:30:50 -0700 (PDT)	[thread overview]
Message-ID: <33216.75.164.221.130.1209659450.squirrel@clueserver.org> (raw)
In-Reply-To: <20080501160946.GA26089@elf.ucw.cz>

> Hi!
>
>> The ICH9 apparently provides a pair of memory mapped on-die thermal
>> sensors.
>>
>> The sensors basically shut off your hardware if it gets too hot.
>
> Are the sensors driven by ACPI? Probably yes, otherwise they would be
> unable to shut down the system.
>
>> ICH9 exports the base address for the sensors via a PCI device --
>> D31:F6, aka Linux 00:1f.6
>>
>> I'm not aware of a native Linux device driver that talks to this device
>> (nor can I think of a useful purpose for such a driver)
>> So it seems what is in play here is any BIOS code that talks to this
>> device,
>> and Linux's standard PCI config space restore.
>>
>> My guess is that the BIOS is enabling the device on cold boot,
>> but not enabling it after resume from S3.
>
> That sounds like a BIOS problem, right? If the piece of hardware is
> driven by BIOS, Linux can't be responsible for saving/restoring it.

I was having a similar problem on my old laptop. It seemed a lot more
sensitive to the problem on later kernels.

What was actually happening is that the last time the laptop went in for
repairs they did not seat the heat sink correctly.  It slowly worked
itself loose.  After regreasing it with heat sink grease (not a heat sink
pad, but actual silver grease) and reseating it and tightening it down,
the machine worked fine.  (I also found some nasty tool marks in the soft
metal next to the heat sink that shows that whoever did it slipped at
least once.)

Sometimes hardware problems increase slowly.


      reply	other threads:[~2008-05-01 16:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 20:42 Gabriel C
2008-04-30 20:46 ` Jay Cliburn
2008-04-30 20:59   ` Gabriel C
2008-04-30 21:02   ` Jay Cliburn
2008-05-01  5:57 ` Len Brown
2008-05-01 12:53   ` Matthew Garrett
2008-05-01 12:57     ` Rafael J. Wysocki
2008-05-01 13:06       ` Matthew Garrett
2008-05-01 17:14         ` Rafael J. Wysocki
2008-05-01 13:19   ` Gabriel C
2008-05-01 16:09   ` Pavel Machek
2008-05-01 16:30     ` Alan [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=33216.75.164.221.130.1209659450.squirrel@clueserver.org \
    --to=alan@clueserver.org \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=nix.or.die@googlemail.com \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    /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

all inboxes | Powered by JetHome®