Comment 6 for bug 1769309

Although I did not get the same entry in dmesg as Tonio, it did point me towards dmesg. So I have attached my dmesg ouput. I have listed the parts where significant time is somehow lost (please note that I am not an expert and therefore I am not able to tell where exactly the gdm login screen appeared).

#1
[ 2.780216] clocksource: Switched to clocksource tsc
[ 34.422902] random: crng init done

#2
[ 40.242284] EXT4-fs (dm-2): mounted filesystem with ordered data mode. Opts: (null)
[ 128.816712] audit: type=1400 audit(1525590690.456:2): apparmor="STATUS" operation="profile_load" profile="unconfined" name="/snap/core/4486/usr/lib
/snapd/snap-confine" pid=1126 comm="apparmor_parser"

#3
[ 135.805543] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
[ 166.755990] ata4: exception Emask 0x10 SAct 0x0 SErr 0x4090000 action 0xe frozen

#4
[ 171.739128] rfkill: input handler disabled
[ 193.135040] FS-Cache: Loaded

#5 & 6
[ 193.148640] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
[ 261.690048] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
[ 467.025578] kauditd_printk_skb: 48 callbacks suppressed