From: Corentin Labbe <clabbe.montjoie@gmail.com> To: Daniel Jordan <daniel.m.jordan@oracle.com> Cc: tj@kernel.org, jiangshanlai@gmail.com, will@kernel.org, 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: Thu, 20 Feb 2020 10:03:50 +0100 [thread overview] Message-ID: <20200220090350.GA19858@Red> (raw) In-Reply-To: <20200218163504.y5ofvaejleuf5tbh@ca-dmjordan1.us.oracle.com> On Tue, Feb 18, 2020 at 11:35:04AM -0500, Daniel Jordan wrote: > Hi Corentin, > > On Mon, Feb 17, 2020 at 09:48:03PM +0100, Corentin Labbe wrote: > > When running some CI test jobs (targeting crypto tests), I always get the following WARNING: > > Can you be more specific about which test triggers this? I used the config > option you mention and failed to reproduce after doing the boot-time crypto > tests and running various tcrypt incantations. > Hello It appears before any user space start. But according to the "Modules linked", probably ghash is already loaded and perhaps tested. Removing GHASH lead to: [ 7.920931] ------------[ cut here ]------------ [ 7.920955] WARNING: CPU: 1 PID: 120 at kernel/workqueue.c:1469 __queue_work+0x370/0x388 [ 7.920960] Modules linked in: ccm And removing CCM lead to [ 7.798877] ------------[ cut here ]------------ [ 7.798902] WARNING: CPU: 2 PID: 127 at kernel/workqueue.c:1469 __queue_work+0x370/0x388 [ 7.798907] Modules linked in: ctr So it confirm that the problem is not related to the tested crypto algorithm. > > [ 7.886361] ------------[ cut here ]------------ > > [ 7.886388] WARNING: CPU: 2 PID: 147 at kernel/workqueue.c:1473 __queue_work+0x3b8/0x3d0 > > [ 7.886394] Modules linked in: ghash_generic > > [ 7.886409] CPU: 2 PID: 147 Comm: modprobe Not tainted 5.6.0-rc1-next-20200214-00068-g166c9264f0b1-dirty #545 > > I was using just plain next-20200214. Can't find 166c9264f0b1, what tag/branch > were you using exactly? > The pasted example has some commit to try to debug it. 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. But for reproductability on different hardware, I agree it is difficult. For the moment, I got it only on Allwinner H5, A64, H6 SoCs and imx8q. [ 6.611449] ------------[ cut here ]------------ [ 6.613234] WARNING: CPU: 1 PID: 157 at /srv/data/clabbe/linux-next/kernel/workqueue.c:1471 __queue_work+0x324/0x3b0 [ 6.623809] Modules linked in: ghash_generic [ 6.628101] CPU: 1 PID: 157 Comm: modprobe Not tainted 5.6.0-rc2-next-20200220 #82 [ 6.635710] Hardware name: NXP i.MX8MNano DDR4 EVK board (DT) I tried amlogic boards and some qemu "virt" without success. (I have added linux-crypto@vger.kernel.org to the CC)
WARNING: multiple messages have this Message-ID (diff)
From: Corentin Labbe <clabbe.montjoie@gmail.com> To: Daniel Jordan <daniel.m.jordan@oracle.com> Cc: mark.rutland@arm.com, jiangshanlai@gmail.com, linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org, tj@kernel.org, will@kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: WARNING: at kernel/workqueue.c:1473 __queue_work+0x3b8/0x3d0 Date: Thu, 20 Feb 2020 10:03:50 +0100 [thread overview] Message-ID: <20200220090350.GA19858@Red> (raw) In-Reply-To: <20200218163504.y5ofvaejleuf5tbh@ca-dmjordan1.us.oracle.com> On Tue, Feb 18, 2020 at 11:35:04AM -0500, Daniel Jordan wrote: > Hi Corentin, > > On Mon, Feb 17, 2020 at 09:48:03PM +0100, Corentin Labbe wrote: > > When running some CI test jobs (targeting crypto tests), I always get the following WARNING: > > Can you be more specific about which test triggers this? I used the config > option you mention and failed to reproduce after doing the boot-time crypto > tests and running various tcrypt incantations. > Hello It appears before any user space start. But according to the "Modules linked", probably ghash is already loaded and perhaps tested. Removing GHASH lead to: [ 7.920931] ------------[ cut here ]------------ [ 7.920955] WARNING: CPU: 1 PID: 120 at kernel/workqueue.c:1469 __queue_work+0x370/0x388 [ 7.920960] Modules linked in: ccm And removing CCM lead to [ 7.798877] ------------[ cut here ]------------ [ 7.798902] WARNING: CPU: 2 PID: 127 at kernel/workqueue.c:1469 __queue_work+0x370/0x388 [ 7.798907] Modules linked in: ctr So it confirm that the problem is not related to the tested crypto algorithm. > > [ 7.886361] ------------[ cut here ]------------ > > [ 7.886388] WARNING: CPU: 2 PID: 147 at kernel/workqueue.c:1473 __queue_work+0x3b8/0x3d0 > > [ 7.886394] Modules linked in: ghash_generic > > [ 7.886409] CPU: 2 PID: 147 Comm: modprobe Not tainted 5.6.0-rc1-next-20200214-00068-g166c9264f0b1-dirty #545 > > I was using just plain next-20200214. Can't find 166c9264f0b1, what tag/branch > were you using exactly? > The pasted example has some commit to try to debug it. 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. But for reproductability on different hardware, I agree it is difficult. For the moment, I got it only on Allwinner H5, A64, H6 SoCs and imx8q. [ 6.611449] ------------[ cut here ]------------ [ 6.613234] WARNING: CPU: 1 PID: 157 at /srv/data/clabbe/linux-next/kernel/workqueue.c:1471 __queue_work+0x324/0x3b0 [ 6.623809] Modules linked in: ghash_generic [ 6.628101] CPU: 1 PID: 157 Comm: modprobe Not tainted 5.6.0-rc2-next-20200220 #82 [ 6.635710] Hardware name: NXP i.MX8MNano DDR4 EVK board (DT) I tried amlogic boards and some qemu "virt" without success. (I have added linux-crypto@vger.kernel.org to the CC) _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-02-20 9:03 UTC|newest] Thread overview: 39+ 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-17 20:48 ` Corentin Labbe 2020-02-18 16:35 ` Daniel Jordan 2020-02-18 16:35 ` Daniel Jordan 2020-02-20 9:03 ` Corentin Labbe [this message] 2020-02-20 9:03 ` Corentin Labbe 2020-02-21 17:42 ` Daniel Jordan 2020-02-21 17:42 ` Daniel Jordan 2020-02-28 12:33 ` Will Deacon 2020-02-28 12:33 ` Will Deacon 2020-02-28 15:33 ` Daniel Jordan 2020-02-28 15:33 ` Daniel Jordan 2020-03-01 17:53 ` Corentin Labbe 2020-03-01 17:53 ` Corentin Labbe 2020-03-02 17:25 ` Daniel Jordan 2020-03-02 17:25 ` Daniel Jordan 2020-03-02 18:00 ` Robin Murphy 2020-03-02 18:00 ` Robin Murphy 2020-03-03 21:30 ` Daniel Jordan 2020-03-03 21:30 ` Daniel Jordan 2020-03-03 22:43 ` Eric Biggers 2020-03-03 22:43 ` Eric Biggers 2020-03-06 16:12 ` Daniel Jordan 2020-03-06 16:12 ` Daniel Jordan 2020-10-01 17:50 ` Corentin Labbe 2020-10-05 17:09 ` Daniel Jordan 2020-10-05 17:09 ` Daniel Jordan 2020-10-07 19:41 ` Corentin Labbe 2020-10-07 19:41 ` Corentin Labbe 2020-10-08 17:07 ` Daniel Jordan 2020-10-08 17:07 ` Daniel Jordan 2020-03-03 7:48 ` Corentin Labbe 2020-03-03 7:48 ` Corentin Labbe 2020-03-03 21:31 ` Daniel Jordan 2020-03-03 21:31 ` Daniel Jordan 2020-09-25 18:12 ` Corentin Labbe 2020-09-25 18:12 ` Corentin Labbe 2020-09-30 18:18 ` Daniel Jordan 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=20200220090350.GA19858@Red \ --to=clabbe.montjoie@gmail.com \ --cc=daniel.m.jordan@oracle.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.