Messages in this thread | | | From | "Zheng, Lv" <> | Subject | RE: [PATCH 03/32] ACPICA: Hardware: Enable 64-bit firmware waking vector for selected FACS. | Date | Wed, 24 Jun 2015 00:13:43 +0000 |
| |
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 <lv.zheng@intel.com> 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
| |