I am experiencing this bug as well, on the same hardware. I have tested the mainline builds, and can confirm that the bug
exists with linux-image-4.4.0-040400rc7-generic_4.4.0-040400rc7.201512272230_amd64 as well.
As such, it probably occurs on most machines with Intel BayTrail processors, and is so far unresolved in upstream,
to my knowledge.
As the bug report mentions, there is a workaround, namely to add "intel_idle.max_cstate=1" to the boot options
(using grub, add this to the GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then run update-grub). This likely
comes at the cost of some increase in power consumption, but so far it seems to work for me. If I get any more
hangs even with this option, I will leave another comment.
I am experiencing this bug as well, on the same hardware. I have tested the mainline builds, and can confirm that the bug 4.4.0-040400rc7 -generic_ 4.4.0-040400rc7 .201512272230_ amd64 as well.
exists with linux-image-
After some searching, it appears that this bug is known in upstream: https:/ /bugzilla. kernel. org/show_ bug.cgi? id=109051
As such, it probably occurs on most machines with Intel BayTrail processors, and is so far unresolved in upstream,
to my knowledge.
As the bug report mentions, there is a workaround, namely to add "intel_ idle.max_ cstate= 1" to the boot options LINUX_DEFAULT in /etc/default/grub, then run update-grub). This likely
(using grub, add this to the GRUB_CMDLINE_
comes at the cost of some increase in power consumption, but so far it seems to work for me. If I get any more
hangs even with this option, I will leave another comment.