From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mout02.posteo.de (mout02.posteo.de [185.67.36.66]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C620646D579 for ; Sun, 4 Oct 2026 18:25:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=185.67.36.66 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791138326; cv=none; b=h6ZOSjvD6Gmgoqut31ncyC2glZ/M1TA+kVKch26/MIJuEQMY1VMnjh30R57bSoc9CSKaIAVEIDmuoFtW1hMOHnalKld1mhvX8G+0i0PPAH9dIcf4GK6laFjmZTroW8A93YGxsFJLVWa/cMUoSuFuOlbX9LBCxUw2/EymODC78Pc= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1791138326; c=relaxed/simple; bh=F1BF7ZhJBLxJ2rF4Nu+DwYItNVCoVTxgkn/uMcDkA5I=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=hlt0/J+ioinQ0CSbyxOAEcB8sXAPo+STdxiMzBLVREZCgdMwkCjTFMhBxBFbqdxJr2RLrPTjJf/uSASbZcXVHweaPt0uQ1vtwlJz9kOw/7cZ5apYYycUOC6TwkllnAb522K47Zvrtzh1yyIWamQiUJDlbSIcm35VwRsSbfixSzw= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=posteo.de; spf=pass smtp.mailfrom=posteo.de; dkim=pass (2048-bit key) header.d=posteo.de header.i=@posteo.de header.b=D3cEOvme; arc=none smtp.client-ip=185.67.36.66 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=posteo.de Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=posteo.de Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=posteo.de header.i=@posteo.de header.b="D3cEOvme" Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 9D6FD240101 for ; Sun, 4 Oct 2026 20:25:20 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=posteo.de; s=1984.8680eb; t=1791138320; bh=F1BF7ZhJBLxJ2rF4Nu+DwYItNVCoVTxgkn/uMcDkA5I=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:From:Content-Type: Content-Transfer-Encoding:From; b=D3cEOvmeqQYIv9ZVYmWcTV4lxl0d0MJelw8vdUv8x9wwqmuh0lkIrAYDei0Oi7Wni 8TU3DuaH01OUPSfxB5lxvIi2WxRHtWrMtGOFnEB7WDpLWhvmULZLH16TInSlrkWQ71 +7CyDxt1I+TTyd4K/mSzmUknCVFiZS0pY+WrPD9N1Pup1WJn1HUll8AH5HZIa8P5CE On9wFt6V7woEjCyXFoOVTNfNlep86LFHhwkPxJektxqyZSuz53pSIoAIzYl20fSd5r nf6MiCr5XsYZqLnManD200HZuLoHZIXfrHEFO+PU+UV2kE++M8QTneIxo9xzDIHAVC CEWziGQZb8mbA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4hyWCf1XxGz6v19; Sun, 4 Oct 2026 20:25:18 +0200 (CEST) Message-ID: <49b62a23-3e05-42de-b3ed-92294311cbdd@posteo.de> Date: Sun, 04 Oct 2026 18:25:20 +0000 Precedence: bulk X-Mailing-List: linux-wireless@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Subject: Re: [PATCH v2] wifi: mt76: mt7925: keep MLD membership consistent during link add To: Andrei Rusu de Castro , linux-wireless@vger.kernel.org, Devin Wittmayer Cc: Felix Fietkau , Lorenzo Bianconi , Ryder Lee , Shayne Chen , Sean Wang , Sean Wang , Thorsten Leemhuis , regressions@lists.linux.dev, linux-mediatek@lists.infradead.org References: <503eb10e-80cf-493e-95fd-04fc0f94ce01@posteo.de> <476e7721-580e-4a6b-86e5-5ed782a2c7ec@leemhuis.info> <20260829221319.25334-1-lucid_duck@justthetip.ca> <20261003180334.83575-1-lucid_duck@justthetip.ca> <20261004-mt7925-mld-v2-results-248bb5e6404f@empyreal.works> <20261004-mt7925-mld-v2-248bb5e6404f@empyreal.works> Content-Language: en-US, de-DE From: Jonas Hort In-Reply-To: <20261004-mt7925-mld-v2-248bb5e6404f@empyreal.works> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Hi Andrei, Tested v2 on top of v7.3-rc5 on my setup:   hardware   MT7925 PCIe (mt7925e)   firmware   20260813113118   AP         FritzBox 5690 Pro, FRITZ!OS 8.25   links      5GHz + 6GHz MLO (5200 + 6135 MHz)   stock 7.1.8 / 7.2-rc7   stalled after 3-5 minutes (WFDMA0 tail frozen)   v7.3-rc5 + v2           46 minutes, no stall Both links stayed active throughout, with about 4.2 GB received and 340 MB sent during the run. My watchdog (ping + WFDMA0 queue monitoring) did not trigger once. Tested-by: Jonas Hort Thanks for the fix! Jonas