From: Thomas Gleixner <tglx@linutronix.de>
To: Corentin Labbe <clabbe.montjoie@gmail.com>
Cc: herbert@gondor.apana.org.au, mripard@kernel.org, wens@csie.org,
linux-arm-kernel@lists.infradead.org,
linux-crypto@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: crypto: sun4i-ss: error with kmap
Date: Wed, 02 Dec 2020 21:59:36 +0100 [thread overview]
Message-ID: <877dpzexfr.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <20201202195501.GA29296@Red>
On Wed, Dec 02 2020 at 20:55, Corentin Labbe wrote:
> On Tue, Dec 01, 2020 at 04:15:08PM +0100, Thomas Gleixner wrote:
>
> The result could be seen at http://kernel.montjoie.ovh/129768.log
> The log is 9Mb, but the ftrace dump seems not terminated, tell me if you need more.
Correct, the interesting entries right before the crash are missing. Can
you try to make the trace buffers smaller or wait longer before
terminating the thing?
16k buffer size per CPU should be completely sufficient. That should
give us roughly the last 100 entries per CPU.
'trace_buf_size=16k'
is the command line option for that.
Thanks,
tglx
next prev parent reply other threads:[~2020-12-02 21:00 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-01 13:01 crypto: sun4i-ss: error with kmap Corentin Labbe
2020-12-01 13:28 ` Thomas Gleixner
2020-12-01 13:52 ` Corentin Labbe
2020-12-01 14:16 ` Thomas Gleixner
2020-12-01 14:45 ` Corentin Labbe
2020-12-01 15:15 ` Thomas Gleixner
2020-12-02 19:55 ` Corentin Labbe
2020-12-02 20:59 ` Thomas Gleixner [this message]
2020-12-03 17:38 ` Corentin Labbe
2020-12-03 23:34 ` Thomas Gleixner
2020-12-04 13:26 ` Corentin Labbe
2020-12-04 15:08 ` Thomas Gleixner
2020-12-04 19:27 ` Corentin Labbe
2020-12-04 20:58 ` Thomas Gleixner
2020-12-05 18:43 ` Corentin Labbe
2020-12-05 19:48 ` Thomas Gleixner
2020-12-05 20:16 ` Julia Lawall
2020-12-06 21:40 ` Corentin Labbe
2020-12-07 0:15 ` Thomas Gleixner
2020-12-07 12:18 ` Corentin Labbe
2020-12-07 15:53 ` Thomas Gleixner
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=877dpzexfr.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=clabbe.montjoie@gmail.com \
--cc=herbert@gondor.apana.org.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=wens@csie.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