public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Andres Salomon <dilinger@queued.net>,
	"Timur I. Davletshin" <timur.davletshin@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Regressions <regressions@lists.linux.dev>,
	Linux AMD GEODE <linux-geode@lists.infradead.org>
Subject: Fwd: AMD Geode LX hardware RNG driver produces regular patterns (geode-rng.c)
Date: Thu, 7 Sep 2023 18:37:00 +0700	[thread overview]
Message-ID: <9a28c2fc-d769-4802-a1f2-77ba2cb34d25@gmail.com> (raw)

Hi,

I notice a regression report on Bugzilla [1]. Quoting from it:

> System: Alix board 2d13 (AMD Geode LX800) running OpenWrt 23.05.0-rc3 (kernel 5.15.127)
> 
> Steps to reproduce:
> 
> cat /dev/hwrng and see output. Output in console shows regular pattern, rngd daemon (from rng-tools) refuses to run because of low entropy from /dev/hwrng. Pattern doesn't change until I reboot system.
> 
> Important notice: This problem started somewhere between 4.14.267 (kernel used in OpenWrt 19.07.9) and my current 5.15.127.
> 
> OpenWrt developers recommended addressing this problem upstream since they did not alter this driver in any way.

See Bugzilla for the full thread.

Anyway, I'm adding it to regzbot:

#regzbot ^introduced: v4.14.267..v5.15.127
#regzbot title: predictable urandom output on Alix 2d13

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217882

-- 
An old man doll... just what I always wanted! - Clara

             reply	other threads:[~2023-09-07 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 11:37 Bagas Sanjaya [this message]
2023-09-10  8:54 ` Fwd: AMD Geode LX hardware RNG driver produces regular patterns (geode-rng.c) Bagas Sanjaya
2023-09-26  0:45   ` Bagas Sanjaya
2023-09-26  4:39     ` Linux regression tracking #update (Thorsten Leemhuis)

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=9a28c2fc-d769-4802-a1f2-77ba2cb34d25@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=dilinger@queued.net \
    --cc=linux-geode@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    --cc=timur.davletshin@gmail.com \
    /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