From: Bjorn Helgaas <bjorn.helgaas@hp.com>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: Shaohua Li <shaohua.li@intel.com>,
Rene Herman <rene.herman@keyaccess.nl>,
yakui.zhao@intel.com, Chris Holvenstot <cholvenstot@comcast.net>,
linux-kernel@vger.kernel.org, trenn@suse.de,
Andrew Morton <akpm@osdl.org>
Subject: Re: pnpacpi : exceeded the max number of IO resources
Date: Wed, 5 Dec 2007 13:39:04 -0700 [thread overview]
Message-ID: <200712051339.04936.bjorn.helgaas@hp.com> (raw)
In-Reply-To: <20071204011540.GA2713@darkstar.lan>
On Monday 03 December 2007 06:15:40 pm Dave Young wrote:
> On Tue, Dec 04, 2007 at 08:55:13AM +0800, Shaohua Li wrote:
> >
> > On Mon, 2007-12-03 at 18:02 +0100, Rene Herman wrote:
> > > On 30-11-07 23:22, Rene Herman wrote:
> > >
> > > > On 30-11-07 14:14, Chris Holvenstot wrote:
> > > >
> > > >> For what it is worth I too have seen this problem this morning and it
> > > >> DOES appear to be new (in contrast to a previous comment)
> > > >>
> > > >> The message: pnpacpi: exceeded the max number of mem resources: 12
> > > >>
> > > >> is displayed each time the system is booted with the 2.6.24-rc3-git5
> > > >> kernel but is NOT displayed when booting 2.6.24-rc3-git4
> > > >>
> > > >> I have made no changes in my config file between these two kernels other
> > > >> than to accept any new defaults when running make oldconfig.
> > > >>
> > > >> If you had already narrowed it down to a change between git4 and git5 I
> > > >> apologize for wasting your time. Have to run to work now.
> > > >
> > > > Thanks, and re-added the proper CCs. Sigh...
> > > >
> > > > Well, yes, the warning is actually new as well. Previously your kernel
> > > > just silently ignored 8 more mem resources than it does now it seems.
> > > >
> > > > Given that people are hitting these limits, it might make sense to just
> > > > do away with the warning for 2.6.24 again while waiting for the dynamic
> > > > code?
> > >
> > > Ping. Should these warnings be reverted for 2.6.24?
> > Revert the warning doesn't make any sense. I'd suggest changing the IO
> > resources number bigger till Thomas's patch in.
> Agree.
> Change it to 90 works for me, But I think maybe 128 is better.
>
> include/linux/pnp.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff -upr linux/include/linux/pnp.h linux.new/include/linux/pnp.h
> --- linux/include/linux/pnp.h 2007-12-04 09:09:23.000000000 +0800
> +++ linux.new/include/linux/pnp.h 2007-12-04 09:09:40.000000000 +0800
> @@ -13,7 +13,7 @@
> #include <linux/errno.h>
> #include <linux/mod_devicetable.h>
>
> -#define PNP_MAX_PORT 24
> +#define PNP_MAX_PORT 128
> #define PNP_MAX_MEM 12
> #define PNP_MAX_IRQ 2
> #define PNP_MAX_DMA 2
I don't think we can increase PNP_MAX_PORT to 128. Only one or two
devices need that many, so just bumping the max wastes a LOT of space.
A struct resource is seven longs, so on a 32-bit system with sixteen
PNP devices, we'd be wasting (128-24)*7*4*16 = almost 47Kbytes.
In hindsight, I should not have removed drivers/acpi/motherboard.c
until we had dynamic PNP resource tables. We could revert that
change [1], but the driver's been gone since 2.6.21, so I don't
think it's that urgent. It's just that we used to silently ignore
resources past the limits, and in -mm, we now print a KERN_ERR message.
So I think we should either remove the message altogether (so we're
exactly like 2.6.23 in this regard), or at least tone it down to
a KERN_WARN or something.
And we need to get Thomas' dynamic patch into -mm ASAP :-)
Bjorn
[1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=5eca338fb510af78eee5372ff6a3525768ab913f
next prev parent reply other threads:[~2007-12-05 20:39 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-30 13:14 pnpacpi : exceeded the max number of IO resources Chris Holvenstot
2007-11-30 22:22 ` Rene Herman
2007-12-03 17:02 ` Rene Herman
2007-12-03 22:51 ` Chris Holvenstot
2007-12-04 0:55 ` Shaohua Li
2007-12-04 1:15 ` Dave Young
2007-12-05 20:39 ` Bjorn Helgaas [this message]
2007-12-19 3:07 ` Valdis.Kletnieks
2008-01-09 3:50 ` Len Brown
2008-01-09 9:34 ` Frans Pop
2008-01-09 14:47 ` Rene Herman
2008-01-16 5:55 ` Dave Young
2008-01-16 8:00 ` Rene Herman
2008-01-16 13:04 ` Rene Herman
2008-01-19 11:03 ` Frans Pop
2008-01-19 18:38 ` Bjorn Helgaas
-- strict thread matches above, loose matches on Subject: below --
2007-11-29 9:11 Dave Young
2007-11-30 1:18 ` Dave Young
2007-11-30 2:21 ` Zhao Yakui
2007-11-30 6:40 ` Valdis.Kletnieks
2007-11-30 8:14 ` Zhao Yakui
2007-11-30 2:18 ` Rene Herman
2007-11-30 2:32 ` Shaohua Li
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=200712051339.04936.bjorn.helgaas@hp.com \
--to=bjorn.helgaas@hp.com \
--cc=akpm@osdl.org \
--cc=cholvenstot@comcast.net \
--cc=hidave.darkstar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@keyaccess.nl \
--cc=shaohua.li@intel.com \
--cc=trenn@suse.de \
--cc=yakui.zhao@intel.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;
as well as URLs for NNTP newsgroup(s).