Comment 6 for bug 1992517

After some more testing, I don't think these parameters matter. Reloading the module (i.e. removing and inserting it again) sometimes fixes the issue for some time, that's why I thought these settings fixed the issue, but the behaviour after module reload is independent of these parameters.

I have also narrowed down the last working kernel version to 5.18, not 5.16. Another bug seems to be introduced in 5.17 ("failed to get tx report from firmware", "timed out to flush queue 0", "imed out to flush pci tx ring[1]" in dmesg, intermittent failures to send packets) that confounded me. I am currently bisecting commits between 5.18 and 5.19 to find the one that causes the issue in this bug report.