iwlwifi Microcode SW error + CPU-Warning

Getting your soundcard to work, using Debian on non-i386 hardware, etc

iwlwifi Microcode SW error + CPU-Warning

Postby /dev/human » 2018-05-29 15:11

Hello,

my name is /dev/human and I would like to ask for some help.
I recently bought two same notebooks. I installed Debian 9 "stretch" on both. They have the same WLAN configuration, i.e. the /etc/network/interfaces and /etc/wpa_supplicant/wpa_supplicant.conf files are perfectly the same. I don't use the "network-manager", "wicd" or similar tools.

Now, one of these two notebooks has the following error: sometimes, there is no WLAN connection after suspend. Not always, but perhaps 0.5-1 times per day (average).

In the system logs, i found the following suspicious messages:
Code: Select all
[13239.182442] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
[13239.183084] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
[13239.315630] iwlwifi 0000:02:00.0: Microcode SW error detected.  Restarting 0x2000000.
[13239.315959] iwlwifi 0000:02:00.0:                 FH_TSSR_TX_ERROR_REG: 0X00000000
[13239.316066] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[13239.316150] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[13239.316200] iwlwifi 0000:02:00.0: Failed to run INIT ucode: -5
[13239.320805] WARNING: CPU: 5 PID: 3368 at /build/linux-6WgLIg/linux-4.9.88/net/mac80211/util.c:1861 ieee80211_reconfig+0x9e/0x1350 [mac80211]
[13239.320863]  [<ffffffffaea78a5e>] ? __warn+0xbe/0xe0
[13239.320864]  [<ffffffffaea78adf>] ? warn_slowpath_fmt+0x5f/0x80
[13239.321242] WARNING: CPU: 6 PID: 3368 at /build/linux-6WgLIg/linux-4.9.88/net/mac80211/driver-ops.h:17 ieee80211_do_stop+0x57e/0x860 [mac80211]
[13239.321243] p2p-dev-wlp2s0:  Failed check-sdata-in-driver check, flags: 0x0
[13239.321286]  [<ffffffffaea78a5e>] ? __warn+0xbe/0xe0
[13239.321287]  [<ffffffffaea78adf>] ? warn_slowpath_fmt+0x5f/0x80
[13239.321451] WARNING: CPU: 0 PID: 3368 at /build/linux-6WgLIg/linux-4.9.88/net/mac80211/driver-ops.h:17 ieee80211_do_stop+0x57e/0x860 [mac80211]
[13239.321452] wlp2s0:  Failed check-sdata-in-driver check, flags: 0x4
[13239.321495]  [<ffffffffaea78a5e>] ? __warn+0xbe/0xe0
[13239.321497]  [<ffffffffaea78adf>] ? warn_slowpath_fmt+0x5f/0x80
[13239.321572] WARNING: CPU: 0 PID: 3368 at /build/linux-6WgLIg/linux-4.9.88/net/mac80211/driver-ops.c:39 ieee80211_do_stop+0x567/0x860 [mac80211]
[13239.321610]  [<ffffffffaea78a5e>] ? __warn+0xbe/0xe0
[13239.321712] PM: Device phy0 failed to resume async: error -5


Some other information:
WLAN and Bluetooth card: Intel Dual AC 8265 & Bluetooth (M.2 2230)
Kernel: default, i.e. "4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07)"
Version of Package "firmware-iwlwifi": "20161130-3" (stretch)
I tried the firmware-iwlwifi package from backports, too, but the problem persisted.
Anyway, the newer firmware isn't necessary. Look here for the list: https://www.intel.com/content/www/us/en ... rking.html
Intel states for my card:
Device: "Intel® Dual Band Wireless-AC 8265"
Kernels: "4.6+"
Firmware: "iwlwifi-8265-ucode-22.361476.0.tgz"
The kernel page says the same thing: https://wireless.wiki.kernel.org/en/use ... rs/iwlwifi
The firmware-iwlwifi package from the stretch repository contains that driver.
Look here: https://packages.debian.org/stretch/firmware-iwlwifi
* Intel Wireless 8265 firmware, version 21.302800.0
(iwlwifi-8265-21.ucode)
* Intel Wireless 8265 firmware, version 22.361476.0
(iwlwifi-8265-22.ucode)


As I said earlier: the other notebook runs perfectly fine!

I would really appreciate your help!

Greetings from /dev/human

Edit: typo
Last edited by /dev/human on 2018-05-29 16:25, edited 1 time in total.
/dev/human
 
Posts: 5
Joined: 2018-05-29 14:41

Re: iwlwifi Microcode SW error + CPU-Warning

Postby stevepusser » 2018-05-29 16:07

Since the Intel iwlwifi driver is included in the kernel, have you tried one of the newer kernels available in stretch-backports to see if a fix has been implemented in those?
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: Flightgear 2018.2.2, Pale Moon 28.2.0, wine-staging 3.20, GIMP 2.10.8, Cinnamon 3.8, Midori 6.0
User avatar
stevepusser
 
Posts: 10136
Joined: 2009-10-06 05:53

Re: iwlwifi Microcode SW error + CPU-Warning

Postby /dev/human » 2018-05-29 16:18

No, I haven't, because the other notebook with the same hardware has no problems. Additionally, the problem occurs only sometimes after suspend, not after all suspends. So I can't imagine that it's related to the firmware itself. Perhaps there are some other things I could check?
/dev/human
 
Posts: 5
Joined: 2018-05-29 14:41

Re: iwlwifi Microcode SW error + CPU-Warning

Postby M51 » 2018-05-29 16:52

You could swap hdd/ssd and see if the problem moves to the other machine.

Even with the "same" hardware there could be slight version changes, different eeprom values, different bios revision/config, etc.

Building a custom kernel with debugfs enabled for your card would give you a better picture of the card's internals that you could inspect directly from the filesystem.

Beyond that you could also swap wifi cards between the machines to help narrow down the problem. If they're Mini PCI-E or M.2 it's easy enough to do, although reconnecting (snap on) the antenna leads can be a pain just because the connectors are so tiny.
M51
 
Posts: 390
Joined: 2013-05-13 01:38

Re: iwlwifi Microcode SW error + CPU-Warning

Postby /dev/human » 2018-05-29 18:16

@M51: Thanks, but that sounds rather complicated. I'm just /dev/human...
I have an idea: Perhpas, the desktop software is responsible. On the "good" notebook, it's "i3", on the "bad", it's xfce4. I will substitute the xfce4 suspend procedure with "systemctl suspend", as I use it with i3. Then we'll see. I'm going to report in some days.

P.S. It's not only the same hardware, the two notebooks are the same brand, the same model, the same hardware configuration and they are bought at the same time.
/dev/human
 
Posts: 5
Joined: 2018-05-29 14:41

Re: iwlwifi Microcode SW error + CPU-Warning

Postby M51 » 2018-05-30 00:26

Swapping hdd/sdd on a laptop is pretty simple. You just need a screwdriver. :)

Typically you just have to remove the bottom screws and pry off the bottom cover. The hard drive may be held in place by a single retaining screw, and has a small cable you can simply pull off. To put one in, just reverse those steps. It shouldn't take more than 15 minutes per laptop, mostly because there are usually a dozen or more screws. Generally the hardest part is figuring out how to unsnap the bottom cover after you've gotten all the screws out.

Wifi card swapping is only marginally harder just because snapping the antenna connectors back on is difficult due to them being really small (for M.2 cards they're practically microscopic).
M51
 
Posts: 390
Joined: 2013-05-13 01:38

Re: iwlwifi Microcode SW error + CPU-Warning

Postby /dev/human » 2018-06-03 12:26

Ok, since the "systemctl suspend" command is used instead of the xfce4 builtin suspend, the issue didn't appear again.
But what's the problem with the suspend procedure of xfce4? I looked at the code, but I do not really understand what's going on.
Perhaps someone can see what's wrong? Or is it still a problem with the hardware and only systemd can manage it? Or is dbus the problem?
I got the tarball from https://packages.debian.org/stretch/xfce4-session (it's [xfce4-session_4.12.1.orig.tar.bz2]). Then I looked at "xfce4-session-4.12.1/xfce4-session-logout/main.c". Here is an excerpt:
Code: Select all
  /* open session bus */
  conn = dbus_g_bus_get (DBUS_BUS_SESSION, &err);
  if (conn == NULL)
    {
      xfce_session_logout_notify_error (_("Unable to contact D-Bus session bus"), err, have_display);
      g_error_free (err);
      return EXIT_FAILURE;
    }

  /* save the session, unless fast is provided */
  allow_save = !opt_fast;

  /* create messsage */
  proxy = dbus_g_proxy_new_for_name_owner (conn,
                                           "org.xfce.SessionManager",
                                           "/org/xfce/SessionManager",
                                           "org.xfce.Session.Manager",
                                           &err);
  if (proxy != NULL)
    {
*snip*
      else if (opt_suspend)
        {
          result = dbus_g_proxy_call (proxy, "Suspend", &err,
                                      G_TYPE_INVALID, G_TYPE_INVALID);
        }
/dev/human
 
Posts: 5
Joined: 2018-05-29 14:41

Re: iwlwifi Microcode SW error + CPU-Warning

Postby bw123 » 2018-06-03 12:38

I looked up this error from your first post...
iwlwifi 0000:02:00.0: Failed to run INIT ucode: -5

found this "[SOLVED] Intel N 7260 Wireless card stop working after ..."
https://bbs.archlinux.org/viewtopic.php?id=200653

There are probably different ways to pull/reinsert the module(s) during the suspend process that might help. I have also had to blacklist devices from suspend like card readers, but I don't recall the exact way it was done ATM.

If you can make it work doing something like this manually in a terminal...
remove module
suspend/close lid
resume/open lid
modprobe module

Then that should be easy to do by adding a script in /usr/lib/pm-utils/sleep.d or the correct /etc/pm-utils or /usr/local equivalent. There are probably a few in there already to give you an idea how it works.
User avatar
bw123
 
Posts: 3532
Joined: 2011-05-09 06:02
Location: TN_USA

Re: iwlwifi Microcode SW error + CPU-Warning

Postby stevepusser » 2018-06-03 20:18

I have it working on my system:

Create or edit as sysadmin: /etc/pm/config.d/config

Add one line:
Code: Select all
SUSPEND_MODULES="iwlwifi"
The MX Linux repositories: Backports galore! If we don't have something, just ask and we'll try--we like challenges. New packages: Flightgear 2018.2.2, Pale Moon 28.2.0, wine-staging 3.20, GIMP 2.10.8, Cinnamon 3.8, Midori 6.0
User avatar
stevepusser
 
Posts: 10136
Joined: 2009-10-06 05:53

Re: iwlwifi Microcode SW error + CPU-Warning

Postby /dev/human » 2018-06-07 07:14

bw123 wrote:There are probably different ways to pull/reinsert the module(s) during the suspend process
Yes, that's the explanation for the different behaviour.

With systemd, it works, the problem hasn't reappeared yet.

stevepusser wrote:Create or edit as sysadmin: /etc/pm/config.d/config

Does the xfce4 suspend procedure uses pm-utils?
/dev/human
 
Posts: 5
Joined: 2018-05-29 14:41

Re: iwlwifi Microcode SW error + CPU-Warning

Postby bw123 » 2018-06-07 12:56

/dev/human wrote:...
Does the xfce4 suspend procedure uses pm-utils?


Wouldn't that be easier for you to answer, since you have xfce installed?
On all of my systems, even when pm-utils package isn't installed, pm settings and scripts in above mentioned locations are used by the os.

If xfce is not, I might consider that a bug, but not sure.

https://docs.xfce.org/xfce/xfce4-power-manager/faq
User avatar
bw123
 
Posts: 3532
Joined: 2011-05-09 06:02
Location: TN_USA


Return to Hardware

Who is online

Users browsing this forum: No registered users and 5 guests

fashionable