From: Alistair John Strachan <s0348365@sms.ed.ac.uk>
To: "Miles Lane" <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, "Andrew Morton" <akpm@osdl.org>
Subject: Re: 2.6.17-rc5-mm2 -- PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 'pci=assign-busses')
Date: Thu, 1 Jun 2006 20:45:29 +0100 [thread overview]
Message-ID: <200606012045.29146.s0348365@sms.ed.ac.uk> (raw)
In-Reply-To: <a44ae5cd0606010752n637c6411l805115f8170f0ebb@mail.gmail.com>
On Thursday 01 June 2006 15:52, Miles Lane wrote:
> ACPI: setting ELCR to 0200 (from 0c38)
> PM: Adding info for No Bus:platform
> NET: Registered protocol family 16
> ACPI: bus type pci registered
> PCI: PCI BIOS revision 2.10 entry at 0xfd9c2, last bus=2
> Setting up standard PCI resources
> ACPI: Subsystem revision 20060310
> ACPI: Interpreter enabled
> ACPI: Using PIC for interrupt routing
> PM: Adding info for acpi:acpi
> ACPI: PCI Root Bridge [PCI0] (0000:00)
> PCI: Probing PCI hardware (bus 00)
> PM: Adding info for No Bus:pci0000:00
> Boot video device is 0000:00:02.0
> PCI quirk: region 1000-107f claimed by ICH4 ACPI/GPIO/TCO
> PCI quirk: region 1180-11bf claimed by ICH4 GPIO
> PCI: Ignoring BAR0-3 of IDE controller 0000:00:1f.1
> 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
Is this an HP/Compaq notebook by any chance?
--
Cheers,
Alistair.
Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.
next prev parent reply other threads:[~2006-06-01 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 14:52 Miles Lane
2006-06-01 16:53 ` Andrew Morton
2006-06-01 21:07 ` Greg KH
2006-06-01 21:35 ` Alessandro Suardi
2006-06-01 19:45 ` Alistair John Strachan [this message]
2006-06-01 20:30 ` Miles Lane
2006-06-01 20:55 ` Alistair John Strachan
2006-06-01 21:31 ` Greg KH
2006-06-01 21:59 ` Alistair John Strachan
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=200606012045.29146.s0348365@sms.ed.ac.uk \
--to=s0348365@sms.ed.ac.uk \
--cc=akpm@osdl.org \
--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®