linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: Abdul Haleem <abdhalee@linux.vnet.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	mpe <mpe@ellerman.id.au>, sachinp <sachinp@linux.vnet.ibm.com>
Subject: Re: WARNING: CPU: 2 PID: 7 at kernel/workqueue.c:2041 process_one_work
Date: Tue, 13 Jun 2017 16:59:38 -0400	[thread overview]
Message-ID: <20170613205938.GC7359@htj.duckdns.org> (raw)
In-Reply-To: <1496130846.13350.19.camel@abdul.in.ibm.com>

On Tue, May 30, 2017 at 01:24:06PM +0530, Abdul Haleem wrote:
> Hi,
> 
> Test : stress-ng
> Machine : Power 8 Bare Metal
> Kernel : 4.12.0-rc3
> Config : attached
> gcc version: 4.8.5
> 
> 
> In file kernel/workqueue.c at line 2041
> 
>     /* ensure we're on the correct CPU */
>     WARN_ON_ONCE(!(pool->flags & POOL_DISASSOCIATED) &&
>              raw_smp_processor_id() != pool->cpu);
> 
> 
> WARN_ON_ONCE() is being triggered on Linus mainline kernel (4.12.0-rc3)
> when running stress-ng test.
> 
> 
> request_module: runaway loop modprobe net-pf-10
> request_module: runaway loop modprobe net-pf-10
> hrtimer: interrupt took 500359 ns
> RT Watchdog Timeout (hard): stress-ng-rlimi[80236]

Paul and Steven reported the same problem a while back.  Debugging on
the following thread.

 http://lkml.kernel.org/r/<20170501165747.GA993@linux.vnet.ibm.com>

Thanks.

-- 
tejun

      reply	other threads:[~2017-06-13 20:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-30  7:54 WARNING: CPU: 2 PID: 7 at kernel/workqueue.c:2041 process_one_work Abdul Haleem
2017-06-13 20: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=20170613205938.GC7359@htj.duckdns.org \
    --to=tj@kernel.org \
    --cc=abdhalee@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=sachinp@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).