From: Rene Herman <rene.herman@keyaccess.nl>
To: Dave Young <hidave.darkstar@gmail.com>
Cc: lenb@kernel.org, linux-acpi@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Zhao Yakui <yakui.zhao@intel.com>,
Li Shaohua <shaohua.li@intel.com>,
Bjorn Helgaas <bjorn.helgaas@hp.com>,
Thomas Renninger <trenn@suse.de>
Subject: Re: pnpacpi : exceeded the max number of IO resources
Date: Fri, 30 Nov 2007 03:18:11 +0100 [thread overview]
Message-ID: <474F72E3.4040608@keyaccess.nl> (raw)
In-Reply-To: <a8e1da0711290111m65b071cft90b4361ec0155096@mail.gmail.com>
On 29-11-07 10:11, Dave Young wrote:
> The pnpacpi rsparser.c report warnings of:
> exceeded the max number of IO resources: 24
>
> dmesg|grep exceeded|wc
> 66 594 3564
Heavens... (added CCs of people who just upped it from 8 -- I suppose the
problem is not new then?)
Rene.
next prev parent reply other threads:[~2007-11-30 2:18 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
2007-11-30 2:18 ` Rene Herman [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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=474F72E3.4040608@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=bjorn.helgaas@hp.com \
--cc=hidave.darkstar@gmail.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.