From: Valdis.Kletnieks@vt.edu
To: Zhao Yakui <yakui.zhao@intel.com>
Cc: Frans Pop <elendil@planet.nl>, linux-kernel@vger.kernel.org
Subject: Re: pnpacpi: exceeded the max number of IO resources: 24
Date: Mon, 07 Jan 2008 16:32:40 -0500 [thread overview]
Message-ID: <21603.1199741560@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Mon, 07 Jan 2008 13:07:28 +0800." <1199682448.2379.12.camel@yakui_zhao.sh.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]
On Mon, 07 Jan 2008 13:07:28 +0800, Zhao Yakui said:
> The resources of PNP device are obtained by calling the _CRS method.
> Maybe some resources has been reserved. For example: Some system will
> reserve the following resources.
> BIOS-e820: 00000000fec00000 - 00000000fed40000 (reserved)
> BIOS-e820: 00000000fed45000 - 0000000100000000 (reserved)
> So the system will report that some resources can't be reserved.
...
> The error message is harmless. It only tells us that the resource
> definition of PNP device exceeds the predefined PNP constant and maybe
> there will be potential problem if some important resources can't be
> reserved. For example about 90 IOPORT resources are defined in some PNP
> device. So it will print the message. Of course it is more appropriate
> to change the message level from ERR to DEBUG.
Is it possible to add some cookie crumbs to the currently non-informative
message - things like "what address range", "what PNP devices' _CRS was
asking for it", and so on?
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
prev parent reply other threads:[~2008-01-07 21:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-24 5:12 Frans Pop
[not found] ` <1198803416.21142.7.camel@yakui_zhao.sh.intel.com>
2008-01-06 23:48 ` Frans Pop
2008-01-07 5:07 ` Zhao Yakui
2008-01-07 14:18 ` Frans Pop
2008-01-07 21:32 ` Valdis.Kletnieks [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=21603.1199741560@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®