All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramses <ramses@well-founded.dev>
To: "Zhuo, Qiuxu" <qiuxu.zhuo@intel.com>
Cc: John <therealgraysky@proton.me>,
	Linux Edac <linux-edac@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Luck, Tony" <tony.luck@intel.com>
Subject: RE: Flood of edac-related errors since 6.13
Date: Mon, 10 Feb 2025 09:49:57 +0100 (CET)	[thread overview]
Message-ID: <OIj2FiD--F-9@well-founded.dev> (raw)
In-Reply-To: <CY8PR11MB7134358940D4625E5196349B89F22@CY8PR11MB7134.namprd11.prod.outlook.com>

Feb 10, 2025, 09:05 by qiuxu.zhuo@intel.com:

> Hi Ramses,
>
>> From: Ramses <>> ramses@well-founded.dev>> >
>> [...]
>>
>> Thanks for your reply!
>>
>> I recompiled the kernel with that option enabled, and attached the dmesg
>> output to this email. Let me know if I can do anything else to help debug this.
>>
>
> Thanks for helping debug the issue and taking the useful dmesg log.
> From the dmesg log, the ECC error log register of this SoC contained the
> invalid error value ~0, resulting in a flood of invalid error reports in polling mode.
>
> @Ramses & @John,
> Can you please apply the attached fix patch and see whether it fixes the issue?
> Thanks!
>
> -Qiuxu
>

I just booted into a kernel with that patch applied and I'm not getting the errors anymore, so that seems to fix the issue for me indeed!

Thanks a bunch!
Ramses



  reply	other threads:[~2025-02-10  8:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-06 22:28 Flood of edac-related errors since 6.13 Ramses
2025-02-07  3:18 ` Zhuo, Qiuxu
2025-02-07  9:25   ` Ramses
2025-02-10  8:04     ` Zhuo, Qiuxu
2025-02-10  8:49       ` Ramses [this message]
2025-02-11  1:55         ` Zhuo, Qiuxu
2025-02-11 19:47           ` John
2025-02-12  8:35             ` Zhuo, Qiuxu
  -- strict thread matches above, loose matches on Subject: below --
2025-02-09 11:50 John

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=OIj2FiD--F-9@well-founded.dev \
    --to=ramses@well-founded.dev \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=qiuxu.zhuo@intel.com \
    --cc=therealgraysky@proton.me \
    --cc=tony.luck@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.