Comment 22 for bug 1567237

However there is something that is very worrying about marking this bug as duplicate of the one for 4.2 kernel: the other bug was marked as medium importance because I always could use the 3.19 series of kernels to get security patches. But now that the 3.19 series of kernels also got broken, I am left with no good option to further get security patches. I could downgrade to 3.16 series of kernels to see if that series is still OK, but I do not want to do that. I would rather switch to another operating system rather that downgrade my kernel lower than 3.19. That is why I do not agree that this bug will not be looked at and the other one (for 4.2 kernels) is less important. Could you change this the other way around: make the other bug a duplicate of this one and keep this one opened with its higher importance and focus on this one? I think that would make it also easier to figure out what got broken: by looking at the changes between 3.19.0-51 kernel (which works) and 3.19.0-58 kernel (which doesn't) it should be easier to figure out what is the problem than by comparing 3.19.0-51 kernel with a 4.2 kernel.