linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Emmanuel Grumbach <egrumbach@gmail.com>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
	Petko Manolov <petkan@nucleusys.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"ilw@linux.intel.com" <ilw@linux.intel.com>,
	"Berg, Johannes" <johannes.berg@intel.com>
Subject: Re: iwlwifi crash with 3.13
Date: Thu, 23 Jan 2014 21:11:52 +0200	[thread overview]
Message-ID: <52E16978.3040602@gmail.com> (raw)
In-Reply-To: <0BA3FCBA62E2DC44AF3030971E174FB303D57045@HASMSX103.ger.corp.intel.com>

[-- Attachment #1: Type: text/plain, Size: 590 bytes --]

Ok -  I put the pieces together:

> iwlwifi 0000:01:00.0: loaded firmware version 22.15.8.0 op_mode iwlmvm
> iwlwifi 0000:01:00.0: Detected Intel(R) Wireless N 7260, REV=0x144

This means that your NIC is 2.4GHz only. Dual band NICs print something
else.

Now here come the catch. You seem to have an "old" NIC in a way that the
NVM (EEPROM like) is old. In that NVM, there was a bug that advertised
the A band channels but disabled the A band in SKU cap.

Can you please try the patch attached?
I will prevent the driver from trying to work on A band while the HW
doesn't allow.

emmanuel

[-- Attachment #2: 0001-iwlwifi-mvm-don-t-allow-A-band-if-SKU-forbids-it.patch --]
[-- Type: text/x-patch, Size: 976 bytes --]

>From dd40219d34426e4f9c7d1b10653ece3dc67588c5 Mon Sep 17 00:00:00 2001
From: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Date: Thu, 5 Dec 2013 22:42:55 +0200
Subject: [PATCH] iwlwifi: mvm: don't allow A band if SKU forbids it

Change-Id: I920b7c53dc05a41de43ab9762eb7853dc4bed1ed
Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
---
 drivers/net/wireless/iwlwifi/iwl-nvm-parse.c | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/drivers/net/wireless/iwlwifi/iwl-nvm-parse.c b/drivers/net/wireless/iwlwifi/iwl-nvm-parse.c
index 1fce0ec..9600afc 100644
--- a/drivers/net/wireless/iwlwifi/iwl-nvm-parse.c
+++ b/drivers/net/wireless/iwlwifi/iwl-nvm-parse.c
@@ -192,6 +192,10 @@ static int iwl_init_channel_map(struct device *dev, const struct iwl_cfg *cfg,
 			continue;
 		}
 
+		if (ch_idx >= NUM_2GHZ_CHANNELS &&
+		    !data->sku_cap_band_52GHz_enable)
+			continue;
+
 		channel = &data->channels[n_channels];
 		n_channels++;
 
-- 
1.8.1.msysgit.1


  reply	other threads:[~2014-01-23 19:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-23  9:16 iwlwifi crash with 3.13 Petko Manolov
2014-01-23  9:22 ` Grumbach, Emmanuel
2014-01-23 12:31   ` Petko Manolov
2014-01-23 12:34     ` Grumbach, Emmanuel
2014-01-23 12:45     ` Grumbach, Emmanuel
2014-01-23 19:11       ` Emmanuel Grumbach [this message]
2014-01-23 20:19         ` Petko Manolov
2014-01-23 20:00       ` Petko Manolov
2014-01-23 20:07         ` Emmanuel Grumbach
2014-01-23 20:21           ` Petko Manolov
2014-02-07 21:40             ` Petko Manolov
2014-02-08 18:10               ` Emmanuel Grumbach
2014-02-09 13:26                 ` Petko Manolov
2014-02-09 13:31                   ` Grumbach, Emmanuel
2014-02-09 13:49                     ` Petko Manolov
2014-02-07 11:08           ` Niklas Claesson
2014-02-08 18:11             ` Emmanuel Grumbach

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=52E16978.3040602@gmail.com \
    --to=egrumbach@gmail.com \
    --cc=emmanuel.grumbach@intel.com \
    --cc=ilw@linux.intel.com \
    --cc=johannes.berg@intel.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=petkan@nucleusys.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 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).