Comment 3 for bug 1474342

This morning there was a new kernel 3.19.0-25 so I updated again. The problem still exists.
While trying to do the update I noticed that 3.19.0-20 had some problem with aport.grub (not sure of the spelling).
Since the problem is at boot I decide to drop back to 3.19.0-18 which reported no errors.
Now perhaps the update would work?

No luck and the list of bad kernels keeps getting longer and longer. If the system decides to wipe out my old kernels I will really be dead in the water.
Can anyone give me some help?

Thanks,
Ilan