From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To: "jkosina@suse.cz" <jkosina@suse.cz>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ilw@linux.intel.com" <ilw@linux.intel.com>,
"Berg, Johannes" <johannes.berg@intel.com>
Subject: Re: iwlwifi getting stuck with current Linus' tree (646da63172)
Date: Thu, 23 Apr 2015 09:12:46 +0000 [thread overview]
Message-ID: <1429780366.11859.1.camel@intel.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1504231011500.3695@pobox.suse.cz>
T24gVGh1LCAyMDE1LTA0LTIzIGF0IDEwOjE1ICswMjAwLCBKaXJpIEtvc2luYSB3cm90ZToNCj4g
T24gVGh1LCAyMyBBcHIgMjAxNSwgR3J1bWJhY2gsIEVtbWFudWVsIHdyb3RlOg0KPiANCj4gPiA+
IEkndmUgYmVlbiBydW5uaW5nIGN1cnJlbnQgTGludXMnIHRyZWUgYW5kIGhhdmUgYmVlbiBnZXR0
aW5nIHN5c3RlbSBsb2NrdXBzIA0KPiA+ID4gZnJlcXVlbnRseS4gQWZ0ZXIgYSBmZXcgInNpbGVu
dCIgbG9ja3VwcywgSSB3YXMgYWJsZSB0byBvYnRhaW4gYSBkbWVzZyANCj4gPiA+IGJlZm9yZSB0
aGUgbWFjaGluZSB0dXJuZWQgZGVhZCBhZ2FpbiAod2lmaSBzdG9wcGVkIHdvcmtpbmcgc2hvcnRs
eSBiZWZvcmUgDQo+ID4gPiB0aGF0KS4NCj4gPiA+IA0KPiA+ID4gQmVmb3JlIHN0YXJ0aW5nIHRv
IGRlYnVnIC8gYmlzZWN0IChsYXN0IGtub3duIGdvb2Qgb24gdGhpcyBtYWNoaW5lIGlzIA0KPiA+
ID4gNC4wLXJjNiksIEkgYW0gYXR0YWNoaW5nIHRoZSBkbWVzZyBpbiBjYXNlIHNvbWVvbmUgYWxy
ZWFkeSBrbm93cyB3aGF0IHRoZSANCj4gPiA+IGlzc3VlIGlzLg0KPiA+ID4gDQo+ID4gDQo+ID4g
SSBicmllZmx5IHdlbnQgb3ZlciB0aGUgaXdsd2lmaSBjb21taXRzIGJldHdlZW4gNC4wLXJjNiBh
bmQgbGludXgvbWFzdGVyDQo+ID4gYW5kIGNvdWxkbid0IGZpbmQgYW55dGhpbmcgb2J2aW91cy4N
Cj4gPiBOb3RlIHRoYXQgZm9yIHRoZSBkZXZpY2UgeW91IGhhdmUsIHRoZSBjb21taXRzIHRoYXQg
dG91Y2gNCj4gPiBkcml2ZXJzL25ldC93aXJlbGVzcy9pd2x3aWZpL212bSBhcmUgbm90IHJlbGV2
YW50Lg0KPiA+IA0KPiA+IFdoYXQgeW91IGFyZSBzZWVpbmcgaXMgdGhhdCB0aGUgUENJIGhvc3Qg
aXMgZGlzY29ubmVjdGluZyB0aGUgV2lGaSBOSUMNCj4gPiBmb3Igc29tZSB3ZWlyZCByZWFzb24u
IEl0IGlzIG5vdCB0aGUgZmlyc3QgdGltZSBJIHNlZSB0aGF0LCBidXQNCj4gPiB1bmZvcnR1bmF0
ZWx5LCBJIGhhdmUgbmV2ZXIgYmVlbiBhYmxlIHRvIGRlYnVnIHRoaXMuIEkgYW0gcGVyc29uYWxs
eSBub3QNCj4gPiBhIEhXIFBDSSBleHBlcnQgYW5kIEkgY291bGRuJ3QgcmVwcm9kdWNlIGVpdGhl
ci4uLg0KPiA+IA0KPiA+IEkgYW0gYWZyYWlkIEkgd29uJ3Qgc2F2ZSB5b3UgdGhlIHRpbWUgb2Yg
dGhlIGJpc2VjdGlvbiwgYnV0IEkgYW0gbm90DQo+ID4gZW50aXJlbHkgc3VyZSB0aGF0IGJpc2Vj
dGluZyB0aGUgaXdsd2lmaSBkcml2ZXIgaXMgZW5vdWdoIHRvIGZpbmQgdGhlDQo+ID4gY29tbWl0
IHRoYXQgYnJva2UgaXQuIFlvdSBtYXkgd2FudCB0byBiaXNlY3QgdGhlIHBjaSBidXMgZHJpdmVy
IGFzIHdlbGwuDQo+IA0KPiBUaGUgcHJvYmxlbSBpcyB0aGF0IEkgY2FuJ3QgcmVhbGx5IHJlbGlh
Ymx5IHJlcHJvZHVjZSBpdDsgaXQgaGFwcGVucyANCj4gcmF0aGVyIG9mdGVuLCBidXQgbm90IHNv
IG9mdGVuIHRoYXQgSSBjb3VsZCBiZSBjZXJ0YWlubHkgc3VyZSB0aGF0IG15IA0KPiBkaXN0aW5j
dGlvbiBvZiBnb29kIGFuZCBiYWQga2VybmVscyB3b3VsZCBiZSBhY2N1cmF0ZS4NCj4gDQo+IEkg
d2lsbCB0cnkgaXQsIGJ1dCBJIGV4cGVjdCB0aGUgcmVzdWx0IHRvIGJlIGJvZ3VzIGJlY2F1c2Ug
b2YgdGhpcywgDQo+IHVuZm9ydHVuYXRlbHkuDQo+IA0KDQpJIGNhbiB1bmRlcnN0YW5kLiBBIGZl
dyB1c2VycyByZXBvcnRlZCB0aGF0IHRoaXMgYnVnIG9jY3VycmVkIG1vcmUNCnJlbGlhYmx5IHdo
ZW4gbW92aW5nIHRoZWlyIHN5c3RlbSwgYWx0aG91Z2ggaXQgc2VlbXMgdmVyeSB3ZWlyZCB0byBt
ZS4NCg0KPiA+IEZpcnN0IHF1ZXN0aW9uIGlzOiBBcmUgeW91IHN1cmUgdGhhdCA0LjAtcmM2IHdh
cyBnb29kPw0KPiANCj4gUHJldHR5IG11Y2gsIHllcy4gSSd2ZSBiZWVuIHJ1bm5pbmcgaXQgZm9y
IHF1aXRlIHNvbWUgdGltZSBvbiB0aGlzIA0KPiBtYWNoaW5lIHdpdGhvdXQgYW55IGlzc3Vlcy4g
QnV0IGFmdGVyIHVwZGF0aW5nIHRvIGN1cnJlbnQgSEVBRCB0d28gZGF5cyANCj4gYWdvLCB0aGUg
aXNzdWUgdHJpZ2dlcmVkIGxpa2UgNiBvciA3IHRpbWVzIGFscmVhZHkuDQo+IA0KDQpPayAtIEkg
d2lsbCB0cnkgdG8gbG9vayBhdCB0aGUgUENJIGNvbW1pdHMgdGhlcmUgYWx0aG91Z2ggSSBhbSBu
b3Qgc3VyZQ0KSSdsbCBiZSBhYmxlIHRvIG1ha2UgbXVjaCBzZW5zZSBvZiB0aGVtLi4uDQoNCj4g
VGhhbmtzLA0KPiANCg0K
WARNING: multiple messages have this Message-ID (diff)
From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To: "jkosina@suse.cz" <jkosina@suse.cz>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"ilw@linux.intel.com" <ilw@linux.intel.com>,
"Berg, Johannes" <johannes.berg@intel.com>
Subject: Re: iwlwifi getting stuck with current Linus' tree (646da63172)
Date: Thu, 23 Apr 2015 09:12:46 +0000 [thread overview]
Message-ID: <1429780366.11859.1.camel@intel.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1504231011500.3695@pobox.suse.cz>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2290 bytes --]
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Ç+‰·Ÿ®‰†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a¢f£¢·hšïêÿ‘êçz_è®\x03(階ŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨èÚ&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥
next prev parent reply other threads:[~2015-04-23 9:12 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 20:42 iwlwifi getting stuck with current Linus' tree (646da63172) Jiri Kosina
2015-04-23 4:47 ` Grumbach, Emmanuel
2015-04-23 4:47 ` Grumbach, Emmanuel
2015-04-23 8:15 ` Jiri Kosina
2015-04-23 9:12 ` Grumbach, Emmanuel [this message]
2015-04-23 9:12 ` Grumbach, Emmanuel
2015-04-23 9:15 ` Jiri Kosina
2015-04-23 12:48 ` Piotr Karbowski
2015-04-23 18:10 ` Grumbach, Emmanuel
2015-04-23 18:10 ` Grumbach, Emmanuel
2015-05-03 21:42 ` Jiri Kosina
2015-05-04 4:32 ` Grumbach, Emmanuel
2015-05-04 4:32 ` Grumbach, Emmanuel
2015-05-04 6:55 ` Jiri Kosina
2015-05-04 7:02 ` Grumbach, Emmanuel
2015-05-04 7:02 ` Grumbach, Emmanuel
2015-05-07 8:54 ` Jiri Kosina
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1429780366.11859.1.camel@intel.com \
--to=emmanuel.grumbach@intel.com \
--cc=ilw@linux.intel.com \
--cc=jkosina@suse.cz \
--cc=johannes.berg@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.