login
Login
/
Register
Search
Forums
News
Blogs
Features
Site
Home
»
Mailing list archives
»
linux-kernel
»
2007
»
April
»
19
Re: PCI bridge range sizing bug
view
thread
!MAILaRCHIVE_VOTE_RePLACE
Previous message: [
thread
] [
date
] [
author
]
Next message: [
thread
] [
date
] [
author
]
[view in full thread]
From:
Greg KH <gregkh@...>
To: Jesse Barnes <jesse.barnes@...>, Ivan Kokshaysky <ink@...>, <torvalds@...>
Cc: Adam Jackson <ajackson@...>, <linux-kernel@...>
Subject:
Re: PCI bridge range sizing bug
Date: Thursday, April 19, 2007 - 7:40 pm
On Thu, Apr 19, 2007 at 04:11:50PM -0700, Jesse Barnes wrote:
quoted text
> On Thursday, April 5, 2007 3:37 pm Adam Jackson wrote: > > So I'm attempting to do something fairly heinous (X server across > > five video cards), and I hit a fun bug in bridge range setup. See > > attached lspci and dmesg, but the short of it is I've got two VGA > > chips on one card behind a bridge, which is itself behind a second > > PCI bridge, and the bridge ranges get set up so that I can't map the > > ROMs, which means I can't post them, and therefore can't use them > > period. > > > > The alignment restriction on the ROMs seems a bit extreme: > > > > % sudo setpci -s 7:2 ROM_ADDRESS=ffffffff > > % sudo setpci -s 7:2 ROM_ADDRESS > > f0000001 > > > > (same for 7:1) so that might be part of the problem. > > ... > Allocating PCI resources starting at 88000000 (gap: 80000000:7ff00000) > ... > > That's ~2G of space, which should be plenty for your PCI resources I > hope? If you have a bunch of cards with large BARS though you might be > running out. > > ... > PCI: Bridge: 0000:00:01.0 > IO window: 4000-4fff > MEM window: a3500000-a35fffff (1M) > PREFETCH window: 90000000-97ffffff > PCI: Bridge: 0000:00:03.0 > IO window: disabled. > MEM window: a3400000-a34fffff (1M) > PREFETCH window: 98000000-9fffffff > PCI: Bridge: 0000:00:1c.0 > IO window: disabled. > MEM window: a3300000-a33fffff (1M) > PREFETCH window: 80000000-8fffffff > PCI: Bridge: 0000:00:1c.4 > IO window: 3000-3fff > MEM window: a3200000-a32fffff (1M) > PREFETCH window: a3700000-a37fffff > PCI: Bridge: 0000:00:1c.5 > IO window: 2000-2fff > MEM window: a3100000-a31fffff (1M) > PREFETCH window: disabled. > PCI: Failed to allocate mem resource #6:10000000@b0000000 for > 0000:07:01.0 > PCI: Failed to allocate mem resource #6:10000000@b0000000 for > 0000:07:02.0 > ... > > Yep, looks like those two devices had a problem. Supposedly they want > to sit at 256M? Given that we're only giving each bridge 1M of memory > space that would definitely be a problem. > > The total so far is only 5M of PCI space... so we're not making good use > of the 2G we were given. > > ... > PCI: Bridge: 0000:06:00.0 > IO window: disabled. > MEM window: a1000000-a2ffffff (32M) > PREFETCH window: disabled. > PCI: Bridge: 0000:00:1e.0 > IO window: 1000-1fff > MEM window: a1000000-a30fffff (~32M) > PREFETCH window: a0000000-a0ffffff > ... > > And these bridges got more space somehow... Greg who's in charge of our > bridge resource allocation code?
Ivan and Linus seem to be doing the most of the work in this area, I gladly pass these issues on to them :) thanks, greg k-h -
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to
majordomo@vger.kernel.org
More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
http://www.tux.org/lkml/
Previous message: [
thread
] [
date
] [
author
]
Next message: [
thread
] [
date
] [
author
]
Messages in current thread:
Re: PCI bridge range sizing bug
, Jesse Barnes
, (Thu Apr 19, 7:11 pm)
Re: PCI bridge range sizing bug
, Greg KH
, (Thu Apr 19, 7:40 pm)
Re: PCI bridge range sizing bug
, Linus Torvalds
, (Thu Apr 19, 8:19 pm)
Re: PCI bridge range sizing bug
, Ivan Kokshaysky
, (Fri Apr 20, 5:23 am)
Re: PCI bridge range sizing bug
, Jesse Barnes
, (Fri Apr 20, 12:32 pm)
Re: PCI bridge range sizing bug
, Linus Torvalds
, (Fri Apr 20, 2:28 pm)
Re: PCI bridge range sizing bug
, Jesse Barnes
, (Fri Apr 20, 4:34 pm)
Re: PCI bridge range sizing bug
, Rik van Riel
, (Sat Apr 21, 1:31 am)
Re: PCI bridge range sizing bug
, Ivan Kokshaysky
, (Fri Apr 20, 4:30 pm)
Re: PCI bridge range sizing bug
, Jesse Barnes
, (Mon May 14, 1:45 pm)
Re: PCI bridge range sizing bug
, Ivan Kokshaysky
, (Tue May 15, 6:39 pm)
Navigation
Create content
Mailing list archives
Recent posts
Popular discussions
linux-kernel
:
Glauber de Oliveira Costa
[PATCH 08/79] [PATCH] use identify_boot_cpu
David Woodhouse
[PATCH v2] Stop pmac_zilog from abusing 8250's device numbers.
Greg Kroah-Hartman
[PATCH 002/196] Chinese: rephrase English introduction in HOWTO
Jeremy Fitzhardinge
[PATCH 30 of 31] xen: no need for domU to worry about MCE/MCA
git
:
openbsd-misc
:
linux-netdev
:
Gerrit Renker
[PATCH 03/37] dccp: List management for new feature negotiation
Jarek Poplawski
[PATCH] pkt_sched: Destroy gen estimators under rtnl_lock().
David Miller
[GIT]: Networking
Frans Pop
svc: failed to register lockdv1 RPC service (errno 97).
Colocation donated by:
Who's online
There are currently
4 users
and
1081 guests
online.
Online users
hloeung
zeekec
oilrubbedbronz
brothersewingm
Syndicate