All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Coelho <luca@coelho.fi>
To: Christian Lamparter <chunkeey@googlemail.com>
Cc: linux-wireless@vger.kernel.org, ilw@linux.intel.com,
	emmanuel.grumbach@intel.com, johannes.berg@intel.com
Subject: Re: Iwlwifi 3160 AC (firmware?) clashes with CONFIG_IWLWIFI_BCAST_FILTERING
Date: Mon, 25 Aug 2014 23:09:26 +0300	[thread overview]
Message-ID: <1408997366.17421.5.camel@dubbel> (raw)
In-Reply-To: <6715079.xd2j4mnUMo@debian64>

Hi Christian,

I'm not the best person to talk about the iwlwifi firmwares (that would
be Emmanuel, but he is not available now), but I'll try.

On Sat, 2014-08-23 at 00:01 +0200, Christian Lamparter wrote:
> Hello,
> 
> I got new hardware. Among the new stuff, there was one
> Intel® Dual Band Wireless-AC 3160. When I tried to connect
> to one (in fact any) of my networks, I was getting the
> following errors:
> 
> [ 1021.092378] iwlwifi 0000:01:00.0: Microcode SW error detected.  Restarting 0x82000000.
> [...]
> [ 1021.093935] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
> [ 1021.093939] iwlwifi 0000:01:00.0: Status: 0x00000000, count: 6
> [ 1021.093942] iwlwifi 0000:01:00.0: Loaded firmware version: 25.223.9.0
> [ 1021.093947] iwlwifi 0000:01:00.0: 0x00000038 | BAD_COMMAND <---                
> [ 1021.093951] iwlwifi 0000:01:00.0: 0x00A00220 | uPc

Where did you get this firmware version? AFAICT the last version
Emmanuel sent to linux-firmware.git is 23.214.9.0 (the one you also
mentioned below).


> [...]
> [ 1021.094192] Call Trace:
> [ 1021.094205]  [<ffffffff813ce9bd>] ? dump_stack+0x41/0x51
> [ 1021.094217]  [<ffffffffa0b9cd8b>] ? iwl_trans_pcie_send_hcmd+0x367/0x438 [iwlwifi]
> [ 1021.094226]  [<ffffffffa0b9b52c>] ? iwl_pcie_enqueue_hcmd+0x5e3/0x5fe [iwlwifi]
> [ 1021.094235]  [<ffffffff8105fd4c>] ? finish_wait+0x5d/0x5d
> [ 1021.094250]  [<ffffffffa0d50106>] ? iwl_mvm_send_cmd+0xd/0x22 [iwlmvm]
> [ 1021.094262]  [<ffffffffa0d50160>] ? iwl_mvm_send_cmd_pdu+0x45/0x52 [iwlmvm]
> [ 1021.094273]  [<ffffffffa0d4c5fb>] ? iwl_mvm_configure_bcast_filter.isra.14.part.15+0x36/0x3f [iwlmvm]
> 
> (Full log attached below)
> 
> What cough my eye was the "BAD_COMMAND" in the error log. I disabled
> "CONFIG_IWLWIFI_BCAST_FILTERING" option and the 3160 is now working.
> 
> As far as I can tell, there is already a firmware feature flag:
> "IWL_UCODE_TLV_FLAGS_BCAST_FILTERING" which can be used to
> distinguish whenever the feature is supported or not. But it
> seems to be "stuck on" for the 3160.

Weird, but it's possible that they set the flag mistakenly for the 3160
firmware.  I'll check this with the firmware team.


> Regards
> Christian
> 
> BTW: I also tried the older "23.214.9.0" firmware too.
> => Same result [Doesn't work with BCAST_FILTERING enabled].

Thanks a lot for your report! Broadcast filtering is not set by default,
so I haven't seen that bug before.

--
Cheers,
Luca.


  reply	other threads:[~2014-08-25 20:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 22:01 Iwlwifi 3160 AC (firmware?) clashes with CONFIG_IWLWIFI_BCAST_FILTERING Christian Lamparter
2014-08-25 20:09 ` Luca Coelho [this message]
2014-08-25 20:20   ` Emmanuel Grumbach
2014-08-25 20:25     ` Emmanuel Grumbach
2014-08-25 20:26       ` Emmanuel Grumbach
2014-08-25 20:38     ` Christian Lamparter

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=1408997366.17421.5.camel@dubbel \
    --to=luca@coelho.fi \
    --cc=chunkeey@googlemail.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=ilw@linux.intel.com \
    --cc=johannes.berg@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 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.