mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: George Rapp <george.rapp@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: pci 0000:01:00.0: BAR 0: can't allocate resource
Date: Tue, 24 Feb 2009 08:53:25 -0500	[thread overview]
Message-ID: <f1f3dd8f0902240553j15a4714bte24e9273c702f540@mail.gmail.com> (raw)
In-Reply-To: <f1f3dd8f0902240542m58aa6adfn3fc09cee162636a1@mail.gmail.com>

[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@gmail.com> wrote:
>
> On Sun, Feb 22, 2009 at 10:50 PM, Linus Torvalds <torvalds@linux-foundation.org> wrote:
>>
>> Can you also show the contents of /proc/iomem?
>
> Linus -
>
> Here it is:
>
> [root@newbackend ~]# 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
>
>
>
\

  parent reply	other threads:[~2009-02-24 13:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f1f3dd8f0902221910n2722b024pe3ec8748fd3aed5b@mail.gmail.com>
2009-02-23  3:13 ` Fwd: " George Rapp
2009-02-23  3:50 ` Linus Torvalds
2009-02-23  7:32   ` H. Peter Anvin
2009-02-23  8:01     ` Dave Airlie
     [not found]   ` <f1f3dd8f0902240542m58aa6adfn3fc09cee162636a1@mail.gmail.com>
2009-02-24 13:53     ` George Rapp [this message]
2009-02-24 16:45     ` Linus Torvalds

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f1f3dd8f0902240553j15a4714bte24e9273c702f540@mail.gmail.com \
    --to=george.rapp@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®