From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751376AbdAFB1S (ORCPT ); Thu, 5 Jan 2017 20:27:18 -0500 Received: from mga04.intel.com ([192.55.52.120]:32943 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751069AbdAFB1E (ORCPT ); Thu, 5 Jan 2017 20:27:04 -0500 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.33,323,1477983600"; d="scan'208";a="46162319" Date: Thu, 5 Jan 2017 17:26:17 -0800 From: "Raj, Ashok" To: Borislav Petkov Cc: Alexander Alemayhu , Daniel J Blueman , Paul Menzel , tony.luck@intel.com, linux@leemhuis.info, len.brown@intel.com, Linux Kernel , ashok.raj@intel.com Subject: Re: Dell XPS13: MCE (Hardware Error) reported Message-ID: <20170106012617.GA28713@otc-nc-03> References: <20170105201034.GA15245@gmail.com> <20170105203146.egi3kveypclmwllp@pd.tnic> <20170105232800.GA82321@otc-brkl-03> <20170105235611.yj4ayqpg2ysibeqy@pd.tnic> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170105235611.yj4ayqpg2ysibeqy@pd.tnic> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 06, 2017 at 12:56:11AM +0100, Borislav Petkov wrote: > Oh, and it's not like the user can do anything - there's a thermald > which is supposed to deal with all that. Which is not really > trouble-free too, TBH. What happens if that thing dies? Fried CPU? > > So I say we should rip out that mce_log_therm_throt_event() and never > ever handle thermal events with MCEs. It is a bad idea. Agree, since we have both a log and another agent to deal with it, it makes no good reason to continue... Will pass this along, and have someone look at cleaning this up. Cheers, Ashok