LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Greg KH <gregkh@suse.de>
Cc: linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, stable@kernel.org,
	Zhao Yakui <yakui.zhao@intel.com>,
	Li Shaohua <shaohua.li@intel.com>,
	Thomas Renninger <trenn@suse.de>, Adam Belay <ambx1@neo.rr.com>,
	Len Brown <lenb@kernel.org>
Subject: Re: Linux 2.6.23.12
Date: Thu, 10 Jan 2008 09:06:47 -0700	[thread overview]
Message-ID: <200801100906.48288.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20080110034952.GC20448@suse.de>

On Wednesday 09 January 2008 08:49:52 pm Greg KH wrote:
> On Wed, Jan 02, 2008 at 01:42:23PM -0700, Bjorn Helgaas wrote:
> > The patch below was put in 2.6.23.12 as a fix for
> > http://bugzilla.kernel.org/show_bug.cgi?id=9514.  It apparently
> > does make 9514 go away, but only by coincidence.  There are a
> > couple other ideas about fixing 9514.  My proposed patch is
> > attached in the bugzilla.
> > 
> > The .12 patch reduces the number of resources we reserve from
> > 24 to 8 ioport regions and from 12 to 4 mmio regions per PNP device.
> > It also removes a warning about regions we ignore.
> 
> That patch was merely a revert of a prior patch, it did not "do"
> anything new at all :)
> 
> > Obviously, we want to reserve ALL the regions for PNP devices,
> > and Thomas is working on a patch for that (which I hope will be
> > ready for 2.6.25).  But in the meantime, the .12 patch makes it
> > more likely that we will have resource conflicts with PNP devices.
> > 
> > http://bugzilla.kernel.org/show_bug.cgi?id=9630 appears to be
> > such a conflict.
> > 
> > I think the patch below should be removed from the stable series.
> 
> What do you mean "removed"?  It was a revert of a prior patch, as this
> patch was reported to cause real problems.
> 
> Do you want me to add it back, and then add another patch?  If so, can
> you please send the requested patches to stable@kernel.org so I can do
> it?

Stepping back, the biggest part of the problem is that I replaced the
ACPI motherboard driver, which reserved all resources, with the PNP
motherboard driver, which currently can reserve only a limited number
of resources, because I didn't realize that restriction.

So we've had a variety of problems, and we've tried to address them
with hacks like increasing the PNP limits.  I think we need to put
back the ACPI motherboard driver until we have dynamic PNP resources.
We will also need an it87 change to deal with
http://bugzilla.kernel.org/show_bug.cgi?id=9514.

I'll work these up and post them soon.

Bjorn

      reply	other threads:[~2008-01-10 16:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-18 22:45 Greg Kroah-Hartman
2007-12-18 22:46 ` Greg Kroah-Hartman
2008-01-02 20:42   ` Bjorn Helgaas
2008-01-03  1:16     ` Shaohua Li
2008-01-10  3:49     ` Greg KH
2008-01-10 16:06       ` Bjorn Helgaas [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=200801100906.48288.bjorn.helgaas@hp.com \
    --to=bjorn.helgaas@hp.com \
    --cc=akpm@linux-foundation.org \
    --cc=ambx1@neo.rr.com \
    --cc=gregkh@suse.de \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    --cc=stable@kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=trenn@suse.de \
    --cc=yakui.zhao@intel.com \
    --subject='Re: Linux 2.6.23.12' \
    /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).