linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petko Manolov <petkan@nucleusys.com>
To: Emmanuel Grumbach <egrumbach@gmail.com>
Cc: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>,
	"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: Sun, 9 Feb 2014 15:26:54 +0200	[thread overview]
Message-ID: <20140209132653.GA8352@localhost> (raw)
In-Reply-To: <52F67313.1030706@gmail.com>

On 14-02-08 20:10:27, Emmanuel Grumbach wrote:
> 
> There is no problem to be fixed. When I said that I found the issue, I meant that you are using a NIC which is not supposed to work on 5GHz on 
> these channels and this leads to the issues.

Right, wireless-N 7260 is not advertised as 5GHz card.  I just got over my laziness and searched the net.

> The fact that it doesn't work for you with -8.ucode proves that I am correct.

This is something i'd rather not comment on. :P

> I sent a patch that will disable 5GHz band for you from the driver level so that you won't suffer from firmware asserts.

Sweet.

> You told me you could work on 5GHz with this NIC - good for you. Conclude whatever you want from this, this is none of my business - but for 
> sure, the "issues" you are seeing are related to the fact that your NIC isn't supposed to be working on 5GHz, and hence, there is no bug to be 
> fixed.

Now that's funny.  Intel made an effort to put 5GHz radio on this card.  They even released firmware that can actually make use of this band.  I 
am pretty sure you won't answer these, but i'll ask why is that anyway:

	a) is the 'A' band implementation so buggy that you/Intel decided to disable it altogether?
	b) it is on sale too cheap to give it's customers the 'A' band;
	c) a mix of both (or none) of the above;

I kind of doubt it is a) since my laptop would happily stay connected to the router (on AN band) for days.  Were it not for the ugly 'dmesg' i'd 
never know there is a problem.  I have no idea of the device internals, but blowing up the workqueue (or whatever) is a bit too much.  With or 
without the A band functionality. ;)

Thanks for taking the time to look at my 'problem'.


		Petko

  reply	other threads:[~2014-02-09 13:27 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
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 [this message]
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=20140209132653.GA8352@localhost \
    --to=petkan@nucleusys.com \
    --cc=egrumbach@gmail.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 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).