public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gabriel C <nix.or.die@googlemail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Cc: Len Brown <len.brown@intel.com>,
	linux-pm@lists.linux-foundation.org, pavel@suse.cz,
	"Rafael J. Wysocki" <rjw@sisk.pl>
Subject: Some sort corruption of my Thermal Subsystem after suspend to ram
Date: Wed, 30 Apr 2008 22:42:19 +0200	[thread overview]
Message-ID: <4818D9AB.3040402@googlemail.com> (raw)

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


             reply	other threads:[~2008-04-30 20:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 20:42 Gabriel C [this message]
2008-04-30 20:46 ` Some sort corruption of my Thermal Subsystem after suspend to ram 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

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=4818D9AB.3040402@googlemail.com \
    --to=nix.or.die@googlemail.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.linux-foundation.org \
    --cc=pavel@suse.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