From: Andreas Koch <koch@esa.informatik.tu-darmstadt.de>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Andreas Koch <koch@esa.informatik.tu-darmstadt.de>,
linux-pci@atrey.karlin.mff.cuni.cz, linux-kernel@vger.kernel.org,
gregkh@suse.de
Subject: Re: PROBLEM: Devices behind PCI Express-to-PCI bridge not mapped
Date: Sat, 4 Jun 2005 04:26:00 +0200 [thread overview]
Message-ID: <20050604022600.GA8221@erebor.esa.informatik.tu-darmstadt.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0506031851220.1876@ppc970.osdl.org>
On Fri, Jun 03, 2005 at 06:55:40PM -0700, Linus Torvalds wrote:
>
>
> On Sat, 4 Jun 2005, Andreas Koch wrote:
> >
> > As you suspected, it wasn't a panacea: The kernel now panics, with a
> > call chain of
> >
> > ...
> > pcibios_init()
> > pci_assign_unassigned_resources()
> > pci_bus_assign_resources()
> > pci_setup_bridge()
> >
> > I can collect more specific info if necessary.
>
> It would be nice to know exactly what it is that panics, I could well
> imagine that it's something like the "bus->self" that ends up being NULL
> for the root bus or something silly like that, simply because x86 has
> never needed to use these functions.
>
> If so, it migth be as easy as just skipping buses that don't have bridge
> device associated with them, but this would require that you try to debug
> the oops a bit to figure out where it is..
Actually, I tried that already. But I didn't get any usable info from
the oops and GDB (`list *pci_setup_bridge+0x1a2' shows an include file,
not a line in the function) . I'll make another attempt tomorrow when
I am more awake :-)
Andreas
next prev parent reply other threads:[~2005-06-04 2:26 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 [this message]
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
2005-06-04 16:16 ` Andreas Koch
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=20050604022600.GA8221@erebor.esa.informatik.tu-darmstadt.de \
--to=koch@esa.informatik.tu-darmstadt.de \
--cc=gregkh@suse.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;
as well as URLs for NNTP newsgroup(s).