Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932765AbbFXAOZ (ORCPT ); Tue, 23 Jun 2015 20:14:25 -0400 Received: from mga09.intel.com ([134.134.136.24]:25942 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751870AbbFXAOS (ORCPT ); Tue, 23 Jun 2015 20:14:18 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,669,1427785200"; d="scan'208";a="733378673" From: "Zheng, Lv" To: "Rafael J. Wysocki" CC: "Wysocki, Rafael J" , "Brown, Len" , Lv Zheng , "Linux Kernel Mailing List" , ACPI Devel Maling List , "Moore, Robert" Subject: RE: [PATCH 03/32] ACPICA: Hardware: Enable 64-bit firmware waking vector for selected FACS. Thread-Topic: [PATCH 03/32] ACPICA: Hardware: Enable 64-bit firmware waking vector for selected FACS. Thread-Index: AQHQrchAji6zwa7NYUmJDlzwTOY9w526ySog Date: Wed, 24 Jun 2015 00:13:43 +0000 Message-ID: <1AE640813FDE7649BE1B193DEA596E88027335D6@SHSMSX101.ccr.corp.intel.com> References: <261af597362906597365810a650c8e5c189e86da.1434684719.git.lv.zheng@intel.com> In-Reply-To: Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.239.127.40] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id t5O0EZB7013792 Content-Length: 1514 Lines: 36 Hi, Rafael > From: rjwysocki@gmail.com [mailto:rjwysocki@gmail.com] On Behalf Of Rafael J. Wysocki > Sent: Tuesday, June 23, 2015 11:21 PM > > Hi Lv, > > On Fri, Jun 19, 2015 at 5:38 AM, Lv Zheng wrote: > > ACPICA commit 7aa598d711644ab0de5f70ad88f1e2de253115e4 > > > > The root cause of the reported bug might be one of the followings: > > 1. BIOS may favor the 64-bit firmware waking vector address when the > > version of the FACS is greater than 0 and Linux currently only supports > > resuming from the real mode, so the 64-bit firmware waking vector has > > never been set and might be invalid to BIOS while the commit enables > > higher version FACS. > > 2. BIOS may favor the FACS reported via the "FIRMWARE_CTRL" field in the > > FADT while the commit doesn't set the firmware waking vector address of > > Can you please tell me which commit this is about? It's the bisected commit on the Bugzilla entry: https://bugzilla.kernel.org/show_bug.cgi?id=74021#c23 Since the part of this series originally belongs to a regression fix series, the commit is not mentioned again here. Let me update the description. Thanks and best regards -Lv > > > the FACS reported by "FIRMWARE_CTRL", it only sets the firware waking > > vector address of the FACS reported by "X_FIRMWARE_CTRL". > > Thanks, > Rafael ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?