From: Andrew Morton <akpm@linux-foundation.org>
To: "Miles Lane" <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, Greg KH <greg@kroah.com>
Subject: Re: 2.6.22-rc4-mm2 -- Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 'pci=assign-busses')
Date: Thu, 7 Jun 2007 13:27:09 -0700 [thread overview]
Message-ID: <20070607132709.32cd9f4a.akpm@linux-foundation.org> (raw)
In-Reply-To: <a44ae5cd0706071133w19272d8bkb392ffe58f1af6b7@mail.gmail.com>
On Thu, 7 Jun 2007 11:33:12 -0700
"Miles Lane" <miles.lane@gmail.com> wrote:
> Andrew, is it okay to debug this with the MM tree? I see this with
> Linus' kernels as well. It's a long-standing issue, but I have always
> just used pci=assign-busses in the past.
>
Dunno, but let's not miss an opportunity to bug the PCI maintainer.
>
> [ 0.215128] PCI: Transparent bridge - 0000:00:1e.0
> [ 0.215142] PCI: Scanning behind PCI bridge 0000:02:09.0, config
> 000000, pass 0
> [ 0.215158] PCI: Scanning behind PCI bridge 0000:02:09.0, config
> 000000, pass 1
> [ 0.215184] PCI: Bus #03 (-#06) is hidden behind transparent bridge
> #02 (-#02) (try 'pci=assign-busses')
> [ 0.215187] Please report the result to linux-kernel to fix this permanently
> [ 0.215192] PCI: Bus scan for 0000:02 returning with max=06
> [ 0.215199] PCI: Scanning behind PCI bridge 0000:00:1e.0, config
> 020200, pass 1
> [ 0.215209] PCI: Bus scan for 0000:00 returning with max=06
>
Does the kernel otherwise work OK with and without pci=assign-busses?
next prev parent reply other threads:[~2007-06-07 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-07 18:33 2.6.22-rc4-mm2 -- Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 'pci=assign-busses') Miles Lane
2007-06-07 20:27 ` Andrew Morton [this message]
2007-06-07 23:13 ` Miles Lane
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=20070607132709.32cd9f4a.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miles.lane@gmail.com \
/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