From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mga09.intel.com ([134.134.136.24]:28514 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751956AbbFDTnb (ORCPT ); Thu, 4 Jun 2015 15:43:31 -0400 From: "Grumbach, Emmanuel" To: "kirill@shutemov.name" CC: "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "ilw@linux.intel.com" , "Berg, Johannes" Subject: Re: [BUG 4.1.0-rc6] iwlwifi: "Error sending REPLY_TXFIFO_FLUSH: time out after 2000ms" Date: Thu, 4 Jun 2015 19:43:02 +0000 Message-ID: <1433446982.22937.4.camel@intel.com> (sfid-20150604_214355_143272_4CFB178E) References: <20150604173710.GA1188@node.dhcp.inet.fi> <1433441600.17813.0.camel@intel.com> <20150604193234.GA1795@node.dhcp.inet.fi> In-Reply-To: <20150604193234.GA1795@node.dhcp.inet.fi> Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: T24gVGh1LCAyMDE1LTA2LTA0IGF0IDIyOjMyICswMzAwLCBLaXJpbGwgQS4gU2h1dGVtb3Ygd3Jv dGU6DQo+IE9uIFRodSwgSnVuIDA0LCAyMDE1IGF0IDA2OjEzOjIyUE0gKzAwMDAsIEdydW1iYWNo LCBFbW1hbnVlbCB3cm90ZToNCj4gPiBPbiBUaHUsIDIwMTUtMDYtMDQgYXQgMjA6MzcgKzAzMDAs IEtpcmlsbCBBLiBTaHV0ZW1vdiB3cm90ZToNCj4gPiA+IEhpLA0KPiA+ID4gDQo+ID4gPiBJJ3Zl IHRyaWdlcmVkIHRoZSBidWcgZmV3IHRpbWVzIGFmdGVyIHNldmVyYWwgc3VzcGVuZC9yZXN1bWUg Y3ljbGVzLg0KPiA+ID4gSGFyZHdhcmUgaXMgVGhpbmtwYWQgWDEgMjAxMyB3aXRoIEludGVsIENv cnBvcmF0aW9uIENlbnRyaW5vIEFkdmFuY2VkLU4NCj4gPiA+IDYyMDUgKDgwODY6MDA4NSkgKHJl diA5NikuDQo+ID4gPiANCj4gPiANCj4gPiBUaGlzIHJlYWxseSBsb29rcyBsaWtlIHRoZSBwbGF0 Zm9ybSBwcm9ibGVtIHBlb3BsZSBoYXZlIGJlZW4gaGl0dGluZy4NCj4gPiBUaGUgZGV2aWNlIGlz IG5vIGxvbmdlciBhY2Nlc3NpYmxlLg0KPiA+IFVuZm9ydHVuYXRlbHksIEkgcmVhbGx5IGRvbid0 IGtub3cgd2hhdCB3ZSBjYW4gZG8gaW4gdGhhdCBjYXNlLg0KPiANCj4gSXMgdGhlcmUgYW55dGhp bmcgSSBjYW4gZG8gdG8gcHJvdmlkZSBpbmZvIHlvdSBuZWVkPw0KPiANClRoaW5nIGlzIHRoYXQg SSBoYXZlIGFscmVhZHkgdGFsa2VkIHRvIHRoZSByZWxldmFudCBwZW9wbGUgaW50ZXJuYWxseS4N ClRoZSBwcm9ibGVtIGhlcmUgaXMgdGhhdCB0aGUgUENJIGJ1cyBpcyBub3QgZG9pbmcgaXRzIHdv cmsgYW55bW9yZS4gVGhpcw0KY2FuIGhhcHBlbiB3aGVuIG9uZSBvZiB0aGUgc2lkZXMgZG9lcyBh IHZpb2xhdGlvbiB0aGF0IHRoZSBvdGhlciBzaWRlDQppc24ndCByZWFkeSB0byBjb3BlIHdpdGgu IFRoZSBwcm9wZXIgd2F5IHRvIGNvcGUgd2l0aCB0aGlzIGlzIHRvIHRha2UNCnRoZSBtYWNoaW5l IGFuZCB0byBwbHVnIGl0IGluIGEgUENJIGFuYWx5emVyLiBUaGlzIGlzIGFuIGVxdWlwbWVudCB0 aGF0DQptb25pdG9ycyBhbGwgdGhlIFBDSSB0cmFuc2FjdGlvbnMgb24gdGhlIGJ1cy4gWW91IGFy ZSBub3QgdGhlIGZpcnN0IHRvDQpjb21wbGFpbiwgSSBoYXZlIGhhZCBhIGxvdCBvZiBjb21wbGFp bnRzIGFib3V0IHRoaXMgcmVjZW50bHkuIFNvbWVvbmUNCmV2ZW4gdHJpZWQgdG8gYmlzZWN0IGJl Y2F1c2UgaGUgdGhvdWdodCB0aGlzIHdhcyBhIHJlZ3Jlc3Npb24uIFRoaXMNCmRpZG4ndCBicmlu ZyBhbnkgY29uY2x1c2lvbiBzaW5jZSB0aGUgY29tbWl0IHRoYXQgc2VydmVkIGFzIHRoZSAnZ29v ZCcNCmJhc2VsaW5lIHdhc24ndCB3b3JraW5nIGFueW1vcmUgYWZ0ZXIgaGUgZmluaXNoZWQgdGhl IGJpc2VjdGlvbi4NCkluIHNob3J0LCB1bmxlc3MgeW91IGFyZSByZWFkeSB0byBzZW5kIHRoZSBh Y3R1YWwgc3lzdGVtIHRoYXQgaXMgZ2l2aW5nDQp5b3UgdHJvdWJsZSwgdGhlcmUgaXNuJ3QgbXVj aCBJIGNhbiBkby4NCllvdSBjYW4gdHJ5IHRoZSBzdGVwIGluDQpodHRwczovL2J1Z3ppbGxhLmtl cm5lbC5vcmcvc2hvd19idWcuY2dpP2lkPTkxMTcxI2M0MiB0byBzZWUgaWYgaXQgY2FuDQpoZWxw IHJlY292ZXJpbmcuDQo= From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752981AbbFDTnf (ORCPT ); Thu, 4 Jun 2015 15:43:35 -0400 Received: from mga09.intel.com ([134.134.136.24]:28514 "EHLO mga09.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751956AbbFDTnb (ORCPT ); Thu, 4 Jun 2015 15:43:31 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.13,554,1427785200"; d="scan'208";a="741139642" From: "Grumbach, Emmanuel" To: "kirill@shutemov.name" CC: "linux-wireless@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "ilw@linux.intel.com" , "Berg, Johannes" Subject: Re: [BUG 4.1.0-rc6] iwlwifi: "Error sending REPLY_TXFIFO_FLUSH: time out after 2000ms" Thread-Topic: [BUG 4.1.0-rc6] iwlwifi: "Error sending REPLY_TXFIFO_FLUSH: time out after 2000ms" Thread-Index: AQHQnu0jm5nWS9brA0+3EbOm86dEtJ2cdCEAgAAWIwCAAALsAA== Date: Thu, 4 Jun 2015 19:43:02 +0000 Message-ID: <1433446982.22937.4.camel@intel.com> References: <20150604173710.GA1188@node.dhcp.inet.fi> <1433441600.17813.0.camel@intel.com> <20150604193234.GA1795@node.dhcp.inet.fi> In-Reply-To: <20150604193234.GA1795@node.dhcp.inet.fi> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.254.151.63] 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 t54Jhjx5006976 On Thu, 2015-06-04 at 22:32 +0300, Kirill A. Shutemov wrote: > On Thu, Jun 04, 2015 at 06:13:22PM +0000, Grumbach, Emmanuel wrote: > > On Thu, 2015-06-04 at 20:37 +0300, Kirill A. Shutemov wrote: > > > Hi, > > > > > > I've trigered the bug few times after several suspend/resume cycles. > > > Hardware is Thinkpad X1 2013 with Intel Corporation Centrino Advanced-N > > > 6205 (8086:0085) (rev 96). > > > > > > > This really looks like the platform problem people have been hitting. > > The device is no longer accessible. > > Unfortunately, I really don't know what we can do in that case. > > Is there anything I can do to provide info you need? > Thing is that I have already talked to the relevant people internally. The problem here is that the PCI bus is not doing its work anymore. This can happen when one of the sides does a violation that the other side isn't ready to cope with. The proper way to cope with this is to take the machine and to plug it in a PCI analyzer. This is an equipment that monitors all the PCI transactions on the bus. You are not the first to complain, I have had a lot of complaints about this recently. Someone even tried to bisect because he thought this was a regression. This didn't bring any conclusion since the commit that served as the 'good' baseline wasn't working anymore after he finished the bisection. In short, unless you are ready to send the actual system that is giving you trouble, there isn't much I can do. You can try the step in https://bugzilla.kernel.org/show_bug.cgi?id=91171#c42 to see if it can help recovering. {.n++%ݶw{.n+{G{ayʇڙ,jfhz_(階ݢj"mG?&~iOzv^m ?I