Gathering more evidence in support of a faulty motherboard theory. At some point I got this (system wasn't under heavy load - just a browser opened + remote video playback):
https://gist.github.com/dshcherb/06f4e4a0260b6d5313df1594d959849a#file- nvme-failure-razer-dmesg-log-L2073 сен 10 22:23:39 blade kernel: nvme nvme0: I/O 916 QID 3 timeout, aborting сен 10 22:23:39 blade kernel: nvme nvme0: I/O 917 QID 3 timeout, aborting сен 10 22:23:39 blade kernel: nvme nvme0: I/O 918 QID 3 timeout, aborting сен 10 22:23:39 blade kernel: nvme nvme0: I/O 919 QID 3 timeout, aborting сен 10 22:23:45 blade kernel: nvme nvme0: I/O 920 QID 3 timeout, aborting сен 10 22:23:55 blade kernel: nvme nvme0: I/O 921 QID 3 timeout, aborting сен 10 22:24:10 blade kernel: nvme nvme0: I/O 916 QID 3 timeout, reset controller сен 10 22:24:39 blade kernel: nvme nvme0: I/O 11 QID 0 timeout, reset controller сен 10 22:25:42 blade kernel: nvme nvme0: Device not ready; aborting reset So the kernel tried to reset a controller after a timeout which is normal and could not do so after 100ms => aborted reset. http://elixir.free- electrons.com/linux/v4.13/source/drivers/nvme/host/core.c#L1378 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1670706 Title: Kernel Call Trace After Disabling an ath10k Wireless Device (Atheros QCA6174 802.11ac (rev 32)) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1670706/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
