From: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
To: Andreas Koch <koch@esa.informatik.tu-darmstadt.de>
Cc: linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: Continuing PCI and Yenta troubles in 2.6.13.1 and 2.6.14-rc1
Date: Tue, 20 Sep 2005 16:59:02 +0400 [thread overview]
Message-ID: <20050920165902.A27065@jurassic.park.msu.ru> (raw)
In-Reply-To: <200509201202.24318.koch@esa.informatik.tu-darmstadt.de>; from koch@esa.informatik.tu-darmstadt.de on Tue, Sep 20, 2005 at 12:02:23PM +0200
On Tue, Sep 20, 2005 at 12:02:23PM +0200, Andreas Koch wrote:
> Thus, I believe there is still something rotten in the PCI code since the
> 2.6.12-rc6 days.
Thanks a lot for the report.
You are right, and I believe the change that broke things is
introduction of pci_fixup_parent_subordinate_busnr()...
The patch here does two things:
- hunk #1 should fix the problems you've seen when you boot without
additional "pci" kernel options;
- hunk #2 supposedly fixes boot with "pci=assign-busses" option which
otherwise hangs Acer TM81xx machines as reported.
Please try this with and without "pci=assign-busses". If it boots,
I'd like to see 'lspci -vvx' for both cases.
Ivan.
--- 2.6.13.2/drivers/pci/probe.c Mon Aug 8 12:20:28 2005
+++ linux/drivers/pci/probe.c Tue Sep 20 16:17:23 2005
@@ -400,6 +400,12 @@ static void pci_enable_crs(struct pci_de
static void __devinit pci_fixup_parent_subordinate_busnr(struct pci_bus *child, int max)
{
struct pci_bus *parent = child->parent;
+
+ /* Attempts to fix that up are really dangerous unless
+ we're going to re-assign all bus numbers. */
+ if (!pcibios_assign_all_busses())
+ return;
+
while (parent->parent && parent->subordinate < max) {
parent->subordinate = max;
pci_write_config_byte(parent->self, PCI_SUBORDINATE_BUS, max);
@@ -476,8 +482,18 @@ int __devinit pci_scan_bridge(struct pci
* We need to assign a number to this bus which we always
* do in the second pass.
*/
- if (!pass)
+ if (!pass) {
+ if (pcibios_assign_all_busses())
+ /* Temporarily disable forwarding of the
+ configuration cycles on all bridges in
+ this bus segment to avoid possible
+ conflicts in the second pass between two
+ bridges programmed with overlapping
+ bus ranges. */
+ pci_write_config_dword(dev, PCI_PRIMARY_BUS,
+ buses & ~0xffffff);
return max;
+ }
/* Clear errors */
pci_write_config_word(dev, PCI_STATUS, 0xffff);
next prev parent reply other threads:[~2005-09-20 12:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-02 23:38 2.6.13: Crash in Yenta initialization Andreas Koch
2005-09-03 0:37 ` Andrew Morton
2005-09-03 0:45 ` Andreas Koch
2005-09-03 18:34 ` Ivan Kokshaysky
2005-09-12 17:42 ` Olaf Hering
2005-09-12 20:07 ` Ivan Kokshaysky
2005-09-13 6:30 ` Olaf Hering
2005-09-13 11:45 ` Ivan Kokshaysky
2005-09-14 4:10 ` Olaf Hering
2005-09-20 10:02 ` Continuing PCI and Yenta troubles in 2.6.13.1 and 2.6.14-rc1 Andreas Koch
2005-09-20 12:59 ` Ivan Kokshaysky [this message]
[not found] ` <200509202006.19193.koch@esa.informatik.tu-darmstadt.de>
2005-09-21 15:55 ` Ivan Kokshaysky
2005-09-13 12:36 ` 2.6.13: Crash in Yenta initialization Andreas Koch
2005-09-13 12:43 ` Andreas Koch
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=20050920165902.A27065@jurassic.park.msu.ru \
--to=ink@jurassic.park.msu.ru \
--cc=koch@esa.informatik.tu-darmstadt.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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
all inboxes | Powered by JetHome®