Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp358423ybl; Sat, 17 Aug 2019 02:09:49 -0700 (PDT) X-Google-Smtp-Source: APXvYqxJF+C+CTEyE9bLUXKJ5rXLXs3oZ//3WnlG1rD6dcTa/sZ1AjfumesRxz7/Ko0Zwklc8B2H X-Received: by 2002:a63:e5a:: with SMTP id 26mr10813146pgo.3.1566032989166; Sat, 17 Aug 2019 02:09:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566032989; cv=none; d=google.com; s=arc-20160816; b=ZXF1Dbfx5U4T3G05WButJ5BPDHipq2ITopg0DnHfgRas6bByXO9ilYf95Mj4R/zOmG MwCzqPkcKPA2KSJdn/TLmbQ8/3BcRNWDmPtxZbk9Ol6Ni7J7s4e/P+py0S3d/bHoNmmV A10uK9TRMeaErxceG1n762rVZMV4ppQE9SarQqG7jQCcrnF3Ei3d+FyoKy15wlMXksRy dU/m4C6zpTrKN93gm4stRmlclY5O9FhvM3p3fKNRXXI2nxNZs1/S+E66hQRpKdGdtxIi 5fHGYC5FlzYJIBV0korV+dAzcrdVtBHXeyKNZUpHSmHtZdCN2G/anSLMvofwI6ZhmrK/ smgw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:message-id:date :references:in-reply-to:subject:cc:to:from; bh=6SOcv+nurpGhG+WY88wxRHhIo92sZuyoghpfe2lucI0=; b=i9guREi9CZzpVMGjR9pQFWHOceiAiojTP9MEHGhoG0ye4s2rIexB8BJCCcmetrrb1I oARX044MwflNMTys0HryvSsWcoX8oAmZ2LKMAsw2cnyBgMbIehNjWM/ZOneAeqg7CL0H y0BDpGR4D64XOzeaEAgaTrj11/B9xxguHsLNpqj5jR9cLh3DnHOFYgRWB5oR1eV/IMXf vBOuKKFaVSXUwaQdppmlzmtaUc22otFCo8N4qwpLJPrwKUCMBTtHoNd2signUA+9Ub7r 44btdGpoWzXtnxZG3NXWJmid3NKHcdn+a9EQFWxuRL0FIqeJw8cYElklGWoiz/LO7itT wnyA== 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 q5si5670321pll.279.2019.08.17.02.09.34; Sat, 17 Aug 2019 02:09:49 -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 S1726082AbfHQJIq (ORCPT + 99 others); Sat, 17 Aug 2019 05:08:46 -0400 Received: from depni-mx.sinp.msu.ru ([213.131.7.21]:25 "EHLO depni-mx.sinp.msu.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725267AbfHQJIq (ORCPT ); Sat, 17 Aug 2019 05:08:46 -0400 X-Greylist: delayed 523 seconds by postgrey-1.27 at vger.kernel.org; Sat, 17 Aug 2019 05:08:45 EDT Received: from spider (unknown [109.63.188.125]) by depni-mx.sinp.msu.ru (Postfix) with ESMTPSA id 54DBD1BF45B; Sat, 17 Aug 2019 12:00:01 +0300 (MSK) From: Serge Belyshev To: Stuart Little Cc: Johannes Berg , Emmanuel Grumbach , Luca Coelho , kernel list , Intel Linux Wireless , linux-wireless@vger.kernel.org, Haim Dreyfuss Subject: Re: PROBLEM: 5.3.0-rc* causes iwlwifi failure In-Reply-To: <20190817041258.GA1641@chirva-slack.chirva-slack> References: <20190817041258.GA1641@chirva-slack.chirva-slack> Date: Sat, 17 Aug 2019 11:59:59 +0300 Message-ID: <87y2zsf9ps.fsf@depni.sinp.msu.ru> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > I am on an Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz running Linux > x86_64 (Slackware), with a custom-compiled 5.3.0-rc4 (.config > attached). > > I am using the Intel wifi adapter on this machine: > > 02:00.0 Network controller: Intel Corporation Device 24fb (rev 10) > > with the iwlwifi driver. I am attaching the output to 'lspci -vv -s > 02:00.0' as the file device-info. > > All 5.3.0-rc* versions I have tried (including rc4) cause multiple > dmesg iwlwifi-related errors (dmesg attached). Examples: > > iwlwifi 0000:02:00.0: Failed to get geographic profile info -5 > iwlwifi 0000:02:00.0: Microcode SW error detected. Restarting 0x82000000 > iwlwifi 0000:02:00.0: 0x00000038 | BAD_COMMAND > I have my logs filled with similar garbage throughout 5.3-rc*. Also since 5.3-rcsomething not only it WARNS in dmesg about firmware failure, but completely stops working after suspend/resume cycle. It looks like that: commit 4fd445a2c855bbcab81fbe06d110e78dbd974a5b Author: Haim Dreyfuss Date: Thu May 2 11:45:02 2019 +0300 iwlwifi: mvm: Add log information about SAR status Inform users when SAR status is changing. Signed-off-by: Haim Dreyfuss Signed-off-by: Luca Coelho is the culprit. (manually) reverting it on top of 5.3-rc4 makes everything work again.