On Fri, Apr 5, 2013 at 9:49 PM, Leland Lucius <[email protected]> wrote: > On 4/5/2013 8:33 PM, Gregg Levine wrote: >> >> On Fri, Apr 5, 2013 at 9:26 PM, Leland Lucius <[email protected]> wrote: >>> >>> On 4/5/2013 5:59 PM, Pedro Principeza wrote: >>>> >>>> >>>> Hi. >>>> >>>> Although it seems to have all the needed permissions and nodes. Have >>>> you >>>> tried to recreate it, using: >>>> >>>> mknod /dev/urandom c 1 9 >>>> >>> Same result...still returning zero bytes. >>> >>> Leland >>> >>> >> >> Hello! >> Isn't the mechanism that works that thing connected to the I/O >> functions of the average System Z? I seem to recall that when an >> almost related problem surfaced a while back, the solution was to >> engage those I/O functions by doing some. >> >> Ideally why not have the system write something (or other) to files >> and then check to see if the thing is working. >> >> Feel free to disregard my suggestion if it doesn't work, or if its not >> at all applicable. > > > Yepper, urandom and, I believe, the whole in-kernel entropy thing is > related to various pseudo-random activities occurring within the system. > Unless (or maybe in addition to) you have a hardware prng which we do > on z. > > But, I believe the guest has lost his cookies. Here's what the current > kernel random proc config looks like on a healthy server: > > pzsfs102:~ # grep '' /proc/sys/kernel/random/* > /proc/sys/kernel/random/boot_id:2a009fed-694b-4ad1-a110-471f5310ed16 > /proc/sys/kernel/random/entropy_avail:2782 > /proc/sys/kernel/random/poolsize:4096 > /proc/sys/kernel/random/read_wakeup_threshold:64 > /proc/sys/kernel/random/uuid:6cf52c84-b907-42c8-a963-7ed9d4b252d9 > /proc/sys/kernel/random/write_wakeup_threshold:1024 > > And here's the values on the sickly fella: > > pzsfs101:~ # grep '' /proc/sys/kernel/random/* > /proc/sys/kernel/random/boot_id:00000000-0000-4000-8000-000000000000 > /proc/sys/kernel/random/entropy_avail:1380 > /proc/sys/kernel/random/poolsize:4096 > /proc/sys/kernel/random/read_wakeup_threshold:64 > /proc/sys/kernel/random/uuid:00000000-0000-4000-8000-000000000000 > /proc/sys/kernel/random/write_wakeup_threshold:1024 > > The boot_id and uuid values make me believe that something is not quite > right. > > > Leland
Hello! I quite agree. What we are seeing is a very sick penguin. I just ran your grep command string against my Intel system, and obviously the returned boot_id and uuid values are different then the healthy bird, but the rest is similar. So why does the system need to be restarted? That's the strange part. What's causing it and why does it get fixed that way. And then why does it happen? ----- Gregg C Levine [email protected] "This signature fought the Time Wars, time and again." ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390 ---------------------------------------------------------------------- For more information on Linux on System z, visit http://wiki.linuxvm.org/
