[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20170613205938.GC7359@htj.duckdns.org>
Date: Tue, 13 Jun 2017 16:59:38 -0400
From: Tejun Heo <tj@...nel.org>
To: Abdul Haleem <abdhalee@...ux.vnet.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@...ts.ozlabs.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
mpe <mpe@...erman.id.au>, sachinp <sachinp@...ux.vnet.ibm.com>
Subject: Re: WARNING: CPU: 2 PID: 7 at kernel/workqueue.c:2041
process_one_work
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@...ux.vnet.ibm.com>
Thanks.
--
tejun
Powered by blists - more mailing lists