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]

Message-ID: <CA+8MBbKnT=mE3kev8BRPq0GeTgHx8WVa6o54tJuBX_XXLpHdYQ@mail.gmail.com>
Date:	Mon, 26 Jan 2015 11:58:16 -0800
From:	Tony Luck <tony.luck@...il.com>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.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>, zermond@...il.com,
	David Airlie <airlied@...ux.ie>,
	Alex Deucher <alexander.deucher@....com>
Subject: Re: [GIT PULL] PCI fixes for v3.19

I'm seeing these new messages in v3.19-rc6 on ia64:

pci 0000:01:00.0: can't claim BAR 6 [mem 0xfffe0000-0xffffffff pref]:
no compatible bridge window
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
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
pci 0000:81:00.0: can't claim BAR 6 [mem 0xfffe0000-0xffffffff pref]:
no compatible bridge window
pci 0000:81:00.1: can't claim BAR 6 [mem 0xfffe0000-0xffffffff pref]:
no compatible bridge window
pci 0000:80:05.0: can't claim BAR 8 [mem 0xa0000000-0xa00fffff]: no
compatible bridge window
pci 0000:83:00.0: can't claim BAR 6 [mem 0xffe00000-0xffffffff pref]:
no compatible bridge window

Bisection pointed to:

>       ia64/PCI: Clip bridge windows to fit in upstream windows

and reverting commit ce821ef0333fc1 makes them go away again.

How do I tell whether I really have a bunch of badly configured busses
that we are just
now able to detect, or there is something spurious in this patch? Contents of
/proc/iomem (from the kernel with the reverted patch) attached.

-Tony

View attachment "iomem.txt" of type "text/plain" (7174 bytes)