After doing some research I'm quite sure that this bug was introduced by [1] in the 5.4.29 mainline kernel and the 5.4.0-22.26 ubuntu kernel.
The bug was already fixed by [2] in the 5.4.32 mainline kernel. At least that's the case on my machine [3] and Heiner Kallweit also pointed in this direction [4].
The only thing that doesn't fit in this picture is that adding realtek to /etc/modules fixed the problem for Ryan. But it didn't fix the problem for me.
After doing some research I'm quite sure that this bug was introduced by [1] in the 5.4.29 mainline kernel and the 5.4.0-22.26 ubuntu kernel.
The bug was already fixed by [2] in the 5.4.32 mainline kernel. At least that's the case on my machine [3] and Heiner Kallweit also pointed in this direction [4].
The only thing that doesn't fit in this picture is that adding realtek to /etc/modules fixed the problem for Ryan. But it didn't fix the problem for me.
[1] https:/ /git.kernel. org/pub/ scm/linux/ kernel/ git/stable/ linux.git/ commit/ ?h=v5.4. 32&id=791c420f4 2289fe9afed9e32 5c6b21eb6a5a329 e
[2] https:/ /git.kernel. org/pub/ scm/linux/ kernel/ git/stable/ linux.git/ commit/ ?h=v5.4. 32&id=3fcd53b1d 859799686a08785 afb8990566c31cf a
[3] https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1873552
[4] https:/ /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/1873512/ comments/ 20