X-Original-To: alpine-user@lists.alpinelinux.org Received: from sdaoden.eu (sdaoden.eu [217.144.132.164]) by lists.alpinelinux.org (Postfix) with ESMTP id EE376F84F7E for ; Sat, 19 Jan 2019 17:15:34 +0000 (UTC) Received: by sdaoden.eu (Postfix, from userid 1000) id 2DA921604A; Sat, 19 Jan 2019 18:15:33 +0100 (CET) Date: Sat, 19 Jan 2019 18:15:35 +0100 From: Steffen Nurpmeso To: Natanael Copa Cc: alpine-user@lists.alpinelinux.org Subject: Re: [alpine-user] Startup hangs (aports: sshd?) Message-ID: <20190119171535.pcxs8%steffen@sdaoden.eu> In-Reply-To: <20190119004724.78b1b0c9@ncopa-macbook.copa.dup.pw> References: <20190117140207.lqzvY%steffen@sdaoden.eu> <20190119004724.78b1b0c9@ncopa-macbook.copa.dup.pw> Mail-Followup-To: Natanael Copa , alpine-user@lists.alpinelinux.org User-Agent: s-nail v14.9.11-174-g0ca07f7b-dirty OpenPGP: id=EE19E1C1F2F7054F8D3954D8308964B51883A0DD; url=https://ftp.sdaoden.eu/steffen.asc; preference=signencrypt BlahBlahBlah: Any stupid boy can crush a beetle. But all the professors in the world can make no bugs. X-Mailinglist: alpine-user Precedence: list List-Id: Alpine Development List-Unsubscribe: List-Post: List-Help: List-Subscribe: Natanael Copa wrote in <20190119004724.78b1b0c9@ncopa-macbook.copa.dup.pw>: |On Thu, 17 Jan 2019 15:02:07 +0100 |Steffen Nurpmeso wrote: | |> Hello. |> |> After upgrading to [edge] i see a possibly endless hang upon |> startup, which seems to be caused by PRNG init. | |Try add random.trust_cpu=1 as boot option. Will do when i finally can upgrade to 4.19.y series. Merci. |See: |https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/\ |?h=linux-4.19.y&id=39a8883a2b989d1d21bd8dd99f5557f0c5e89694 | |and: |https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/\ |?h=linux-4.19.y&id=9b25436662d5fb4c66eb527ead53cab15f596ee0 I am back at 4.14.89 since the nf_conntrack crashes persist, and even 4.19.16 does not seem to have anything related. (4.19.15 had, but crashes, ehm, persist.) That is: i have to wait. But ok i mean all that seems to be problematic, for example with the program i have posted: #?64|xhost:/etc/init.d# /sbin/entropy-saver save - 1588 bits of entropy available at /dev/random - 2422 bits of entropy remain at /dev/random Insufficient entropy to save from /dev/random (-834 bits) Two adjacent ioctl() asking for entropy_avail with just one read (!) of /dev/random in between causes the entropy to explode! This _cannot_ be right, can it? Thereafter it works for the second try: #?0|xhost:/etc/init.d# /sbin/entropy-saver save - 2435 bits of entropy available at /dev/random - 1411 bits of entropy remain at /dev/random - 1024 bits / 80 bytes of entropy saved to /var/lib/misc/random.dat Very weakly rated, this stuff. Say, isn't that flaky? This VM really crawls along, with jitterentropy, with haveged, and with the above. While i am writing, the entropy went down to 1343, with only postfix (urandom), mailman (1000 x urandom), dnsmasq (using internal surf rand with one-time seeding), lighttpd (uses getrandom/urandom) and cgit running. Whereas my laptop is stable at 38xy. So sorry to bother you all with this! I will turn to use linux-virt on the VM. Sorry for the noise. A nice weekend i wish. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) --- Unsubscribe: alpine-user+unsubscribe@lists.alpinelinux.org Help: alpine-user+help@lists.alpinelinux.org ---