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. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1973167 Title: linux-image-4.15.0-177-generic freezes on the welcome screen Status in linux package in Ubuntu: Confirmed Bug description: After updating to linux-image-4.15.0-177-generic, my machine completely freezes on the Ubuntu Welcome screen, i.e. right after switching to GUI mode. The mouse pointer is frozen, the keyboard does not even respond to CAPS LOCK or NUM LOCK, pressing CTRL+ALT+F2 shows no reaction. I cannot work with my machine at this point and have to hard reset it. Selecting advanced boot options in grub and selecting the previous linux kernel 4.15.0-176 makes it work again. So this bad bug was introduced with the 4.15.0-177 kernel release. I tried removing the nvidia-driver-510 package, presumably making Ubuntu use the "nouveau" driver, and with that, I could use the welcome screen and log in, but the machine still froze shortly afterwards. So maybe this is some sort of interference with my GeForce 1080 graphics card, but it is not specific to the driver used. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-177-generic:amd64 4.15.0-177.186 ProcVersionSignature: Ubuntu 4.15.0-176.185-generic 4.15.18 Uname: Linux 4.15.0-176-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.27 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC1: robert 2082 F.... pulseaudio /dev/snd/controlC0: robert 2082 F.... pulseaudio /dev/snd/controlC2: robert 2082 F.... pulseaudio CurrentDesktop: Unity:Unity7:ubuntu Date: Thu May 12 13:36:28 2022 EcryptfsInUse: Yes InstallationDate: Installed on 2015-10-29 (2386 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) MachineType: Supermicro Super Server ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-176-generic root=UUID=7c296e4d-0189-43a0-aef8-7d536b98a536 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-176-generic N/A linux-backports-modules-4.15.0-176-generic N/A linux-firmware 1.173.21 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2019-07-29 (1017 days ago) dmi.bios.date: 09/18/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3.4 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X11SAE dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3.4:bd09/18/2020:svnSupermicro:pnSuperServer:pvr0123456789:rvnSupermicro:rnX11SAE:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: To be filled by O.E.M. dmi.product.name: Super Server dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
