Intel 8260 / iwlwifi Occasionally unusuable after restart

Bug #1558252 reported by Ryan
42
This bug affects 9 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Hello,
Some times my wifi card is inaccessible immediately after boot. Typically, restarting the machine or reloading the iwlwifi kernel module resolves the issue.

dmesg on inaccessible card:

[ 13.146917] iwlwifi 0000:04:00.0: Unsupported splx structure
[ 13.147620] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2
[ 13.147754] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2
[ 13.147765] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2
[ 13.154952] iwlwifi 0000:04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm
[ 13.191912] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
[ 13.198415] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 13.199446] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 13.200661] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
[ 14.218185] iwlwifi 0000:04:00.0: SecBoot CPU1 Status: 0x3090003, CPU2 Status: 0x0
[ 14.218190] iwlwifi 0000:04:00.0: Failed to start INIT ucode: -110
[ 14.219090] iwlwifi 0000:04:00.0: Failed to run INIT ucode: -110
[ 14.219157] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-13-generic 4.4.0-13.29
ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
Uname: Linux 4.4.0-13-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ryan 1999 F.... pulseaudio
Date: Wed Mar 16 12:00:48 2016
HibernationDevice: RESUME=UUID=04e04e17-3976-4daa-a1dd-2dd369aee83d
InstallationDate: Installed on 2015-09-21 (176 days ago)
InstallationMedia: It
IwConfig:
 enp0s31f6 no wireless extensions.

 lo no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 20FNCTO1WW
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-13-generic root=/dev/mapper/it--vg-root ro quiet intel_pstate=no_hwp
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-13-generic N/A
 linux-backports-modules-4.4.0-13-generic N/A
 linux-firmware 1.156
RfKill:
 0: tpacpi_bluetooth_sw: Bluetooth
  Soft blocked: yes
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to xenial on 2016-02-24 (20 days ago)
dmi.bios.date: 01/05/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R06ET33W (1.07 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FNCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: dmi:bvnLENOVO:bvrR06ET33W(1.07):bd01/05/2016:svnLENOVO:pn20FNCTO1WW:pvrThinkPadT460:rvnLENOVO:rn20FNCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.name: 20FNCTO1WW
dmi.product.version: ThinkPad T460
dmi.sys.vendor: LENOVO

Revision history for this message
Ryan (carbonfreeze) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.5 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Marv (144dbspl) wrote :

I am on Debian Testing and have the same problem with kernels 4.3 and 4.4 (Debian one's) as well as 4.5 (compiled from unmodified source with Debian config). Sometimes I have to reboot around 10 times to get a connected with NetworkManager, although the device seems to be available through iwconfig.

Revision history for this message
Ryan (carbonfreeze) wrote :

I tested 4.5.0-040500-generic, did 20 reboots/shutdown cycles, both powered and on battery. I haven't been able to trigger the issue again.

tags: added: kernel-fixed-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Ryan (carbonfreeze) wrote :

I was able to trigger this again today on 4.4.0-16:

[ 13.665350] iwlwifi 0000:04:00.0: Unsupported splx structure
[ 13.678584] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2
[ 13.679439] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2
[ 13.681595] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2
[ 13.696430] iwlwifi 0000:04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm
[ 13.738654] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
[ 13.739014] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 13.739585] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 13.741861] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
[ 14.761845] iwlwifi 0000:04:00.0: SecBoot CPU1 Status: 0x3090001, CPU2 Status: 0x0
[ 14.761849] iwlwifi 0000:04:00.0: Failed to start INIT ucode: -110
[ 14.762365] iwlwifi 0000:04:00.0: Failed to run INIT ucode: -110
[ 14.762575] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 48.788008] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2
[ 48.788016] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2
[ 48.788023] iwlwifi 0000:04:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2
[ 48.788854] iwlwifi 0000:04:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm
[ 48.788916] iwlwifi 0000:04:00.0: Unsupported splx structure
[ 48.793638] iwlwifi 0000:04:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
[ 48.793949] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 48.794322] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 48.795508] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
[ 48.953491] ieee80211 phy1: Selected rate control algorithm 'iwl-mvm-rs'
[ 48.955333] iwlwifi 0000:04:00.0 wlp4s0: renamed from wlan0
[ 48.976863] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 48.977285] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 48.978049] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected
[ 49.124083] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 49.124547] iwlwifi 0000:04:00.0: L1 Enabled - LTR Enabled
[ 49.125305] iwlwifi 0000:04:00.0: can't access the RSA semaphore it is write protected

Revision history for this message
fletch (richard-artumi) wrote :

I'm seeing similar problems. The Intel 8260 provides bluetooth as we well as wifi connectivity. It seems that for me Wifi can't be enabled until bluetooth is enabled. I'm using linux 4.4.0-18-generic

Revision history for this message
fichtenelch (t-hillebrandt) wrote :

I'm also seeing the same problems running Ubuntu 16.04 on an Intel NUC6i5SYK. I installed Ubuntu a couple of days ago starting with kernel 4.4.0-21-generic, here the wifi worked most of the time. Updating to kernel 4.4.0-22-generic made this problem even worse. Now wifi doesn't work at all, even after several reboots. Booting with the previous kernel makes it work again...

Revision history for this message
openfred (openfred) wrote :

Please have a look at this solution: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1590985
Post #9

I had a similar issue after restarting a Lenovo thinkpad T520 (iwlwifi on a Centrino 6205).
After a cold start, not all the time. Sometimes I needed up to 4 restart before the wifi connexion succeeds.

The solution described in bug 1590985 solved both issues:
wifi connection at startup _AND_ wifi restore after suspend.

Revision history for this message
Decio Della Fortuna (decio-dellafortuna) wrote :

The problem persists. Thinkpad P50 BIOS 1.60 (latest) Ubuntu 20.04 kernel 5.4.0-28-generic.
Some time after restart wifi is unusable. Under system settings wifi item is not available.
Previously I used Fedora 30 and 31 with the same problem. After several restarts or if I shut down and power off wifi back available.

Revision history for this message
Decio Della Fortuna (decio-dellafortuna) wrote :

The problem persists. Thinkpad P50 BIOS 1.62 (latest) Ubuntu 20.04.1 kernel 5.4.0-42-generic.
Some time after a restart or cold start, wifi is unusable. Under system settings wifi item is not available.

Revision history for this message
David (dcorneli) wrote :

S

Revision history for this message
David (dcorneli) wrote :

Same issue here on a Thinkoad P70, as a workaround I keep switching airplane mode on & off until the Wifi adapter gets detected again. Using bluetooth on this laptop is a bit erratic too
(have to switch on & off multiple times). I've got the impression that it might be caused by some USB issue as my fingerprint reader is not always detected too.

Had this issue since Ubuntu 16, now running on 20.10

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.