I noticed a similar bug #1541743 which describes the same problem, except also with 4.2.0-27; Might suggest this issue is related to one of the supporting packages related to the build process and not with a specific kernel version.
I noticed a similar bug #1541743 which describes the same problem, except also with 4.2.0-27; Might suggest this issue is related to one of the supporting packages related to the build process and not with a specific kernel version.