I am closing this bug because it seems to have been fixed in more recent
microcode versions.
** Changed in: linux-firmware (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
It seems a recent Ubuntu update has overwritten my
/etc/modprobe.d/iwlwifi.conf re-enabling 11n.
Setting disable_11n=1 made this problem go away again.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/14
Maybe this is a solution
https://communities.intel.com/thread/59595
http://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git/commit/?id=a876c69f042cf4732755b325d3b709125bb51a06
but i don't know how to confirm.
--
You received this bug notification because you are a member of Ubun
I am on Ubuntu 14.10 and I see this error every time. I just sent many "crash
reports" about that.
kernel 3.16.0-30-generic
[ 12.449818] iwlwifi :08:00.0: irq 62 for MSI/MSI-X
[ 12.961430] iwlwifi :08:00.0: loaded firmware version 25.228.9.0 op_mode
iwlmvm
[ 12.972905] iwlwifi 00
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1405842
Title:
Microcode SW error detected.
To manage notifications about
I am on Ubuntu 15.04 and this error pops up very frequently. Each time
it happens a crash report dialog pops up talking about NMI_INTERRUPT_WDG
with the iwlwifi driver.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launc
> Did this issue start happening after an update/upgrade?
No idea. I only saw this problem once and I cannot reproduce it.
Therefore I do not know if it occurs rarely or if it occurs with
specific kernel+FW versions.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Did this issue start happening after an update/upgrade? Was there a
kernel version where you were not having this particular problem? This
will help determine if the problem you are seeing is the result of a
regression, and when this regression was introduced. If this is a
regression, we can perf
