From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752807Ab1HPSMO (ORCPT ); Tue, 16 Aug 2011 14:12:14 -0400 Received: from ogre.sisk.pl ([217.79.144.158]:45518 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751952Ab1HPSMM (ORCPT ); Tue, 16 Aug 2011 14:12:12 -0400 From: "Rafael J. Wysocki" To: "Carlos R. Mafra" Subject: Re: 3.0-rc2 failed s2ram: Freezing of tasks failed after 20.00 seconds Date: Tue, 16 Aug 2011 20:13:55 +0200 User-Agent: KMail/1.13.6 (Linux/3.1.0-rc2+; KDE/4.6.0; x86_64; ; ) Cc: LKML , Linux PM mailing list References: <20110816094245.GA2042@Pilar.site> In-Reply-To: <20110816094245.GA2042@Pilar.site> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201108162013.55341.rjw@sisk.pl> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tuesday, August 16, 2011, Carlos R. Mafra wrote: > I started testing 3.0-rc2 yesterday and after a few successful suspend to ram > it did not suspend anymore and I got this: > > PM: Syncing filesystems ... done. > PM: Preparing system for mem sleep > Freezing user space processes ... > Freezing of tasks failed after 20.00 seconds (1 tasks refusing to freeze, wq_busy=0): > udisks-daemon D ffff8800a641e5d0 0 5848 5845 0x00800004 > ffff8800a6741928 0000000000000082 ffff880000000000 00000000000105c0 > ffff8800a641e200 00000000000105c0 ffff8800a6741fd8 00000000000105c0 > 00000000000105c0 ffff8800a6740000 ffff8800a6741fd8 00000000000105c0 > Call Trace: > [] schedule_timeout+0x1c5/0x230 > [] ? schedule+0x399/0x8a0 > [] wait_for_common+0xc0/0x160 > [] ? try_to_wake_up+0x290/0x290 > [] ? _raw_spin_unlock_irq+0x2a/0x40 > [] wait_for_completion+0x18/0x20 > [] flush_work+0x2b/0x40 > [] ? do_work_for_cpu+0x30/0x30 > [] flush_delayed_work+0x46/0x50 > [] disk_clear_events+0x76/0x110 > [] check_disk_change+0x32/0x80 > [] sd_open+0xb9/0x190 > [] __blkdev_get+0x91/0x3d0 > [] ? blkdev_get+0x340/0x340 > [] blkdev_get+0x4e/0x340 > [] ? do_lookup+0xb7/0x380 > [] ? blkdev_get+0x340/0x340 > [] blkdev_open+0x5d/0x80 > [] __dentry_open+0x130/0x320 > [] nameidata_to_filp+0x71/0x80 > [] do_last+0xb1/0x800 > [] path_openat+0xd3/0x3f0 > [] ? kobject_put+0x27/0x60 > [] ? put_device+0x12/0x20 > [] do_filp_open+0x44/0xa0 > [] ? alloc_fd+0xf4/0x150 > [] do_sys_open+0xfc/0x1e0 > [] ? filp_close+0x56/0x80 > [] sys_open+0x1b/0x20 > [] system_call_fastpath+0x16/0x1b > > Restarting tasks ... done. > video LNXVIDEO:01: Restoring backlight state > acpid: 1 client rule loaded > EXT4-fs (sda2): re-mounted. Opts: discard,commit=600 > INFO: task udisks-daemon:5848 blocked for more than 120 seconds. > "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > udisks-daemon D ffff8800a641e5d0 0 5848 5845 0x00000004 > ffff8800a6741928 0000000000000082 ffff880000000000 00000000000105c0 > ffff8800a641e200 00000000000105c0 ffff8800a6741fd8 00000000000105c0 > 00000000000105c0 ffff8800a6740000 ffff8800a6741fd8 00000000000105c0 > Call Trace: > [] schedule_timeout+0x1c5/0x230 > [] ? schedule+0x399/0x8a0 > [] wait_for_common+0xc0/0x160 > [] ? try_to_wake_up+0x290/0x290 > [] ? _raw_spin_unlock_irq+0x2a/0x40 > [] wait_for_completion+0x18/0x20 > [] flush_work+0x2b/0x40 > [] ? do_work_for_cpu+0x30/0x30 > [] flush_delayed_work+0x46/0x50 > [] disk_clear_events+0x76/0x110 > [] check_disk_change+0x32/0x80 > [] sd_open+0xb9/0x190 > [] __blkdev_get+0x91/0x3d0 > [] ? blkdev_get+0x340/0x340 > [] blkdev_get+0x4e/0x340 > [] ? do_lookup+0xb7/0x380 > [] ? blkdev_get+0x340/0x340 > [] blkdev_open+0x5d/0x80 > [] __dentry_open+0x130/0x320 > [] nameidata_to_filp+0x71/0x80 > [] do_last+0xb1/0x800 > [] path_openat+0xd3/0x3f0 > [] ? kobject_put+0x27/0x60 > [] ? put_device+0x12/0x20 > [] do_filp_open+0x44/0xa0 > [] ? alloc_fd+0xf4/0x150 > [] do_sys_open+0xfc/0x1e0 > [] ? filp_close+0x56/0x80 > [] sys_open+0x1b/0x20 > [] system_call_fastpath+0x16/0x1b > > > and there are some more of these traces in the logs, but they all look the > same. It looks like udisks-daemon is waiting for a completion that's never completed. Do you use any removable storage devices? Rafael