From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: linux-usb@vger.kernel.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>,
Ozan Caglayan <ozan@pardus.org.tr>
Subject: Re: 2.6.38 regression caused by commit 415e12b
Date: Wed, 2 Mar 2011 01:17:04 +0100 [thread overview]
Message-ID: <201103020117.04251.rjw@sisk.pl> (raw)
In-Reply-To: <20110302000445.GA2621@xanatos>
On Wednesday, March 02, 2011, Sarah Sharp wrote:
> On Wed, Mar 02, 2011 at 12:30:16AM +0100, Rafael J. Wysocki wrote:
> > On Tuesday, March 01, 2011, Sarah Sharp wrote:
> > > On Tue, Mar 01, 2011 at 09:55:33PM +0100, Rafael J. Wysocki wrote:
> > > > Please check if the appended patch (on top of the Linus' current) helps.
> > >
> > > Sorry, it doesn't help. Same message as before.
> >
> > Can you send dmesg with the patch applied, please?
>
> Attached.
Something's fishy. Evidently, _OSC is not executed on your system
although it should be with the patch.
Please try the patch below instead and send dmesg (either way).
Thanks,
Rafael
---
drivers/acpi/pci_root.c | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
Index: linux-2.6/drivers/acpi/pci_root.c
===================================================================
--- linux-2.6.orig/drivers/acpi/pci_root.c
+++ linux-2.6/drivers/acpi/pci_root.c
@@ -48,10 +48,7 @@ static int acpi_pci_root_add(struct acpi
static int acpi_pci_root_remove(struct acpi_device *device, int type);
static int acpi_pci_root_start(struct acpi_device *device);
-#define ACPI_PCIE_REQ_SUPPORT (OSC_EXT_PCI_CONFIG_SUPPORT \
- | OSC_ACTIVE_STATE_PWR_SUPPORT \
- | OSC_CLOCK_PWR_CAPABILITY_SUPPORT \
- | OSC_MSI_SUPPORT)
+#define ACPI_PCIE_REQ_SUPPORT (OSC_EXT_PCI_CONFIG_SUPPORT | OSC_MSI_SUPPORT)
static const struct acpi_device_id root_device_ids[] = {
{"PNP0A03", 0},
@@ -572,8 +569,10 @@ static int __devinit acpi_pci_root_add(s
if (flags != base_flags)
acpi_pci_osc_support(root, flags);
- if (!pcie_ports_disabled
- && (flags & ACPI_PCIE_REQ_SUPPORT) == ACPI_PCIE_REQ_SUPPORT) {
+ if (!pcie_ports_disabled) {
+ dev_info(root->bus->bridge,
+ "ACPI _OSC support set (0x%02x)\n", flags);
+
flags = OSC_PCI_EXPRESS_CAP_STRUCTURE_CONTROL
| OSC_PCI_EXPRESS_NATIVE_HP_CONTROL
| OSC_PCI_EXPRESS_PME_CONTROL;
next prev parent reply other threads:[~2011-03-02 0:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 1:42 2.6.38 regression caused by commit 415e12b Sarah Sharp
2011-02-28 5:34 ` Sarah Sharp
2011-02-28 20:29 ` Rafael J. Wysocki
2011-03-01 18:31 ` Sarah Sharp
2011-03-01 20:55 ` Rafael J. Wysocki
2011-03-01 22:51 ` Sarah Sharp
2011-03-01 23:30 ` Rafael J. Wysocki
2011-03-02 0:04 ` Sarah Sharp
2011-03-02 0:17 ` Rafael J. Wysocki [this message]
2011-03-02 3:42 ` Sarah Sharp
2011-03-02 11:21 ` Rafael J. Wysocki
2011-03-02 22:30 ` [PATCH 0/2] " Rafael J. Wysocki
2011-03-02 22:32 ` [PATCH 1/2] PCI/ACPI: Report ASPM support to BIOS if not disabled from command line Rafael J. Wysocki
2011-03-02 22:33 ` [PATCH 2/2] PCI/ACPI: Report MSI " Rafael J. Wysocki
2011-03-04 17:52 ` [PATCH 0/2] Re: 2.6.38 regression caused by commit 415e12b Sarah Sharp
2011-03-04 20:32 ` Rafael J. Wysocki
2011-03-14 23:56 ` Sarah Sharp
2011-03-15 0:02 ` Rafael J. Wysocki
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=201103020117.04251.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ozan@pardus.org.tr \
--cc=sarah.a.sharp@linux.intel.com \
/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