From: Dave Hansen <dave.hansen@intel.com>
To: Jim Mattson <jmattson@google.com>, dave.hansen@linux.intel.com
Cc: andrew.cooper3@citrix.com, len.brown@intel.com,
linux-kernel@vger.kernel.org, peterz@infradead.org,
rafael.j.wysocki@intel.com, srinivas.pandruvada@linux.intel.com,
stable@vger.kernel.org, x86@kernel.org,
meenashanmugam@google.com, eranian@google.com
Subject: Re: [PATCH] Handle Ice Lake MONITOR erratum
Date: Wed, 27 May 2026 20:36:29 -0700 [thread overview]
Message-ID: <089e8bae-73c6-47a1-a046-6ddd8610d21b@intel.com> (raw)
In-Reply-To: <20260528030604.2669758-1-jmattson@google.com>
On 5/27/26 20:06, Jim Mattson wrote:
>> The erratum is called ICX143 in the "3rd Gen Intel Xeon Scalable
>> Processors, Codename Ice Lake Specification Update". It is Intel
>> document 637780, currently available here:
>>
>> https://cdrdv2.intel.com/v1/dl/getContent/637780
> The erratum says, "Due to this erratum, the processor may hang."
>
> We are seeing some Ice Lake Xeon E5 machines panic due to hard lockups, and
> then the kdump kernel dies with "Fatal machine check from unknown source."
> Is this behavior consistent with this erratum?
That sounds like something different to me. I don't remember machine
checks being implicated for this erratum at all.
My usual rule of thumb is that machine checks mean bad hardware unless
there's a specific and compelling reason otherwise.
next prev parent reply other threads:[~2026-05-28 3:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 19:22 Dave Hansen
2025-04-21 19:32 ` Andrew Cooper
2025-04-21 23:02 ` srinivas pandruvada
2025-04-22 6:46 ` Ingo Molnar
2025-04-22 14:18 ` Dave Hansen
2025-04-22 19:35 ` Ingo Molnar
2026-05-28 3:06 ` Jim Mattson
2026-05-28 3:36 ` Dave Hansen [this message]
2026-05-28 16:03 ` Andrew Cooper
2026-05-28 17:47 ` Jim Mattson
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=089e8bae-73c6-47a1-a046-6ddd8610d21b@intel.com \
--to=dave.hansen@intel.com \
--cc=andrew.cooper3@citrix.com \
--cc=dave.hansen@linux.intel.com \
--cc=eranian@google.com \
--cc=jmattson@google.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=meenashanmugam@google.com \
--cc=peterz@infradead.org \
--cc=rafael.j.wysocki@intel.com \
--cc=srinivas.pandruvada@linux.intel.com \
--cc=stable@vger.kernel.org \
--cc=x86@kernel.org \
/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
all inboxes | Powered by JetHome®