From: Greg KH <gregkh@suse.de>
To: Andreas Koch <koch@esa.informatik.tu-darmstadt.de>
Cc: linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
torvalds@osdl.org
Subject: Re: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
Date: Fri, 3 Jun 2005 23:46:27 -0700 [thread overview]
Message-ID: <20050604064627.GB13238@suse.de> (raw)
In-Reply-To: <20050603232828.GA29860@erebor.esa.informatik.tu-darmstadt.de>
On Sat, Jun 04, 2005 at 01:28:28AM +0200, Andreas Koch wrote:
> [Greg K-H suggested I distribute this more widely]
>
> Hello all,
>
> there appear to be difficulties correctly mapping addresses behind a
> PCI Express-to-PCI bridge in kernel 2.6.12-rc5.
>
> Specifically, this occurs on my Acer Travelmate 8100 notebook (Pentium
> M, Intel 915M chipset) when it is connected via PCI Express to the
> ezDock docking station.
Are you connecting it at boot time, or after the box is up and running?
> While all of the USB and FireWire devices are visible using config
> space reads, they cannot be accessed correctly (all normal reads
> appear to return 0xff). After checking the dmesg logs, I find
>
> PCI: Cannot allocate resource region 7 of bridge 0000:02:00.0
> PCI: Cannot allocate resource region 8 of bridge 0000:02:00.0
>
> This would confirm my hypothesis, since reads go the route of
>
> Processor
> Intel 82801xx ICH6 southbridge
> PCI Express port 3 0000:00:1c.2
> Intel 6702PXH PCIE-PCI bridge 0000:02:00.0
> ezDock-internal PCI bus 0000:03:xx.x
> USB
> Firewire
> ...
>
> Since the PCIE-PCI bridge cannot be memory-mapped, the devices behind it
> cannot be accessed correctly.
>
> I am no expert on debugging this part of the kernel, but I will gladly
> provide additional info to resolve this problem.
Hm, another idea, can you load the pci express and standard pci hotplug
drivers? You might have to "enable" those slots in order for the pci
core to scan the devices and set everything up properly.
To do this, after loading the modules (pciehp and shpchp), look in
/sys/bus/pci/slots/
If there are any "slots" listed there, go into those directories and
"power them on" by simply writing a "1" to the file 'power' by using
echo.
Let us know if that helps out any or not.
Oh, and this isn't "PCI ExpressCard" type hardware is it (next
generation pcmcia/cardbus evolution.)
thanks,
greg k-h
next prev parent reply other threads:[~2005-06-04 6:46 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 23:28 PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped Andreas Koch
2005-06-04 0:22 ` Linus Torvalds
2005-06-04 1:33 ` Andreas Koch
2005-06-04 1:55 ` Linus Torvalds
2005-06-04 2:26 ` Andreas Koch
2005-06-04 4:50 ` Linus Torvalds
2005-06-04 15:57 ` Andreas Koch
2005-06-05 16:46 ` Ivan Kokshaysky
2005-06-06 0:27 ` Andreas Koch
2005-06-06 14:43 ` Ivan Kokshaysky
2005-06-08 17:34 ` Andreas Koch
2005-06-08 22:36 ` Ivan Kokshaysky
2005-06-09 0:29 ` Andreas Koch
2005-06-09 4:04 ` Benjamin Herrenschmidt
2005-06-09 13:54 ` Ivan Kokshaysky
2005-06-09 17:54 ` Andreas Koch
2005-06-09 22:38 ` Andreas Koch
2005-06-09 23:20 ` Linus Torvalds
2005-06-10 14:33 ` Andreas Koch
2005-06-10 14:48 ` Ivan Kokshaysky
2005-06-10 20:47 ` Andreas Koch
2005-06-10 23:50 ` Sean Bruno
2005-06-14 15:19 ` Sean Bruno
2005-06-16 14:20 ` Andreas Koch
2005-06-16 17:20 ` Peter Buckingham
2005-06-16 20:53 ` Sean Bruno
2005-06-16 21:05 ` Peter Buckingham
2005-06-16 21:12 ` Roland Dreier
2005-06-16 21:21 ` Peter Buckingham
2005-06-17 9:54 ` Ivan Kokshaysky
2005-06-17 16:34 ` Peter Buckingham
2005-06-17 16:51 ` Sean Bruno
2005-06-17 17:59 ` Sean Bruno
2005-06-18 7:45 ` Ivan Kokshaysky
2005-06-18 17:55 ` Sean Bruno
2005-06-20 16:51 ` Peter Buckingham
2005-06-20 21:31 ` Peter Buckingham
2005-06-20 23:39 ` Peter Buckingham
2005-06-04 15:17 ` Linus Torvalds
2005-06-04 6:38 ` Greg KH
2005-06-04 6:51 ` Grant Grundler
2005-06-04 7:12 ` Grant Grundler
2005-06-04 7:19 ` Greg KH
2005-06-04 6:46 ` Greg KH [this message]
2005-06-04 16:16 ` Andreas Koch
-- strict thread matches above, loose matches on Subject: below --
2005-06-11 5:33 linux
2005-06-11 10:26 ` Ivan Kokshaysky
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=20050604064627.GB13238@suse.de \
--to=gregkh@suse.de \
--cc=koch@esa.informatik.tu-darmstadt.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
--cc=torvalds@osdl.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