linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: pat-lkml <pat-lkml@erley.org>, Bernhard Kaindl <bk@suse.de>
Cc: linux-kernel@vger.kernel.org, gregkh@suse.de,
	linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: PCI Quirk / Hidden Bus Report
Date: Mon, 30 Jul 2007 13:55:05 +0200	[thread overview]
Message-ID: <20070730115505.GP16817@stusta.de> (raw)
In-Reply-To: <469EDBA3.2000404@erley.org>

Bernhard?

cu
Adrian


On Wed, Jul 18, 2007 at 11:33:55PM -0400, pat-lkml wrote:
> I received:
> 
> PCI: Bus #0b (-#0e) is hidden behind transparent bridge #0a (-#0a) (try
> 'pci=assign-busses')
> Please report the result to linux-kernel to fix this permanently
> 
> in my dmesg in 2.6.22, and am reporting it.  Context of message follows.
>  Full dmesg output available on request.  This is a Clevo d900t laptop
> motherboard, and everything works perfectly on it.
> 
> Pat Erley
> 
> --
> 
> ENABLING IO-APIC IRQs
> ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
> checking TSC synchronization [CPU#0 -> CPU#1]: passed.
> Brought up 2 CPUs
> migration_cost=22
> NET: Registered protocol family 16
> EISA bus registered
> ACPI: bus type pci registered
> PCI: BIOS Bug: MCFG area at e0000000 is not E820-reserved
> PCI: Not using MMCONFIG.
> PCI: PCI BIOS revision 2.10 entry at 0xfd951, last bus=10
> PCI: Using configuration type 1
> 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)
> 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
> PCI: Bus #0b (-#0e) is hidden behind transparent bridge #0a (-#0a) (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.PEG_._PRT]
> ACPI: PCI Interrupt Routing Table [\_SB_.PCI0.PCIB._PRT]
> ACPI: PCI Interrupt Link [LNKA] (IRQs 10) *11
> ACPI: PCI Interrupt Link [LNKB] (IRQs 11) *10
> ACPI: PCI Interrupt Link [LNKC] (IRQs 10) *5
> ACPI: PCI Interrupt Link [LNKD] (IRQs 11) *10
> ACPI: PCI Interrupt Link [LNKE] (IRQs *10)
> ACPI: PCI Interrupt Link [LNKF] (IRQs *11)
> ACPI: PCI Interrupt Link [LNKG] (IRQs 10) *0, disabled.
> ACPI: PCI Interrupt Link [LNKH] (IRQs *11)
> Linux Plug and Play Support v0.97 (c) Adam Belay
> pnp: PnP ACPI init
> ACPI: bus type pnp registered
> pnp: PnP ACPI: found 12 devices
> ACPI: ACPI bus type pnp unregistered
> SCSI subsystem initialized
> libata version 2.21 loaded.
> PCI: Using ACPI for IRQ routing
> PCI: If a device doesn't work, try "pci=routeirq".  If it helps, post a
> report
> Time: tsc clocksource has been installed.

  reply	other threads:[~2007-07-30 11:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-19  3:33 PCI Quirk / Hidden Bus Report pat-lkml
2007-07-30 11:55 ` Adrian Bunk [this message]
2007-07-30 13:44   ` pat-lkml
2007-07-30 15:04   ` Jeffrey Hundstad

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=20070730115505.GP16817@stusta.de \
    --to=bunk@stusta.de \
    --cc=bk@suse.de \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=pat-lkml@erley.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).