Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933310AbbFWPVA (ORCPT ); Tue, 23 Jun 2015 11:21:00 -0400 Received: from mail-wi0-f175.google.com ([209.85.212.175]:38305 "EHLO mail-wi0-f175.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932328AbbFWPUx (ORCPT ); Tue, 23 Jun 2015 11:20:53 -0400 MIME-Version: 1.0 In-Reply-To: <261af597362906597365810a650c8e5c189e86da.1434684719.git.lv.zheng@intel.com> References: <261af597362906597365810a650c8e5c189e86da.1434684719.git.lv.zheng@intel.com> Date: Tue, 23 Jun 2015 17:20:51 +0200 X-Google-Sender-Auth: Z1IsTXlC1LcCk4Oov8CU2U3AiU4 Message-ID: Subject: Re: [PATCH 03/32] ACPICA: Hardware: Enable 64-bit firmware waking vector for selected FACS. From: "Rafael J. Wysocki" To: Lv Zheng Cc: "Rafael J. Wysocki" , Len Brown , Lv Zheng , Linux Kernel Mailing List , ACPI Devel Maling List , Bob Moore Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1133 Lines: 26 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? > the FACS reported by "FIRMWARE_CTRL", it only sets the firware waking > vector address of the FACS reported by "X_FIRMWARE_CTRL". Thanks, Rafael -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/