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] [day] [month] [year] [list]
Message-ID: <21d7e9970902230001p509c7a77w9a94b76d552844c9@mail.gmail.com>
Date:	Mon, 23 Feb 2009 18:01:53 +1000
From:	Dave Airlie <airlied@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	George Rapp <george.rapp@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: pci 0000:01:00.0: BAR 0: can't allocate resource

On Mon, Feb 23, 2009 at 5:32 PM, H. Peter Anvin <hpa@...or.com> wrote:
> 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.
>

Its not ioremap mapping it, its just getting the resource mapping for
PCI that is needed.

So nothing to do with vmalloc.

Dave.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ