Bug 112981 - Intel 8260 fails to load at boot
Summary: Intel 8260 fails to load at boot
Status: CLOSED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: network-wireless (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: DO NOT USE - assign "network-wireless-intel" component instead
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-02-23 17:51 UTC by digimer
Modified: 2016-06-05 07:40 UTC (History)
3 users (show)

See Also:
Kernel Version: 4.4.2
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description digimer 2016-02-23 17:51:08 UTC
Environment (kernel is epel's -ml);

====
# cat /etc/redhat-release 
CentOS Linux release 7.2.1511 (Core) 

# uname -r
4.4.2-1.el7.elrepo.x86_64

# lspci |grep -i wireless
04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)

# lshw -C network
  *-network               
       description: Wireless interface
       product: Wireless 8260
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:04:00.0
       logical name: wlp4s0
       version: 3a
       serial: a4:34:d9:71:bb:64
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=4.4.2-1.el7.elrepo.x86_64 firmware=25.30.13.0 latency=0 link=no multicast=yes wireless=IEEE 802.11abgn
       resources: irq:131 memory:b3c00000-b3c01fff

# lsmod |grep iwlwifi
iwlwifi               131072  1 iwlmvm
cfg80211              557056  3 iwlwifi,mac80211,iwlmvm

# ip a | grep wlp -A 1
5: wlp4s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN qlen 1000
    link/ether a4:34:d9:71:bb:64 brd ff:ff:ff:ff:ff:ff
====

When I boot the machine, at first, the driver fails to load:

====
# dmesg |grep iwlwifi
[    4.412126] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
[    4.431192] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2
[    4.431717] iwlwifi 0000:04:00.0: Falling back to user helper
[   64.163674] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2
[   64.163683] iwlwifi 0000:04:00.0: Falling back to user helper
[  124.165666] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2
[  124.165675] iwlwifi 0000:04:00.0: Falling back to user helper
====

If I leave the system alone, the driver eventually loads:

====
[  184.168675] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-16.ucode failed with error -2
[  184.168684] iwlwifi 0000:04:00.0: Falling back to user helper
[  244.171402] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-15.ucode failed with error -2
[  244.171410] iwlwifi 0000:04:00.0: Falling back to user helper
[  304.173409] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-14.ucode failed with error -2
[  304.173418] iwlwifi 0000:04:00.0: Falling back to user helper
[  364.191288] iwlwifi 0000:04:00.0: loaded firmware version 25.30.13.0 op_mode iwlmvm
[  364.214989] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
[  364.215280] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[  364.216210] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[  364.217254] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
[  364.382321] iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0
[  364.400946] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[  364.401351] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[  364.402247] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
[  364.545979] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[  364.546470] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[  364.548015] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
====
Comment 1 Emmanuel Grumbach 2016-02-23 18:40:27 UTC
You should really get -16.ucode.

I wonder why it takes 60 seconds to fallback to older firmwares.
Comment 2 digimer 2016-02-23 18:43:51 UTC
> You should really get -16.ucode.

Should I file a bug for RHEL then?
Comment 3 Emmanuel Grumbach 2016-02-24 12:48:40 UTC
what do you have in /lib/firmware/iwlwifi-8000C* ?
Comment 4 digimer 2016-02-24 16:00:48 UTC
# ls -lah /lib/firmware/iwlwifi-8000C*
-rw-r--r--. 1 root root 1.7M Nov 20 01:22 /lib/firmware/iwlwifi-8000C-13.ucode
Comment 5 digimer 2016-02-24 16:09:14 UTC
I downloaded iwlwifi-8000C-16.ucode from https://github.com/OpenELEC/iwlwifi-firmware/blob/master/firmware/iwlwifi-8000C-16.ucode, set the ownership and mode:

# ls -lah /lib/firmware/iwlwifi-8000C*
-rw-r--r--. 1 root root 1.7M Nov 20 01:22 /lib/firmware/iwlwifi-8000C-13.ucode
-rw-r--r--. 1 root root 2.3M Feb 24 10:02 /lib/firmware/iwlwifi-8000C-16.ucode

And rebooted. It still is exhibiting the same behaviour.

====
# dmesg |grep iwlwifi
[    4.340292] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
[    4.354269] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2
[    4.354984] iwlwifi 0000:04:00.0: Falling back to user helper
[   64.183747] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2
[   64.183759] iwlwifi 0000:04:00.0: Falling back to user helper
[  124.185127] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2
[  124.185138] iwlwifi 0000:04:00.0: Falling back to user helper
[  184.188493] iwlwifi 0000:04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm
[  184.223830] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
[  184.224130] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[  184.225121] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[  184.226445] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
[  184.399727] iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0
[  184.418313] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[  184.418760] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[  184.419711] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
[  184.565105] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[  184.565788] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[  184.567191] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
====

Here are the sums:

====
# md5sum /lib/firmware/iwlwifi-8000C*
fd0ac79f34b10ce98d58100b509be73f  /lib/firmware/iwlwifi-8000C-13.ucode
2d2b06c5644c9d718e7c0495aafa215b  /lib/firmware/iwlwifi-8000C-16.ucode
====
Comment 6 Emmanuel Grumbach 2016-02-24 16:33:44 UTC
I don't understand why it takes 60 seconds to fail.

I'll try to find out.

Is iwlwifi compiled in the kernel or as a loadable module?
Comment 7 digimer 2016-02-24 16:36:12 UTC
# lsmod |grep iwlwifi
iwlwifi               131072  1 iwlmvm
cfg80211              557056  3 iwlwifi,mac80211,iwlmvm

So it looks like it's a module.
Comment 8 digimer 2016-02-24 16:37:34 UTC
If there is anything you would like me to try, this machine is not in use at this time. I am happy to test anything for you as there is no concern with reinstalling if needed.
Comment 9 Emmanuel Grumbach 2016-03-14 13:13:37 UTC
Are sure you have udev running properly?
This looks like a distro issue. The user space isn't responding to the kernel's request.

For sure, this is not a wifi bug.
Comment 10 Emmanuel Grumbach 2016-03-14 17:59:17 UTC
Closing as I can't do much with this.
Please contact your distribution.
Comment 11 Akemi Yagi 2016-06-05 07:27:44 UTC
According to https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi/core_release , iwlwifi-8000C-16.ucode (Core13) is marked EOL. Maybe the latest (-21.ucode) should be tried. Or at least -19.ucode as a minimum.
Comment 12 digimer 2016-06-05 07:35:52 UTC
I don't remember what machine I was having this problem on. It hasn't been an issue on anything I'm running for a while now. So consider it resolved and close the bug. :)
Comment 13 Akemi Yagi 2016-06-05 07:39:19 UTC
Your article: https://alteeve.ca/w/Thinkpad_P70

:-)
Comment 14 digimer 2016-06-05 07:40:38 UTC
Oh riiiiight! OK, I will reinstall when Fedora 24 comes out. If I hit the issue then, I'll try the newer driver. If not, I'll update that to remove the notes about the drivers.

Thanks!

Note You need to log in before you can comment on or make changes to this bug.