$ dmesg | grep iwl [ 9.990094] iwlwifi 0000:3d:00.0: enabling device (0000 -> 0002) [ 10.013099] iwlwifi 0000:3d:00.0: loaded firmware version 17.459231.0 op_mode iwlmvm [ 10.048453] iwlwifi 0000:3d:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144 [ 15.196743] iwlwifi 0000:3d:00.0: Failed to load firmware chunk! [ 15.196808] iwlwifi 0000:3d:00.0: Could not load the [0] uCode section [ 15.196984] iwlwifi 0000:3d:00.0: Failed to start INIT ucode: -110 [ 15.215869] iwlwifi 0000:3d:00.0: Failed to run INIT ucode: -110
https://www.spinics.net/lists/linux-wireless/msg166018.html Please check this
Thanks for the response. However, that email was talking about 8260. My wifi card is 7260. It has been end of lifed by Intel. Hence the last firmware version that is supported is being loaded, which is -17. However this fails to load in the latest kernel. 4.13. When I rollback by kernel to 4.12 it starts to work again. Let me know if there is any info you need from my side. It should be reproducible on Intel Dual Band Wireless AC 7260 card.
The discussion on the thread isn't device dependent. If missed the fact that you are taking about 4.13. sorry.
ok, thanks. I apologize if I misunderstood the thread. There seems to be a lot going on in the thread. However, it seems like the revert which is supposed to have fixed the issue made it to 4.13 rc? But I'm not seeing it, so, it is not clear to me if the issue has already been fixed or what I'm seeing is a new issue. At any rate, let me know if you need more info.
Just a quick update. This is still a problem in 4.13.4-1-ARCH
To clarify, the bug in the thread Emmanuel pointed out was introduced in 4.14, so it's not the same thing.
I tried to reproduce this issue with 4.13 and the same firmware, but it works fine for me: [ 10.434927] iwlwifi 0000:0b:00.0: loaded firmware version 17.459231.0 op_mode iwlmvm [ 10.434953] iwlwifi 0000:0b:00.0: Detected Intel(R) Dual Band Wireless AC 7260, REV=0x144 [ 10.453584] iwlwifi 0000:0b:00.0: base HW address: 0c:8b:fd:01:2d:5e Can you attach the full dmesg? Also, since you can always reproduce this with 4.13, but not with 4.12, is there any chance you could bisect?
I was able to load it by passing intel_iommu=off. I'm assuming this change is something by design?
(In reply to Jonny Mako from comment #8) > I was able to load it by passing intel_iommu=off. I'm assuming this change > is something by design? Nope. This only means that the component should be updated :) Doing this now...
ok, thanks. This is now fixed in 4.13.7-1-ARCH.
Hello, Could you point a parch which fixes this issue ? Current Ubuntu kernel seems to suffer this bug.