From: Zhao Yakui <yakui.zhao@intel.com>
To: Valdis.Kletnieks@vt.edu
Cc: Dave Young <hidave.darkstar@gmail.com>,
lenb@kernel.org, linux-acpi@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: pnpacpi : exceeded the max number of IO resources
Date: Fri, 30 Nov 2007 16:14:14 +0800 [thread overview]
Message-ID: <1196410454.19722.39.camel@yakui_zhao.sh.intel.com> (raw)
In-Reply-To: <22018.1196404859@turing-police.cc.vt.edu>
On Fri, 2007-11-30 at 01:40 -0500, Valdis.Kletnieks@vt.edu wrote:
> On Fri, 30 Nov 2007 10:21:28 +0800, Zhao Yakui said:
> > Thanks for the acpidump & dmesg.
> > In the acpidump there are so many IO resource definitions in the device
> > of mem2 and the number exceeds the predefined number(24).
>
> On a semi-related note, I'm seeing 7 of these at each boot on a Dell Latitude D820:
>
> pnpacpi: exceeded the max number of mem resources: 12
>
> 2.6.24-rc3-mm2 does it, it didn't do it for 2.6.23-mm1.
>
> pnp-increase-the-maximum-number-of-resources.patch raised it from 4 to 12, but
> I don't understand why it didn't complain at 4 in 23-mm1, but it does at 12 now.
In the 23-mm1 there is no such debug info. When the number of mem
resource (for one Pnp device) defined by BIOS exceeds the predefined
constant, the mem resource can't be added. But it won't report this
case.
In the 24-mm2 the PnP constant is raised and the debug info is added.
When the number exceeds the predifined constant, it will give the debug
info.
Thanks.
>
next prev parent reply other threads:[~2007-11-30 8:04 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 9:11 pnpacpi : exceeded the max number of IO resources 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 [this message]
2007-11-30 2:18 ` Rene Herman
2007-11-30 2:32 ` Shaohua Li
2007-11-30 10:14 ` [PATCH] Set pnp_init_resource_table, pnp_resource_change, pnp_manual_config_dev deprecated Thomas Renninger
2007-11-30 17:27 ` Rene Herman
2008-01-16 21:56 ` Len Brown
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
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
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=1196410454.19722.39.camel@yakui_zhao.sh.intel.com \
--to=yakui.zhao@intel.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=hidave.darkstar@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).