All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ken Brownfield <brownfld@irridia.com>
To: Robert Love <rml@tech9.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Continuing /dev/random problems with 2.4
Date: Fri, 1 Feb 2002 13:52:25 -0600	[thread overview]
Message-ID: <20020201135225.D8599@asooo.flowerfire.com> (raw)
In-Reply-To: <20020201031744.A32127@asooo.flowerfire.com> <1012582401.813.1.camel@phantasy> <a3enf3$93p$1@cesium.transmeta.com> <20020201133833.B8599@asooo.flowerfire.com> <1012593032.1095.7.camel@phantasy>
In-Reply-To: <1012593032.1095.7.camel@phantasy>; from rml@tech9.net on Fri, Feb 01, 2002 at 02:50:31PM -0500

On Fri, Feb 01, 2002 at 02:50:31PM -0500, Robert Love wrote:
| What is the output of `/proc/sys/kernel/random/entropy_avail' when
| programs are stalled?  Is it actually 0?

Yep, and it never raises above that -- it doesn't jump around even after
a month.

| Can you see if any programs are perhaps draining entropy in the
| background?  See what has /dev/[u]random open ... note even /dev/urandom
| uses entropy, its the same as /dev/random, except it doesn't care when
| the entropy estimate is 0.

I've scanned /proc to verify that all PIDs do not have an FD open to
/dev/random.  This was my first guess when this started -- some
developer was draining entropy in a while(1) loop.  I believe I went so
far as to go to runlevel 1 with nothing but sh and kernel threads.

That may not be comprehensive, so I'm open to other diagnostic tips.
And yes, /dev/urandom does continue to work, as expected.

Thanks!
-- 
Ken.
brownfld@irridia.com

| 	Robert Love

  reply	other threads:[~2002-02-01 19:53 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-01  9:17 Continuing /dev/random problems with 2.4 Ken Brownfield
2002-02-01 16:36 ` Andreas Dilger
2002-02-01 17:00   ` Ken Brownfield
2002-02-01 16:53 ` Robert Love
2002-02-01 17:01   ` Ken Brownfield
2002-02-04  9:28     ` Sean Hunter
2002-02-01 18:40   ` H. Peter Anvin
2002-02-01 19:38     ` Ken Brownfield
2002-02-01 19:50       ` Robert Love
2002-02-01 19:52         ` Ken Brownfield [this message]
2002-02-01 19:57       ` Andreas Dilger
2002-02-01 20:22         ` Ken Brownfield
2002-02-01 19:43     ` Andreas Dilger
2002-02-01 20:12       ` H. Peter Anvin
2002-02-01 20:28         ` Jeff Garzik
2002-02-02  1:33           ` David Wagner
2002-02-02  8:01             ` Jeff Garzik
2002-02-02  8:54           ` Kai Henningsen
2002-02-02 11:13             ` Andreas Dilger
2002-02-04 22:13         ` Bill Davidsen
2002-02-04 22:37           ` Roland Dreier
2002-02-04 22:45             ` Robert Love
2002-02-05 23:02               ` Bill Davidsen
2002-02-05 23:17                 ` Robert Love
2002-02-06 16:16                   ` Bill Davidsen
2002-02-06 16:31                     ` Need a clew WRT fig2dev Kirk Reiser
2002-02-06 16:42                       ` Adrian Bunk
2002-02-06 20:40                       ` Jeff Garzik
2002-02-09 19:45                     ` Continuing /dev/random problems with 2.4 Nix N. Nix
2002-02-03 12:51       ` Henning P. Schmiedehausen
2002-02-01 20:23     ` Peter Monta
2002-02-01 20:27       ` H. Peter Anvin
2002-02-01 20:36         ` Jeff Garzik
2002-02-01 20:33       ` Jeff Garzik
2002-02-01 20:40         ` H. Peter Anvin
2002-02-01 20:54           ` Jeff Garzik
2002-02-01 20:56         ` Peter Monta
2002-02-01 22:54           ` H. Peter Anvin
2002-02-01 23:27             ` Peter Monta
2002-02-02  1:50               ` H. Peter Anvin
2002-02-02  2:05       ` David Wagner
2002-02-02  3:30         ` Peter Monta
2002-02-02 21:02         ` Martin Dalecki
  -- strict thread matches above, loose matches on Subject: below --
2002-02-04 21:53 Ishan O. Jayawardena

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=20020201135225.D8599@asooo.flowerfire.com \
    --to=brownfld@irridia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    /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.