linux-kernel - Re: [GIT PULL] PCI fixes for v3.19

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 26 Jan 2015 15:02:29 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Tony Luck <tony.luck@...il.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Lucas Stach <l.stach@...gutronix.de>,
	Richard Zhu <Richard.Zhu@...escale.com>,
	Yinghai Lu <yinghai@...nel.org>,
	Marek Kordik <kordikmarek@...il.com>,
	Alex Williamson <alex.williamson@...hat.com>,
	Andreas Hartmann <andihartmann@...enet.de>,
	Alexey Voronkov <zermond@...il.com>,
	David Airlie <airlied@...ux.ie>,
	Alex Deucher <alexander.deucher@....com>
Subject: Re: [GIT PULL] PCI fixes for v3.19

On Mon, Jan 26, 2015 at 1:58 PM, Tony Luck <tony.luck@...il.com> wrote:
> I'm seeing these new messages in v3.19-rc6 on ia64:

Hi Tony,

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.

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

These are option ROMs, probably just not assigned.  We should be able
to assign space for them, so this might not even be a problem, but we
certainly need a better message if that's all it is.

> pci 0000:01:00.1: can't claim BAR 6 [mem 0xfffe0000-0xffffffff pref]:
> no compatible bridge window
> pci 0000:03:00.0: can't claim BAR 6 [mem 0xffe00000-0xffffffff pref]:
> no compatible bridge window
> pci 0000:0b:04.0: can't claim BAR 6 [mem 0xfffe0000-0xffffffff pref]:
> no compatible bridge window
> pci 0000:80:13.0: can't claim BAR 0 [mem 0xa0220000-0xa0220fff]: no
> compatible bridge window

Interesting.  There's no mention of bus 80 at all in /proc/iomem;
maybe this is found by blind probing?  Do we even do that on ia64?
Dmesg should have a clue.

> pci 0000:80:16.0: can't claim BAR 0 [mem 0xa0200000-0xa0203fff 64bit]:
> no compatible bridge window
> pci 0000:80:16.1: can't claim BAR 0 [mem 0xa0204000-0xa0207fff 64bit]:
> no compatible bridge window
> pci 0000:80:16.2: can't claim BAR 0 [mem 0xa0208000-0xa020bfff 64bit]:
> no compatible bridge window
> pci 0000:80:16.3: can't claim BAR 0 [mem 0xa020c000-0xa020ffff 64bit]:
> no compatible bridge window
> pci 0000:80:16.4: can't claim BAR 0 [mem 0xa0210000-0xa0213fff 64bit]:
> no compatible bridge window
> pci 0000:80:16.5: can't claim BAR 0 [mem 0xa0214000-0xa0217fff 64bit]:
> no compatible bridge window
> pci 0000:80:16.6: can't claim BAR 0 [mem 0xa0218000-0xa021bfff 64bit]:
> no compatible bridge window
> pci 0000:80:16.7: can't claim BAR 0 [mem 0xa021c000-0xa021ffff 64bit]:
> no compatible bridge window
> pci 0000:80:01.0: can't claim BAR 8 [mem 0xa0100000-0xa01fffff]: no
> compatible bridge window

Looks like a bridge window (assuming you have CONFIG_PCI_IOV unset).
There's definitely something wrong -- all those mpt and igb devices at
the top level *should* be under some PCI hierarchy, but the hierarchy
is missing from iomem.

Bjorn
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/