From: Len Brown <lenb@kernel.org>
To: Doug Chapman <doug.chapman@hp.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: [PATCH] increase ACPI_MAX_REFERENCE_COUNT for larger systems
Date: Thu, 21 Dec 2006 14:59:36 -0500 [thread overview]
Message-ID: <200612211459.36486.lenb@kernel.org> (raw)
In-Reply-To: <1166721103.13323.12.camel@dchapman.boston.redhat.com>
Applied.
thanks,
-Len
On Thursday 21 December 2006 12:11, Doug Chapman wrote:
> We have some new larger ia64 systems in HP that trip over the
> ACPI_MAX_REFERENCE_COUNT limit which triggers a large number of these
> debug messages:
>
> ACPI Warning (utdelete-0397): Large Reference Count (XXX) in object e0000a0ff6797ab0 [20060707]
>
> This was increased once in the past as described in this very brief thread:
>
> http://www.mail-archive.com/linux-acpi@vger.kernel.org/msg00890.html
>
>
> signed-off-by: Doug Chapman <doug.chapman@hp.com>
>
> --- linux-2.6.20-rc1/include/acpi/acconfig.h.prev 2006-12-21 12:06:56.000000000 -0500
> +++ linux-2.6.20-rc1/include/acpi/acconfig.h 2006-12-21 12:07:49.000000000 -0500
> @@ -105,7 +105,7 @@
>
> /* Maximum object reference count (detects object deletion issues) */
>
> -#define ACPI_MAX_REFERENCE_COUNT 0x800
> +#define ACPI_MAX_REFERENCE_COUNT 0x1000
>
> /* Size of cached memory mapping for system memory operation region */
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2006-12-21 20:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 17:11 [PATCH] increase ACPI_MAX_REFERENCE_COUNT for larger systems Doug Chapman
2006-12-21 19:59 ` Len Brown [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=200612211459.36486.lenb@kernel.org \
--to=lenb@kernel.org \
--cc=doug.chapman@hp.com \
--cc=linux-acpi@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 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.