(adding back linux-wireless, please don't drop lists and people from Cc) rwahler@xxxxxxx writes: > From: Sultan Alsawaf <sultan@xxxxxxxxxxxxxxx> > > Sultan Alsawaf <sultan@xxxxxxxxxxxxxxx> writes: > >> 3. For insignificant/low-bandwidth traffic like ICMP to the AP, high latency is >> expected since the amount of traffic doesn't warrant kicking the chipset out >> of powersave. So although it's not pretty to look at, bad ping times to the >> AP aren't representative of the full user experience. > > Without the proposed patch ping times are often > 3000ms with a packet > loss of ~20%. And it's not only ICMP packets because i.e. ssh to the > laptop is also not working. It is unusable slow and very often the > connection breaks completely. To which direction? When reporting power save issues it's a good idea to be specific as possible, we don't have crystal balls. > Kalle Valo <kvalo@xxxxxxxxxx> writes: > >> Mario Limonciello <mario.limonciello@xxxxxxx> writes: >> >> > Several users have reported awful latency when powersaving is enabled >> > with certain access point combinations. >> >> What APs are these exactly? In the past 802.11 Power Save Mode was >> challenging due to badly behaving APs. But nowadays with so many mobile >> devices in the market I would assume that APs work a lot better. It >> would be best to investigate the issues in detail and try to fix them in >> mt76, assuming the bugs are in mt76 driver or firmware. > > I'm using a FritzBox 6591 Cable Router with latest Firmware for Wlan > and use a Framework13 Laptop with built in MT7921 module. I can > reliably reproduce the problem with high round trip times and packet > loss for inbound connections. Have you tried other clients with that AP? Especially mobile devices like phones is good to test, they usually have pretty aggressive power savings. Also testing with other APs is good. > If i can help with some tests to find the problem i'm happy to support you. I don't know about mt76 driver internals but hopefully others can help. But what I recommend is to provide comprehensive and detailed bug reports, even better if you can include a 802.11 frame capture from a sniffer. Just saying "it doesn't work" doesn't get very far. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
