- To: Jonathan Nieder <jrnieder@xxxxxxxxx>
- Subject: Re: [3.0.y, 3.2.y, 3.3.y] Re: [PATCH 04/76] ACPICA: Fix regression in FADT revision checks
- From: Josh Boyer <jwboyer@xxxxxxxxx>
- Date: Tue, 3 Apr 2012 16:15:32 -0400
- Cc: Len Brown <len.brown@xxxxxxxxx>, Greg Kroah-Hartman <greg@xxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, stable@xxxxxxxxxxxxxxx, linux-acpi@xxxxxxxxxxxxxxx, Julian Anastasov <ja@xxxxxx>, linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx, wzab@xxxxxxxxxxxxx
- Delivered-to: linux-pm@xxxxxxxxxxxxxxxxxxxxxxxx
- In-reply-to: <20120403195804.GA19239@burratino>
- References: <09f98a825a821f7a3f1b162f9ed023f37213a63b.1333101989.git.len.brown@intel.com> <1333102459-23750-1-git-send-email-lenb@kernel.org> <3e80acd1af40fcd91a200b0416a7616b20c5d647.1333101989.git.len.brown@intel.com> <CA+5PVA4EBdoxgSrYKYRnaO2qSXDP_rxeQEogD+6jkKPi8sQB-g@mail.gmail.com> <20120403195804.GA19239@burratino>
On Tue, Apr 3, 2012 at 3:58 PM, Jonathan Nieder <jrnieder@xxxxxxxxx> wrote:
> Hi Greg,
>
> Josh Boyer wrote:
>> On Fri, Mar 30, 2012 at 6:13 AM, Len Brown <lenb@xxxxxxxxxx> wrote:
>
>>> From: Julian Anastasov <ja@xxxxxx>
>>>
>>> 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 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@xxxxxx>
>>> Acked-by: Bob Moore <robert.moore@xxxxxxxxx>
>>> Signed-off-by: Len Brown <len.brown@xxxxxxxxx>
>>
>> This one should go into the stable trees.
>
> Please apply
>
> 3e80acd1af40 "ACPICA: Fix regression in FADT revision checks"
>
> which is in linus's master to the 3.0.y, 3.2.y, and 3.3.y series to
> fix this old boot problem. (Many affected people disabled HT in the
> BIOS to work around it in the meantime.)
>
> WZab (cc-ed) has tested that the patch addresses the problem when
> applied to the 3.2.y and 3.3.y branches. [1] has details.
We've had this applied in Fedora on 3.2 and 3.3 for a while now as
well.
josh
_______________________________________________
linux-pm mailing list
linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx
https://lists.linuxfoundation.org/mailman/listinfo/linux-pm
[Netdev]
[Ethernet Bridging]
[Linux Wireless]
[CPU Freq]
[Kernel Newbies]
[Fedora Kernel]
[Security]
[Linux for Hams]
[Netfilter]
[Bugtraq]
[Photo]
[Yosemite]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux RAID]
[Linux Admin]
[Samba]
[Video 4 Linux]
[Linux Resources]
[Free Dating]
[Archives]