Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp322441imm; Wed, 29 Aug 2018 22:57:39 -0700 (PDT) X-Google-Smtp-Source: ANB0VdYD9LbenHllGR0sarrQOfhU+YauFTTGORz00AlepUZxt5phVLxZvrStNtHARd/VutXs04ES X-Received: by 2002:a17:902:722:: with SMTP id 31-v6mr8716861pli.207.1535608659161; Wed, 29 Aug 2018 22:57:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1535608659; cv=none; d=google.com; s=arc-20160816; b=IUSc0/wvtnB0Xi9uCfT+fz8bDKVB93GHVjT2SDEG9o0/zWwphN98sJZWP+Xp8wbjvJ 5ZQoYqKOWa4MZ8r3P7Z/P3QVvAjWMKGk9sl3NFkR+WxQ89vdfe2e6H+YwBxDRQ3wOo+p 5Zfck75XcChgaAeByHnO7JwKhnOUEoIB4/CSgbNPFDcYywhfr8VesNtktaj+dVK1Obi3 LQXgDHR/wr2X5e/8R2OqyhG4y9zHlYkIq9ca1oRYoSWKyExrOBYSpVBkhY7wSIHEN9j4 7qEvZqOoKasNseaVuR/UDW2bSPzAISX8licsI5T5208fdC5NHKhSxNdLNUuKPk/SjcIy KRuQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:subject:content-transfer-encoding :mime-version:references:in-reply-to:date:cc:to:from:message-id :arc-authentication-results; bh=AopbsfzL0504daGsEsAIWhT8ta8FUBiZSNzFx7kMtvE=; b=S9Yxv5w3iI5kh239NWD2vJW1hKHLKTtQx51SwJd4DKp6htQ2RMS0yQhUpK26b7Edxc c2FLIG4RUSaWtqYD19kBaDFhnRhfPtm0rnLGfVVFgD0MXbFpJeNfEKFWyO5IBahLYhte OXGRDeJHaHrnEvHajPZW9faesds/eJceqxBZduM6Yz8jy8hjX6Kfpod1dlI0vGT58iQu 98Bo0RVccDc9RFM7M5QdksvRjmah7EgcqoeHLwnqTMOkXKSsvxuEXx0FJKvflM99cVdb Iu992OvrGepmNo+d+dYbcoUCNWdGrELOgRlD7axQZnEmZ8DabKLgEs5N6kuxbo5bKCf+ CBeQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-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 v19-v6si5904092pgh.36.2018.08.29.22.57.24; Wed, 29 Aug 2018 22:57:39 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-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-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727545AbeH3Jzz (ORCPT + 99 others); Thu, 30 Aug 2018 05:55:55 -0400 Received: from paleale.coelho.fi ([176.9.41.70]:45156 "EHLO farmhouse.coelho.fi" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725904AbeH3Jzz (ORCPT ); Thu, 30 Aug 2018 05:55:55 -0400 Received: from 91-156-4-241.elisa-laajakaista.fi ([91.156.4.241] helo=redipa) by farmhouse.coelho.fi with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.91) (envelope-from ) id 1fvFvR-0004UY-Fn; Thu, 30 Aug 2018 08:55:26 +0300 Message-ID: From: Luca Coelho To: Dave Young Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org, linuxwifi@intel.com Date: Thu, 30 Aug 2018 08:55:24 +0300 In-Reply-To: <20180830050632.GB2307@dhcp-128-65.nay.redhat.com> References: <20180829065442.GA3488@dhcp-128-65.nay.redhat.com> <6bb91f750e8d37d45da3c2cf1e7e5fc5d453ee8c.camel@coelho.fi> <20180830050632.GB2307@dhcp-128-65.nay.redhat.com> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5-1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 91.156.4.241 X-SA-Exim-Mail-From: luca@coelho.fi X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on farmhouse.coelho.fi X-Spam-Level: X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00, TVD_RCVD_IP autolearn=ham autolearn_force=no version=3.4.1 Subject: Re: Intel Wireless 8265/8275 (rev 78) issue X-SA-Exim-Version: 4.2.1 (built Tue, 02 Aug 2016 21:08:31 +0000) X-SA-Exim-Scanned: Yes (on farmhouse.coelho.fi) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 2018-08-30 at 13:06 +0800, Dave Young wrote: > On 08/30/18 at 07:15am, Luca Coelho wrote: > > On Wed, 2018-08-29 at 14:54 +0800, Dave Young wrote: > > > [ 74.123114] wlp61s0: authenticate with 00:1f:c6:82:0a:57 > > > [ 74.126099] wlp61s0: send auth to 00:1f:c6:82:0a:57 (try 1/3) > > > [ 74.139740] wlp61s0: authenticated > > > [ 74.140142] iwlwifi 0000:3d:00.0 wlp61s0: disabling HE/HT/VHT due to WEP/TKIP use > > > [ 74.140146] iwlwifi 0000:3d:00.0 wlp61s0: disabling HT as WMM/QoS is not supported by the AP > > > [ 74.140149] iwlwifi 0000:3d:00.0 wlp61s0: disabling VHT as WMM/QoS is not supported by the AP > > > > Your AP seems to be configured to use WEP or TKIP, which is not allowed > > by IEEE802.11n, so we disable all the higher rates, as you can see > > here. It should still work, but you will only get very basic rates > > (i.e. slow). > > Luka, thanks for the suggestion, moved AP to use WPA2-personal + AES. > seems I got only two features disabled this time: > [ 20.949347] iwlwifi 0000:3d:00.0 wlp61s0: disabling HT as WMM/QoS is not supported by the AP > [ 20.949351] iwlwifi 0000:3d:00.0 wlp61s0: disabling VHT as WMM/QoS is not supported by the AP > [ 20.949622] wlp61s0: associate with 00:1f:c6:82:0a:57 (try 1/3) There are many interoperability problems with old 11n APs that either support a draft version of the specs or simply have bugs in their implementations of the 11n specs. When we detect these problems, we disable 11n rates, so connectivity will be slower, but it will at least remain connected. This seems to be the case with your AP. :( > > > [ 2521.068469] wlp61s0: deauthenticating from 00:1f:c6:82:0a:57 by local choice (Reason: 3=DEAUTH_LEAVING) > > > > Other than that I can't really see what is going on, except that > > something is deciding to disconnect here... > > > > So, first thing I'd suggest would be to try to reconfigure your AP to > > use something else than WEP or TKIP, just to see if it improves in any > > way. > > Will observe if it works or not. BTW, my old laptop Thinkpad T440s works > well with the same AP. I hope it improves. If not, we should debug it further. It's a good thing not to use WEP and TKIP anyway, because they're not very secure anyway. > > And BTW, is this a regression in recent kernels or has this always > > happened to you with this laptop/AP combination? > > From my observation it just always happen, but hmm not 100% sure.. Okay, so we don't have enough information on this. It doesn't matter. What is the NIC on your old T440s? -- Cheers, Luca.