On 21.08.2017 08:08, Neil Bothwick wrote: > Ah, so silentoldconfig is effectively the same as old config.
Silentoldconfig is quite a useful make target, since it only asks about newly introduced kernel options. > Does your old kernel still work ad before? Just wondering if another > update could have caused this. Both affected virtual servers run fine when I boot kernel 4.9.34 while leaving everything else unchanged. I'm currently comparing .config files for kernel versions 4.9.34 and 4.12.5 again, but nothing catches my eye. As for the symptoms, I wonder: Outbound nameserver access is seizing up completely, while I can still access the servers via SSH at the same time. Could it be something that kills UDP after the servers are active for a while, but leaves TCP alive? -Ralph
