From: Chuck Ebbert <76306.1226@compuserve.com>
To: Andrew Morton <akpm@osdl.org>
Cc: Miles Lane <miles.lane@gmail.com>, Greg KH <greg@kroah.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.17-rc5-mm2 -- PCI: Bus #03 (-#06) is hidden behind transparent bridge
Date: Thu, 1 Jun 2006 17:39:07 -0400 [thread overview]
Message-ID: <200606011741_MC3-1-C158-4567@compuserve.com> (raw)
In-Reply-To: <20060601095335.c778bc98.akpm@osdl.org>
On Thu, 1 Jun 2006 09:53:35 -0700, Andrew Morton wrote:
> On Thu, 1 Jun 2006 10:52:26 -0400
> "Miles Lane" <miles.lane@gmail.com> wrote:
>
> > PCI: Transparent bridge - 0000:00:1e.0
> > PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02)
> > (try 'pci=assign-busses')
> > Please report the result to linux-kernel to fix this permanently
>
> I guess you're supposed to try 'pci=assign-busses'.
>
> Does the machine work OK without pci=assign-busses?
>
> Does the machine work OK with pci=assign-busses?
>
> Greg, what are we supposed to be doing here? Grab the PCI IDs and add a
> quirk somewhere?
I get that message all the time and it's annoying because pci=assign-busses
does nothing but change the bus numbers. No new devices or busses appear.
System is Compaq Presario v2000 notebook with ATI chipset and AMD Turion CPU.
Without pci=assign-busses:
dmesg:
PCI: Transparent bridge - 0000:00:14.4
PCI: Bus #06 (-#09) is hidden behind transparent bridge #05 (-#06) (try 'pci=assign-busses')
lspci -t:
-[0000:00]-+-00.0
+-01.0-[0000:01]----05.0
+-13.0
+-13.1
+-13.2
+-14.0
+-14.1
+-14.3
+-14.4-[0000:05-06]--+-00.0
| +-02.0
| +-09.0
| +-09.2
| +-09.3
| \-09.4
+-14.5
+-14.6
+-18.0
+-18.1
+-18.2
\-18.3
With pci=assign-busses:
lspci -t:
-[0000:00]-+-00.0
+-01.0-[0000:01]----05.0
+-13.0
+-13.1
+-13.2
+-14.0
+-14.1
+-14.3
+-14.4-[0000:02-06]--+-00.0
| +-02.0
| +-09.0
| +-09.2
| +-09.3
| \-09.4
+-14.5
+-14.6
+-18.0
+-18.1
+-18.2
\-18.3
--
Chuck
reply other threads:[~2006-06-01 21:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200606011741_MC3-1-C158-4567@compuserve.com \
--to=76306.1226@compuserve.com \
--cc=akpm@osdl.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
all inboxes | Powered by JetHome®