From mboxrd@z Thu Jan 1 00:00:00 1970 From: Benjamin Herrenschmidt Subject: Re: [PATCH] Remove process freezer from suspend to RAM pathway Date: Sun, 08 Jul 2007 10:40:46 +1000 Message-ID: <1183855247.3388.231.camel@localhost.localdomain> References: <1183779845.3388.206.camel@localhost.localdomain> <20070707114917.GC2789@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070707114917.GC2789@elf.ucw.cz> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.linux-foundation.org Errors-To: linux-pm-bounces@lists.linux-foundation.org To: Pavel Machek Cc: Matthew Garrett , linux-kernel@vger.kernel.org, Kyle Moffett , linux-pm@lists.linux-foundation.org List-Id: linux-pm@vger.kernel.org On Sat, 2007-07-07 at 13:49 +0200, Pavel Machek wrote: > And anyway I believe that current issue (fuse deadlocks with s2ram) > should be present on powerbooks, too... it is just way harder to > trigger. All that is neccessary is fused (or one of its helpers) to > get frozen by accessing suspended device. I don't see any fuse specific issue without a freezer, but I see generic issues such as kmalloc blocking in a driver with a mutex held etc... but I've talked about these already. They have nothing to do with the freezer though. Ben.