All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Ziegler <br015@umbiko.net>
To: buildroot@busybox.net
Subject: [Buildroot] SSH server starts too late
Date: Mon, 24 Feb 2020 14:22:04 +0100	[thread overview]
Message-ID: <ab1578656655630d72babe9984a136b8@umbiko.net> (raw)
In-Reply-To: <CAGSpp9ng2yxCK=RZeq1Z_Bce4pwij9FQED23SpGuvjqm5awHhg@mail.gmail.com>

On 2020-02-24 13:33, Hammami Omar wrote:

Hi Omar,

> The problem is that, in kernel logs, I cannot see that my ssh server
> was blocked.
> That is why, I am thinking if my problem is really du to entropy or
> no.

You should experience a time lag in kernel log time stamps when that 
happens. If this lag is caused by an entropy issue, starting to type 
randomly on the keyboard should resolve it quite fast. This will speed 
up the time until you see the final random output:

> [   77.847665] random: nonblocking pool is initialized

The SSH server will definitely not be operative until this pool is 
initialized.

Kind regards,
Andreas

  parent reply	other threads:[~2020-02-24 13:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.11.1582286403.41897.buildroot@busybox.net>
2020-02-21 12:51 ` [Buildroot] SSH server starts too late Andreas Ziegler
2020-02-24  9:29   ` Hammami Omar
     [not found]     ` <1d91f38acaeecb790f5a44d104ae0ca1@umbiko.net>
2020-02-24 13:07       ` Andreas Ziegler
     [not found]       ` <CAGSpp9ng2yxCK=RZeq1Z_Bce4pwij9FQED23SpGuvjqm5awHhg@mail.gmail.com>
2020-02-24 13:22         ` Andreas Ziegler [this message]
2020-02-24 14:07           ` Hammami Omar
2020-02-24 15:16             ` Hammami Omar
2020-02-21  9:13 Hammami Omar
2020-02-21 10:19 ` Peter Seiderer
2020-02-21 14:50   ` Hammami Omar
2020-02-21 16:16     ` Hammami Omar
2020-02-21 18:08     ` Grant Edwards
2020-02-21 18:30       ` Hammami Omar
2020-03-03 12:33         ` Hammami Omar

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=ab1578656655630d72babe9984a136b8@umbiko.net \
    --to=br015@umbiko.net \
    --cc=buildroot@busybox.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.