Note that the same problem occurs with the 4.2 kernel in 16.04 (a pre-release from a week or two ago). I haven't yet tested the firmware workaround with 16.04.
Note that the same problem occurs with the 4.2 kernel in 16.04 (a pre-release from a week or two ago). I haven't yet tested the firmware workaround with 16.04.