From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 9A4D2C433EF for ; Thu, 2 Jun 2022 16:26:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237023AbiFBQ0I (ORCPT ); Thu, 2 Jun 2022 12:26:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33636 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S237010AbiFBQ0H (ORCPT ); Thu, 2 Jun 2022 12:26:07 -0400 Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6BB672B07F6; Thu, 2 Jun 2022 09:26:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1654187166; x=1685723166; h=message-id:subject:from:to:cc:date:in-reply-to: references:mime-version:content-transfer-encoding; bh=K0itMtVsdIh11uGolFyo+JgLbg/FBJd2Kzp6ffSaV2k=; b=JkqVPzyhVIlNYX8Mn0eHbll8avkwM1Y640efMMk/DW2OBnUtsTQRollV 8ftH58O4DXGBHKRxbcltiO07/zAahYJ4nzzKo2zWqCn99Jb5YzaEggmlC BhkVADyu4kjIo2JNx/FT8s5dwxcQGRqd9Emuw2cFT6WD9r2LvKoG7amnJ URJ5R605cGwepRE7bNgBELsVS1RWX5H/c7EpG5/RtIPvsJcIkOoFdUJMy leDMDc9KnA1vVrNEtSXmgvUH0Uip5aMzA01M9Ze77tfL+hlWXdROuOKG0 1HnrKKV3YUCdCa4PFWX1A45Mod46mve6V++kL8qt9hlkJODvTdcMVaNmT w==; X-IronPort-AV: E=McAfee;i="6400,9594,10366"; a="276074059" X-IronPort-AV: E=Sophos;i="5.91,271,1647327600"; d="scan'208";a="276074059" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Jun 2022 09:26:06 -0700 X-IronPort-AV: E=Sophos;i="5.91,271,1647327600"; d="scan'208";a="563381701" Received: from spandruv-desk.jf.intel.com ([10.54.75.8]) by orsmga002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 02 Jun 2022 09:26:05 -0700 Message-ID: <079945077b128fcc3cb470e9d52267f7ac763b7a.camel@linux.intel.com> Subject: Re: x86/mce/therm_throt incorrect THERM_STATUS_CLEAR_CORE_MASK? From: srinivas pandruvada To: Arnd Bergmann Cc: Len Brown , Ricardo Neri , "Rafael J. Wysocki" , Daniel Lezcano , Amit Kucheria , Zhang Rui , linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org Date: Thu, 02 Jun 2022 09:25:57 -0700 In-Reply-To: References: <6caf53e059758234ee12a236f967412f1df1f8a0.camel@linux.intel.com> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.4 (3.38.4-1.fc33) MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-pm@vger.kernel.org On Thu, 2022-06-02 at 18:18 +0200, Arnd Bergmann wrote: > On Thu, Jun 2, 2022 at 5:52 PM srinivas pandruvada > 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