From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Michael Witten" Subject: Re: 2.6.30: hibernation/swsusp lockup due to acpi-cpufreq Date: Sat, 04 Jul 2009 11:09:55 -0700 (PDT) Message-ID: <4a4f9af3.27015a0a.48c6.ffffa6d5@mx.google.com> References: Return-path: Received: from mail-gx0-f226.google.com ([209.85.217.226]:61852 "EHLO mail-gx0-f226.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752139AbZGDSJy (ORCPT ); Sat, 4 Jul 2009 14:09:54 -0400 In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: "Rafael J. Wysocki" Cc: Johannes Stezenbach , Andrew Morton , Venkatesh Pallipadi , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org On Tue, 16 Jun 2009 23:39:59 +0200, Rafael J. Wysocki wrote (http://www.spinics.net/lists/linux-acpi/msg22661.html): > In fact, we need to do this entire thing differently. > > The basic problem is that cpufreq_suspend() is a sysdev thing, so it will > always be called with iterrupts off and *only* for CPU0. So, it looks like > the majority of things we do there is just unnecessary (at least). What's the status? This bug is driving me nuts. Thanks, Michael Witten PS See http://groups.google.com/group/linux.kernel/browse_thread/thread/bb3f4e0fc32273c4/e83178dfc9374669