LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
To: jwoithe@physics.adelaide.edu.au (Jonathan Woithe)
Cc: linux-kernel@vger.kernel.org
Subject: PCI: Bus is behind transparent bridge
Date: Tue, 20 Feb 2007 10:35:55 +1030 (CST)	[thread overview]
Message-ID: <200702200005.l1K05tJi016929@turbo.physics.adelaide.edu.au> (raw)
In-Reply-To: <200702140006.l1E06awJ013179@turbo.physics.adelaide.edu.au> from "Jonathan Woithe" at Feb 14, 2007 10:36:36 AM

Further to my previous email:

> When booting my laptop I notice the following message:
> 
>   PCI quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
>   PCI quirk: region 1180-11bf claimed by ICH6 GPIO
>   PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
>   PCI: Transparent bridge - 0000:00:1e.0
>   PCI: Bus #07 (-#0a) is hidden behind transparent bridge #06 (-#07) (try
>   'pci=assign-busses')
>   Please report the result to linux-kernel to fix this permanently
:
> The machine is a 2.0 GHz Dothan Centrino.  I'm happy to test things and/or
> provide more info if it will help.

A closer inspection under 2.6.20 showed that "pci=assign-busses" did have
some effect.  Without it I see:

> ACPI: Core revision 20060707
> ENABLING IO-APIC IRQs
> .TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
> NET: Registered protocol family 16
> ACPI: bus type pci registered
> PCI: Using MMCONFIG
> Setting up standard PCI resources
> ACPI: Interpreter enabled
> ACPI: Using IOAPIC for interrupt routing
> ACPI: PCI Root Bridge [PCI0] (0000:00)
> PCI: Probing PCI hardware (bus 00)
> Boot video device is 0000:00:02.0
> PCI quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
> PCI quirk: region 1180-11bf claimed by ICH6 GPIO
> PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
> PCI: Transparent bridge - 0000:00:1e.0
> PCI: Bus #07 (-#0a) is hidden behind transparent bridge #06 (-#07) (try 'pci=assign-busses')
> Please report the result to linux-kernel to fix this permanently
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
> ACPI: PCI Interrupt Link [LNKA] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
> ACPI: PCI Interrupt Link [LNKB] (IRQs 1 3 4 5 6 7 *11 12 14 15)
> ACPI: PCI Interrupt Link [LNKC] (IRQs 1 3 4 5 6 7 10 12 14 15) *11
> ACPI: PCI Interrupt Link [LNKD] (IRQs 1 3 4 5 6 7 *11 12 14 15)
> ACPI: PCI Interrupt Link [LNKE] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
> ACPI: PCI Interrupt Link [LNKF] (IRQs 1 3 4 5 6 7 *11 12 14 15)
> ACPI: PCI Interrupt Link [LNKG] (IRQs 1 3 4 5 6 7 10 12 14 15) *0, disabled.
> ACPI: PCI Interrupt Link [LNKH] (IRQs 1 3 4 5 6 7 *11 12 14 15)
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP1._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.EXP2._PRT]

Using "assign-busses" I get

  :
  PCI quirk: region 1000-107f claimed by ICH6 ACPI/GPIO/TCO
  PCI quirk: region 1180-11bf claimed by ICH6 GPIO
  PCI: Transparent bridge - 0000:00:1e.0
  ACPI: PCI Interrupt Routing Table [\_SB_.PCI0._PRT]
  ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
  :

Is there any more information required for this to be "fixed permanently"?

Regards
  jonathan

      reply	other threads:[~2007-02-20  0:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-14  0:06 Bus " Jonathan Woithe
2007-02-20  0:05 ` Jonathan Woithe [this message]

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=200702200005.l1K05tJi016929@turbo.physics.adelaide.edu.au \
    --to=jwoithe@physics.adelaide.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: PCI: Bus is behind transparent bridge' \
    /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

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).