From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Mikael Pettersson <mikpelinux@gmail.com>,
Linux SPARC Kernel Mailing List <sparclinux@vger.kernel.org>,
linux-block@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: [5.0-rc5 regression] "scsi: kill off the legacy IO path" causes 5 minute delay during boot on Sun Blade 2500
Date: Sat, 09 Feb 2019 10:19:01 -0800 [thread overview]
Message-ID: <1549736341.2971.7.camel@HansenPartnership.com> (raw)
In-Reply-To: <CAM43=SO6bdDAEULEPArfgdbjLAYDo9OiPBa8gL4fsSg7Dky=gA@mail.gmail.com>
On Sat, 2019-02-09 at 18:04 +0100, Mikael Pettersson wrote:
> 4.20 and earlier kernels boot fine on my Sun Blade 2500 (UltraSPARC
> IIIi), but the 5.0-rc kernels consistently experience a 5 minute
> delay
> late during boot, after enabling networking but before allowing user
> logins. E.g. 5.0-rc5 dmesg has:
>
> [Fri Feb 8 17:13:17 2019] random: dbus-daemon: uninitialized urandom
> read (12 bytes read)
> [Fri Feb 8 17:18:14 2019] random: crng init done
I've had the same problem on several of my test systems. Are you sure
it's not this bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=912087
?
The solution for me was to install the haveged package which does
active entropy gathering during boot and can make /dev/urandom
available much earlier.
> During this interval the machine answers pings but won't allow user
> logins either on the console or over the network.
>
> A git bisect identified commit
> f664a3cc17b7d0a2bc3b3ab96181e1029b0ec0e6
> Author: Jens Axboe <axboe@kernel.dk>
> Date: Thu Nov 1 16:36:27 2018 -0600
>
> scsi: kill off the legacy IO path
>
> as the point where this 5m delay was introduced.
I think the reason for this is that the block mq path doesn't feed the
kernel entropy pool correctly, hence the need to install an entropy
gatherer for systems that don't have other good random number sources.
James
next prev parent reply other threads:[~2019-02-09 18:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-09 17:04 [5.0-rc5 regression] "scsi: kill off the legacy IO path" causes 5 minute delay during boot on Sun Blade 2500 Mikael Pettersson
2019-02-09 18:19 ` James Bottomley [this message]
2019-02-10 9:17 ` Mikael Pettersson
2019-02-10 15:44 ` James Bottomley
2019-02-10 16:05 ` Jens Axboe
2019-02-10 16:25 ` James Bottomley
2019-02-10 16:35 ` Jens Axboe
2019-02-11 15:25 ` James Bottomley
2019-02-11 15:28 ` Jens Axboe
2019-02-11 15:42 ` James Bottomley
2019-02-11 15:46 ` Jens Axboe
2019-02-11 16:28 ` James Bottomley
2019-02-11 16:31 ` Jens Axboe
2019-02-12 2:13 ` James Bottomley
2019-02-12 2:50 ` Jens Axboe
2019-02-12 3:37 ` Elliott, Robert (Persistent Memory)
2019-02-12 4:15 ` James Bottomley
2019-02-12 15:24 ` James Bottomley
2019-02-12 15:27 ` Jens Axboe
2019-02-14 18:35 ` Mikael Pettersson
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=1549736341.2971.7.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpelinux@gmail.com \
--cc=sparclinux@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