Comment 6 for bug 1894867

Since that time, I determined that the cause of this problem is that I have two kernels for each kernel release: lowlatency and generic. The upgrade puts the headers in for generic whether I am running lowlatency when the silent upgrade takes place or do the upgrade in a terminal window by hand. Therefore, the upgrade does not check to see if I have the same release in both lowlatency and generic. I have to remember to install the headers for lowlatency after any kernel update. Since the header update includes virtualbox updates I analyze that this solves the failed WiFi and Virtualbox corruption I found before I realized the headers were not up to date. The failed WiFi and Virtualbox were disguised because I could boot partially with previous low latency headers but not correctly. The ethernet hid the WiFi problem.

I recommend that upgrades for kernels and headers be scripted for when both lowlatency and generic (when present).