[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20231213172757.46199-1-rwahler@gmx.net>
Date: Wed, 13 Dec 2023 18:27:57 +0100
From: rwahler@....net
To: kvalo@...nel.org
Cc: linux-kernel@...r.kernel.org,
Sultan Alsawaf <sultan@...neltoast.com>
Subject: Re: [PATCH 1/2] wifi: mt76: mt7921: Disable powersaving by default
From: Sultan Alsawaf <sultan@...neltoast.com>
Sultan Alsawaf <sultan@...neltoast.com> 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.
Kalle Valo <kvalo@...nel.org> writes:
> Mario Limonciello <mario.limonciello@....com> 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.
If i can help with some tests to find the problem i'm happy to support you.
Powered by blists - more mailing lists