linux-kernel - Re: Some sort corruption of my Thermal Subsystem after suspend to ram

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <33216.75.164.221.130.1209659450.squirrel@clueserver.org>
Date:	Thu, 1 May 2008 09:30:50 -0700 (PDT)
From:	"Alan" <alan@...eserver.org>
To:	"Pavel Machek" <pavel@....cz>
Cc:	"Len Brown" <lenb@...nel.org>,
	"Gabriel C" <nix.or.die@...glemail.com>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	linux-pm@...ts.linux-foundation.org,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: Some sort corruption of my Thermal Subsystem after suspend to 
     ram

> 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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/