From: Andrew Luebke <andrew.luebke@gmail.com>
To: Borislav Petkov <bp@alien8.de>
Cc: Tony Luck <tony.luck@intel.com>,
Aristeu Rozanski <aris@redhat.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] EDAC/i5000: Fix the slot loop and re-enable the driver
Date: Thu, 12 Nov 2026 08:58:40 -0800 [thread overview]
Message-ID: <d259e498-5cc6-4e23-a589-cdffce1764e9@gmail.com> (raw)
In-Reply-To: <20261112001752.GCavUFsCwZIRkfLI7T@fat_crate.local>
> was all the energy you've spent on fixing this
> - especially the AI tokens - worth the effort?
For me, yes. I still test and repair old medical equipment built on the
xw8400 and xw6400 (as well as even older systems), and FB-DIMMs are the
part that fails. Having EDAC name the slot beats swapping sticks.
> can I jot you down as the one who will be testing any future
> patches for that driver?
Yes, please do. I have the hardware on the bench, with single- and
dual-ranked FB-DIMMs, and can test patches on request.
On 11/11/26 4:17 PM, Borislav Petkov wrote:
> On Wed, Nov 11, 2026 at 03:25:27PM -0800, Andrew Luebke wrote:
>> Analysis and test kernels were prepared with LLM help; the tests ran on my
>> hardware.
> Just out of curiosity, was all the energy you've spent on fixing this
> - especially the AI tokens - worth the effort?
>
> This chip is documented on something called the retro web:
> https://theretroweb.com/chips/317 and it says it is from 2006 and it sports
> DDR2 memory. So that is retro alright.
>
> The HP xw8400 has a whopping quad-core Xeon in it.
>
> But whatever...
>
> Now, if you really wanna do this, can I jot you down as the one who will be
> testing any future patches for that driver?
>
next prev parent reply other threads:[~2026-11-12 16:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 23:25 [PATCH 0/2] EDAC/i5000: Fix the slot loop and re-enable the driver Andrew Luebke
2026-11-11 23:25 ` [PATCH 1/2] i5000_edac: fix slot number passed to determine_mtr() Andrew Luebke
2026-11-11 23:25 ` [PATCH 2/2] Revert "EDAC/i5000: Mark as BROKEN" Andrew Luebke
2026-11-12 0:17 ` [PATCH 0/2] EDAC/i5000: Fix the slot loop and re-enable the driver Borislav Petkov
2026-11-12 16:58 ` Andrew Luebke [this message]
2026-11-12 18:00 ` Borislav Petkov
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=d259e498-5cc6-4e23-a589-cdffce1764e9@gmail.com \
--to=andrew.luebke@gmail.com \
--cc=aris@redhat.com \
--cc=bp@alien8.de \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--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.