linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kurt Roeckx <kurt@roeckx.be>
To: "Theodore Y. Ts'o" <tytso@mit.edu>,
	"Sebastian Andrzej Siewior" <sebastian@breakpoint.cc>,
	912087@bugs.debian.org,
	"Package Development List for OpenSSL packages."
	<pkg-openssl-devel@alioth-lists.debian.net>,
	linux-kernel@vger.kernel.org,
	"Bernhard Übelacker" <bernhardu@mailbox.org>,
	pkg-systemd-maintainers@lists.alioth.debian.org,
	debian-ssh@lists.debian.org, 912087-submitter@bugs.debian.org
Subject: Re: Bug#912087: openssh-server: Slow startup after the upgrade to 7.9p1
Date: Fri, 2 Nov 2018 01:24:25 +0100	[thread overview]
Message-ID: <20181102002424.GD1547@roeckx.be> (raw)
In-Reply-To: <20181101235035.GC25621@thunk.org>

On Thu, Nov 01, 2018 at 07:50:35PM -0400, Theodore Y. Ts'o wrote:
> On Thu, Nov 01, 2018 at 11:18:14PM +0100, Sebastian Andrzej Siewior wrote:
> > Okay. So you wrote what can be done for a system with HW-RNG/kvm. On
> > bare metal with nothing fancy I have:
> > [    3.544985] systemd[1]: systemd 239 running in system mode. (+PAM…
> > [   10.363377] r8169 0000:05:00.0 eth0: link up
> > [   41.966375] random: crng init done
> > 
> > which means I have to wait about half a minute until I can ssh into. And
> > there is no way to speed it up?
> 
> So that surprises me.  Can you tell me more about the hardware?  Is it
> something like a Rasberry Pi?  Or is it an x86 server or desktop?  In
> my experience for most x86 platforms this isn't an issue.

The original poster had:
Architecture: amd64 (x86_64)
Kernel: Linux 4.18.0-2-amd64 (SMP w/2 CPU cores)

But I'm not sure if that's a real machine or some virtual host,
I'm going to guess it's a virtual host.

Anyway, on my laptop I get:
[   12.675935] random: crng init done

If the TPM is enabled, I also have an /etc/hwrng, but rng-tools is
started later after the init is done.

On my desktop (with a chaos key attached)
[    3.844484] random: crng init done
[    5.312406] systemd[1]: systemd 239 running in system mode.


Kurt


  reply	other threads:[~2018-11-02  0:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20181029223334.GH10011@roeckx.be>
2018-10-30  0:18 ` Bug#912087: openssh-server: Slow startup after the upgrade to 7.9p1 Sebastian Andrzej Siewior
2018-10-30 14:15   ` Theodore Y. Ts'o
2018-10-30 18:37     ` Kurt Roeckx
2018-10-30 20:51       ` Theodore Y. Ts'o
2018-10-31 11:21         ` Sebastian Andrzej Siewior
2018-10-31 22:41           ` Theodore Y. Ts'o
2018-11-01 22:18             ` Sebastian Andrzej Siewior
2018-11-01 23:50               ` Theodore Y. Ts'o
2018-11-02  0:24                 ` Kurt Roeckx [this message]
2018-11-02  2:13                   ` Theodore Y. Ts'o
2018-11-04  0:18                 ` Sebastian Andrzej Siewior

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=20181102002424.GD1547@roeckx.be \
    --to=kurt@roeckx.be \
    --cc=912087-submitter@bugs.debian.org \
    --cc=912087@bugs.debian.org \
    --cc=bernhardu@mailbox.org \
    --cc=debian-ssh@lists.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pkg-openssl-devel@alioth-lists.debian.net \
    --cc=pkg-systemd-maintainers@lists.alioth.debian.org \
    --cc=sebastian@breakpoint.cc \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).