Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753094AbdIGELn (ORCPT ); Thu, 7 Sep 2017 00:11:43 -0400 Received: from mga05.intel.com ([192.55.52.43]:9381 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750742AbdIGELl (ORCPT ); Thu, 7 Sep 2017 00:11:41 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.42,356,1500966000"; d="scan'208";a="308894093" From: "Coelho, Luciano" To: "torvalds@linux-foundation.org" , "davem@davemloft.net" , "kvalo@codeaurora.org" , "Berg, Johannes" , "Grumbach, Emmanuel" CC: linuxwifi , "netdev@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "linux-wireless@vger.kernel.org" , "akpm@linux-foundation.org" Subject: Re: [GIT] Networking Thread-Topic: [GIT] Networking Thread-Index: AQHTJ2e1r+p5kKpHi0+CCZ9Rdj3td6KovzaA Date: Thu, 7 Sep 2017 04:11:36 +0000 Message-ID: <1504757495.5400.89.camel@intel.com> References: <20170905.214143.826912481689443792.davem@davemloft.net> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.252.30.157] Content-Type: text/plain; charset="utf-8" Content-ID: MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id v874BlYY026283 Content-Length: 1744 Lines: 43 On Wed, 2017-09-06 at 16:27 -0700, Linus Torvalds wrote: > This pull request completely breaks Intel wireless for me. > > This is my trusty old XPS 13 (9350), using Intel Wireless 8260 (rev 3a). > > That remains a very standard Intel machine with absolutely zero odd > things going on. > > The firmware is iwlwifi-8000C-28.ucode from > iwl7260-firmware-25.30.13.0-75.fc26.noarch, and the kernel reports > > iwlwifi 0000:3a:00.0: loaded firmware version 27.455470.0 op_mode iwlmvm > > the thing starts acting badly with this: > > iwlwifi 0000:3a:00.0: FW Error notification: type 0x00000000 cmd_id 0x04 > iwlwifi 0000:3a:00.0: FW Error notification: seq 0x0000 service 0x00000004 > iwlwifi 0000:3a:00.0: FW Error notification: timestamp 0x 5D84 > iwlwifi 0000:3a:00.0: Microcode SW error detected. Restarting 0x2000000. > iwlwifi 0000:3a:00.0: Start IWL Error Log Dump: > iwlwifi 0000:3a:00.0: Status: 0x00000100, count: 6 > iwlwifi 0000:3a:00.0: Loaded firmware version: 27.455470.0 > iwlwifi 0000:3a:00.0: 0x00000038 | BAD_COMMAND > iwlwifi 0000:3a:00.0: 0x00A002F0 | trm_hw_status0 > ... > iwlwifi 0000:3a:00.0: 0x00000000 | isr status reg > ieee80211 phy0: Hardware restart was requested > iwlwifi 0000:3a:00.0: FW error in SYNC CMD MAC_CONTEXT_CMD This seems to be a problem with backwards-compatibility with FW version 27. We are now in version 31[1] and upgrading will probably fix that. But obviously the driver should not fail miserably like this with version 27, because it claims to support it still. I'm looking into this now and will provide a fix asap. [1] https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/iwlwifi-8000C-31.ucode -- Cheers, Luca.