linux-kernel - Re: [PATCH v2] ACPI: Leave Bus Master Arbitration enabled for suspend/resume

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 08 Jul 2012 13:43:59 -0700
From:	"Octavio Alvarez" <alvarezp@...arezp.com>
To:	"Jonathan Nieder" <jrnieder@...il.com>,
	"Bob Moore" <robert.moore@...el.com>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Cc:	"Adrian Knoth" <adi@...omp.erfurt.thur.de>,
	"Shaohua Li" <shli@...nel.org>, "Len Brown" <len.brown@...el.com>,
	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] ACPI: Leave Bus Master Arbitration enabled for
 suspend/resume

On Sun, 08 Jul 2012 13:08:19 -0700, Rafael J. Wysocki <rjw@...k.pl> wrote:

>> This is an old suspend/resume lockup fix:
>>
>> 	commit 2780cc4660e1
>> 	Author: Len Brown <len.brown@...el.com>
>> 	Date:   Thu Dec 23 13:43:30 2004 -0500
>>
>> 	    [ACPI] Fix suspend/resume lockup issue
>> 	    by leaving Bus Master Arbitration enabled.
>> 	    The ACPI spec mandates it be disabled only for C3.
>>
>> The bug snuck back in in commit 2feec47d4c5f (ACPICA: ACPI 5: Support
>> for new FADT SleepStatus, SleepControl registers, 2012-02-14),
>> presumably by copy/pasting a copy of the code without that fix for the
>> legacy case.
>>
>> On affected machines, after that commit, the machine locks up hard on
>> resume from suspend.  The same fix as seven years ago still works.
>>
> Applied to the linux-next branch of the linux-pm.git tree.
>
> I think I'll push it for v3.6, since the bug is serious and is a  
> regression.
>
> Bob, I think we should incorporate this into ACPICA, shouldn't we?

This bug affects since 3.4. I'd like to ask for this to be applied in the
stable branches too, considering Jonathan's comments that this is a replay
of an old and proven fix.

(I don't know if 3.3 is affected too. I know 3.2 is not affected by this.)

Thanks.

-- 
Octavio.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/