Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp4171852ybg; Tue, 29 Oct 2019 03:16:35 -0700 (PDT) X-Google-Smtp-Source: APXvYqzas3Xp6Jqi7pGQhwYOQPraCUAr0SWfsF1XjbekaxNdV1Qa9Hz2nWmw6AF4f0erG4BTH0OJ X-Received: by 2002:a17:906:eda2:: with SMTP id sa2mr2373740ejb.14.1572344195609; Tue, 29 Oct 2019 03:16:35 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572344195; cv=none; d=google.com; s=arc-20160816; b=WAcYcrlEaYsXyEEfT2gc4H/0BZmgBaDJWgKklwCbvQqpOrYUqIS5hJ/sFqYiHooc5q XkHfSlbc31ycrkH7/lhDYucRweKfIi2qlrg/chkeuHLYUDj2aP21I2wqs3Tl/6WztwoN eyP5qhGUSFUqW2Nc0ylX5brQ4UlAFjhC/e1azXSyenyXD/vujUXVzncKXbyE3q/Tzke4 o4pMcE8eQU1/Ss71wSPMFV7h2oGTbwvanO6nT7Mh18F2gj+UuQdOCFEhmIYNtczgYutU Zx6MD8M2m0IIXKQFhZxw2uq3Mt6GdGu9/nuUjuSVCKzsjHotCtxcFnlp9yBavqVY8UEw yf9w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=DPaHC+IAqdLUlr+Tg3VmL3gzB0Q1Iv+hfOtIOMxEG8E=; b=K0uT8BjjK3/08nRGN2oBa2gGTyT7X73NHDfAiIt9vHzrGK0dF5A9tTBN92OMPSIs+u e/a7vk7qx9Y0gZ1Kb8rKLXxFROl3HrGelGP6tmsdtf8+eVAF/oeZdYWC/hnYMQhZg8N/ a/HOJWjYN59gxzkUPQndl5j14TFhFC7EbTIcfixRxPXNOTHOlVRu8h2aRKsmX+pFamcf AkHj7W9r2dX16ZAqBOnnOvDkB3qGIqY1v6euzc24cxMagg/RwRqjGaLzKGPpDhO4WZvG bH4W/is41WH+RmfihuhcUJZUpOY1SEdb+BGkI/ANCshVhVzQwVmBR45Rl9nzaeUGRGqA AvWQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id pg2si7997294ejb.133.2019.10.29.03.16.10; Tue, 29 Oct 2019 03:16:35 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-wireless-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730473AbfJ2JDM (ORCPT + 99 others); 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-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@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