On 06/30/2018 09:53 AM, Markus Egg wrote:
The worst one seems to be "NMI watchdog : BUG soft lockup CPU4 stuck for 22s!"
No, it isn't scary, and it is quite common (though the message is generally "stuck for 23s"). google: "NMI watchdog : BUG soft lockup CPU stuck" You can read until you are content this isn't specific to your laptop. If you look at dmesg output that is simply an initialization issue usually associated with PCI bus and one of the Cores early in the boot process. Watchdog timers are specifically set to monitor the various initializations and to reset (or restart or kill) any process that gets stuck. Don't kill the boot. It will proceed after the watchdog timer handles the issue, but it will trigger a verification process that will loop over each core in your box to ultimately find out that everything is OK and then continue to boot. (THIS CAN TAKE 5 MINUTES) This is a kernel issue that appeared early in the 4.16.x set of releases and is also present in the 4.17 kernel for some hardware: Example: https://bugs.archlinux.org/task/59091 There is no guarantee this is your exact problem, but I suspect it is related. If you are able to boot after letting the box sit and sort itself out, then capture the dmesg output (e.g. open a terminal and...) $ dmesg > my_dmesg_output You can then view the my_dmesg_output and determine if this is related, and the output can be used as an attachment to any bug report (or posted to susepaste so others can attach it if needed to a bug report) Good luck, your hardware will work fine, it just may take sorting out a bug or two first. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org