linux-kernel - Re: 2.6.30: hibernation/swsusp lockup due to acpi-cpufreq

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]

Message-Id: <200906160216.29537.rjw@sisk.pl>
Date:	Tue, 16 Jun 2009 02:16:28 +0200
From:	"Rafael J. Wysocki" <rjw@...k.pl>
To:	Johannes Stezenbach <js@...21.net>,
	Andrew Morton <akpm@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org, Dave Jones <davej@...hat.com>,
	Pavel Machek <pavel@....cz>,
	ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
	Len Brown <lenb@...nel.org>,
	Venki Pallipadi <venkatesh.pallipadi@...el.com>,
	Arjan van de Ven <arjan@...radead.org>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: 2.6.30: hibernation/swsusp lockup due to acpi-cpufreq

On Tuesday 16 June 2009, Johannes Stezenbach wrote:
> Hi,
> 
> on my aging Thinkpad T42p resume from hibernation
> fails in 2.6.30. There is a backtrace on suspend prior
> to writing out the disk image, but I cannot capture
> it due to lack of a serial port on the T42p. On
> resume the machine is dead after reading the image
> from disk.
> 
> I've bisected this to:
> 
>  commit 01599fca6758d2cd133e78f87426fc851c9ea725
>  Author: Andrew Morton <akpm@...ux-foundation.org>
>  Date:   Mon Apr 13 10:27:49 2009 -0700
> 
>     cpufreq: use smp_call_function_[single|many]() in acpi-cpufreq.c
> 
> I see in git log that this commit is known broken, but the
> resume on my machine is still broken in 2.6.30.
> 
> If I disable CONFIG_X86_ACPI_CPUFREQ suspend/resume works in 2.6.30.

Thanks a lot for bisecting this!

Is it the reason for the enabling of interrupts during cpufreq_suspend()?

/me wonders

Is there anything we can do to fix this quickly?

Rafael
--
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/