From: Tejun Heo <tj@kernel.org>
To: kernel test robot <ying.huang@linux.intel.com>
Cc: lkp@01.org, LKML <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Chris Mason <clm@fb.com>, Michal Hocko <mhocko@suse.com>,
Ulrich Obergfell <uobergfe@redhat.com>,
Don Zickus <dzickus@redhat.com>
Subject: Re: [lkp] [workqueue] 82607adcf9: BUG: workqueue lockup - pool cpus=0 flags=0x4 nice=0 stuck for 42s!
Date: Mon, 15 Feb 2016 13:59:12 -0500 [thread overview]
Message-ID: <20160215185912.GJ3965@htj.duckdns.org> (raw)
In-Reply-To: <87y4ao6qx3.fsf@yhuang-dev.intel.com>
Hello,
On Sun, Feb 14, 2016 at 09:07:04AM +0800, kernel test robot wrote:
> FYI, we noticed the below changes on
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> commit 82607adcf9cdf40fb7b5331269780c8f70ec6e35 ("workqueue: implement lockup detector")
>
>
> [ 75.684302] virtio-pci 0000:00:06.0: virtio_pci: leaving for legacy driver
> [ 88.791869] ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 11
> [ 88.795120] virtio-pci 0000:00:07.0: virtio_pci: leaving for legacy driver
> [ 90.789792] BUG: workqueue lockup - pool cpus=0 flags=0x4 nice=0 stuck for 42s!
> [ 90.794158] Showing busy workqueues and worker pools:
> [ 90.796507] workqueue cgroup_pidlist_destroy: flags=0x0
> [ 90.798976] pwq 0: cpus=0 node=0 flags=0x0 nice=0 active=1/1
Was the VM not executing for a long time? I can't think why
cgroup_pidlist_destroy would hang for over 40s.
Thanks.
--
tejun
prev parent reply other threads:[~2016-02-15 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-14 1:07 [lkp] [workqueue] 82607adcf9: BUG: workqueue lockup - pool cpus=0 flags=0x4 nice=0 stuck for 42s! kernel test robot
2016-02-15 18:59 ` Tejun Heo [this message]
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=20160215185912.GJ3965@htj.duckdns.org \
--to=tj@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=clm@fb.com \
--cc=dzickus@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=mhocko@suse.com \
--cc=uobergfe@redhat.com \
--cc=ying.huang@linux.intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox