Comment 3 for bug 1973167

After finding someone reporting the same issue (https://forums.linuxmint.com/viewtopic.php?t=373747&p=2175201) and reading that the machine may come alive after a while, I found that indeed after 3 minutes the machine works. dmesg that reveals that it seemingly was the initialization of the intel_lpss driver that took 3 minutes:

[ 6.889189] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)
[ 7.112397] input: PC Speaker as /devices/platform/pcspkr/input/input5
[ 7.220480] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer
[ 7.220481] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[ 7.220481] RAPL PMU: hw unit of domain package 2^-14 Joules
[ 7.220482] RAPL PMU: hw unit of domain dram 2^-14 Joules
[ 7.220482] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[ 7.220483] RAPL PMU: hw unit of domain psys 2^-14 Joules
[ 9.882380] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 10.068162] IPv6: ADDRCONF(NETDEV_UP): eno1: link is not ready
[ 10.070009] IPv6: ADDRCONF(NETDEV_UP): eno2: link is not ready
[ 10.115669] IPv6: ADDRCONF(NETDEV_UP): eno2: link is not ready
[ 10.117735] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[ 10.615555] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[ 14.114836] e1000e: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: Rx/Tx
[ 14.114883] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
[ 15.199994] atlantic: link change old 0 new 1000
[ 15.200150] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
[ 187.423062] intel-lpss 0000:00:15.1: enabling device (0000 -> 0002)
[ 187.432242] mei_me 0000:00:16.0: enabling device (0000 -> 0002)
[ 187.432264] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 187.441672] AVX2 version of gcm_enc/dec engaged.
[ 187.441673] AES CTR mode by8 optimization enabled
[ 187.445619] idma64 idma64.0: Found Intel integrated DMA 64-bit
[ 187.452528] idma64 idma64.1: Found Intel integrated DMA 64-bit

Note these lines:
[ 6.889189] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)
[ 187.423062] intel-lpss 0000:00:15.1: enabling device (0000 -> 0002)
[ 187.432242] mei_me 0000:00:16.0: enabling device (0000 -> 0002)
[ 187.445619] idma64 idma64.0: Found Intel integrated DMA 64-bit
[ 187.452528] idma64 idma64.1: Found Intel integrated DMA 64-bit

For comparison, the same lines from the 4.15.0-176 dmesg:

[ 6.321873] intel-lpss 0000:00:15.0: enabling device (0000 -> 0002)
[ 6.340549] idma64 idma64.0: Found Intel integrated DMA 64-bit
[ 6.345409] intel-lpss 0000:00:15.1: enabling device (0000 -> 0002)
[ 6.345610] idma64 idma64.1: Found Intel integrated DMA 64-bit
[ 6.350618] mei_me 0000:00:16.0: enabling device (0000 -> 0002)

So the initialization time increased from 30ms of 180s, i.e. by a factor of 6,000. This cannot be right.