From: Emmanuel Grumbach <egrumbach@gmail.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: iwlwifi: Microcode SW error detected. Restarting 0x2000000.
Date: Sat, 18 Jul 2015 22:07:24 +0300 [thread overview]
Message-ID: <CANUX_P1NbGYnkwEqYebcTtL+C4NQF1NS4ji47fsRi9OzcoQk2A@mail.gmail.com> (raw)
In-Reply-To: <55A90BF4.6040402@gmx.de>
Emmanuel Grumbach
egrumbach@gmail.com
On Fri, Jul 17, 2015 at 5:06 PM, Toralf Förster <toralf.foerster@gmx.de> wrote:
> On 07/14/2015 08:43 AM, Emmanuel Grumbach wrote:
>> You are not using the latest firmware. Please upgrade to 25.17.12.0.
>
> At least with this firmware the issue is self-healing after a short while - I do not need to restart the interface.
>
Thanks for the feedback.
> FWIW it worked flawlessly since Dec last year so far - no software upgrade at the fritz box nor any hardware change.
> So the current kernel uncovered then an (existing hidden ?) issue, right ?
The current kernel might just be loading a newer firmware that has a regression.
It may very well be a regression in iwlwifi (kernel or firmware).
What you can try is to use an older firmware. kernel 4.0 can still
load -9.ucode and up. So you can just try to downgrade the firmware.
Please use: ethtool -i wlan0 to check the version of the firmware.
Don't rely on the information in modinfo.
prev parent reply other threads:[~2015-07-18 19:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 21:53 iwlwifi: Microcode SW error detected. Restarting 0x2000000 Toralf Förster
2015-07-14 6:43 ` Emmanuel Grumbach
2015-07-15 13:26 ` Toralf Förster
2015-07-15 17:48 ` Emmanuel Grumbach
2015-07-15 19:20 ` Toralf Förster
2015-07-15 19:47 ` Emmanuel Grumbach
2015-07-15 20:03 ` Toralf Förster
2015-07-17 14:06 ` Toralf Förster
2015-07-18 19:07 ` Emmanuel Grumbach [this message]
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=CANUX_P1NbGYnkwEqYebcTtL+C4NQF1NS4ji47fsRi9OzcoQk2A@mail.gmail.com \
--to=egrumbach@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=toralf.foerster@gmx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.