Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752457AbbEDHCV (ORCPT ); Mon, 4 May 2015 03:02:21 -0400 Received: from mga02.intel.com ([134.134.136.20]:46475 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752425AbbEDHCO (ORCPT ); Mon, 4 May 2015 03:02:14 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,365,1427785200"; d="scan'208";a="689439543" From: "Grumbach, Emmanuel" To: "jkosina@suse.cz" CC: "piotr.karbowski@gmail.com" , "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/zAIAAAKAAgAA7vYCAAFnKgIAP8o8AgAByhACAACf0AIAAAfMA Date: Mon, 4 May 2015 07:02:07 +0000 Message-ID: <1430722924.26162.4.camel@intel.com> References: <1429764440.4084.5.camel@intel.com> <1429780366.11859.1.camel@intel.com> <1429812611.23202.4.camel@intel.com> <1430713926.3388.1.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.255.198.144] Content-Type: text/plain; charset="utf-8" Content-ID: <1689A9DBC4553F4882EAE22D8B8AE746@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 t4472QDx023587 Content-Length: 1515 Lines: 33 On Mon, 2015-05-04 at 08:55 +0200, Jiri Kosina wrote: > On Mon, 4 May 2015, Grumbach, Emmanuel wrote: > > > > so over a past few days, I tried to perform a bisect, but failed as > > > expected. The issue is not reliably enough reproducible for me, so I ended > > > up with a completely bogus commit. > > > > > > *However*, now that I have been following the causes and symptoms more > > > closely (due to the bisect attempt), I have to confirm that the issue > > > happens much more often when the machine is question is physically being > > > moved when associated. > > > > > > > I am doing this all the time and I don't hit your problem. Without any > > logs I don't see how I can help here. Please try to catch logs of the > > crash. Thanks. > > I have provided them in the very first e-mail to this thread; see > > https://lkml.org/lkml/2015/4/22/601 > > If there is any way how to obtain more verbose / useful logs, please let > me know, I'll be happy to do that. > Sorry, my bad. I lost context here... So I really don't know what to say. I can't see any iwlwifi commit that could be causing this, OTOH, bisection didn't bring any results. You can try to unregister the device from PCI and then to rescan. It worked for some people. Other than that, I can't do much. Did you update your BIOS before you started to see this failure? ????{.n?+???????+%?????ݶ??w??{.n?+????{??G?????{ay?ʇڙ?,j??f???h?????????z_??(?階?ݢj"???m??????G????????????&???~???iO???z??v?^?m???? ????????I?