On Fri, 2021-06-18 at 12:15 -0600, Chris Murphy wrote:
On Fri, Jun 18, 2021, 11:10 AM Patrick O'Callaghan
<pocallaghan(a)gmail.com>
wrote:
>
> My problem is that one drive comes up almost instantly and the other
> takes 30 seconds. In fact I can live with that. My real gripe is that
> the kernel makes me wait even though the drive is not being accessed.
> If it just wants to make the drive available, it should be able to
> wait
> asynchronously.
Keep the hardware config the same, but boot a Fedora Live image (from
USB
stick or whatever). Does it still hang during boot?
The kernel shouldn't wait unless the device has put some kind of busy
state
on the bus shared by sysroot.
I'm suspicious that something is trying to mount it, or otherwise
access
it, but I haven't seen the logs.
OK, I've done that and uploaded the results to:
https://drive.google.com/drive/folders/1J3unPJIN-XNQwuwLZNsaPp7JqYH6M3YB?...
This is using Fedora-KDE-Live-x86_64-34-1.2.iso.
There are three files:
live-blame (output of systemd-analyze blame)
live-boot.svg (output of systemd-analyze plot)
live-journal (output of journal after logging into KDE)
Clearly the 30-second delay is not happening. There is a 14-second
delay due to usb-settle, but it doesn't hold up the boot process.
(There's another delay is due to checking the MD5 checksum on the
thumbdrive before the boot proper starts, and which I interrupted).
poc