Comment 42 for bug 1567602

@ Benjamin

Thank you for your insights. Is it possible to determine a scope of affected systems out there? So far a specific config is required to trigger this bug it seems, but I'm not sure how common such a configuration is. Extensive back-ports and reworks of the kernel are out of the question. However, we do have LTS hardware enablement kernel stacks - https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Kernel.2FSupport.A16.04.x_Ubuntu_Kernel_Support in essence, some time after 16.10 release, the 16.10 kernels will be backported to 16.04, and 16.04.2 release installation media will use the updated kernel by default - v4.8 (current estimate for 16.10 kernel), such that affected systems will be able to use much newer kernel during installation and regular runtime eventually in the future (current approximate timing February 2017).

Is it at all possible to test this issue with mainline kernels? and/or I guess we can wait for 16.10 to get upgraded kernel and retest on 16.10 to see if this issue is resolved with a newer kernel.