linux-kernel - Re: BAR 14: can't assign mem (size 0x200000)

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 PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Fri, 28 Mar 2014 21:55:01 -0400
From:	Parag Warudkar <parag.lkml@...il.com>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Bjorn Helgaas <bhelgaas@...gle.com>,
	Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: BAR 14: can't assign mem (size 0x200000)

On Fri, Mar 28, 2014 at 9:16 PM, Yinghai Lu <yinghai@...nel.org> wrote:
> On Fri, Mar 28, 2014 at 5:40 PM, Parag Warudkar <parag.lkml@...il.com> wrote:
>> No issues with fresh boot, however after resume from suspend I see
>> these messages -
>>
>> [11548.934625] pci_bus 0000:03: Allocating resources
>> [11548.934645] pci 0000:02:00.0: bridge window [io  0x1000-0x0fff] to
>> [bus 03] add_size 1000
>> [11548.934648] pci 0000:02:00.0: bridge window [mem
>> 0x00100000-0x000fffff 64bit pref] to [bus 03] add_size 200000
>> [11548.934650] pci 0000:02:00.0: bridge window [mem
>> 0x00100000-0x000fffff] to [bus 03] add_size 200000
>> [11548.934653] pci 0000:02:00.0: res[14]=[mem 0x00100000-0x000fffff]
>> get_res_add_size add_size 200000
>> [11548.934655] pci 0000:02:00.0: res[15]=[mem 0x00100000-0x000fffff
>> 64bit pref] get_res_add_size add_size 200000
>> [11548.934656] pci 0000:02:00.0: res[13]=[io  0x1000-0x0fff]
>> get_res_add_size add_size 1000
>> [11548.934659] pci 0000:02:00.0: BAR 14: can't assign mem (size 0x200000)
>> [11548.934661] pci 0000:02:00.0: BAR 15: can't assign mem pref (size 0x200000)
>> [11548.934662] pci 0000:02:00.0: BAR 13: can't assign io (size 0x1000)
>> [11548.934664] pci 0000:02:00.0: BAR 14: can't assign mem (size 0x200000)
>> [11548.934666] pci 0000:02:00.0: BAR 15: can't assign mem pref (size 0x200000)
>> [11548.934667] pci 0000:02:00.0: BAR 13: can't assign io (size 0x1000)
>> [11548.934669] pci 0000:02:00.0: PCI bridge to [bus 03]
>> [11548.934697] pci 0000:02:00.0: no hotplug settings from platform
>> [11548.934698] pci 0000:02:00.0: using default PCI settings
>>
>

> Can you send out whole boot log (include init booting and from resume) and
> lspci -tv and lspci -vvxxxx ?

lspci -tv
-----------
~# lspci -tv
-[0000:00]-+-00.0  Intel Corporation Xeon E3-1200 v3 Processor DRAM Controller
           +-02.0  Intel Corporation Xeon E3-1200 v3 Processor
Integrated Graphics Controller
           +-03.0  Intel Corporation Xeon E3-1200 v3/4th Gen Core
Processor HD Audio Controller
           +-14.0  Intel Corporation 8 Series/C220 Series Chipset
Family USB xHCI
           +-16.0  Intel Corporation 8 Series/C220 Series Chipset
Family MEI Controller #1
           +-16.3  Intel Corporation 8 Series/C220 Series Chipset
Family KT Controller
           +-19.0  Intel Corporation Ethernet Connection I217-LM
           +-1a.0  Intel Corporation 8 Series/C220 Series Chipset
Family USB EHCI #2
           +-1b.0  Intel Corporation 8 Series/C220 Series Chipset High
Definition Audio Controller
           +-1c.0-[01]--
           +-1c.3-[02-03]----00.0-[03]--
           +-1c.4-[04-3c]--
           +-1d.0  Intel Corporation 8 Series/C220 Series Chipset
Family USB EHCI #1
           +-1f.0  Intel Corporation C226 Series Chipset Family Server
Advanced SKU LPC Controller
           +-1f.2  Intel Corporation 8 Series/C220 Series Chipset
Family 6-port SATA Controller 1 [AHCI mode]
           \-1f.3  Intel Corporation 8 Series/C220 Series Chipset
Family SMBus Controller

lspci -vvxxxx and dmesg output are kind of big, so attached.

Parag

View attachment "dmesg.txt" of type "text/plain" (92285 bytes)

View attachment "lspcivvx.txt" of type "text/plain" (98970 bytes)