From: Gunter Ohrner <G.Ohrner@post.rwth-aachen.de>
To: linux-kernel@vger.kernel.org
Subject: Entropy Pool Contents
Date: Thu, 23 Nov 2006 00:54:03 +0100 [thread overview]
Message-ID: <ek2nva$vgk$1@sea.gmane.org> (raw)
Hi!
(PEBKAC warning. I'm probably doing something dump. I just don't know
what...)
I seem to have an entropy pool on a headless machine which is not nearly
empty (a common problem in this case, I know), but completely empty and
stuck in this state...
Hornburg:~# cat /proc/sys/kernel/random/entropy_avail
0
Hornburg:~# fuser /dev/urandom
Hornburg:~# lsof | grep random
Hornburg:~# cat /proc/sys/kernel/random/entropy_avail
0
Hornburg:~# dd if=/dev/hdf of=/dev/urandom bs=512 count=1
1+0 records in
1+0 records out
512 bytes transferred in 0.016268 seconds (31473 bytes/sec)
Hornburg:~# dd if=/dev/hdf of=/dev/random bs=512 count=1
1+0 records in
1+0 records out
512 bytes transferred in 0.031943 seconds (16029 bytes/sec)
Hornburg:~# cat /proc/sys/kernel/random/entropy_avail
0
Hornburg:~# fuser /dev/urandom
Hornburg:~# fuser /dev/random
Hornburg:~# lsof | grep random
Hornburg:~# cat /proc/sys/kernel/random/poolsize
4096
Hornburg:~#
Also causing disk activities doesn't help at all. (Two disks on a Promise
PDC20268 controller.)
The system runs a rather ancient Debian Sarge 2.4 kernel:
Linux Hornburg 2.4.27-3-386 #1 Thu Sep 14 08:44:58 UTC 2006 i486 GNU/Linux
However as the machine itself is also ancient, the 2.4 seems like a good
match. And also 2.4 ought to have a refilling entropy pool, doesn't it?
Maybe someone can shed some light on what's happening here...
Greetings,
Gunter
next reply other threads:[~2006-11-22 23:54 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 23:54 Gunter Ohrner [this message]
2006-11-22 23:59 ` Entropy Pool Contents Gunter Ohrner
2006-11-23 0:10 ` Jan Engelhardt
2006-11-23 21:40 ` Gunter Ohrner
2006-11-27 16:16 ` Phillip Susi
2006-11-27 16:19 ` Chris Friesen
2006-11-27 18:54 ` Phillip Susi
2006-11-27 19:33 ` David Wagner
2006-11-27 20:38 ` Phillip Susi
2006-11-27 20:40 ` David Wagner
2006-11-27 21:52 ` Kyle Moffett
2006-11-28 4:17 ` David Wagner
2006-11-28 5:19 ` Ben Pfaff
2006-11-28 12:13 ` Henrique de Moraes Holschuh
2006-11-28 12:58 ` David Wagner
2006-11-28 13:32 ` Eran Tromer
2006-11-28 13:15 ` Martin Mares
2006-11-28 17:22 ` Phillip Susi
2006-11-28 17:24 ` Martin Mares
2006-11-28 17:46 ` Phillip Susi
2006-11-28 17:49 ` Martin Mares
2006-11-28 18:40 ` Phillip Susi
2006-11-28 21:05 ` Martin Mares
2006-11-29 20:04 ` Phillip Susi
2006-11-28 17:42 ` Phillip Susi
2006-11-28 17:59 ` Martin Mares
2006-11-28 22:50 ` Eran Tromer
2006-11-27 22:21 ` Gunter Ohrner
2006-11-24 0:48 ` Theodore Tso
2006-11-24 1:01 ` Jeff Garzik
2006-11-23 20:54 ` Lennart Sorensen
2006-11-23 21:34 ` Gunter Ohrner
2006-11-23 21:04 ` Jeff Garzik
2006-11-23 21:43 ` Gunter Ohrner
2006-11-26 1:26 ` Folkert van Heusden
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='ek2nva$vgk$1@sea.gmane.org' \
--to=g.ohrner@post.rwth-aachen.de \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox