From: Daniel Jordan <daniel.m.jordan@oracle.com>
To: Will Deacon <will@kernel.org>
Cc: Daniel Jordan <daniel.m.jordan@oracle.com>,
Corentin Labbe <clabbe.montjoie@gmail.com>,
tj@kernel.org, jiangshanlai@gmail.com, mark.rutland@arm.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org
Subject: Re: WARNING: at kernel/workqueue.c:1473 __queue_work+0x3b8/0x3d0
Date: Fri, 28 Feb 2020 10:33:31 -0500 [thread overview]
Message-ID: <20200228153331.uimy62rat2tdxxod@ca-dmjordan1.us.oracle.com> (raw)
In-Reply-To: <20200228123311.GE3275@willie-the-truck>
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
next prev parent reply other threads:[~2020-02-28 15:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 20:48 WARNING: at kernel/workqueue.c:1473 __queue_work+0x3b8/0x3d0 Corentin Labbe
2020-02-18 16:35 ` Daniel Jordan
2020-02-20 9:03 ` Corentin Labbe
2020-02-21 17:42 ` Daniel Jordan
2020-02-28 12:33 ` Will Deacon
2020-02-28 15:33 ` Daniel Jordan [this message]
2020-03-01 17:53 ` Corentin Labbe
2020-03-02 17:25 ` Daniel Jordan
2020-03-02 18:00 ` Robin Murphy
2020-03-03 21:30 ` Daniel Jordan
2020-03-03 22:43 ` Eric Biggers
2020-03-06 16:12 ` Daniel Jordan
2020-10-01 17:50 ` Corentin Labbe
2020-10-05 17:09 ` Daniel Jordan
2020-10-07 19:41 ` Corentin Labbe
2020-10-08 17:07 ` Daniel Jordan
2020-03-03 7:48 ` Corentin Labbe
2020-03-03 21:31 ` Daniel Jordan
2020-09-25 18:12 ` Corentin Labbe
2020-09-30 18:18 ` Daniel Jordan
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=20200228153331.uimy62rat2tdxxod@ca-dmjordan1.us.oracle.com \
--to=daniel.m.jordan@oracle.com \
--cc=clabbe.montjoie@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=tj@kernel.org \
--cc=will@kernel.org \
/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).