mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Stefano Manni <stefano.manni@gmail.com>
To: barebox@lists.infradead.org
Subject: short entropy delay causes RNG hardware error
Date: Mon, 05 Aug 2024 18:01:54 +0200	[thread overview]
Message-ID: <ca751c63f894078f566cf8de12d3f5a81ce252b0.camel@gmail.com> (raw)

Hello,

on a custom board based on imx6ul once linux starts I see lot of errors
like this:

  caam_jr 2141000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error

approximately every 10 seconds. And if I try to read from device the
same error occurs:

  ~# dd if=/dev/hwrng of=/dev/null bs=1 count=1
  caam_jr 2141000.jr: 2000005b: CCB: desc idx 0: RNG: Hardware error
  dd: /dev/hwrng: Invalid argument

No errors are fired in barebox where the RNG self-test is run
succesfully:

  rng_self_test: RNG software self-test passed
  caam 2140000.crypto@2140000.of: Instantiated RNG4 SH0
  caam 2140000.crypto@2140000.of: Instantiated RNG4 SH1
  caam 2140000.crypto@2140000.of: registering rng-caam

Here [1] I found that enlarging the entroy delay may help so I tried to
do the same in barebox by changing RTSDCTL_ENT_DLY_MIN from 3200 to
4800 and it succeded, I no longer see those errors in linux and trying
to read from the device works perfectly.

The strange thing is that on another board based on imx6sx I never see
those errors.

Is it something new to you? 
May we change the delay? On linux-imx 6.6.3 3200 is still used.

Best,
Stefano

[1] 
https://lore.kernel.org/all/CAOMZO5D0m1xCfgFifKz1H+oYQSfxsfuZp4U39rPMACmzv1fvjQ@mail.gmail.com/#t





             reply	other threads:[~2024-08-05 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-05 16:01 Stefano Manni [this message]
2024-08-05 16:56 ` Ahmad Fatoum
2024-08-06  8:33   ` Stefano Manni
2024-08-06 17:00     ` Ahmad Fatoum

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=ca751c63f894078f566cf8de12d3f5a81ce252b0.camel@gmail.com \
    --to=stefano.manni@gmail.com \
    --cc=barebox@lists.infradead.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