From: Larry Finger <Larry.Finger@lwfinger.net>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Johannes Berg <johannes.berg@intel.com>,
Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Cc: Intel Linux Wireless <ilw@linux.intel.com>,
"John W. Linville" <linville@tuxdriver.com>,
Linux Wireless List <linux-wireless@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>
Subject: Re: Intel wireless microcode problem..
Date: Thu, 14 Aug 2014 10:42:08 -0500 [thread overview]
Message-ID: <53ECD8D0.4050709@lwfinger.net> (raw)
In-Reply-To: <CA+55aFxdt-9e9X0EYCu2Ku8sSTspUGPk5qKa72XH63zrkdPthw@mail.gmail.com>
On 08/14/2014 10:05 AM, Linus Torvalds wrote:
> Ok, so it seems the current merge window introduces some horrid intel
> microcode problem, because I don't seem to see this with 3.16. But
> maybe that's just happenstance.
>
> Any ideas? This fills up all the logs etc.
>
> Linus
Linus,
There is a new firmware that seems to help the problem. You can get it from
Emmanuel's git clone. As he wrote earlier
==========================
We released an experimental firmware for 3160 / 7260 / 7265.
It is available from my linux-firmware.git clone:
3160:
https://git.kernel.org/cgit/linux/kernel/git/egrumbach/linux-firmware.git/plain/iwlwifi-3160-9.ucode?h=Core6
7260:
https://git.kernel.org/cgit/linux/kernel/git/egrumbach/linux-firmware.git/plain/iwlwifi-7260-9.ucode?h=Core6
7265:
https://git.kernel.org/cgit/linux/kernel/git/egrumbach/linux-firmware.git/plain/iwlwifi-7265-9.ucode?h=Core6
We had an issue with the version number in this stream, so I can't release it
officially, nor can I send a pull request to integrate it to linux-firmware.git.
I am working with the firmware team to fix the version issue.
I still would be glad to have more testing on this firmware, so any feedback
would be greatly appreciated.
It has gone through our regular testing cycles, but "field" feedback is always
valuable.
Thanks in advance to anyone who will test it.
New (temporary) version number: 25.223.9.0
============================================
Larry
next prev parent reply other threads:[~2014-08-14 15:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 15:05 Intel wireless microcode problem Linus Torvalds
2014-08-14 15:42 ` Larry Finger [this message]
[not found] ` <53ECD8D0.4050709-tQ5ms3gMjBLk1uMJSBkQmQ@public.gmane.org>
2014-08-14 15:51 ` Linus Torvalds
[not found] ` <CA+55aFw1LWO+zxePYtUBi9YOWHPX+98xbM2h3j4pcN+6V0G1zA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-08-14 15:56 ` Grumbach, Emmanuel
[not found] ` <0BA3FCBA62E2DC44AF3030971E174FB31B266E67-Jy8z56yoSI9wl47ZQwxUxrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-08-14 16:34 ` Emmanuel Grumbach
2014-08-14 16:46 ` Linus Torvalds
2014-08-14 15:50 ` 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=53ECD8D0.4050709@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=emmanuel.grumbach@intel.com \
--cc=ilw@linux.intel.com \
--cc=johannes.berg@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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).