From: wzyboy <wzyboy@wzyboy.org>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: "ilw@linux.intel.com" <ilw@linux.intel.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [Ilw] Intel Wireless 7260 hardware timed out randomly
Date: Wed, 6 Nov 2013 14:34:50 +0800 [thread overview]
Message-ID: <CALkVjQZDNSgUUFyi94Y8da_NDzW61rCvaMrZpUugFKW_LRNFFA@mail.gmail.com> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB301DE9FC6@HASMSX103.ger.corp.intel.com>
2013/11/6 Grumbach, Emmanuel <emmanuel.grumbach@intel.com>:
>>
>> Hi, I'm back.
>>
>> This terriable bug occurs again in Linux 3.12. This time I've been prepared for
>> it and wrote down the complete process of its apperance and my reacting, as
>> attached.
>
> Thanks - was that with power save disabled?
Yes, Linux 3.12 with "options iwlmvm power_scheme=1". (I did not touch
that .conf file after the kernel upgrade)
>
>>
>> IMHO they are quite similar with those errors in 3.11...
>
> Indeed. The only difference is that you don’t have PCI complain about not being able to disable L1.
I see. But I still cannot figure out what is the "trigger" of this
bug. Today (Nov 06 UTC+8) this bug occurs twice till now (14:30), they
were at 12:31 and 13:30. At the first time I was about to do a system
upgrade and at the second time I was using rsync to upload photos from
my Android phone to my laptop.
Sometimes I was not even using network (the traffic was near zero)
when the bug occurs. So this bug seems to occur no matter of network
traffic states?
Could you think of a possible "trigger" of this bug so I could try to
avoid it (I hate rebooting) before the final fix is released? For
example, if there is something wrong with the "modules linked in" I
could blacklist that module...
Sincere regards.
--
wzyboy
next prev parent reply other threads:[~2013-11-06 6:35 UTC|newest]
Thread overview: 97+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-03 9:11 Intel Wireless 7260 hardware timed out randomly wzyboy
2013-11-03 9:23 ` [Ilw] " Grumbach, Emmanuel
[not found] ` <CALkVjQYh-SUte4S6LdqOc3KSc3_pDU6jz1KXp+Jsd5_RFPXSqA@mail.gmail.com>
2013-11-04 9:21 ` Fwd: " wzyboy
2013-11-04 9:42 ` Sedat Dilek
2013-11-04 9:53 ` wzyboy
2013-11-04 9:42 ` Grumbach, Emmanuel
2013-11-05 4:34 ` wzyboy
2013-11-05 11:04 ` Grumbach, Emmanuel
[not found] ` <CALkVjQbW8FeiEh8pBZ=KQFD9+8AdjgT0G_RG7qJe0MRdBvMD-A@mail.gmail.com>
2013-11-05 11:42 ` Fwd: " wzyboy
2013-11-06 4:47 ` wzyboy
2013-11-06 6:18 ` Grumbach, Emmanuel
2013-11-06 6:34 ` wzyboy [this message]
2013-11-06 6:37 ` Grumbach, Emmanuel
2013-11-06 6:47 ` wzyboy
2013-11-06 7:07 ` wzyboy
2013-11-06 7:10 ` Grumbach, Emmanuel
2013-11-06 7:12 ` wzyboy
2013-11-06 17:50 ` Emmanuel Grumbach
2013-11-06 18:32 ` Bjorn Helgaas
2013-11-07 4:49 ` wzyboy
2013-11-07 14:24 ` wzyboy
2013-11-08 4:41 ` wzyboy
2013-11-08 4:46 ` wzyboy
2013-11-08 17:20 ` Bjorn Helgaas
2013-11-08 17:38 ` Bjorn Helgaas
2013-11-10 10:19 ` wzyboy
2013-11-10 11:32 ` Emmanuel Grumbach
2013-11-10 11:38 ` wzyboy
2013-11-10 11:41 ` Grumbach, Emmanuel
2013-11-10 12:13 ` wzyboy
2013-11-10 12:17 ` Grumbach, Emmanuel
2013-11-11 9:43 ` Emmanuel Grumbach
2013-11-11 11:40 ` wzyboy
2013-11-11 21:55 ` Bjorn Helgaas
2013-11-09 2:46 ` wzyboy
2013-11-10 7:03 ` Emmanuel Grumbach
2013-11-10 7:08 ` wzyboy
2013-11-11 22:44 ` Bjorn Helgaas
2013-11-12 5:42 ` wzyboy
2013-11-12 7:02 ` Emmanuel Grumbach
2013-11-12 9:36 ` Emmanuel Grumbach
2013-11-12 12:10 ` wzyboy
2013-11-12 12:16 ` Grumbach, Emmanuel
2013-11-12 12:25 ` wzyboy
2013-11-12 12:45 ` Grumbach, Emmanuel
2013-11-12 12:59 ` wzyboy
2013-11-12 18:14 ` Bjorn Helgaas
2013-11-12 18:25 ` Grumbach, Emmanuel
2013-11-12 19:14 ` Bjorn Helgaas
2013-11-12 19:37 ` Emmanuel Grumbach
2013-11-12 22:09 ` Bjorn Helgaas
2013-11-13 5:39 ` wzyboy
2013-11-13 6:46 ` wzyboy
[not found] ` <0BA3FCBA62E2DC44AF3030971E174FB301DFBCB5@HASMSX103.ger.corp.intel.com>
2013-11-13 7:25 ` wzyboy
2013-11-13 17:42 ` Bjorn Helgaas
2013-11-13 20:30 ` Grumbach, Emmanuel
2013-11-14 4:23 ` wzyboy
2013-11-14 6:20 ` Grumbach, Emmanuel
2013-11-14 7:01 ` wzyboy
2013-11-14 7:04 ` Grumbach, Emmanuel
2013-11-14 7:09 ` wzyboy
2013-11-14 8:39 ` Grumbach, Emmanuel
2013-11-14 17:53 ` Bjorn Helgaas
2013-11-15 3:06 ` wzyboy
2013-11-15 3:09 ` wzyboy
2013-11-15 8:49 ` Emmanuel Grumbach
2013-11-15 9:04 ` wzyboy
2013-12-25 8:27 ` Emmanuel Grumbach
2013-12-25 10:34 ` wzyboy
2013-12-25 10:38 ` Grumbach, Emmanuel
2013-12-28 9:54 ` wzyboy
2013-12-28 9:57 ` wzyboy
2013-12-29 8:14 ` Grumbach, Emmanuel
2013-12-29 9:23 ` wzyboy
2013-12-29 11:45 ` Emmanuel Grumbach
2013-12-29 13:06 ` wzyboy
2014-01-02 21:34 ` Bjorn Helgaas
2014-01-04 14:41 ` wzyboy
2014-01-13 6:01 ` Grumbach, Emmanuel
2014-01-13 6:15 ` wzyboy
2014-01-13 7:56 ` wzyboy
2014-01-13 8:26 ` Grumbach, Emmanuel
2014-01-13 8:50 ` wzyboy
2014-01-13 8:59 ` Grumbach, Emmanuel
2014-01-13 9:05 ` wzyboy
2014-01-13 10:51 ` Grumbach, Emmanuel
2014-01-13 10:56 ` wzyboy
2014-01-13 17:29 ` Bjorn Helgaas
2014-01-14 3:56 ` Sascha Weaver
2013-11-13 8:45 ` Grumbach, Emmanuel
2013-11-13 9:47 ` Grumbach, Emmanuel
2013-11-13 12:13 ` Grumbach, Emmanuel
2013-11-13 12:18 ` wzyboy
2013-11-13 12:21 ` Grumbach, Emmanuel
2013-11-13 12:33 ` wzyboy
2013-11-13 13:48 ` Bjørn Mork
2013-11-13 14:16 ` Grumbach, Emmanuel
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=CALkVjQZDNSgUUFyi94Y8da_NDzW61rCvaMrZpUugFKW_LRNFFA@mail.gmail.com \
--to=wzyboy@wzyboy.org \
--cc=emmanuel.grumbach@intel.com \
--cc=ilw@linux.intel.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).