@userunknown - I'd try using 'less /var/log/kern.log' after you've logged in to see if there are any clues to why there's such a long wait before the login screen.
I haven't experienced any random and total system freezes with the two Bay Trail CPU machines I've been testing and using, but can understand if you have that you'd not be keen to try without the 'cstate' parameter. As far as I can tell, there's not been much activity on the bug report that you linked to since April. The most recent posts are someone sending information about a non-Bay Trail processor (and it being discussed that it's a different bug that's affecting them), someone not getting the microcode update automatically in Manjaro and then a link or two to microcode updates. I'd be tempted to think that if you have the latest microcode updates (if 'dmesg | grep micro' says you've got revision 836) then it could be worth trying without the 'cstate fix' to see if it's still needed. (preferably not testing it when doing important work! ;) ) I don't know if the graphical issues are somehow linked to the 'cstate' usage, but it'd be good to rule it out. I've not had any graphical issues (using Ubuntu & KDE Plasma) or pre- login delays yet and assume @cmeerw would have mentioned it if it had occurred too. Is anyone else experiencing graphic flickering issues or long delays before the login screen when using the 4.15 kernel with the patch applied? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1774950 Title: Suspend fails in Ubuntu and Kubuntu 18.04 but works fine in Ubuntu and Kubuntu 17.10 (and on Kubuntu 18.04 using kernel 4.14.47) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1774950/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
