I would bet that if you "cat /proc/cmdline" you will see a resume= parameter, but even if not this may be the default. At any rate, it doesn't look like your resume attempt is the reason for the delay, as the delay has already occurred when the resume is attempted:

Jun 30 12:19:40 amito kernel: Console: switching to colour frame buffer device 240x75
        <Note 1:28 minute Delay>
Jun 30 12:21:08 amito dracut-initqueue[526]: WARNING: D-Bus notification failed: Transport endpoint is not connected

Note that delay has already occurred at this point.

Jun 30 12:21:08 amito systemd[1]: Found device /dev/mapper/fedora-swap.
Jun 30 12:21:08 amito systemd[1]: Starting Resume from hibernation using device /dev/mapper/fedora-swap...
Jun 30 12:21:08 amito systemd-hibernate-resume[547]: Could not resume from '/dev/mapper/fedora-swap' (253:1).

...and the resume failure is a second or less after the attempted resume starts.

--Greg


On Thu, Jul 1, 2021 at 8:14 AM Jonathan Ryshpan <jonrysh@pacbell.net> wrote:
The system always tries to restore from hibernation on startup; this
causes about a 1-1/2 minute delay.  I see no reason for this, since the
system is halted by "(Start)->Shut Do..."  Here is an extract from the
system log with inserted comments.

Jun 30 12:19:38 amito dracut-initqueue[523]: inactive          '/dev/fedora/windows' [400.00 GiB] inherit
Jun 30 12:19:38 amito dracut-initqueue[523]: inactive          '/dev/fedora/root' [100.00 GiB] inherit
Jun 30 12:19:38 amito dracut-initqueue[523]: inactive          '/dev/fedora/swap' [24.00 GiB] inherit
Jun 30 12:19:38 amito dracut-initqueue[523]: inactive          '/dev/fedora/home' [<1.31 TiB] inherit
Jun 30 12:19:38 amito systemd[1]: Found device /dev/mapper/fedora-root.
        <Last message to appear on the screen before delay>
Jun 30 12:19:38 amito systemd[1]: Reached target Initrd Root Device.
Jun 30 12:19:40 amito kernel: fbcon: Taking over console
Jun 30 12:19:40 amito kernel: Console: switching to colour frame buffer device 240x75
        <Note 1:28 minute Delay>
Jun 30 12:21:08 amito dracut-initqueue[526]: WARNING: D-Bus notification failed: Transport endpoint is not connected
Jun 30 12:21:08 amito systemd[1]: Found device /dev/mapper/fedora-swap.
Jun 30 12:21:08 amito systemd[1]: Starting Resume from hibernation using device /dev/mapper/fedora-swap...
Jun 30 12:21:08 amito systemd-hibernate-resume[547]: Could not resume from '/dev/mapper/fedora-swap' (253:1).
Jun 30 12:21:08 amito systemd[1]: systemd-hibernate-resume@dev-mapper-fedora\x2dswap.service: Deactivated successfully.
Jun 30 12:21:08 amito systemd[1]: Finished Resume from hibernation using device /dev/mapper/fedora-swap.
Jun 30 12:21:08 amito kernel: PM: Image not found (code -22)
Jun 30 12:21:08 amito kernel: kauditd_printk_skb: 7 callbacks suppressed

System configuration" 
   Operating System: Fedora 34
   KDE Plasma Version: 5.22.2
   KDE Frameworks Version: 5.83.0
   Qt Version: 5.15.2
   Kernel Version: 5.12.13-300.fc34.x86_64 (64-bit)
   Graphics Platform: Wayland
   Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz
   Memory: 15.5 GiB of RAM
   Graphics Processor: Mesa DRI Intel® HD Graphics 4600

--
Sincerely Jonathan Ryshpan <jonrysh@pacbell.net>

        But what are all these mysteries to me,
         2      Whose thoughts are full of indices and surds.
        X  +  7 X  +  53
                = 11 / 3.
        -- Lewis Carrol
_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-leave@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