From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: linux-kernel@vger.kernel.org
Subject: S2RAM and PCI quirks
Date: Wed, 08 Nov 2006 15:45:05 +0000 [thread overview]
Message-ID: <1163000705.23956.18.camel@localhost.localdomain> (raw)
I'm tracing down a case where suspend to ram/resume from RAM causes
horrible corruption but not immediately. From a PCI dump it appears that
we are not running the PCI quirks again on the S2RAM resume. Is this
actually the case or am I missing something scanning through the code.
If it is the case then we have multiple corruptors lurking because the
PCI config restore doesn't cover the special registers that need poking
in some cases.
Alan
next reply other threads:[~2006-11-08 15:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-08 15:45 Alan Cox [this message]
2006-11-08 15:48 ` S2RAM and PCI quirks Arjan van de Ven
2006-11-08 16:01 ` Alan Cox
2006-11-08 21:18 ` Rafael J. Wysocki
2006-11-08 23:47 ` [linux-pm] " Pavel Machek
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=1163000705.23956.18.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--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