From: Daniel Jordan <daniel.m.jordan@oracle.com>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: Daniel Jordan <daniel.m.jordan@oracle.com>,
Robin Murphy <robin.murphy@arm.com>,
mark.rutland@arm.com, jiangshanlai@gmail.com,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
tj@kernel.org, Will Deacon <will@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: WARNING: at kernel/workqueue.c:1473 __queue_work+0x3b8/0x3d0
Date: Thu, 8 Oct 2020 13:07:36 -0400 [thread overview]
Message-ID: <20201008170736.h3ajky2wgonbfred@ca-dmjordan1.us.oracle.com> (raw)
In-Reply-To: <20201007194117.GA4859@Red>
On Wed, Oct 07, 2020 at 09:41:17PM +0200, Corentin Labbe wrote:
> I have added CONFIG_FTRACE=y and your second patch.
> The boot log can be seen at http://kernel.montjoie.ovh/108789.log
>
> But it seems the latest dump_stack addition flood a bit.
Heh, sorry for making it spew, there wasn't such a flood when I tried. Your
output is sufficiently incriminating, so I'll go post the fix now.
> I have started to read ftrace documentation, but if you have a quick what to do in /sys/kernel/debug/tracing, it will be helpfull.
Sure, you can view the trace in /sys/kernel/debug/tracing/trace and
kernel-parameters.txt has the boot options documented.
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Jordan <daniel.m.jordan@oracle.com>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: mark.rutland@arm.com, Will Deacon <will@kernel.org>,
jiangshanlai@gmail.com, linux-kernel@vger.kernel.org,
Daniel Jordan <daniel.m.jordan@oracle.com>,
linux-crypto@vger.kernel.org, tj@kernel.org,
Robin Murphy <robin.murphy@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: WARNING: at kernel/workqueue.c:1473 __queue_work+0x3b8/0x3d0
Date: Thu, 8 Oct 2020 13:07:36 -0400 [thread overview]
Message-ID: <20201008170736.h3ajky2wgonbfred@ca-dmjordan1.us.oracle.com> (raw)
In-Reply-To: <20201007194117.GA4859@Red>
On Wed, Oct 07, 2020 at 09:41:17PM +0200, Corentin Labbe wrote:
> I have added CONFIG_FTRACE=y and your second patch.
> The boot log can be seen at http://kernel.montjoie.ovh/108789.log
>
> But it seems the latest dump_stack addition flood a bit.
Heh, sorry for making it spew, there wasn't such a flood when I tried. Your
output is sufficiently incriminating, so I'll go post the fix now.
> I have started to read ftrace documentation, but if you have a quick what to do in /sys/kernel/debug/tracing, it will be helpfull.
Sure, you can view the trace in /sys/kernel/debug/tracing/trace and
kernel-parameters.txt has the boot options documented.
_______________________________________________
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-10-08 17:00 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
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 [this message]
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=20201008170736.h3ajky2wgonbfred@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=robin.murphy@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 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.