From: Frans Pop <elendil@planet.nl>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-pci@vger.kernel.org
Subject: Re: Comparison between .28 and .29-rc3 for STR cycle
Date: Tue, 3 Feb 2009 15:41:49 +0100 [thread overview]
Message-ID: <200902031541.50182.elendil@planet.nl> (raw)
In-Reply-To: <200902031237.53579.elendil@planet.nl>
On Tuesday 03 February 2009, Frans Pop wrote:
> # Of the next 4 lines only the 3rd line also appears during normal
> boot.
> +pci 0000:00:02.0: PME# disabled
> +pci 0000:00:02.1: PME# disabled
> +pci 0000:00:03.0: PME# disabled
> +pci 0000:00:03.2: PME# disabled
The 3rd device is also the only one that has a "PME# supported" line
during normal boot.
Problem seems to be in drivers/pci/pci.c in pci_enable_wake(), which has:
if (!enable || pci_pme_capable(dev, state)) {
pci_pme_active(dev, enable);
pme_done = true;
}
So it's always called if enable is false, regardless of whether the device
is PME# capable. Should a test for dev->pme_support be added somewhere?
It seems harmless, just inconsistent.
next prev parent reply other threads:[~2009-02-03 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 11:37 Comparison between .28 and .29-rc3 for STR cycle Frans Pop
2009-02-03 14:41 ` Frans Pop [this message]
2009-02-04 12:02 ` Frans Pop
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=200902031541.50182.elendil@planet.nl \
--to=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--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