Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932980AbbDWJM6 (ORCPT ); Thu, 23 Apr 2015 05:12:58 -0400 Received: from mga14.intel.com ([192.55.52.115]:52218 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752256AbbDWJMx (ORCPT ); Thu, 23 Apr 2015 05:12:53 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,629,1422950400"; d="scan'208";a="714170325" From: "Grumbach, Emmanuel" To: "jkosina@suse.cz" CC: "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "ilw@linux.intel.com" , "Berg, Johannes" Subject: Re: iwlwifi getting stuck with current Linus' tree (646da63172) Thread-Topic: iwlwifi getting stuck with current Linus' tree (646da63172) Thread-Index: AQHQfTzjJftp7aVbakmHVHohb9QTqJ1Z1GUAgAA6NoCAAA/zAA== Date: Thu, 23 Apr 2015 09:12:46 +0000 Message-ID: <1429780366.11859.1.camel@intel.com> References: <1429764440.4084.5.camel@intel.com> In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.254.151.56] Content-Type: text/plain; charset="utf-8" Content-ID: <11F035032F924B4BA848B282422A49B6@intel.com> 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 t3N9D6N7026322 Content-Length: 2290 Lines: 52 On Thu, 2015-04-23 at 10:15 +0200, Jiri Kosina wrote: > On Thu, 23 Apr 2015, Grumbach, Emmanuel wrote: > > > > I've been running current Linus' tree and have been getting system lockups > > > frequently. After a few "silent" lockups, I was able to obtain a dmesg > > > before the machine turned dead again (wifi stopped working shortly before > > > that). > > > > > > Before starting to debug / bisect (last known good on this machine is > > > 4.0-rc6), I am attaching the dmesg in case someone already knows what the > > > issue is. > > > > > > > I briefly went over the iwlwifi commits between 4.0-rc6 and linux/master > > and couldn't find anything obvious. > > Note that for the device you have, the commits that touch > > drivers/net/wireless/iwlwifi/mvm are not relevant. > > > > What you are seeing is that the PCI host is disconnecting the WiFi NIC > > for some weird reason. It is not the first time I see that, but > > unfortunately, I have never been able to debug this. I am personally not > > a HW PCI expert and I couldn't reproduce either... > > > > I am afraid I won't save you the time of the bisection, but I am not > > entirely sure that bisecting the iwlwifi driver is enough to find the > > commit that broke it. You may want to bisect the pci bus driver as well. > > The problem is that I can't really reliably reproduce it; it happens > rather often, but not so often that I could be certainly sure that my > distinction of good and bad kernels would be accurate. > > I will try it, but I expect the result to be bogus because of this, > unfortunately. > I can understand. A few users reported that this bug occurred more reliably when moving their system, although it seems very weird to me. > > First question is: Are you sure that 4.0-rc6 was good? > > Pretty much, yes. I've been running it for quite some time on this > machine without any issues. But after updating to current HEAD two days > ago, the issue triggered like 6 or 7 times already. > Ok - I will try to look at the PCI commits there although I am not sure I'll be able to make much sense of them... > Thanks, > ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?