From: Lukas Hejtmanek <xhejtman@mail.muni.cz>
To: gregkh@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: Linux kernel 2.6.17-git14 and PCI suspend/resume
Date: Tue, 4 Jul 2006 01:11:21 +0200 [thread overview]
Message-ID: <20060703231121.GB2752@mail.muni.cz> (raw)
Hello,
in this kernel I'm seeing these messages after S3 resume:
kernel: PM: Writing back config space on device 0000:01:01.1 at offset f (was 4020205, writing ffffffff)
kernel: PM: Writing back config space on device 0000:01:01.1 at offset e (was 0, writing ffffffff)
kernel: PM: Writing back config space on device 0000:01:01.1 at offset d (was dc, writing ffffffff)
kernel: PM: Writing back config space on device 0000:01:01.1 at offset c (was 0, writing ffffffff)
kernel: PM: Writing back config space on device 0000:01:01.1 at offset b (was 19671043, writing ffffffff)
kernel: PM: Writing back config space on device 0000:01:01.1 at offset a (was 0, writing ffffffff)
kernel: PM: Writing back config space on device 0000:01:01.1 at offset 9 (was 0, writing ffffffff)
kernel: PM: Writing back config space on device 0000:01:01.1 at offset 8 (was 0, writing ffffffff)
kernel: PM: Writing back config space on device 0000:01:01.1 at offset 7 (was 0, writing ffffffff)
kernel: PM: Writing back config space on device 0000:01:01.1 at offset 6 (was 0, writing ffffffff)
kernel: PM: Writing back config space on device 0000:01:01.1 at offset 5 (was 0, writing ffffffff)
kernel: PM: Writing back config space on device 0000:01:01.1 at offset 4 (was fe8fd800, writing ffffffff)
kernel: PM: Writing back config space on device 0000:01:01.1 at offset 3 (was 804000, writing ffffffff)
kernel: PM: Writing back config space on device 0000:01:01.1 at offset 2 (was c001008, writing ffffffff)
kernel: PM: Writing back config space on device 0000:01:01.1 at offset 1 (was 2100006, writing ffffffff)
kernel: PM: Writing back config space on device 0000:01:01.1 at offset 0 (was 5521180, writing ffffffff)
Which actually mess up PCI config space (and sdhci driver is unable to set up
MMC device correctly). Do you have any idea what to try?
These messages appear for devices that are not handled by any loaded module.
--
Lukáš Hejtmánek
next reply other threads:[~2006-07-03 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 23:11 Lukas Hejtmanek [this message]
2006-07-03 23:21 ` Greg KH
2006-07-04 7:32 ` Lukas Hejtmanek
2006-07-07 15:02 ` Lukas Hejtmanek
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=20060703231121.GB2752@mail.muni.cz \
--to=xhejtman@mail.muni.cz \
--cc=gregkh@suse.de \
--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
all inboxes | Powered by JetHome®