diff options
| author | Bob Moore <robert.moore@intel.com> | 2007-04-28 20:53:50 -0400 |
|---|---|---|
| committer | Len Brown <len.brown@intel.com> | 2007-04-28 20:55:06 -0400 |
| commit | 79fff270026dc46634563a29b99e4034028ee919 (patch) | |
| tree | ddc0f97ebc7c756cecbd824b4d0b7162f1e7cb6f /fs/proc/array.c | |
| parent | de46c33745f5e2ad594c72f2cf5f490861b16ce1 (diff) | |
| download | kernel-crypto-79fff270026dc46634563a29b99e4034028ee919.tar.gz kernel-crypto-79fff270026dc46634563a29b99e4034028ee919.tar.xz kernel-crypto-79fff270026dc46634563a29b99e4034028ee919.zip | |
ACPICA: clear fields reserved before FADT r3
Linux-2.6.21 stopped booting on a P4/HT because Linux
wrote the FADT.CST_CNT value to the SMI_CMD.
Apparently this stumbled over some SMM instability,
such as confusing SMM when invoking it from cpu1.
Linux did this because even though the r2 FADT reserves
the CST_CNT field, this BIOS set that field and Linux
used it.
Turns out that up through 2.6.20 we explicitly cleared
cst_control for r2 FADTs. So here we go back to doing that,
plus also clear some additional fields that are reserved
until FADT r3.
http://bugzilla.kernel.org/show_bug.cgi?id=8346
Signed-off-by: Bob Moore <robert.moore@intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
Diffstat (limited to 'fs/proc/array.c')
0 files changed, 0 insertions, 0 deletions