From: Russ Anderson <rja@hpe.com>
To: "Moore, Robert" <robert.moore@intel.com>
Cc: Dimitri Sivanich <dimitri.sivanich@hpe.com>,
Russ Anderson <russ.anderson@hpe.com>,
"linux-nvdimm@lists.01.org" <linux-nvdimm@lists.01.org>,
Mike Travis <mike.travis@hpe.com>,
"Wysocki, Rafael J <rafael.j.wysocki@intel.com>,
linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-acpi@vger.kernel.org" <linux-acpi@vger.kernel.org>,
"devel@acpica.org" <devel@acpica.org>, Schmauss,
Subject: Re: [PATCH 1/1] x86, pmem, acpi: Remove excessive ACPI Large Reference Count warnings
Date: Wed, 1 Aug 2018 15:38:27 -0500 [thread overview]
Message-ID: <20180801203827.ozkvldizkpsatmg5@hpe.com> (raw)
In-Reply-To: <94F2FBAB4432B54E8AACC7DFDE6C92E3B94DED8F@ORSMSX108.amr.corp.intel.com>
On Wed, Aug 01, 2018 at 07:49:14PM +0000, Moore, Robert wrote:
> Are there any actual memory leaks, or this a consequence of the number of sockets?
It is a consequence of the number of sockets.
It is not an actual memory leak.
Thanks.
> > -----Original Message-----
> > From: Mike Travis [mailto:mike.travis@hpe.com]
> > Sent: Monday, July 30, 2018 12:56 PM
> > To: Moore, Robert <robert.moore@intel.com>; Schmauss, Erik
> > <erik.schmauss@intel.com>; Wysocki, Rafael J
> > <rafael.j.wysocki@intel.com>; Len Brown <lenb@kernel.org>
> > Cc: Russ Anderson <russ.anderson@hpe.com>; Dimitri Sivanich
> > <dimitri.sivanich@hpe.com>; Ross Zwisler <ross.zwisler@linux.intel.com>;
> > Williams, Dan J <dan.j.williams@intel.com>; Verma, Vishal L
> > <vishal.l.verma@intel.com>; Jiang, Dave <dave.jiang@intel.com>; linux-
> > acpi@vger.kernel.org; devel@acpica.org; linux-nvdimm@lists.01.org;
> > linux-kernel@vger.kernel.org
> > Subject: [PATCH 1/1] x86, pmem, acpi: Remove excessive ACPI Large
> > Reference Count warnings
> >
> > With the Intel BIOS support for 8 processor sockets with a full
> > complement of NVDIMMS potentially installable, and there are empty
> > sockets without NVDIMMS, there is an extremely large amount of the
> > following warnings:
> >
> > ACPI Warning: Large Reference Count (0x1001) in object ffff99453fc71750,
> > Type=0x0A
> >
> > On a 4 socket system with 4 NVDIMMs there were over 6000 of these
> > warning messages and it has been seem on systems from 4 to 32 sockets.
> >
> > Through some guidance from the BIOS developers and testing, it appears
> > that simply bumping up the threshold for warnings from 0x1000 to 0x2000
> > eliminates these messages. Changing them to be ACPI DEBUG messages, or
> > even removing them are other options, but it would then defeat the
> > purpose of the warnings as the problem would effectively be hidden.
> >
> > Reviewed-by: Dimitri Sivanich <dimitri.sivanich@hpe.com>
> > Tested-by: Russ Anderson <russ.anderson@hpe.com>
> > Signed-off-by: Mike Travis <mike.travis@hpe.com>
> > ---
> > include/acpi/acconfig.h | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > --- linux-4.12.orig/include/acpi/acconfig.h
> > +++ linux-4.12/include/acpi/acconfig.h
> > @@ -123,7 +123,7 @@
> >
> > /* Maximum object reference count (detects object deletion issues) */
> >
> > -#define ACPI_MAX_REFERENCE_COUNT 0x1000
> > +#define ACPI_MAX_REFERENCE_COUNT 0x2000
> >
> > /* Default page size for use in mapping memory for operation regions */
> >
> >
> > --
>
--
Russ Anderson, SuperDome Flex Linux Kernel Group Manager
HPE - Hewlett Packard Enterprise (formerly SGI) rja@hpe.com
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
next prev parent reply other threads:[~2018-08-01 20:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180730195545.795802877@stormcage.americas.sgi.com>
2018-07-30 19:55 ` [PATCH 1/1] x86, pmem, acpi: Remove excessive ACPI Large Reference Count warnings Mike Travis
2018-08-01 19:49 ` Moore, Robert
2018-08-01 20:38 ` Russ Anderson [this message]
2018-08-01 21:24 ` Moore, Robert
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=20180801203827.ozkvldizkpsatmg5@hpe.com \
--to=rja@hpe.com \
--cc=devel@acpica.org \
--cc=dimitri.sivanich@hpe.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvdimm@lists.01.org \
--cc=mike.travis@hpe.com \
--cc=robert.moore@intel.com \
--cc=russ.anderson@hpe.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).