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: [PATCH 0/2] Re: 2.6.38 regression caused by commit 415e12b
Date: Fri, 4 Mar 2011 21:32:35 +0100 [thread overview]
Message-ID: <201103042132.35711.rjw@sisk.pl> (raw)
In-Reply-To: <20110304175210.GA3798@xanatos>
On Friday, March 04, 2011, Sarah Sharp wrote:
> On Wed, Mar 02, 2011 at 11:30:49PM +0100, Rafael J. Wysocki wrote:
> > On Wednesday, March 02, 2011, Rafael J. Wysocki wrote:
> > > There are two problems. First, your BIOS says that ASPM is not supported
> > > by it, so we don't call _OSC, which should be fixed by the previous patch.
> > > Second, pci_msi_enabled() returns 0 on your system, which is kind of strange,
> > > because it evidently uses MSIs (as visible in the dmesg).
> > >
> > > While I think we can safely request _OSC control even if ASPM is not supported
> > > by the hardware (according to the BIOS), which is done after the first patch,
> > > we need to figure out why 0 is returned by pci_msi_enabled() on your system
> > > and try to work around that.
> >
> > Regardless, I think we should report MSI and ASPM support to the BIOS unless
> > directly disabled via the kernel command line or .config.
> >
> > I'm going to send two patches in replies to this message. Please apply them
> > both on top of 2.6.38-rc7 and report back.
>
> I applied your patches on top of 2.6.38-rc6 again and tested them.
> dmesg is attached. Let me know if you need me to test Linus' latest
> instead.
-rc6 should be fine.
I don't understand why pci_no_msi_support() is called on your system even
though pci=nomsi is not in the kernel command line.
Please apply this patch on top of the previous two and send me dmesg.
---
drivers/pci/msi.c | 2 ++
1 file changed, 2 insertions(+)
Index: linux-2.6/drivers/pci/msi.c
===================================================================
--- linux-2.6.orig/drivers/pci/msi.c
+++ linux-2.6/drivers/pci/msi.c
@@ -858,6 +858,8 @@ void pci_no_msi(void)
void pci_no_msi_support(void)
{
+ dump_stack();
+
msi_support_enabled = false;
pci_no_msi();
}
next prev parent reply other threads:[~2011-03-04 20:32 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-28 1:42 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
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 [this message]
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=201103042132.35711.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
all inboxes | Powered by JetHome®