Comment # 14 on bug 1188954 from Felix Miata

Since hosts ab250, asa88 & gb250 where this reproduces are all running TDM,
which a forum responder suggested might be at fault, on comment #0 host asa88 I
did a fresh minimal/KDE (no-recommends) install of TW20210810, without
NetworkManager, without Wicked, with systemd-networkd, without sddm, without
lightdm, with xdm. This bug reproduces randomly on it. In 11 successive
reboots:
1-success
2-success
3-failure
4-success
5-success
6-success
7-failure
8-failure
9-failure
10-failure
11-failure

Example failure stats (from #3 above):
# systemd-analyze
Startup finished in 5.768s (firmware) + 7.100s (loader) + 1.846s (kernel) +
2.102s (initrd) + 3.486s (userspace) = 20.304s
graphical.target reached after 3.477s in userspace
# systemd-analyze critical-chain
...
graphical.target @3.477s
������������������multi-user.target @3.477s
  ������������������kbdsettings.service @1.007s +2.469s
    ������������������basic.target @996ms
      ������������������sockets.target @996ms
        ������������������telnet.socket @995ms
          ������������������sysinit.target @987ms
            ������������������systemd-update-utmp.service @958ms +28ms
              ������������������systemd-tmpfiles-setup.service @927ms +28ms
                ������������������local-fs.target @924ms
                  ������������������usr-local.mount @876ms +48ms
                    ������������������systemd-fsck@dev-disk-by\x2dlabel-tvgp04usrlcl.service
@663ms +204ms
                      ������������������local-fs-pre.target @650ms
                        ������������������systemd-tmpfiles-setup-dev.service @630ms +17ms
                          ������������������kmod-static-nodes.service @556ms +55ms
                            ������������������systemd-journald.socket
                              ������������������system.slice
                                ������������������-.slice

The following is from #11 above:
# systemd-analyze blame | head -n22
2.521s kbdsettings.service
1.902s systemd-random-seed.service
1.541s sshd.service
1.140s dracut-initqueue.service
 659ms initrd-switch-root.service
 638ms chronyd.service
 471ms smartd.service
 396ms issue-generator.service
 304ms user@0.service
 303ms initrd-parse-etc.service
 182ms systemd-fsck@dev-disk-by\x2dlabel-tvgp04usrlcl.service
 179ms systemd-fsck@dev-disk-by\x2dlabel-tvgp06pub.service
 179ms systemd-fsck@dev-disk-by\x2dlabel-tvgp05home.service
 178ms systemd-udevd.service
 137ms systemd-networkd.service
 100ms display-manager.service
 100ms systemd-logind.service
  92ms systemd-udev-trigger.service
  82ms apparmor.service
  63ms sound-extra.service
  62ms systemd-tmpfiles-clean.service
  61ms modprobe@drm.service

Without radeon.cik_support=0 amdgpu.cik_support=1 on cmdline I managed success
on 11 straight boots, so it seems amdgpu.ko.xz simply doesn't get loaded as
fast/soon as radeon.ko.xz. 

I started a forum thread about this in June:
https://forums.opensuse.org/showthread.php/555514-boots-too-fast-for-Xorg-to-run