Comment 14 for bug 1824687

Revision history for this message
Dirk (iggs) wrote :

regarding #2 I do not know which kernel ran before.

I assume linux-image-4.4.0-143 due to following apt history logs.
I however do not know if we rebooted.

I have a different type of server here with ubuntu. I can try to stress it and to see.
But I doubt I get the same quality of traffic since the other machine is an tor exit.

Start-Date: 2019-04-03 06:09:30
Commandline: /usr/bin/unattended-upgrade
Install: linux-modules-extra-4.4.0-145-generic:amd64 (4.4.0-145.171, automatic), linux-modules-4.4.0-145-generic:amd64 (4.4.0-145.171, automatic), linux-headers-4.4.0-145:amd64 (4.4.0-145.171, automatic), linux-image-4.4.0-145-generic:amd64 (4.4.0-145.171, automatic), linux-headers-4.4.0-145-generic:amd64 (4.4.0-145.171, automatic)
Upgrade: linux-headers-generic:amd64 (4.4.0.143.151, 4.4.0.145.153), linux-image-generic:amd64 (4.4.0.143.151, 4.4.0.145.153), linux-generic:amd64 (4.4.0.143.151, 4.4.0.145.153)
End-Date: 2019-04-03 06:10:20

Start-Date: 2019-03-17 06:21:38
Commandline: /usr/bin/unattended-upgrade
Install: linux-modules-4.4.0-143-generic:amd64 (4.4.0-143.169, automatic), linux-headers-4.4.0-143:amd64 (4.4.0-143.169, automatic), linux-image-4.4.0-143-generic:amd64 (4.4.0-143.169, automatic), linux-headers-4.4.0-143-generic:amd64 (4.4.0-143.169, automatic), linux-modules-extra-4.4.0-143-generic:amd64 (4.4.0-143.169, automatic)
Upgrade: linux-headers-generic:amd64 (4.4.0.142.148, 4.4.0.143.151), linux-image-generic:amd64 (4.4.0.142.148, 4.4.0.143.151), linux-generic:amd64 (4.4.0.142.148, 4.4.0.143.151)
End-Date: 2019-03-17 06:22:23