linux-kernel - 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-next>] [day] [month] [year] [list]

Date:	Tue, 5 Jan 2010 20:18:02 +1100
From:	Alex Brooks <a.brooks@...athon-robotics.com>
To:	linux-kernel@...r.kernel.org
Subject: BAR 0: can't allocate resource

Hi,

I have a problem getting a couple of PCI cards to play nicely together.  The 
error I get (in dmesg) is:
2.6.26 kernel:
[    0.215619] PCI: Cannot allocate resource region 0 of device 0000:01:04.0
2.6.30 kernel:
[    0.138390] pci 0000:01:04.0: BAR 0: can't allocate resource

And (for both kernels) the output of lspci has the following line:
  01:04.0 Unclassified device [0080]: Device 0002:0080

Hardware Details:
 - My motherboard is a DigitalLogic MSM945.  It has a PC104 bus.
 - I have two PC104 cards:
   i)  8-port serial card (DiamondSystems Emerald-MM-8Plus)
   ii) PC/104+ to MiniPCI Adapter (ConnectTech) (no MiniPCI cards installed).
  (I have run both of these cards with a different motherboard, no problems).

I've compared two conditions:
 a) "working": serial card installed by itself, and
 b) "broken": serial + MiniPCI cards both installed

For the 2.6.26 kernel, I've attached the output of 
 - dmesg
 - lspci
 - lspci -v
 - cat /proc/iomem
for both 'working' and 'broken' cases.

(Note: in both cases the following two lines appear in the dmesg output:
[    0.185656] PCI: BIOS Bug: MCFG area at e0000000 is not reserved in ACPI 
motherboard resources
[    0.185711] PCI: Not using MMCONFIG
Is this significant?)


Does anyone have any ideas what to try here?  I've been fighting with this for 
a while now...
(Please Cc me on any response).

Thanks,

Alex

View attachment "dmesg_broken.txt" of type "text/plain" (24956 bytes)

View attachment "dmesg_working.txt" of type "text/plain" (25566 bytes)

View attachment "lspci_broken.txt" of type "text/plain" (1472 bytes)

View attachment "lspci_working.txt" of type "text/plain" (1486 bytes)

View attachment "lspci_v_broken.txt" of type "text/plain" (5497 bytes)

View attachment "lspci_v_working.txt" of type "text/plain" (5549 bytes)

View attachment "proc_iomem_broken.txt" of type "text/plain" (1100 bytes)

View attachment "proc_iomem_working.txt" of type "text/plain" (1349 bytes)