I'm glad, then, I waited until someone reacted to my "plan". Checking /var/log/kern.log, I have the log from when I first booted w/ the failing situation. I know this, because I shutdown (rare) in anticipation of a coming Hurricane Harvey, and tweeted the next day when weather was stable.
The (attached) log - the interesting starting point, first boot w/ intel-microcode 3.2017.07.07.1 is "Aug 26 12:52" (shutdown was "Aug 26 00:10"). In the meantime, I'll upgrade just the intel-microcode to the Ubuntu release, and shortly provide that associated kern.log and /proc/cpuinfo, then cycle thru the various debian releases @hmh listed, and (finally) end with Ubuntu upgrades, including intel-microcode and kernel. Let's see what happens... ** Attachment added: "kern.log from initial discovery/ report here" https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1713532/+attachment/4941067/+files/kern.log.2017.08.26.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1713532 Title: Intel-8260 not init'd by intel-microcode=3.20170707.1~ubuntu16.04.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1713532/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
