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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LFD.2.00.0902221941510.3111@localhost.localdomain>
Date:	Sun, 22 Feb 2009 19:50:19 -0800 (PST)
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	George Rapp <george.rapp@...il.com>
cc:	linux-kernel@...r.kernel.org
Subject: Re: pci 0000:01:00.0: BAR 0: can't allocate resource



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