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]

Message-Id: <201001101407.26930.a.brooks@marathon-robotics.com>
Date:	Sun, 10 Jan 2010 14:07:26 +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

> I was hoping for a kernel directly from Linus' git repo, e.g.,
> 2.6.33-rc3; I don't think the debug output I'm thinking about went in
> until after 2.6.32 was released.

I'm not sure how to modify the 2.6.33-rc3 kernel source exactly re MCFG -- the 
dmesg output for 2.6.33-rc3 is quite different (attached), including some new 
information about an address collision for the recalcitrant device:

pci 0000:01:04.0: address space collision: [mem 0x00800000-0x00800fff] already 
in use
pci 0000:01:04.0: can't reserve [mem 0x00800000-0x00800fff]

Does this shed any more light on things (or can you tell me what I could 
modify to get better debug info)?


Thanks,

Alex

View attachment "dmesg_2.6.33-rc3.txt" of type "text/plain" (31739 bytes)