From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Miles Lane <miles.lane@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Len Brown <len.brown@intel.com>, Pavel Machek <pavel@ucw.cz>,
"Rafael J. Wysocki" <rjw@sisk.pl>, Tejun Heo <tj@kernel.org>,
Linux PM mailing list <linux-pm@vger.kernel.org>
Subject: Re: 3.2.0-rc4+ (Linus GIT af968e29acd91ebeb4224e899202c46c93171ecd) -- Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze, wq_busy=0):
Date: Sat, 03 Dec 2011 12:25:19 +0530 [thread overview]
Message-ID: <4ED9C7D7.5030300@linux.vnet.ibm.com> (raw)
In-Reply-To: <CAHFgRy_ae70MZOgY8q3i36NJh42=GK=XP=EA=ktxgXiFzjY49w@mail.gmail.com>
On 12/03/2011 09:22 AM, Miles Lane wrote:
> While reading a file in sysfs, I suspended tried to suspend the machine and got:
>
> [ 1058.644957] PM: Syncing filesystems ... done.
> [ 1059.670167] Freezing user space processes ...
> [ 1079.681175] Freezing of tasks failed after 20.01 seconds (1 tasks
> refusing to freeze, wq_busy=0):
> [ 1079.682077] head D ffff88013a753680 5328 9761 9402 0x00800004
> [ 1079.682086] ffff88011b15fd28 0000000000000046 0000000000000006
> ffffffff8160d020
> [ 1079.682095] ffff880100000000 ffff88013a7532d0 ffff88011b15ffd8
> ffff88011b15ffd8
> [ 1079.682102] 0000000000010bc0 ffff88013a7532d0 ffffffff81372d96
> 000000013a7532d0
> [ 1079.682110] Call Trace:
> [ 1079.682120] [<ffffffff81372d96>] ? __mutex_lock_common+0x26e/0x41e
> [ 1079.682126] [<ffffffff8137241a>] schedule+0x55/0x57
> [ 1079.682131] [<ffffffff81372dbf>] __mutex_lock_common+0x297/0x41e
> [ 1079.682137] [<ffffffff810c675d>] ? lock_memory_hotplug+0x20/0x22
> [ 1079.682142] [<ffffffff810c675d>] ? lock_memory_hotplug+0x20/0x22
> [ 1079.682149] [<ffffffff8137302d>] mutex_lock_nested+0x36/0x3b
> [ 1079.682153] [<ffffffff810c675d>] lock_memory_hotplug+0x20/0x22
^^^^^^^^^^^^^^^^^^
Wow! There, Tejun, did you see that? That is just what we fixed in
https://lkml.org/lkml/2011/11/21/334 !! :-)
But since Rafael kept it for the next merge window, we hit this failure
in 3.2-rc4.
Well, atleast for once I am feeling extremely happy that we *actually*
fixed a problem _before_ hitting it! :-)
Miles, thanks for the report. Can you please try the patch given in the
above link?
> [ 1079.682160] [<ffffffff810c53e7>] show_slab_objects+0xfc/0x1e5
> [ 1079.682166] [<ffffffff810c550e>] partial_show+0xe/0x10
> [ 1079.682171] [<ffffffff810c23b7>] slab_attr_show+0x1d/0x21
> [ 1079.682177] [<ffffffff811235c9>] sysfs_read_file+0xb7/0x13c
> [ 1079.682183] [<ffffffff810ccdd3>] vfs_read+0xa0/0xc7
> [ 1079.682188] [<ffffffff810ce0d3>] ? fget_light+0x35/0x97
> [ 1079.682194] [<ffffffff810cce3f>] sys_read+0x45/0x69
> [ 1079.682199] [<ffffffff81378d3b>] system_call_fastpath+0x16/0x1b
>
Regards,
Srivatsa S. Bhat
IBM Linux Technology Center
next prev parent reply other threads:[~2011-12-03 6:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 3:52 3.2.0-rc4+ (Linus GIT af968e29acd91ebeb4224e899202c46c93171ecd) -- Freezing of tasks failed after 20.01 seconds (1 tasks refusing to freeze, wq_busy=0): Miles Lane
2011-12-03 6:55 ` Srivatsa S. Bhat [this message]
2011-12-03 15:37 ` Miles Lane
2011-12-03 16:20 ` Srivatsa S. Bhat
2011-12-03 16:44 ` Srivatsa S. Bhat
2011-12-03 17:17 ` Miles Lane
2011-12-03 17:37 ` Srivatsa S. Bhat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4ED9C7D7.5030300@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=miles.lane@gmail.com \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
--cc=tj@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.