From: Andrew Morton <akpm@linux-foundation.org>
To: "Francis Moreau" <francis.moro@gmail.com>
Cc: linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>
Subject: Re: PCI probing failure in 2.6.21-rc3
Date: Thu, 15 Mar 2007 11:06:47 -0800 [thread overview]
Message-ID: <20070315110647.710bff5f.akpm@linux-foundation.org> (raw)
In-Reply-To: <38b2ab8a0703140147s24bfc656o1bbff4abc405d61d@mail.gmail.com>
> On Wed, 14 Mar 2007 09:47:42 +0100 "Francis Moreau" <francis.moro@gmail.com> wrote:
> I already posted this issue but it was on a 2.6.19.7 kernel
> (2.6.19-1.2911.6.5.fc6 to be accurate). So it doesn't seem to be a
> regression.
>
> During boot the console shows up this:
>
> [...]
> 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
> 0000:00:1f.2: trying to change BAR0 from 0000 to 01F0
> 0000:00:1f.2: trying to change BAR1 from 0000 to 03F4
> 0000:00:1f.2: trying to change BAR2 from 0000 to 0170
> 0000:00:1f.2: trying to change BAR3 from 0000 to 0374
> Boot video device is 0000:01:00.0
> 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
> [...]
>
> I haven't time to test 'pci=assign-busses' option, I'll do it later,
> but I wanted to report this ASAP.
Greg, could we please either
a) start doing something about these reports or
b) publish sufficient info to permit others to do something about these
reports or
c) remove the printk?
Thanks.
next prev parent reply other threads:[~2007-03-15 19:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-14 8:47 PCI probing failure in 2.6.21-rc3 Francis Moreau
2007-03-15 19:06 ` Andrew Morton [this message]
2007-03-15 21:06 ` Francis Moreau
2007-03-21 12:32 ` Francis Moreau
2007-03-23 22:49 ` Greg KH
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=20070315110647.710bff5f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=francis.moro@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.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