From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1752063AbbHRIum (ORCPT <rfc822;w@1wt.eu>);
	Tue, 18 Aug 2015 04:50:42 -0400
Received: from mga14.intel.com ([192.55.52.115]:1362 "EHLO mga14.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1750950AbbHRIuk (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Tue, 18 Aug 2015 04:50:40 -0400
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.15,700,1432623600"; 
   d="scan'208";a="786198031"
Message-ID: <55D2F2AD.20208@intel.com>
Date: Tue, 18 Aug 2015 16:54:05 +0800
From: Yu Chen <yu.c.chen@intel.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: Pavel Machek <pavel@ucw.cz>
CC: Ingo Molnar <mingo@kernel.org>, rjw@rjwysocki.net, tglx@linutronix.de,
        mingo@redhat.com, hpa@zytor.com, rui.zhang@intel.com, x86@kernel.org,
        linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86, suspend: Save/restore THERM_CONTROL register for
 suspend
References: <1439800192-3034-1-git-send-email-yu.c.chen@intel.com> <20150817101115.GA27204@gmail.com> <20150817132726.GA11047@amd> <55D2972C.3030709@intel.com> <20150818080218.GA17017@amd>
In-Reply-To: <20150818080218.GA17017@amd>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Hi!
On 08/18/2015 04:02 PM, Pavel Machek wrote:
> Hi!
>
>>>>> A bug is reported(https://bugzilla.redhat.com/show_bug.cgi?id=1227208)
>>>
>>> Access denied :-(
>>>
>> Might need to register for accessing.
>>>
>>> What HW is this on?
>>>
>> Intel Braswell and Broadwell, detail for Broadwell:
>> Platform: MayanCity
>> Processor: 2x BROADWELL BDX_EP A0 QHPR
>> Chipset: Wellsburg B1 QR7E
>
> So it is desktop board?
>
It is a server of Xeon family.

>>> Doing this unconditionally is asking for trouble. Blacklist entry with
>>> affected BIOS info might be acceptable, but...
>>>
>> you mean a quirk here(accroding to dmi info ,etc)?
>
> Yes, please.
Will do. thanks
> 									Pavel
>

Best Regards,
Yu