Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp698758ybl; Fri, 9 Aug 2019 12:20:15 -0700 (PDT) X-Google-Smtp-Source: APXvYqy62wfEbdJT2T7lgvvFUnnMeOUTg3FZx01VaH6IFZaD2XGspyWOdI/w7uFZn7ibjt+Yet6C X-Received: by 2002:a17:90a:ca11:: with SMTP id x17mr10961695pjt.107.1565378414988; Fri, 09 Aug 2019 12:20:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1565378414; cv=none; d=google.com; s=arc-20160816; b=0YTrssrp1oRmK4U4xJKKW/ASEyPfu154MFSsVT/81zwZZIxoPqAH69HvcqsNqQop9z IsuKsC9Se1b7BS85qfMIEQj7DnyHifqcphC/LmnkgrU9F87axDkSXgx9XVS83CNVW7q5 akx65oIMd0Kjhhgmi9jVYcypmdVLfk5XyGaTNlPJyhv2hZznxlOx6P9rbe+XxFPlflB5 MQmxx7EeDgAeiZfStXN+Qa3YW8vbDbmMmyWYGhpPQ/lnBDkyfaja1YvwPbS/iL2MuLE1 dHglV2ZQr5+e6bIdHLfQNdgacrdF2zqFqEfwX3CXBG5wrw+YwoeF5IzezZj6dOtywbSn ljEg== 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 :content-language:in-reply-to:mime-version:date:message-id:from :references:cc:to:subject; bh=q9nQDJMzuHCCdgY8NK+Xq1Gr9RLCMC3gm+HGtekaWEU=; b=XwTWITrT8ZD09EGeelxpM1RZ47oNakOFW4xtL53xBlfP8si1K/2xH0wZ7aNeRK174i 0WOOvgYIM+rc94EnGy2Jkoxnq+SRkf2YXiux32WsMYdg/K4gSq/OamGbALtbLxcFWXPC O+QSmNva+zUwUEvYvkhM/YKYgHid7CSvuefEf9Pavvz+cI4lJ0F508O7Bj5EAcvp6jRA leJEBAP1vF+PTu6ziqOXX3w86MGmiOw2w8H8HhohGEWBELrUUOoeIdS9C2nRnct3JtRD RZCYbUk6dNng1dR0S5SBbvU6X+NwXGexj4JJO7C9j2Ki7W/6ztsrcPq6m2t5t/QuzVrE CEQw== 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 m32si52281244pld.236.2019.08.09.12.19.48; Fri, 09 Aug 2019 12:20:14 -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 S1725943AbfHITPY (ORCPT + 99 others); Fri, 9 Aug 2019 15:15:24 -0400 Received: from mx2.yrkesakademin.fi ([85.134.45.195]:33007 "EHLO mx2.yrkesakademin.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725904AbfHITPY (ORCPT ); Fri, 9 Aug 2019 15:15:24 -0400 X-Greylist: delayed 905 seconds by postgrey-1.27 at vger.kernel.org; Fri, 09 Aug 2019 15:15:23 EDT Subject: Re: Regression with the latest iwlwifi-9260-*-46.ucode To: Takashi Iwai , Luca Coelho CC: , Josh Boyer , Johannes Berg , Emmanuel Grumbach , , References: <280dad08ba9864755c3c45ed3ce26d602fe18a49.camel@intel.com> <38635c1b10018859457787ecff4f92a3ceec34a4.camel@coelho.fi> <99462e51eda721d5d85d9ea9e2c28da62f8b54f5.camel@coelho.fi> From: Thomas Backlund Message-ID: <1736104d-3ef4-83d1-2672-00f36b922ef7@mageia.org> Date: Fri, 9 Aug 2019 22:00:15 +0300 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="windows-1252"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-WatchGuard-Spam-ID: str=0001.0A0C020D.5D4DC64B.002F,ss=1,re=0.000,recu=0.000,reip=0.000,cl=1,cld=1,fgs=0 X-WatchGuard-Spam-Score: 0, clean; 0, virus threat unknown X-WatchGuard-Mail-Client-IP: 85.134.45.195 X-WatchGuard-Mail-From: tmb@mageia.org Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org Den 06-08-2019 kl. 16:04, skrev Takashi Iwai: > On Mon, 05 Aug 2019 14:03:55 +0200, > Now we got a feedback from the latest linux-firmware (20190726) and > surprising the result was negative. The dmesg after the cold boot is > found at: > https://bugzilla.suse.com/show_bug.cgi?id=1142128#c26 > > The kernel is 5.2.3, so it should be new enough. > > If anything else needed (or something missing), let us know. > I read on some forum that some commented that the "Add support for SAR South Korea limitation" fix is needed, but it seemed weird... Anyway, with theese on top of 5.2.7 39bd984c203e86f3 iwlwifi: mvm: don't send GEO_TX_POWER_LIMIT on version < 41 f5a47fae6aa3eb06 iwlwifi: mvm: fix version check for GEO_TX_POWER_LIMIT support 0c3d7282233c7b02 iwlwifi: Add support for SAR South Korea limitation We have confirmation from an affected user that its now stable with both older and newer firmwares... And we earlier tried with only the: 39bd984c203e86f3 iwlwifi: mvm: don't send GEO_TX_POWER_LIMIT on version < 41 But that did not help (not that I really expected it since its loading version 46 firmwares anyway) So my guess is that the newer firmware actually subtly expects to get the behaviour of the: 0c3d7282233c7b02 iwlwifi: Add support for SAR South Korea limitation Of course that's still guessing and I assume only Intel fw guys can verify that... -- Thomas