From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: Arnd Bergmann <arnd@kernel.org>
Cc: Len Brown <len.brown@intel.com>,
Ricardo Neri <ricardo.neri-calderon@linux.intel.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Daniel Lezcano <daniel.lezcano@linaro.org>,
Amit Kucheria <amitk@kernel.org>, Zhang Rui <rui.zhang@intel.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: x86/mce/therm_throt incorrect THERM_STATUS_CLEAR_CORE_MASK?
Date: Thu, 02 Jun 2022 09:25:57 -0700 [thread overview]
Message-ID: <079945077b128fcc3cb470e9d52267f7ac763b7a.camel@linux.intel.com> (raw)
In-Reply-To: <CAK8P3a1mHe3TkZa443fzsPnGUP1XT3w-DN3U5KAL6NBhc2nEsw@mail.gmail.com>
On Thu, 2022-06-02 at 18:18 +0200, Arnd Bergmann wrote:
> On Thu, Jun 2, 2022 at 5:52 PM srinivas pandruvada
> <srinivas.pandruvada@linux.intel.com> wrote:
> >
> > On Thu, 2022-06-02 at 11:19 +0200, Arnd Bergmann wrote:
> > > I have a Xeon W-2265 (family 6, model 85, stepping 7) that
> > > started
> > > constantly spewing messages from the therm_throt driver after one
> > > core overheated:
> > >
> > I think this is a Cascade Lake system. Have you tried the latest
> > micro-
> > code?
>
> Thanks for your quick reply. I have installed the latest microcode
> 0x5003302
> now (manually, because the version provided by the distro was still
> using
> version 0x5003102).
>
> After that, I tried writing the value 0x2a80 from userspace, and
> that did not cause a trap, so I assume that fixed it.
>
Thanks for reporting.
I am aware of this issue and should be fixed by microcode update.
Thanks,
Srinivas
> It's hard to be sure, as the system has only run into the broken
> state twice during its life, and now it's fine. I'll reply here if it
> ever comes back with the new microcode.
>
> Thanks a lot!
>
> Arnd
next prev parent reply other threads:[~2022-06-02 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-02 9:19 x86/mce/therm_throt incorrect THERM_STATUS_CLEAR_CORE_MASK? Arnd Bergmann
2022-06-02 15:52 ` srinivas pandruvada
2022-06-02 16:18 ` Arnd Bergmann
2022-06-02 16:25 ` srinivas pandruvada [this message]
2022-06-02 18:53 ` Arnd Bergmann
2022-06-02 20:10 ` srinivas pandruvada
2022-06-02 20:42 ` Arnd Bergmann
2022-06-02 21:13 ` srinivas pandruvada
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=079945077b128fcc3cb470e9d52267f7ac763b7a.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=amitk@kernel.org \
--cc=arnd@kernel.org \
--cc=daniel.lezcano@linaro.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=ricardo.neri-calderon@linux.intel.com \
--cc=rui.zhang@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;
as well as URLs for NNTP newsgroup(s).