From: Andrew Morton <akpm@linux-foundation.org>
To: Lukas Hejtmanek <xhejtman@ics.muni.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Workaround for a PCI restoring bug
Date: Sat, 12 May 2007 23:47:43 -0700 [thread overview]
Message-ID: <20070512234743.0a8a915f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20070512201237.GB3569@ics.muni.cz>
On Sat, 12 May 2007 22:12:37 +0200 Lukas Hejtmanek <xhejtman@ics.muni.cz> wrote:
> as of 2.6.21-git16, the bugs related to restoring PCI are still present. The
> save pci function reads only -1 from the PCI config space and when restoring,
> it messes up totaly most PCI devices. The attached patch is workaround only
> until proper fix is found and included. Could it be included into the mainline
> for now?
>
> --
> Lukáš Hejtmánek
>
>
> [pci.patch text/x-diff (489B)]
> --- drivers/pci/pci.c.orig 2006-07-15 23:53:08.000000000 +0200
> +++ drivers/pci/pci.c 2006-07-21 00:51:07.000000000 +0200
> @@ -477,7 +477,7 @@
> */
> for (i = 15; i >= 0; i--) {
> pci_read_config_dword(dev, i * 4, &val);
> - if (val != dev->saved_config_space[i]) {
> + if (val != dev->saved_config_space[i] && dev->saved_config_space[i] != 0xffffffff) {
> printk(KERN_DEBUG "PM: Writing back config space on "
> "device %s at offset %x (was %x, writing %x)\n",
> pci_name(dev), i,
This change might indeed be a suitable workaround for some busted hardware,
but we'd need to know quite a bit about the problem before we could merge
anything like this
So, again, please send a full bug report. An emailed one would be OK in
this case.
Thanks.
next prev parent reply other threads:[~2007-05-13 6:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-12 20:12 Lukas Hejtmanek
2007-05-13 6:47 ` Andrew Morton [this message]
2007-05-13 8:57 ` Lukas Hejtmanek
2007-05-13 9:11 ` Andrew Morton
2007-05-13 12:21 ` Lukas Hejtmanek
2007-05-13 18:59 ` Andrew Morton
2007-05-14 10:21 ` Lukas Hejtmanek
[not found] <fa.K6U9hglycxHd65x5b6pmUzJjdoA@ifi.uio.no>
2007-05-13 2:06 ` Robert Hancock
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=20070512234743.0a8a915f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xhejtman@ics.muni.cz \
/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
Powered by JetHome