From: "Kyle Manna" <kyle@kylemanna.com>
To: "Qiuxu Zhuo" <qiuxu.zhuo@intel.com>,
"Tony Luck" <tony.luck@intel.com>,
"Borislav Petkov" <bp@alien8.de>,
"Jason Baron" <jbaron@akamai.com>
Cc: "James Jernigan" <jameswestonjernigan@gmail.com>,
"James Morse" <james.morse@arm.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Robert Richter" <rric@kernel.org>, "Yi1 Lai" <yi1.lai@intel.com>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] EDAC/ie31200: Add two more Intel Alder Lake-S SoCs for EDAC support
Date: Fri, 01 Aug 2025 07:52:14 -0700 [thread overview]
Message-ID: <f9c0fd21-591e-4fd0-a13e-35cdc1aa063d@app.fastmail.com> (raw)
In-Reply-To: <e3bc0591-7ebf-4738-8848-599edd11c10d@app.fastmail.com>
On Thu, Jul 24, 2025, at 19:23, Kyle Manna wrote:
> Hi Qiuxu,
>
> On Thu, Jul 24, 2025, at 07:31, Zhuo, Qiuxu wrote:
>> Do you have access to these machines to load the ie31200_edac
>> driver with your patch? If yes, would you take dmesg logs?
>
> I have access to a i5-12600K, here are the logs that I observed:
>
> $ dmesg | rg -i -e edac -e ecc -e ie31200 | rg -v systemd | rg edac
> [ 14.379905] caller ie31200_init_one+0x1b5/0x480 [ie31200_edac]
> mapping multiple BARs
> [ 14.382709] EDAC MC0: Giving out device to module ie31200_edac
> controller IE31200: DEV 0000:00:00.0 (INTERRUPT)
> [ 14.383042] EDAC MC1: Giving out device to module ie31200_edac
> controller IE31200_1: DEV 0000:00:00.0 (INTERRUPT)
>
> I posted additional logs from sysfs and "ras-mc-ctl" here[0] after I
> learned that support was added for related processors as well as
> discussion with other users trying to get W680 + ECC working.
>
> [0]
> https://forums.servethehome.com/index.php?threads/intel-w680-ddr5-and-ecc-reporting.42559/#post-470425
>
>
>>> diff --git a/drivers/edac/ie31200_edac.c b/drivers/edac/ie31200_edac.c index
>>> a53612be4b2f..2078c12bbed2 100644
>>> --- a/drivers/edac/ie31200_edac.c
>>> +++ b/drivers/edac/ie31200_edac.c
>>> @@ -94,6 +94,8 @@
>>>
>>> /* Alder Lake-S */
>>> #define PCI_DEVICE_ID_INTEL_IE31200_ADL_S_1 0x4660
>>> +#define PCI_DEVICE_ID_INTEL_IE31200_ADL_S_2 0x4668
>>> +#define PCI_DEVICE_ID_INTEL_IE31200_ADL_S_3 0x4648
>>>
>>
>> I didn't find the place in your spec above that indicates these
>> two CPUs with these two DIDs have Out-Of-Band ECC capabilities.
>> Could you point it out to me?
>
> This Intel CPU page[1] lists ECC memory support and the same on the
> Intel W680 chipset page[2]. The datasheet was used to confirm the
> DIDs[3] were valid.
>
> [1]
> https://www.intel.com/content/www/us/en/products/sku/134589/intel-core-i512600k-processor-20m-cache-up-to-4-90-ghz/specifications.html
> [2]
> https://www.intel.com/content/www/us/en/products/sku/218834/intel-w680-chipset/specifications.html
> [3]
> https://edc.intel.com/content/www/us/en/design/ipla/software-development-platforms/client/platforms/alder-lake-desktop/12th-generation-intel-core-processors-datasheet-volume-1-of-2/011/device-ids/
>
> Given that you added the i9-12900k (0x4660) in 180f091224a00 and I've
> personally verified the i5-12600k (0x4648) is working (see dmesg logs
> above), I've added the i7-12700k (0x4668) to assist future users.
Hi Qiuxu and Borislav,
I saw a pull request[0] for a 14th gen version of the same chips and would love to get these 12th gen chips included as well.
Anything I can do to help this along?
[0] https://lore.kernel.org/lkml/20250728141521.GAaIeF-XYJVbfOQdT6@fat_crate.local/
Thanks!
- Kyle
next prev parent reply other threads:[~2025-08-01 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-24 6:44 [PATCH 1/1] EDAC/ie31200: Add two more Intel Alder Lake-S SoCs for EDAC support Kyle Manna
2025-07-24 14:31 ` Zhuo, Qiuxu
2025-07-25 2:23 ` Kyle Manna
2025-08-01 14:52 ` Kyle Manna [this message]
2025-08-01 15:57 ` Zhuo, Qiuxu
2025-08-01 15:50 ` Zhuo, Qiuxu
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=f9c0fd21-591e-4fd0-a13e-35cdc1aa063d@app.fastmail.com \
--to=kyle@kylemanna.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=jameswestonjernigan@gmail.com \
--cc=jbaron@akamai.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=qiuxu.zhuo@intel.com \
--cc=rric@kernel.org \
--cc=tony.luck@intel.com \
--cc=yi1.lai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox