jow-:

Thanks for the report but why didn't you comment on one of the related bugs? Instead of four "random ath9k wifi issues" bugs we know have five...

psyborg:

[[https://bugs.openwrt.org/index.php?do=details&task_id=801|801]] device use ath10k driver
[[https://bugs.openwrt.org/index.php?do=details&task_id=1373|1373]] device use rt2x00 driver
[[https://bugs.openwrt.org/index.php?do=details&task_id=1582|1582]] device use marvell driver

so, completely unrelated

[[https://bugs.openwrt.org/index.php?do=details&task_id=1180|1180]] already contains possible solution, have you tried it?

StephanRichter:

@Jo-Philipp Wich: because I was not sure, whether it is the same bug. Obviously, some think it is not. Usually Bugtrackers allow to merge issues?

@Psyborg: Yes, I have seen that these are different drivers. But the problem
described is very similar. Maybe it is not a problem with the driver (which would explain the different behaviours depending on configuration)? I'm not an expert, just a tought.
I also read the proposed workaround (it is not a real solution, is it?), but as I wrote, I'm not an expert. I have no clue how to "remove 305-ath9k-limit-retries-for-powersave-response-frames.patch" or what "by forcing ps=false" means.

Maybe someone can help me out here? If so, I'm willing to test if this works for me and report here.

StephanRichter:

I just noticed I forgot to mention the problem in the task title - is there a way to alter it?