From: "Luck, Tony" <tony.luck@intel.com>
To: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
Cc: Borislav Petkov <bp@alien8.de>, James Morse <james.morse@arm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Robert Richter <rric@kernel.org>,
Ramses <ramses@well-founded.dev>, John <therealgraysky@proton.me>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] EDAC/igen6: Fix the flood of invalid error reports
Date: Thu, 20 Feb 2025 17:14:58 -0800 [thread overview]
Message-ID: <Z7fTkuQeYANX4QtY@agluck-desk3> (raw)
In-Reply-To: <20250212083354.31919-1-qiuxu.zhuo@intel.com>
On Wed, Feb 12, 2025 at 04:33:54PM +0800, Qiuxu Zhuo wrote:
> The ECC_ERROR_LOG register of certain SoCs may contain the invalid value
> ~0, which results in a flood of invalid error reports in polling mode.
>
> Fix the flood of invalid error reports by skipping the invalid ECC error
> log value ~0.
>
> Fixes: e14232afa944 ("EDAC/igen6: Add polling support")
> Reported-by: Ramses <ramses@well-founded.dev>
> Closes: https://lore.kernel.org/all/OISL8Rv--F-9@well-founded.dev/
> Tested-by: Ramses <ramses@well-founded.dev>
> Reported-by: John <therealgraysky@proton.me>
> Closes: https://lore.kernel.org/all/p5YcxOE6M3Ncxpn2-Ia_wCt61EM4LwIiN3LroQvT_-G2jMrFDSOW5k2A9D8UUzD2toGpQBN1eI0sL5dSKnkO8iteZegLoQEj-DwQaMhGx4A=@proton.me/
> Tested-by: John <therealgraysky@proton.me>
> Signed-off-by: Qiuxu Zhuo <qiuxu.zhuo@intel.com>
Applied to RAS tree edac-drivers branch
Thanks
-Tony
prev parent reply other threads:[~2025-02-21 1:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 8:33 [PATCH 1/1] EDAC/igen6: Fix the flood of invalid error reports Qiuxu Zhuo
2025-02-12 12:08 ` [PATCH] " Markus Elfring
2025-02-12 13:44 ` Zhuo, Qiuxu
2025-02-21 1:14 ` Luck, Tony [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=Z7fTkuQeYANX4QtY@agluck-desk3 \
--to=tony.luck@intel.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=ramses@well-founded.dev \
--cc=rric@kernel.org \
--cc=therealgraysky@proton.me \
/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