linux-kernel - 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <4818D9AB.3040402@googlemail.com>
Date:	Wed, 30 Apr 2008 22:42:19 +0200
From:	Gabriel C <nix.or.die@...glemail.com>
To:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
CC:	Len Brown <len.brown@...el.com>,
	linux-pm@...ts.linux-foundation.org, pavel@...e.cz,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Some sort corruption of my Thermal Subsystem after suspend to ram

Hi all,

I thought I've found all issue with that new box but I was wrong ;)

On an ASUS P5E-VM DO , 4G RAM , Q9300 CPU after suspend to ram Thermal 
Subsystem gets corrupted in some way.

I got some reboot , halt problems and was hunting the issue and noticed these problems only
occurred when I've suspend the box to ram , at least once.

I've tested 2.6.{24*,25,linus-git(before ACPI merge),x86-latest-git} and all got that problem.

Also on x86-latest-git I've tested with MTRR_SANITIZER on/off. It does not make any difference.


lspci output before s2r is :

..


00:1f.6 Signal processing controller [1180]: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem [8086:2932] (rev 02)
        Subsystem: ASUSTeK Computer Inc. Device [1043:8277]
        Flags: fast devsel
        Memory at fed08000 (64-bit, non-prefetchable) [size=4K]
        Capabilities: [50] Power Management version 3                                                                                                       

...


and after :

...

00:1f.6 Signal processing controller [1180]: Intel Corporation 82801I (ICH9 Family) Thermal Subsystem [8086:2932] (rev ff) (prog-if ff)
        !!! Unknown header type 7f

...

dmesg | grep 00:1f.6
[21520.103062] PM: Writing back config space on device 0000:00:1f.6 at offset f (was ffffffff, writing 300)
[21520.103066] PM: Writing back config space on device 0000:00:1f.6 at offset e (was ffffffff, writing 0)
[21520.103070] PM: Writing back config space on device 0000:00:1f.6 at offset d (was ffffffff, writing 50)
[21520.103074] PM: Writing back config space on device 0000:00:1f.6 at offset c (was ffffffff, writing 0)
[21520.103078] PM: Writing back config space on device 0000:00:1f.6 at offset b (was ffffffff, writing 82771043)
[21520.103083] PM: Writing back config space on device 0000:00:1f.6 at offset a (was ffffffff, writing 0)
[21520.103087] PM: Writing back config space on device 0000:00:1f.6 at offset 9 (was ffffffff, writing 0)
[21520.103091] PM: Writing back config space on device 0000:00:1f.6 at offset 8 (was ffffffff, writing 0)
[21520.103095] PM: Writing back config space on device 0000:00:1f.6 at offset 7 (was ffffffff, writing 0)
[21520.103099] PM: Writing back config space on device 0000:00:1f.6 at offset 6 (was ffffffff, writing 0)
[21520.103103] PM: Writing back config space on device 0000:00:1f.6 at offset 5 (was ffffffff, writing 0)
[21520.103107] PM: Writing back config space on device 0000:00:1f.6 at offset 4 (was ffffffff, writing fed08004)
[21520.103111] PM: Writing back config space on device 0000:00:1f.6 at offset 3 (was ffffffff, writing 0)
[21520.103115] PM: Writing back config space on device 0000:00:1f.6 at offset 2 (was ffffffff, writing 11800002)
[21520.103119] PM: Writing back config space on device 0000:00:1f.6 at offset 1 (was ffffffff, writing 100002)
[21520.103123] PM: Writing back config space on device 0000:00:1f.6 at offset 0 (was ffffffff, writing 29328086)

..


Please let me know if you need my config , dmesg or any other informations.


Best Regards,

Gabriel C

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