linux-kernel - Re: BAR 0: can't allocate resource

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 7 Jan 2010 12:09:01 +1100
From:	Alex Brooks <a.brooks@...athon-robotics.com>
To:	Bjorn Helgaas <bjorn.helgaas@...com>
Cc:	linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: BAR 0: can't allocate resource

> You mentioned two messages.  Here's the first:
>   PCI: BIOS Bug: MCFG area at e0000000 is not reserved in ACPI motherboard
> resources PCI: Not using MMCONFIG.
>
> and the second:
>   PCI: Cannot allocate resource region 0 of device 0000:01:04.0
>   PCI: Error while updating region 0000:01:04.0/0 (feb00002 != 00000000)
>
> The "Error while updating region" message is because we wrote something
> to a BAR, read it back, and they didn't match.  I suppose this could be
> some kind of config space problem related to the fact that we're not
> using MMCONFIG.
>
> Can you try removing the MCFG reservation check, so we do try to use
> MMCONFIG?  If you do this on a current kernel, we'll also get a little
> more debug output about the subsequent resource allocation failure.

I did this on my 2.6.26 kernel (is this current enough or would a later kernel 
be better?) and attached the dmesg output.

Alex

View attachment "dmesg_mmconfig.txt" of type "text/plain" (24845 bytes)