From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753215AbcERKwA (ORCPT ); Wed, 18 May 2016 06:52:00 -0400 Received: from mga04.intel.com ([192.55.52.120]:19355 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752580AbcERKv6 (ORCPT ); Wed, 18 May 2016 06:51:58 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,328,1459839600"; d="scan'208";a="106070697" From: "Coelho, Luciano" To: "torvalds@linux-foundation.org" , "egrumbach@gmail.com" CC: "linux-kernel@vger.kernel.org" , linuxwifi , "Berg, Johannes" , "akpm@linux-foundation.org" , "kvalo@codeaurora.org" , "netdev@vger.kernel.org" , "davem@davemloft.net" , "linux-wireless@vger.kernel.org" , "Grumbach, Emmanuel" Subject: Re: [GIT] Networking Thread-Topic: [GIT] Networking Thread-Index: AQHRsLaf8kQ/OuMXFEaLwxa9HQIEjZ++dGMA Date: Wed, 18 May 2016 10:51:54 +0000 Message-ID: <1463568714.13625.18.camel@intel.com> References: <20160517.151113.367799295750703003.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.8.149] 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 mail.home.local id u4IAq5UV026857 Hi Emmanuel, Linus, On Wed, 2016-05-18 at 06:37 +0300, Emmanuel Grumbach wrote: > On Wed, May 18, 2016 at 4:00 AM, Linus Torvalds > wrote: > > > > On Tue, May 17, 2016 at 12:11 PM, David Miller > > wrote: > > > > > > > > > Highlights: > > Lowlights: > > > >  1) the iwlwifi driver seems to be broken > > > > My laptop that uses the intel 7680 iwlwifi module no longer > > connects > > to the network. It fails with a "Microcode SW error detected." and > > spews out register state over and over again. > Can we have the register state and the ASSERT / NMI / whatever that > goes along with it? > This clearly means that the firmware is crashing, but I don't know > why, > I copied here the lines that I need from another bug with another > device with another firmware, > but the log that we will still explain what I need: I managed to reproduce this bug locally with Linus' master.  I'm investigating the cause and I'll let you how it goes. -- Cheers, Luca.