From: Emmanuel Grumbach <egrumbach@gmail.com>
To: Petko Manolov <petkan@nucleusys.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: Sat, 08 Feb 2014 20:10:27 +0200 [thread overview]
Message-ID: <52F67313.1030706@gmail.com> (raw)
In-Reply-To: <20140207214054.GB7167@localhost>
On 02/07/2014 11:40 PM, Petko Manolov wrote:
> On 14-01-23 22:21:42, Petko Manolov wrote:
>> On 14-01-23 22:07:52, Emmanuel Grumbach wrote:
>>>
>>> Unfortunately, I can't see the loading of iwlwifi.
>>
>> It overflowed. That's what happen when debug != 0 ... :)
>>
>>> Doesn't matter any more - I found the issue.
>>
>> Ah, good. Cheers.
>
> Hello Emmanuel, did you manage to fix the problem? I can see iwlwifi related patch went into 3.13.2, but in case it was supposed to fix the
> issue - it didn't do that for me. As usual, can i help with anything?
>
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.
The fact that it doesn't work for you with -8.ucode proves that I am
correct.
I sent a patch that will disable 5GHz band for you from the driver level
so that you won't suffer from firmware asserts.
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.
next prev parent reply other threads:[~2014-02-08 18:10 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 [this message]
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=52F67313.1030706@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).