From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753454Ab1HQNrm (ORCPT ); Wed, 17 Aug 2011 09:47:42 -0400 Received: from mail-bw0-f46.google.com ([209.85.214.46]:57016 "EHLO mail-bw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753230Ab1HQNrk (ORCPT ); Wed, 17 Aug 2011 09:47:40 -0400 Date: Wed, 17 Aug 2011 15:47:05 +0200 From: "Carlos R. Mafra" To: "Rafael J. Wysocki" Cc: LKML , Linux PM mailing list Subject: Re: 3.0-rc2 failed s2ram: Freezing of tasks failed after 20.00 seconds Message-ID: <20110817134705.GA3160@Pilar.site> References: <20110816094245.GA2042@Pilar.site> <201108162320.28297.rjw@sisk.pl> <20110816224500.GA3152@Pilar.site> <201108171114.45096.rjw@sisk.pl> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <201108171114.45096.rjw@sisk.pl> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 17 Aug 2011 at 11:14:44 +0200, Rafael J. Wysocki wrote: > On Wednesday, August 17, 2011, Carlos R. Mafra wrote: > > On Tue, 16 Aug 2011 at 23:20:28 +0200, Rafael J. Wysocki wrote: > > > On Tuesday, August 16, 2011, Carlos R. Mafra wrote: > > > > On Tue, 16 Aug 2011 at 20:13:55 +0200, Rafael J. Wysocki wrote: > > > > > 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? > > > > > > > > Yes, external harddisks connected via USB. But none were mounted > > > > when I closed the lid to suspend. > > > > > > Were they connected to the USB ports? > > > > No. > > > > > > PS: I made a mistake in the Subject:, the kernel is 3.1-rc2 and > > > > not 3.0-rc2. > > > > > > Did 3.0 work correctly? > > > > I didn't test 3.0, but 2.6.39 always worked. > > Can you try 3.0.y too, please? It would give us the time frame the > error started to happen. I tested 3.0.2 this morning and it survived (suspended it about 5-6 times with some mount/unmount of external harddisks in between). Now I'm back to testing 3.1-rc2 and it survived the first two suspends. So this is not something which I can bisect with 100% certainty. I was hoping the above traces could somehow indicate where the problem might be. I will keep testing though.