From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D364BCA9EAE for ; Tue, 29 Oct 2019 09:03:13 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id B001620717 for ; Tue, 29 Oct 2019 09:03:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730517AbfJ2JDM (ORCPT ); Tue, 29 Oct 2019 05:03:12 -0400 Received: from s3.sipsolutions.net ([144.76.43.62]:60414 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727933AbfJ2JDM (ORCPT ); Tue, 29 Oct 2019 05:03:12 -0400 Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.92.2) (envelope-from ) id 1iPNP6-0004Ha-89; Tue, 29 Oct 2019 10:03:04 +0100 Message-ID: Subject: Re: [PATCH v2] 802.11n IBSS: wlan0 stops receiving packets due to aggregation after sender reboot From: Johannes Berg To: Koen Vandeputte , Krzysztof =?UTF-8?Q?Ha=C5=82asa?= Cc: "David S. Miller" , linux-wireless@vger.kernel.org, netdev@vger.kernel.org, linux-kernel@vger.kernel.org Date: Tue, 29 Oct 2019 10:03:02 +0100 In-Reply-To: <30465e05-3465-f496-d57f-5e115551f5cb@ncentric.com> (sfid-20191029_094137_778584_BACBC770) References: <30465e05-3465-f496-d57f-5e115551f5cb@ncentric.com> (sfid-20191029_094137_778584_BACBC770) Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.30.5 (3.30.5-1.fc29) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2019-10-29 at 09:41 +0100, Koen Vandeputte wrote: > I can confirm the issue as I'm also seeing this sometimes in the field here. > > Sometimes when a devices goes out of range and then re-enters, > the link refuses to "come up", as in rx looks to be "stuck" without any > reports in system log or locking issues (lockdep enabled) Right. I've recently debugged this due to issues in distributed beaconing (rather than moving in/out of range), but I guess it would be relatively simple to reproduce this with wmediumd, if that can be controlled dynamically? What kernel are you running? You could check if you have 95697f9907bf ("mac80211: accept deauth frames in IBSS mode") 4b08d1b6a994 ("mac80211: IBSS: send deauth when expiring inactive STAs") which might help somewhat, but don't fully cover the case of moving out of range. johannes