[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200809210149.07755.elendil@planet.nl>
Date: Sun, 21 Sep 2008 01:49:05 +0200
From: Frans Pop <elendil@...net.nl>
To: Bjorn Helgaas <bjorn.helgaas@...com>
Cc: Rene Herman <rene.herman@...access.nl>,
linux-kernel@...r.kernel.org, Rene Herman <rene.herman@...il.com>,
Ingo Molnar <mingo@...e.hu>,
Thomas Gleixner <tglx@...utronix.de>,
Jesse Barnes <jbarnes@...tuousgeek.org>
Subject: Re: [bisected][resend] pnp: Huge number of "io resource overlap" messages
On Thursday 18 September 2008, Bjorn Helgaas wrote:
> On Tuesday 09 September 2008 12:31:09 pm Rene Herman wrote:
> > On 09-09-08 19:40, Bjorn Helgaas wrote:
> > > If the PCI device isn't fully initialized, it doesn't seem right to
> > > check it for resource conflicts. But I don't know how to tell
> > > that.
> >
> > His pci_resource_start() values are 0. How about just checking for
> > that?
>
> Frans, can you test Rene's patch? I think it will solve the problem
> you're seeing, and if so, we should put it in for 2.6.27. But I'd like
> to have your "Tested-by" first.
Tested against current git (v2.6.27-rc6-158-g9824b8f) and looks good.
Attached the patch with Rene's Signed-off and my Tested-by for
convenience.
I had not tested earlier as you said you wanted to better understand the
cause first. Did you get anything more about why things happen as they do
from the info I sent?
Attached also a dmesg diff for boots with the two different BIOS settings
with this kernel (with Rene's patch having filtered out the "io resource
overlap" messages).
It still clearly shows the difference in how some devices get enabled and
how their resources get assigned.
Cheers,
FJP
View attachment "quirk_system_pci_resources.diff" of type "text/x-diff" (745 bytes)
View attachment "dmesg.diff" of type "text/x-diff" (25198 bytes)
Powered by blists - more mailing lists