linux-kernel - Re: [GIT PATCH] PCI and PCI hotplug fixes for 2.6.19-rc2

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: <Pine.LNX.4.64.0610181729270.3962@g5.osdl.org>
Date:	Wed, 18 Oct 2006 17:41:47 -0700 (PDT)
From:	Linus Torvalds <torvalds@...l.org>
To:	Andrew Morton <akpm@...l.org>
cc:	Greg KH <gregkh@...e.de>, aarranz@...aso.ls.fi.upm.es,
	Daniel Ritz <daniel.ritz@....ch>,
	Dominik Brodowski <linux@...inikbrodowski.net>,
	linux-kernel@...r.kernel.org, linux-pci@...ey.karlin.mff.cuni.cz,
	pcihpd-discuss@...ts.sourceforge.net
Subject: Re: [GIT PATCH] PCI and PCI hotplug fixes for 2.6.19-rc2

On Wed, 18 Oct 2006, Andrew Morton wrote:
> 
> pccard: CardBus card inserted into slot 0
> PCI: Failed to allocate mem resource #0:1000000@...00000 for 0000:07:00.2

That seems to be a 16MB memory resource. But we already totally filled up 
the memory space we reserved for cardbus with the memory resources needed 
for 7:0.0 and 7:0.1

That cardbus card seems to have three sub-functions, and it looks like 
they _all_ want a 16MB memory region. We "only" allocated 32MB total for 
it, so the third subfunction gets left out.

(There's another 32MB of memory allocated for the cardbus bridge at 
0x6a000000, but it's prefetchable, so we don't allow a non-prefetchable 
resourc to use it).

I don't think this has _ever_ worked. 

Hmm. I guess the Alvaro could try increasing "BRIDGE_MEM_MAX" in 
drivers/pcmcia/yenta_socket.c. It's currently at 4MB, but I think we gave 
him 32MB exactly because there was a huge memory hole, so we decided to 
extend it further a bit:

                size = BRIDGE_MEM_MAX;
                if (size > avail/8) {
                        size=(avail+1)/8;
                        /* round size down to next power of 2 */
                        i = 0;
                        while ((size /= 2) != 0)
                                i++;
                        size = 1 << i;
                }

but it migth be worth testing with "BRIDGE_MEM_MAX" set to 64MB instead of 
the current 4MB.

Alvaro?

		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/