Observed on the latest four kernel versions:
vmlinuz-5.4.0-7618-generic
vmlinuz-5.4.0-7629-generic
vmlinuz-5.4.0-7634-generic
vmlinuz-5.4.0-7642-generic
I don't know what triggers it. This can occur after boot -- not just after un-suspending. I think I read that killing NetworkManager is a workaround, but haven't been able to test that. Though syslog is flooded, NetworkManager doesn't log at all.
I think I see the same bug on Dell Inc. Latitude 7390 2-in-1/0YNG30, BIOS 1.10.0 07/04/2019
Distributor ID: Pop
Description: Pop!_OS 20.04 LTS
Release: 20.04
Codename: focal
Observed on the latest four kernel versions: 5.4.0-7618- generic 5.4.0-7629- generic 5.4.0-7634- generic 5.4.0-7642- generic
vmlinuz-
vmlinuz-
vmlinuz-
vmlinuz-
I don't know what triggers it. This can occur after boot -- not just after un-suspending. I think I read that killing NetworkManager is a workaround, but haven't been able to test that. Though syslog is flooded, NetworkManager doesn't log at all.