On Thu, 2016-07-07 at 11:46 -0400, Josh Boyer wrote: > We've had a rash of reports of kernels not booting on some Skylake based > machines recently. After working these, we've determined that a recent > Intel microcode update somehow conflicts with something in the system > firmware for these machine, causing a complete failure to boot after grub > loads the kernel. > > Some of these systems have a firmware update (BIOS/UEFI) that restores > functionality even with the microcode being loaded. Other systems do not > yet at this time. If you experience a boot hang on a Skylake based > machine, you can try and determine if the microcode is at fault by > specifying 'dis_ucode_ldr' on the kernel command line. That prevents the > kernel from loading the microcode during the early boot. > > The issue is mostly being tracked here: > https://bugzilla.redhat.com/show_bug.cgi?id=1353103 > > Some of the machines involved are: > > Lenovo Thinkpad T460 > Lenovo Thinkpad x260 > Lenovo Yoga 260 > ASUS Zenbook UX305CA > Samsung Notebook 9 I've blogged about this (so it'll reach planet) and posted to G+. There's also a forum thread for 'failure to boot with kernel 4.6' where we're pretty sure at least some of the reporters are hitting this bug: https://www.happyassassin.net/2016/07/07/psa-failure-to-boot-after-kernel-update-on-skylake-systems/ https://plus.google.com/u/0/+AdamWilliamsonFOSS/posts/Dp7qD3H5s2V http://forums.fedoraforum.org/showthread.php?t=310467 -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | XMPP: adamw AT happyassassin . net http://www.happyassassin.net -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx
