diff options
author | Julian Anastasov <ja@ssi.bg> | 2012-02-23 22:40:43 +0200 |
---|---|---|
committer | Greg Kroah-Hartman <gregkh@linuxfoundation.org> | 2012-04-13 08:14:06 -0700 |
commit | 618f8985e7f0ff20f23660f3d1ebbe34fec0a996 (patch) | |
tree | 7caa123f04134ba78d016e249b051004852b43a3 /scripts | |
parent | f622c87aa350b3be25c98937dc4ae850aee5dee8 (diff) | |
download | kernel_samsung_aries-618f8985e7f0ff20f23660f3d1ebbe34fec0a996.zip kernel_samsung_aries-618f8985e7f0ff20f23660f3d1ebbe34fec0a996.tar.gz kernel_samsung_aries-618f8985e7f0ff20f23660f3d1ebbe34fec0a996.tar.bz2 |
ACPICA: Fix regression in FADT revision checks
commit 3e80acd1af40fcd91a200b0416a7616b20c5d647 upstream.
commit 64b3db22c04586997ab4be46dd5a5b99f8a2d390 (2.6.39),
"Remove use of unreliable FADT revision field" causes regression
for old P4 systems because now cst_control and other fields are
not reset to 0.
The effect is that acpi_processor_power_init will notice
cst_control != 0 and a write to CST_CNT register is performed
that should not happen. As result, the system oopses after the
"No _CST, giving up" message, sometimes in acpi_ns_internalize_name,
sometimes in acpi_ns_get_type, usually at random places. May be
during migration to CPU 1 in acpi_processor_get_throttling.
Every one of these settings help to avoid this problem:
- acpi=off
- processor.nocst=1
- maxcpus=1
The fix is to update acpi_gbl_FADT.header.length after
the original value is used to check for old revisions.
https://bugzilla.kernel.org/show_bug.cgi?id=42700
https://bugzilla.redhat.com/show_bug.cgi?id=727865
Signed-off-by: Julian Anastasov <ja@ssi.bg>
Acked-by: Bob Moore <robert.moore@intel.com>
Signed-off-by: Len Brown <len.brown@intel.com>
Cc: Jonathan Nieder <jrnieder@gmail.com>
Cc: Josh Boyer <jwboyer@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions