linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjorn Helgaas <bhelgaas@google.com>
To: Tony Luck <tony.luck@gmail.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Lucas Stach <l.stach@pengutronix.de>,
	Richard Zhu <Richard.Zhu@freescale.com>,
	Yinghai Lu <yinghai@kernel.org>,
	Marek Kordik <kordikmarek@gmail.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	Andreas Hartmann <andihartmann@freenet.de>,
	Alexey Voronkov <zermond@gmail.com>,
	David Airlie <airlied@linux.ie>,
	Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [GIT PULL] PCI fixes for v3.19
Date: Mon, 26 Jan 2015 17:53:34 -0600	[thread overview]
Message-ID: <20150126235334.GA11624@google.com> (raw)
In-Reply-To: <CA+8MBb+bWiX2eayjBQHsvCjTp3t8H9=AviF9AkV6CC--cC_fYQ@mail.gmail.com>

On Mon, Jan 26, 2015 at 01:24:51PM -0800, Tony Luck wrote:
> On Mon, Jan 26, 2015 at 1:02 PM, Bjorn Helgaas <bhelgaas@google.com> wrote:
> > Sorry for the inconvenience.  Can you collect a complete dmesg log and
> > "lspci -vv" output, too (from the kernel with the reverted commit)?
> > That will have more useful information than just /proc/iomem.
> 
> Full dmesg, lspci -vv, and bonus .config (CONFIG_PCI_IOV is indeed
> not set)

The ROM part is something we should fix:

  pci 0000:01:00.1: can't claim BAR 6 [mem 0xfffe0000-0xffffffff pref]: no compatible bridge window

The ROM BAR is probably disabled, and we shouldn't complain about this if
it's disabled.  Yinghai?

The stuff on bus 0000:80 looks like at least partly a firmware problem:

  ACPI: PCI Root Bridge [PCI1] (domain 0000 [bus 80-ff])
  acpi PNP0A08:01: host bridge window [io  0x9000-0xfffe]
  pci 0000:80:01.0: PCI bridge to [bus 81]
  pci 0000:80:01.0:   bridge window [io  0xa000-0xafff]
  pci 0000:80:01.0:   bridge window [mem 0xa0100000-0xa01fffff]
  pci 0000:80:13.0: reg 0x10: [mem 0xa0220000-0xa0220fff]

ACPI told us about an I/O port aperture, but didn't mention any MMIO
apertures through the host bridge.  Therefore, we have no MMIO space to
assign to the devices on [bus 80-ff].

But presumably these devices, e.g., the igb devices at 81:00.0 and 81:00.1
and the mpt device at 83:00.0, actually DO work, so the PCI1 host bridge
must actually forward some MMIO space that ACPI didn't tell us about.  I
think on x86, we would fall back to whatever the firmware left in those
BARs.  We should probably do the same on x86.

Bjorn

  reply	other threads:[~2015-01-26 23:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-23 20:31 [GIT PULL] PCI fixes for v3.19 Bjorn Helgaas
2015-01-26 19:58 ` Tony Luck
2015-01-26 21:02   ` Bjorn Helgaas
2015-01-26 21:24     ` Tony Luck
2015-01-26 23:53       ` Bjorn Helgaas [this message]
2015-01-27  3:55         ` Yinghai Lu
2015-01-27 14:03           ` Bjorn Helgaas
2015-01-27 23:27             ` Tony Luck
2015-01-27  3:43       ` Yinghai Lu
2015-01-27 23:24         ` Tony Luck
2015-01-28  0:54           ` Yinghai Lu
2015-01-30 16:56             ` Bjorn Helgaas
2015-01-30 18:01               ` Tony Luck
2015-01-30 18:18                 ` Bjorn Helgaas
2015-01-30 21:49               ` Yinghai Lu
2015-01-30 22:12                 ` Bjorn Helgaas
     [not found] <20150204191831.GA13785@google.com>
2015-02-11 16:48 ` Bjorn Helgaas

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=20150126235334.GA11624@google.com \
    --to=bhelgaas@google.com \
    --cc=Richard.Zhu@freescale.com \
    --cc=airlied@linux.ie \
    --cc=alex.williamson@redhat.com \
    --cc=alexander.deucher@amd.com \
    --cc=andihartmann@freenet.de \
    --cc=kordikmarek@gmail.com \
    --cc=l.stach@pengutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=tony.luck@gmail.com \
    --cc=torvalds@linux-foundation.org \
    --cc=yinghai@kernel.org \
    --cc=zermond@gmail.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;
as well as URLs for NNTP newsgroup(s).