On Mon, 2021-06-21 at 06:19 +0800, Ed Greshko wrote: > On 21/06/2021 06:02, Ed Greshko wrote: > > On 21/06/2021 05:48, Patrick O'Callaghan wrote: > > > $ systemd-analyze blame |grep dracut-initqueue.service > > > 486ms dracut-initqueue.service > > > > > > If I power on the dock on after startup is complete, one drive > > > appears > > > immediately and the other takes 30 seconds or so, so the delay is > > > not > > > being caused by the boot process itself. It must be the hardware > > > (the > > > drive or the dock) taking that long for whatever reason, possibly > > > power > > > management as George suggested. As I've said, my goal is to > > > convince > > > the kernel that it doesn't need to wait for this so as to > > > continue with > > > the startup. > > > > Right. I just wanted to confirm that, it would appear, the 30sec > > is in that service/area. > > > > So far I've not found a configuration file/setting which would tell > > it "don't look here...". > > > > > > This may be a bit of work, but *may* help define/narrow the issue. > > https://fedoraproject.org/wiki/How_to_debug_Dracut_problems
Hmm. I see there's a way to breakpoint the boot process e.g. at the pre-udev stage, but I'm not sure what I can achieve by doing that. poc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
