From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Yinghai Lu <yinghai@kernel.org>,
linux-pci@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
ACPI Devel Mailing List <linux-acpi@vger.kernel.org>,
Len Brown <lenb@kernel.org>,
Matthew Garrett <mjg59@srcf.ucam.org>
Subject: Re: [RFT][PATCH] PCI / ACPI: Do not require MSI support for PCIe native features
Date: Thu, 17 Mar 2011 14:56:09 -0700 [thread overview]
Message-ID: <20110317215609.GA5917@xanatos> (raw)
In-Reply-To: <201103172222.33336.rjw@sisk.pl>
On Thu, Mar 17, 2011 at 10:22:33PM +0100, Rafael J. Wysocki wrote:
> On Thursday, March 17, 2011, Yinghai Lu wrote:
> > 2011/3/16 Rafael J. Wysocki <rjw@sisk.pl>:
> > > On Tuesday, March 15, 2011, Sarah Sharp wrote:
> > >> On Tue, Mar 15, 2011 at 01:00:17AM +0100, Rafael J. Wysocki wrote:
> > >> > Well, I must admit I have no idea what the problem is. OK, in addition to the
> > >> > above changes, please replace the "pci_ext_cfg_avail(root->bus->self)" in the
> > >> > same file with "true" and see if _that_ helps.
> > >>
> > >> Yay, that worked! dmesg is attached.
> > >
> > > Good, at least we know what the problem is, now we only have to find the root
> > > cause. ;-)
> > >
> > > So, pci_ext_cfg_avail(root->bus->self) returns 0 on your machine, which is kind
> > > of unexpected (to put it lightly), so very likely we have uncovered a bug
> > > in the init code.
> > >
> > > Unfortunately, I may not be able to take care of this issue for the next few
> > > days, I'll let you know when I get back to it.
> >
> > her .config does not define PCI_MMCONFIG
> >
> > #
> > # Bus options (PCI etc.)
> > #
> > CONFIG_PCI=y
> > CONFIG_PCI_DIRECT=y
> > # CONFIG_PCI_MMCONFIG is not set
>
> Ah, good catch, thanks!
>
> @Sarah: you need to set that for PCI Express to work in general.
Oh, man, sorry to cause so much work to figure that out. :) I'll
compile with that set and see if it helps. Not sure why that config
worked on 2.6.37, but not 2.6.38. I usually just run `make -j4` with
the old .config and basically pick the defaults, except for turning on
the occasional new USB device driver.
Sarah Sharp
next prev parent reply other threads:[~2011-03-17 21:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-05 21:54 [RFT][PATCH] PCI / ACPI: Do not require MSI support for PCIe native features Rafael J. Wysocki
2011-03-14 18:26 ` Sarah Sharp
2011-03-14 20:02 ` Rafael J. Wysocki
2011-03-14 20:19 ` Sarah Sharp
2011-03-14 20:37 ` Rafael J. Wysocki
2011-03-14 23:47 ` Sarah Sharp
2011-03-15 0:00 ` Rafael J. Wysocki
2011-03-15 19:05 ` Sarah Sharp
2011-03-17 0:19 ` Rafael J. Wysocki
2011-03-17 5:23 ` Yinghai Lu
2011-03-17 21:22 ` Rafael J. Wysocki
2011-03-17 21:56 ` Sarah Sharp [this message]
2011-03-21 22:28 ` Hot plug issue on 2.6.38 Sarah Sharp
2011-03-21 22:34 ` Matthew Garrett
2011-03-21 23:31 ` Sarah Sharp
2011-03-21 23:41 ` Rafael J. Wysocki
2011-03-21 22:51 ` Rafael J. Wysocki
2011-03-21 23:54 ` Sarah Sharp
2011-03-22 0:07 ` 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=20110317215609.GA5917@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=rjw@sisk.pl \
--cc=yinghai@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;
as well as URLs for NNTP newsgroup(s).