diff options
| author | Lans Zhang <jia.zhang@windriver.com> | 2013-01-16 09:03:29 +0000 |
|---|---|---|
| committer | Rafael J. Wysocki <rafael.j.wysocki@intel.com> | 2013-01-19 01:34:43 +0100 |
| commit | 25216865392a6e1f3032855aee7407de1fe0b70c (patch) | |
| tree | 7f0f7575967c0ff85464b7540ba9ba1afe3b797c /drivers/cpufreq | |
| parent | f427e5f1cf75bba84cccdac1d8a90552d9ae1065 (diff) | |
| download | linux-3.10-25216865392a6e1f3032855aee7407de1fe0b70c.tar.gz linux-3.10-25216865392a6e1f3032855aee7407de1fe0b70c.tar.bz2 linux-3.10-25216865392a6e1f3032855aee7407de1fe0b70c.zip | |
ACPI, APEI: Fixup incorrect 64-bit access width firmware bug
The bit width check was introduced by 15afae60 (ACPI, APEI: Fix
incorrect APEI register bit width check and usage), and a fixup
for incorrect 32-bit width memory address was given by f712c71
(ACPI, APEI: Fixup common access width firmware bug). Now there
is a similar symptom:
[Firmware Bug]: APEI: Invalid bit width + offset in GAR [0x12345000/64/0/3/0]
Another bogus BIOS reports an incorrect 64-bit width in trigger table.
Thus, apply to a similar workaround for 64-bit width memory address.
Signed-off-by: Lans Zhang <jia.zhang@windriver.com>
Acked-by: Gary Hade <garyhade@us.ibm.com>
Acked-by: Myron Stowe <myron.stowe@redhat.com>
Acked-by: Jean Delvare <jdelvare@suse.de>
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Diffstat (limited to 'drivers/cpufreq')
0 files changed, 0 insertions, 0 deletions