public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: George Rapp <george.rapp@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: pci 0000:01:00.0: BAR 0: can't allocate resource
Date: Sun, 22 Feb 2009 23:32:43 -0800	[thread overview]
Message-ID: <49A2511B.7030606@zytor.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0902221941510.3111@localhost.localdomain>

Linus Torvalds wrote:
> 
> On Sun, 22 Feb 2009, George Rapp wrote:
>> In case the attachments don't survive Gmail, dmesg output is at
>> http://novia.net/~gwr/dmesg_2.6.29-0.33.rc5, and output of 'lspci -vv' is at
>> http://novia.net/~gwr/lspci-vv_2.6.29-0.33.rc5
> 
> Can you also show the contents of /proc/iomem?
> 
> 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 makes sense on 32 bits, since by default the entire vmalloc region
is only 128 MB in size.

Booting with vmalloc=256M or something like that might help.

	-hpa

-- 
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel.  I don't speak on their behalf.


  reply	other threads:[~2009-02-23  7:33 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: pci 0000:01:00.0: BAR 0: can't allocate resource George Rapp
2009-02-23  3:50 ` Linus Torvalds
2009-02-23  7:32   ` H. Peter Anvin [this message]
2009-02-23  8:01     ` Dave Airlie
     [not found]   ` <f1f3dd8f0902240542m58aa6adfn3fc09cee162636a1@mail.gmail.com>
2009-02-24 13:53     ` George Rapp
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=49A2511B.7030606@zytor.com \
    --to=hpa@zytor.com \
    --cc=george.rapp@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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