[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200221174223.r3y6tugavp3k5jdl@ca-dmjordan1.us.oracle.com>
Date: Fri, 21 Feb 2020 12:42:23 -0500
From: Daniel Jordan <daniel.m.jordan@...cle.com>
To: Corentin Labbe <clabbe.montjoie@...il.com>
Cc: Daniel Jordan <daniel.m.jordan@...cle.com>, tj@...nel.org,
jiangshanlai@...il.com, will@...nel.org, mark.rutland@....com,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-crypto@...r.kernel.org
Subject: Re: WARNING: at kernel/workqueue.c:1473 __queue_work+0x3b8/0x3d0
On Thu, Feb 20, 2020 at 10:03:50AM +0100, Corentin Labbe wrote:
> But I got the same with plain next (like yesterday 5.6.0-rc2-next-20200219 and tomorow 5.6.0-rc2-next-20200220) and master got the same issue.
Thanks. I've been trying to reproduce this on an arm board but it's taking a
while to get it setup since I've never used it for kernel work.
Hoping to get it up soon, though someone with a working setup may be in a
better position to help with this.
Powered by blists - more mailing lists