Re: Runtime warnings in powerpc code

2018-12-31 Thread Benjamin Herrenschmidt
On Thu, 2018-12-27 at 11:05 -0800, Guenter Roeck wrote: > Hi, > > I am getting the attached runtime warnings when enabling certain debug > options in powerpc code. The warnings are seen with pretty much all > platforms, and all active kernel releases. > > Question: Is it worthwhile to keep buildi

Re: Runtime warnings in powerpc code

2018-12-28 Thread Guenter Roeck
Hi Scott, On Thu, Dec 27, 2018 at 07:31:33PM -0600, Scott Wood wrote: > On Thu, 2018-12-27 at 11:05 -0800, Guenter Roeck wrote: > > --- > > CONFIG_DEBUG_ATOMIC_SLEEP > > > > [ cut here ] > > do not call blocking ops when !TASK_RUNNING; state=2 set at [<(ptrval)>] > > prepa

Re: Runtime warnings in powerpc code

2018-12-27 Thread Scott Wood
On Thu, 2018-12-27 at 11:05 -0800, Guenter Roeck wrote: > --- > CONFIG_DEBUG_ATOMIC_SLEEP > > [ cut here ] > do not call blocking ops when !TASK_RUNNING; state=2 set at [<(ptrval)>] > prepare_to_wait+0x54/0xe4 > WARNING: CPU: 0 PID: 1 at kernel/sched/core.c:6099 __might_sle

Runtime warnings in powerpc code

2018-12-27 Thread Guenter Roeck
Hi, I am getting the attached runtime warnings when enabling certain debug options in powerpc code. The warnings are seen with pretty much all platforms, and all active kernel releases. Question: Is it worthwhile to keep building / testing powerpc builds with the respective debug options enabled,