From: Andy Lutomirski <luto@amacapital.net>
To: Luca Coelho <luca@coelho.fi>
Cc: Andy Lutomirski <luto@kernel.org>,
Linux Wireless List <linux-wireless@vger.kernel.org>,
Intel Linux Wireless <linuxwifi@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Johannes Berg <johannes.berg@intel.com>
Subject: Re: iwlwifi errors (regression?) on 4.7.0
Date: Tue, 30 Aug 2016 12:02:13 -0700 [thread overview]
Message-ID: <CALCETrWyUQwNQ0YtuLziRFU+mLKcWiLEQSFb_=K5oswJwjq-Vw@mail.gmail.com> (raw)
In-Reply-To: <1472110148.5024.123.camel@coelho.fi>
On Thu, Aug 25, 2016 at 12:29 AM, Luca Coelho <luca@coelho.fi> wrote:
> Hi Andy,
>
> Sorry for the really long delay in replying. :(
>
> On Sun, 2016-08-07 at 01:54 -0700, Andy Lutomirski wrote:
>> My Intel 7265 used to work flawlessly, but for the past week or two
>> it
>> has seemed to be very unreliable. It's also throwing errors. I see
>> problems on firmware versions 16 and 21, although I haven't gotten
>> the
>> warning and backtrace on firmware 16 yet.
>>
>> I have:
>>
>> iwlwifi 0000:3a:00.0: enabling device (0000 -> 0002)
>> iwlwifi 0000:3a:00.0: Unsupported splx structure
>> iwlwifi 0000:3a:00.0: loaded firmware version 21.302800.0 op_mode
>> iwlmvm
>> iwlwifi 0000:3a:00.0: Detected Intel(R) Dual Band Wireless AC 7265,
>> REV=0x210
>> iwlwifi 0000:3a:00.0: L1 Enabled - LTR Disabled
>> iwlwifi 0000:3a:00.0: L1 Enabled - LTR Disabled
>>
>>
>> I just got this error on 4.7.0:
>>
>> [324188.495734] wlp58s0: associated
>> [324281.259579] iwlwifi 0000:3a:00.0: Queue 16 stuck for 10000 ms.
>
> This seems to be a recurring error with the AC-7265. :( We even added
> an entry about it in our wiki:
>
> https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi#about_platform_noise
Shouldn't that cause packet loss, not actual stuck queues? Or is the
problem that the device literally can't transmit at all for 10 seconds
and the driver eventually gets sick of waiting? Could the driver
learn to detect this more sensibly, drop the packets cleanly after
some timeout, and maybe log a message about extremely high noise?
>
>
>> > [324281.263732] iwlwifi 0000:3a:00.0: Start IWL Error Log Dump:
>> > [324281.263739] iwlwifi 0000:3a:00.0: Status: 0x00000000, count: 6
>> > [324281.263745] iwlwifi 0000:3a:00.0: Loaded firmware version: 21.302800.0
>> > [324281.263751] iwlwifi 0000:3a:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN
>
> We have a bugzilla entry with the queue stuck + NMI trigger:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=112931
>
> Unfortunately nothing was found out by our firmware team regarding this
> yet.
Sad :(
>
>
>> Earlier on the same boot I got:
>>
>> [266562.042662] ------------[ cut here ]------------
>> [266562.042693] WARNING: CPU: 2 PID: 994 at
>> drivers/net/wireless/intel/iwlwifi/mvm/tx.c:1377
>> iwl_mvm_rx_tx_cmd+0x665/0x870 [iwlmvm]
>
> We also have an open bugzilla entry with similar WARNING:
>
> https://bugzilla.kernel.org/show_bug.cgi?id=153381
>
>
> So, first I'd recommend that you follow the recommended workarounds in
> our wiki. If that doesn't help and you still want to try to help us
> debug this, please open a bugzilla so we can track it more easily.
I haven't seem any of these problems on 4.8-rc yet. I'll keep you
posted if I do.
prev parent reply other threads:[~2016-08-30 19:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-07 8:54 iwlwifi errors (regression?) on 4.7.0 Andy Lutomirski
2016-08-25 7:29 ` Luca Coelho
2016-08-30 19:02 ` Andy Lutomirski [this message]
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='CALCETrWyUQwNQ0YtuLziRFU+mLKcWiLEQSFb_=K5oswJwjq-Vw@mail.gmail.com' \
--to=luto@amacapital.net \
--cc=emmanuel.grumbach@intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luca@coelho.fi \
--cc=luto@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).