linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Ayman El-Khashab <AymanE@tanisys.com>
Cc: linuxppc-dev@ozlabs.org, Stefan Roese <sr@denx.de>
Subject: RE: Problems with PCI-E devices not being detected with switch
Date: Fri, 17 Oct 2008 11:10:09 +1100	[thread overview]
Message-ID: <1224202209.7654.36.camel@pasglop> (raw)
In-Reply-To: <16691A8B34B5D9458EA3A1C37A11555A0137F822@tanisys-ex2.Tanisys.Local>

On Thu, 2008-10-16 at 10:01 -0500, Ayman El-Khashab wrote:
> Benjamin Herrenschmidt wrote:
> > On Wed, 2008-10-15 at 10:47 -0500, Ayman El-Khashab wrote:
> > 
> > Note for people on CC: This is a problem on 460EX on a canyonland
> > using the 4x port. 
> > 
> >> The problem occurs when Linux boots. It sees the switch (and looking
> >> in /sys/bus/... confirms it), but nothing on the downstream sides of
> >> the switch (secondary busses) is visible.  There were no boot
> >> messages to indicate it had seen the Sil 3531 and it doesn't
> >> function.  We've also tried other PCI-E devices (NI GPIB) on the
> >> downstream side and they are also not detected, so it seems to be
> >> something in Linux, my configuration, etc.  I've included the boot
> >> messages below from u-boot and the kernel.  It is more than just the
> >> pci boot messages, but I was not sure if something else in the log
> >> with provide some insight. 
> > 
> > The messages below look really fishy indeed:

Ok, can you send me a full dmesg log with "debug" on the kernel command
line after adding a #define DEBUG 1 to the top of drivers/pci/probe.c
please ? (before the batch of #include).

The generic code is _supposed_ to somewhat figure out that bridges
haven't been setup by the firmware and fix that up, but for some reason
it's not happening I think. Or something else is wrong ...

Stefan, I could use the same log from your customer too.

Thanks,
Ben.

  parent reply	other threads:[~2008-10-17  0:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 15:47 Problems with PCI-E devices not being detected with switch Ayman El-Khashab
2008-10-16  5:20 ` Benjamin Herrenschmidt
2008-10-16  8:03   ` Stefan Roese
2008-10-16  8:29     ` Benjamin Herrenschmidt
2008-10-16  8:48       ` Stefan Roese
2008-10-16  8:58         ` Benjamin Herrenschmidt
2008-10-16 15:01   ` Ayman El-Khashab
2008-10-16 21:19     ` Benjamin Herrenschmidt
2008-10-17  0:10     ` Benjamin Herrenschmidt [this message]
2008-10-17  7:22       ` Stefan Roese
2008-10-17 14:54       ` Ayman El-Khashab
2008-10-17 21:05         ` Benjamin Herrenschmidt
2008-10-17 21:19         ` Benjamin Herrenschmidt
2008-10-20 21:03           ` Ayman El-Khashab
2008-10-20 21:57             ` Benjamin Herrenschmidt
2008-10-20 22:14               ` Ayman El-Khashab
2008-10-20 22:55                 ` Benjamin Herrenschmidt

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=1224202209.7654.36.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=AymanE@tanisys.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=sr@denx.de \
    /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).