From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: 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 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) Date: Mon, 4 May 2015 07:02:07 +0000 Message-ID: <1430722924.26162.4.camel@intel.com> (sfid-20150504_090220_461790_F11CC64C) 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: Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: T24gTW9uLCAyMDE1LTA1LTA0IGF0IDA4OjU1ICswMjAwLCBKaXJpIEtvc2luYSB3cm90ZToNCj4g T24gTW9uLCA0IE1heSAyMDE1LCBHcnVtYmFjaCwgRW1tYW51ZWwgd3JvdGU6DQo+IA0KPiA+ID4g c28gb3ZlciBhIHBhc3QgZmV3IGRheXMsIEkgdHJpZWQgdG8gcGVyZm9ybSBhIGJpc2VjdCwgYnV0 IGZhaWxlZCBhcyANCj4gPiA+IGV4cGVjdGVkLiBUaGUgaXNzdWUgaXMgbm90IHJlbGlhYmx5IGVu b3VnaCByZXByb2R1Y2libGUgZm9yIG1lLCBzbyBJIGVuZGVkIA0KPiA+ID4gdXAgd2l0aCBhIGNv bXBsZXRlbHkgYm9ndXMgY29tbWl0Lg0KPiA+ID4gDQo+ID4gPiAqSG93ZXZlciosIG5vdyB0aGF0 IEkgaGF2ZSBiZWVuIGZvbGxvd2luZyB0aGUgY2F1c2VzIGFuZCBzeW1wdG9tcyBtb3JlIA0KPiA+ ID4gY2xvc2VseSAoZHVlIHRvIHRoZSBiaXNlY3QgYXR0ZW1wdCksIEkgaGF2ZSB0byBjb25maXJt IHRoYXQgdGhlIGlzc3VlIA0KPiA+ID4gaGFwcGVucyBtdWNoIG1vcmUgb2Z0ZW4gd2hlbiB0aGUg bWFjaGluZSBpcyBxdWVzdGlvbiBpcyBwaHlzaWNhbGx5IGJlaW5nIA0KPiA+ID4gbW92ZWQgd2hl biBhc3NvY2lhdGVkLg0KPiA+ID4gDQo+ID4gDQo+ID4gSSBhbSBkb2luZyB0aGlzIGFsbCB0aGUg dGltZSBhbmQgSSBkb24ndCBoaXQgeW91ciBwcm9ibGVtLiBXaXRob3V0IGFueQ0KPiA+IGxvZ3Mg SSBkb24ndCBzZWUgaG93IEkgY2FuIGhlbHAgaGVyZS4gUGxlYXNlIHRyeSB0byBjYXRjaCBsb2dz IG9mIHRoZQ0KPiA+IGNyYXNoLiBUaGFua3MuDQo+IA0KPiBJIGhhdmUgcHJvdmlkZWQgdGhlbSBp biB0aGUgdmVyeSBmaXJzdCBlLW1haWwgdG8gdGhpcyB0aHJlYWQ7IHNlZQ0KPiANCj4gCWh0dHBz Oi8vbGttbC5vcmcvbGttbC8yMDE1LzQvMjIvNjAxDQo+IA0KPiBJZiB0aGVyZSBpcyBhbnkgd2F5 IGhvdyB0byBvYnRhaW4gbW9yZSB2ZXJib3NlIC8gdXNlZnVsIGxvZ3MsIHBsZWFzZSBsZXQgDQo+ IG1lIGtub3csIEknbGwgYmUgaGFwcHkgdG8gZG8gdGhhdC4NCj4gDQoNCg0KU29ycnksIG15IGJh ZC4gSSBsb3N0IGNvbnRleHQgaGVyZS4uLiBTbyBJIHJlYWxseSBkb24ndCBrbm93IHdoYXQgdG8N CnNheS4gSSBjYW4ndCBzZWUgYW55IGl3bHdpZmkgY29tbWl0IHRoYXQgY291bGQgYmUgY2F1c2lu ZyB0aGlzLCBPVE9ILA0KYmlzZWN0aW9uIGRpZG4ndCBicmluZyBhbnkgcmVzdWx0cy4gWW91IGNh biB0cnkgdG8gdW5yZWdpc3RlciB0aGUgZGV2aWNlDQpmcm9tIFBDSSBhbmQgdGhlbiB0byByZXNj YW4uIEl0IHdvcmtlZCBmb3Igc29tZSBwZW9wbGUuIE90aGVyIHRoYW4gdGhhdCwNCkkgY2FuJ3Qg ZG8gbXVjaC4gRGlkIHlvdSB1cGRhdGUgeW91ciBCSU9TIGJlZm9yZSB5b3Ugc3RhcnRlZCB0byBz ZWUgdGhpcw0KZmFpbHVyZT8NCg== From mboxrd@z Thu Jan 1 00:00:00 1970 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 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ʇڙ,jfhz_(階ݢj"mG?&~iOzv^m ?I