linux-kernel - Re: pci 0000:01:00.0: 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>] [day] [month] [year] [list]

Message-ID: <f1f3dd8f0902240553j15a4714bte24e9273c702f540@mail.gmail.com>
Date:	Tue, 24 Feb 2009 08:53:25 -0500
From:	George Rapp <george.rapp@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: Re: pci 0000:01:00.0: BAR 0: can't allocate resource

[Re-sending; forgot to turn off HTML and lkml bounced my original ...]

On Tue, Feb 24, 2009 at 8:42 AM, George Rapp <george.rapp@...il.com> wrote:
>
> On Sun, Feb 22, 2009 at 10:50 PM, Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>>
>> Can you also show the contents of /proc/iomem?
>
> Linus -
>
> Here it is:
>
> [root@...backend ~]# cat /proc/iomem
> 00000000-0009fbff : System RAM
> 0009fc00-0009ffff : reserved
> 000a0000-000bffff : Video RAM area
> 000c0000-000ccfff : Video ROM
> 000d0000-000d47ff : Adapter ROM
> 000f0000-000fffff : reserved
>   000f0000-000fffff : System ROM
> 00100000-1bffffff : System RAM
>   00400000-006d8200 : Kernel code
>   006d8201-0088aa97 : Kernel data
>   008f8000-009ed14b : Kernel bss
>   01382000-01382fff : Local APIC
> d8000000-e7ffffff : PCI Bus 0000:01
>   d8000000-d801ffff : 0000:01:00.0
> e8000000-efffffff : 0000:00:00.0
> f0000000-f1ffffff : PCI Bus 0000:01
>   f1000000-f100ffff : 0000:01:00.0
> f2000000-f201ffff : 0000:00:0b.0
> f3000000-f307ffff : 0000:00:0c.0
> f4000000-f40001ff : 0000:00:0c.0
>   f4000000-f40001ff : sata_sil
> f4001000-f400107f : 0000:00:0b.0
> ffff0000-ffffffff : reserved
>
>
>
>>
>> It does look like it's this one:
>>
>>        pci 0000:01:00.0: BAR 0: can't allocate mem resource [0xe0000000-0xe7ffffff]
>>
>> and the problem is that the kernel cannot find enough space to map the
>> required 128MB region for the graphics aperture.
>>
>> Which is really odd, because the bridge to that PCI bus#1 is this:
>>
>>        pci 0000:00:01.0: PCI bridge, secondary bus 0000:01
>>        pci 0000:00:01.0:   IO window: 0x9000-0x9fff
>>        pci 0000:00:01.0:   MEM window: 0xf0000000-0xf1ffffff
>>        pci 0000:00:01.0:   PREFETCH window: 0x000000d8000000-0x000000e7ffffff
>>
>> and that prefetch window is _huge_. Certainly big enough to fit BAR 0, but
>> maybe there is something else in it.
>>
>>                Linus
>
>
>
\
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/