[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200228153331.uimy62rat2tdxxod@ca-dmjordan1.us.oracle.com>
Date: Fri, 28 Feb 2020 10:33:31 -0500
From: Daniel Jordan <daniel.m.jordan@...cle.com>
To: Will Deacon <will@...nel.org>
Cc: Daniel Jordan <daniel.m.jordan@...cle.com>,
Corentin Labbe <clabbe.montjoie@...il.com>, tj@...nel.org,
jiangshanlai@...il.com, 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 Fri, Feb 28, 2020 at 12:33:12PM +0000, Will Deacon wrote:
> On Fri, Feb 21, 2020 at 12:42:23PM -0500, Daniel Jordan wrote:
> > 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.
>
> Any joy with this? It sounded to me like the issue also happens on a
> mainline kernel. If this is the case, have you managed to bisect it?
I managed to get recent mainline (rawhide) booting days ago but wasn't able to
reproduce on a rpi 3b+.
My plan had been to try debug-by-email next, but then something exploded
internally and I haven't had time for it yet. Still intending to help once the
explosion is contained, provided someone can't get to it sooner.
thanks,
Daniel
Powered by blists - more mailing lists