Just experienced the same symptom of a complete, silent, freeze with: -- Logs begin at Sun 2018-04-01 13:42:23 BST, end at Wed 2018-11-28 10:33:23 GMT. -- Nov 20 10:48:10 T300CHI kernel: microcode: microcode updated early to revision 0x2b, date = 2018-03-22 Nov 20 10:48:10 T300CHI kernel: Linux version 4.18.0-12-lowlatency (buildd@lgw01-amd64-033) (gcc version 8.2.0 (Ubuntu 8.2.0-7ubuntu1)) #13- Nov 20 10:48:10 T300CHI kernel: Command line: BOOT_IMAGE=/vmlinuz-4.18.0-12-lowlatency root=/dev/mapper/VG02-rootfs ro no_console_suspend acpi_osi=! "acpi_osi=Windows 2013" splash vt.handoff=7 ... Nov 20 10:48:10 T300CHI kernel: efi: EFI v2.40 by American Megatrends Nov 20 10:48:10 T300CHI kernel: efi: ESRT=0xcee2dd98 ACPI=0xcd72b000 ACPI 2.0=0xcd72b000 SMBIOS=0xf05b0 MPS=0xfd6e0 Nov 20 10:48:10 T300CHI kernel: secureboot: Secure boot could not be determined (mode 0) ... Nov 20 10:48:10 T300CHI kernel: smpboot: CPU0: Intel(R) Core(TM) M-5Y71 CPU @ 1.20GHz (family: 0x6, model: 0x3d, stepping: 0x4)
-- 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/1803960 Title: 4.18.0 kernels hang system randomly Status in linux package in Ubuntu: Triaged Status in linux source package in Cosmic: Triaged Bug description: I've been using 18.04 on an Asus T300CHI without issue until I decided to switch to the v4.18 kernels from 18.10 via linux-image-lowlatency- hwe-18.04-edge. Since then the system randomly but regularly completely hangs. Only a hard power-off resolves it. Frustratingly there are never any clues in the kernel logs so it is very difficult to point to anything that might cause it; there is never any obvious pattern in the workload, the user interaction, or state of the PC when the hang occurs. A week ago I switched to the Ubuntu mainline v4.19 builds and that resolved the issue. I was reminded of it again today when it hung a few minutes ago. After the reboot I checked the previous boot log and realised the PC had accidentally been booted with the default v4.18 kernel rather than v4.19. I don't think this report can be debugged but it is worth having a tracking bug in case other people experience the same issue with v4.18. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
