LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Shaohua Li <shaohua.li@intel.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	torvalds@linux-foundation.org, stable@kernel.org,
	Zhao Yakui <yakui.zhao@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, 03 Jan 2008 09:16:55 +0800	[thread overview]
Message-ID: <1199323015.16091.1.camel@sli10-desk.sh.intel.com> (raw)
In-Reply-To: <200801021342.23763.bjorn.helgaas@hp.com>


On Wed, 2008-01-02 at 13:42 -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.
> 
> 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.
Just let you know why we increase the resource number.
http://bugzilla.kernel.org/show_bug.cgi?id=8973
we found real I/O resource conflict here and cause system hang.

Thanks,
Shaohua


  reply	other threads:[~2008-01-03  1:16 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 [this message]
2008-01-10  3:49     ` Greg KH
2008-01-10 16:06       ` Bjorn Helgaas

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=1199323015.16091.1.camel@sli10-desk.sh.intel.com \
    --to=shaohua.li@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=ambx1@neo.rr.com \
    --cc=bjorn.helgaas@hp.com \
    --cc=gregkh@suse.de \
    --cc=lenb@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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).