From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To: "piotr.karbowski@gmail.com" <piotr.karbowski@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jkosina@suse.cz" <jkosina@suse.cz>,
"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 18:10:11 +0000 [thread overview]
Message-ID: <1429812611.23202.4.camel@intel.com> (raw)
In-Reply-To: <CA+uBNfxXoLj9Nfss+j1G3PY9A2t=N6KRiYUAdoxiUOZvigwyAw@mail.gmail.com>
T24gVGh1LCAyMDE1LTA0LTIzIGF0IDE0OjQ4ICswMjAwLCBQaW90ciBLYXJib3dza2kgd3JvdGU6
DQo+IEhlbGxvLA0KPiANCj4gT24gVGh1LCBBcHIgMjMsIDIwMTUgYXQgMTE6MTUgQU0sIEppcmkg
S29zaW5hIDxqa29zaW5hQHN1c2UuY3o+IHdyb3RlOg0KPiA+IE9uIFRodSwgMjMgQXByIDIwMTUs
IEdydW1iYWNoLCBFbW1hbnVlbCB3cm90ZToNCj4gPg0KPiA+PiA+IEkgd2lsbCB0cnkgaXQsIGJ1
dCBJIGV4cGVjdCB0aGUgcmVzdWx0IHRvIGJlIGJvZ3VzIGJlY2F1c2Ugb2YgdGhpcywNCj4gPj4g
PiB1bmZvcnR1bmF0ZWx5Lg0KPiA+Pg0KPiA+PiBJIGNhbiB1bmRlcnN0YW5kLiBBIGZldyB1c2Vy
cyByZXBvcnRlZCB0aGF0IHRoaXMgYnVnIG9jY3VycmVkIG1vcmUNCj4gPj4gcmVsaWFibHkgd2hl
biBtb3ZpbmcgdGhlaXIgc3lzdGVtLCBhbHRob3VnaCBpdCBzZWVtcyB2ZXJ5IHdlaXJkIHRvIG1l
Lg0KPiA+DQo+ID4gTXkgImZlZWxpbmciIHdhcyB0aGF0IGl0IHNvbWV0aW1lcyB3YXMgcmVsYXRl
ZCB0byBzdGFydCBvZiBhdWRpbyBwbGF5YmFjaywNCj4gPiBidXQgbm90IDEwMCUgcmVsaWVibGUg
ZWl0aGVyLg0KPiA+DQo+ID4+ID4gPiBGaXJzdCBxdWVzdGlvbiBpczogQXJlIHlvdSBzdXJlIHRo
YXQgNC4wLXJjNiB3YXMgZ29vZD8NCj4gPj4gPg0KPiA+PiA+IFByZXR0eSBtdWNoLCB5ZXMuIEkn
dmUgYmVlbiBydW5uaW5nIGl0IGZvciBxdWl0ZSBzb21lIHRpbWUgb24gdGhpcw0KPiA+PiA+IG1h
Y2hpbmUgd2l0aG91dCBhbnkgaXNzdWVzLiBCdXQgYWZ0ZXIgdXBkYXRpbmcgdG8gY3VycmVudCBI
RUFEIHR3byBkYXlzDQo+ID4+ID4gYWdvLCB0aGUgaXNzdWUgdHJpZ2dlcmVkIGxpa2UgNiBvciA3
IHRpbWVzIGFscmVhZHkuDQo+ID4+DQo+ID4+IE9rIC0gSSB3aWxsIHRyeSB0byBsb29rIGF0IHRo
ZSBQQ0kgY29tbWl0cyB0aGVyZSBhbHRob3VnaCBJIGFtIG5vdCBzdXJlDQo+ID4+IEknbGwgYmUg
YWJsZSB0byBtYWtlIG11Y2ggc2Vuc2Ugb2YgdGhlbS4uLg0KPiA+DQo+ID4gVGhhbmtzLA0KPiAN
Cj4gaSd2ZSBhbHNvIHN0YXJ0ZWQgbm90aWNpbmcgaGFyZCBzeXN0ZW0gbG9ja3VwcyB3aXRoIGl3
bHdpZmkuIFdoYXQncw0KPiB3b3J0aCBub3RpY2luZyBpcyB0aGF0IEkndmUgc3RhcnRlZCB0byBz
ZWUgdGhpcyBvbiAzLjE5IGFuZCBJIGFsc28NCj4gaGF2ZSBpdCBvbiA0LjAga2VybmVsIHRodXMg
YWxsb3cgbWUgdG8gcmVwb3J0IGl0IGluIHRoaXMgdmVyeSB0aHJlYWQuDQo+IEkgaGFkIG92ZXIg
bW9udGggdXB0aW1lLCB1bnRpbGwgSSd2ZSB1cGRhdGVkIGl3bCB1Y29kZSwgbWF5YmUgdGhpcyB3
YXMNCj4gaW50cm9kdWNlZCBub3QgYnkga2VybmVsIGJ1dCBmaXJtd2FyZT8uIFRoZSBsb2NrdXBz
IGFyZSByYW5kb20gYW5kDQo+IHJlc3VsdCBpbiBoYXJkIHN5c3RlbSBsb2NrdXAsIGZyb3plbiBY
b3JnLCBzY3JlZW4gYXJ0aWZhY3RzL2dsaXRjaGVzLA0KPiBhdWRpbyBwbGF5YmFjayBrZWVwcyBy
ZXBlYXRpbmcgbGFzdCBzZWNvbmQgb3Igc28gb2YgbXVzaWMsIHN5c3JxDQo+IGNhbm5vdCBoYW5k
bGUgaXQgYXMgd2VsbCBhcyBhdXRvLXJlYm9vdCBhZnRlciBrZXJuZWwgcGFuaWMgZG9lcyBub3QN
Cj4ga2lja3MgaW4uDQo+IA0KDQpJIGRvbid0IHNlZSBob3cgdGhlIHVjb2RlIGNhbiBjYXVzZSBj
cmFzaGVzLCBidXQgYSBuZXcgdWNvZGUgY2FuIG1ha2UNCnRoZSBkcml2ZXIgYmVoYXZlIGRpZmZl
cmVudGx5IChuZXcgQVBJcyBiZWluZyBhdmFpbGFibGUpIGFuZCB0aGF0IGNhbg0KY2F1c2UgY3Jh
c2hlcy4gUGxlYXNlIHNoYXJlIGFueSBsb2dzIHlvdSBtYXkgaGF2ZS4NCg0KPiBUaGUgaGFyZHdh
cmUgSSBzZWUgdGhpcyBwcm9ibGVtIG9uIGlzIGl3bCA3MjYwLiBUaGUgb25seSB3b3JrYXJvdW5k
DQo+IEkndmUgZm91bmQgc28gZmFyIHdhcyB0byBkaXNhYmxlIHBvd2VyIHNhdmUgdmlhIGBpdyBk
ZXYgd2xhbjAgc2V0DQo+IHBvd2VyX3NhdmUgb2ZmYCBhbmQgbm90IGEgc2luZ2xlIGxvY2t1cCBz
aW5jZS4gV2hhdCdzIHJhdGhlcg0KPiBkaXN0dXJiaW5nIGlzIHRoYXQgYnkgJ21vZGluZm8gaXds
d2lmaScgaXQgZG9lcyBzYXkgdGhhdCBwb3dlcl9zYXZlIGlzDQo+IGRlZmF1bHQgb2ZmLCBidXQg
aXQgaXMgbm90LiBJIGFtIHN1cmUgdGhhdCBub3RoaW5nIGVsc2UgZW5hYmxlcw0KPiBwb3dlcl9z
YXZlIG9uIG15IHN5c3RlbSBiZWNhdXNlIEkgZG9uJ3QgZXZlbiBoYXZlIHVkZXYsIGFuZCBmb3Ig
dGhlDQo+IHRlc3QgSSd2ZSBhbHNvIGRpc2FibGVkIHdpY2QsIHRoZW4gc2ltcGxlIGBtb2Rwcm9i
ZSBpd2x3aWZpYCBhbmQgYGl3DQo+IGRldiB3bGFuMCBnZXQgcG93ZXJfc2F2ZWAgcmVwb3J0cyAn
b24nLg0KDQpZZWFoIC0gSSBrbm93LiBUaGlzIGlzIGNvbmZ1c2luZy4gVGhpcyBtb2R1bGUgcGFy
YW1ldGVyIGRvZXNuJ3QgYWZmZWN0DQo3MjYwOiBpdCB1c2VzIGl3bG12bSBtb2R1bGUgd2hpY2gg
aXRzIG93biBzZXR0aW5nLiBpd2x3aWZpJ3MgcG93ZXJfc2F2ZQ0KcGFyYW1ldGVyIHNlcnZlcyBv
bGRlciBkZXZpY2VzIHN1Y2ggYXMgNjIwNSB3aGljaCB5b3Ugc2VlbSB0byBoYXZlIGFzDQp3ZWxs
Lg0KSW4gNjIwNSdzIGNhc2UsIHBvd2VyIHNhdmUgaXMgZGlzYWJsZWQgYnkgZGVmYXVsdC4gQnV0
IGFsbCB0aGlzIHNlZW1zDQp2ZXJ5IGZhciBhd2F5IGZyb20gdGhlIG9yaWdpbmFsIHRocmVhZC4N
Cg0KPiANCj4gSSBhbHNvIGhhdmUgYW5vdGhlciBzeXN0ZW0gaXdsIDYyMDUgYW5kIG5vIHNpbmds
ZSBsb2NrdXAgd2FzIG5vdGVkLA0KPiBidXQgaXQgaW5kZWVkIGhhdmUgcG93ZXJfc2F2ZSBkaXNh
YmxlZCwgc28gdGhhdCBtYXkgYmUgdGhlIGNhc2UuDQo+IA0KPiAtLSBQaW90ci4NCg0K
WARNING: multiple messages have this Message-ID (diff)
From: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
To: "piotr.karbowski@gmail.com" <piotr.karbowski@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"jkosina@suse.cz" <jkosina@suse.cz>,
"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 18:10:11 +0000 [thread overview]
Message-ID: <1429812611.23202.4.camel@intel.com> (raw)
In-Reply-To: <CA+uBNfxXoLj9Nfss+j1G3PY9A2t=N6KRiYUAdoxiUOZvigwyAw@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2941 bytes --]
On Thu, 2015-04-23 at 14:48 +0200, Piotr Karbowski wrote:
> Hello,
>
> On Thu, Apr 23, 2015 at 11:15 AM, Jiri Kosina <jkosina@suse.cz> wrote:
> > On Thu, 23 Apr 2015, Grumbach, Emmanuel wrote:
> >
> >> > 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.
> >
> > My "feeling" was that it sometimes was related to start of audio playback,
> > but not 100% relieble either.
> >
> >> > > 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,
>
> i've also started noticing hard system lockups with iwlwifi. What's
> worth noticing is that I've started to see this on 3.19 and I also
> have it on 4.0 kernel thus allow me to report it in this very thread.
> I had over month uptime, untill I've updated iwl ucode, maybe this was
> introduced not by kernel but firmware?. The lockups are random and
> result in hard system lockup, frozen Xorg, screen artifacts/glitches,
> audio playback keeps repeating last second or so of music, sysrq
> cannot handle it as well as auto-reboot after kernel panic does not
> kicks in.
>
I don't see how the ucode can cause crashes, but a new ucode can make
the driver behave differently (new APIs being available) and that can
cause crashes. Please share any logs you may have.
> The hardware I see this problem on is iwl 7260. The only workaround
> I've found so far was to disable power save via `iw dev wlan0 set
> power_save off` and not a single lockup since. What's rather
> disturbing is that by 'modinfo iwlwifi' it does say that power_save is
> default off, but it is not. I am sure that nothing else enables
> power_save on my system because I don't even have udev, and for the
> test I've also disabled wicd, then simple `modprobe iwlwifi` and `iw
> dev wlan0 get power_save` reports 'on'.
Yeah - I know. This is confusing. This module parameter doesn't affect
7260: it uses iwlmvm module which its own setting. iwlwifi's power_save
parameter serves older devices such as 6205 which you seem to have as
well.
In 6205's case, power save is disabled by default. But all this seems
very far away from the original thread.
>
> I also have another system iwl 6205 and no single lockup was noted,
> but it indeed have power_save disabled, so that may be the case.
>
> -- Piotr.
ÿôèº{.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 18:10 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
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 [this message]
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=1429812611.23202.4.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 \
--cc=piotr.karbowski@gmail.com \
/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.