You are not logged in.

Pages: 1

Topic closed

#1 2016-02-28 09:10:22

skioda86
Member
Registered: 2015-05-19
Posts: 13

Intel 8260 connection drop down with dmesg errors

Hi,
I have a problem with my configuration: I bought a xps13 (9350), and i changed the base wifi card, with the Intel 8260.
The new Intel 8260 works with the iwlwifi (and the connection works fine...but...sometimes the connection drop down and I must disconnect and reconnect the connection.
The dmesg write me this:

# dmesg

...
...
[23884.403545] ACPI Error: Cannot release Mutex [PATM], not acquired (20150930/exmutex-376)
[23884.403565] ACPI Error: Method parse/execution failed [\_SB.PCI0.LPCB.ECDV._Q66] (Node ffff8802784da8c0), AE_AML_MUTEX_NOT_ACQUIRED (20150930/psparse-542)
[24638.074819] kvm: zapping shadow pages for mmio generation wraparound
[24638.093065] kvm: zapping shadow pages for mmio generation wraparound
[24647.074475] kvm [7354]: vcpu0 unhandled rdmsr: 0x570
[24647.074497] kvm [7354]: vcpu1 unhandled rdmsr: 0x570
[24647.074550] kvm [7354]: vcpu2 unhandled rdmsr: 0x570
[24647.074573] kvm [7354]: vcpu3 unhandled rdmsr: 0x570
[24647.770488] kvm [7354]: vcpu2 unhandled rdmsr: 0x606
[24799.760571] kvm: zapping shadow pages for mmio generation wraparound
[24799.773891] kvm: zapping shadow pages for mmio generation wraparound
[24808.709320] kvm [8177]: vcpu0 unhandled rdmsr: 0x570
[24808.709335] kvm [8177]: vcpu1 unhandled rdmsr: 0x570
[24808.709367] kvm [8177]: vcpu2 unhandled rdmsr: 0x570
[24808.709380] kvm [8177]: vcpu3 unhandled rdmsr: 0x570
[24809.411191] kvm [8177]: vcpu2 unhandled rdmsr: 0x606
[24819.345424] kvm [8177]: vcpu0 unhandled rdmsr: 0x611
[24819.345435] kvm [8177]: vcpu0 unhandled rdmsr: 0x639
[24819.345440] kvm [8177]: vcpu0 unhandled rdmsr: 0x641
[24819.345445] kvm [8177]: vcpu0 unhandled rdmsr: 0x619
[24819.446974] kvm [8177]: vcpu0 unhandled rdmsr: 0x611
[24819.446985] kvm [8177]: vcpu0 unhandled rdmsr: 0x639
[24819.446990] kvm [8177]: vcpu0 unhandled rdmsr: 0x641
[24819.446994] kvm [8177]: vcpu0 unhandled rdmsr: 0x619
[26743.426917] iwlwifi 0000:3a:00.0: Queue 2 stuck for 10000 ms.
[26743.426938] iwlwifi 0000:3a:00.0: Current SW read_ptr 157 write_ptr 193
[26743.426989] iwl data: 00000000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
[26743.427018] iwlwifi 0000:3a:00.0: FH TRBs(0) = 0xeb6dffff
[26743.427045] iwlwifi 0000:3a:00.0: FH TRBs(1) = 0xc011004a
[26743.427071] iwlwifi 0000:3a:00.0: FH TRBs(2) = 0x8ebd897e
[26743.427098] iwlwifi 0000:3a:00.0: FH TRBs(3) = 0x80300085
[26743.427124] iwlwifi 0000:3a:00.0: FH TRBs(4) = 0xf57e5fd4
[26743.427150] iwlwifi 0000:3a:00.0: FH TRBs(5) = 0x8d594090
[26743.427177] iwlwifi 0000:3a:00.0: FH TRBs(6) = 0x157f68f6
[26743.427203] iwlwifi 0000:3a:00.0: FH TRBs(7) = 0x00709044
[26743.427275] iwlwifi 0000:3a:00.0: Q 0 is active and mapped to fifo 3 ra_tid 0x0000 [134,134]
[26743.427347] iwlwifi 0000:3a:00.0: Q 1 is active and mapped to fifo 2 ra_tid 0x0000 [0,0]
[26743.427418] iwlwifi 0000:3a:00.0: Q 2 is active and mapped to fifo 1 ra_tid 0x0000 [157,193]
[26743.427489] iwlwifi 0000:3a:00.0: Q 3 is active and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.427560] iwlwifi 0000:3a:00.0: Q 4 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.427631] iwlwifi 0000:3a:00.0: Q 5 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.427701] iwlwifi 0000:3a:00.0: Q 6 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.427772] iwlwifi 0000:3a:00.0: Q 7 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.427843] iwlwifi 0000:3a:00.0: Q 8 is active and mapped to fifo 3 ra_tid 0x0000 [0,0]
[26743.427914] iwlwifi 0000:3a:00.0: Q 9 is active and mapped to fifo 7 ra_tid 0x0000 [69,69]
[26743.427985] iwlwifi 0000:3a:00.0: Q 10 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.428055] iwlwifi 0000:3a:00.0: Q 11 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.428126] iwlwifi 0000:3a:00.0: Q 12 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.428197] iwlwifi 0000:3a:00.0: Q 13 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.428268] iwlwifi 0000:3a:00.0: Q 14 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.428339] iwlwifi 0000:3a:00.0: Q 15 is active and mapped to fifo 5 ra_tid 0x0000 [0,0]
[26743.428410] iwlwifi 0000:3a:00.0: Q 16 is active and mapped to fifo 1 ra_tid 0x07ff [59,222]
[26743.428481] iwlwifi 0000:3a:00.0: Q 17 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.428552] iwlwifi 0000:3a:00.0: Q 18 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.428622] iwlwifi 0000:3a:00.0: Q 19 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.428695] iwlwifi 0000:3a:00.0: Q 20 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.428806] iwlwifi 0000:3a:00.0: Q 21 is inactive and mapped to fifo 0 ra_tid 0xf800 [0,0]
[26743.428876] iwlwifi 0000:3a:00.0: Q 22 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.428947] iwlwifi 0000:3a:00.0: Q 23 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.429017] iwlwifi 0000:3a:00.0: Q 24 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.429088] iwlwifi 0000:3a:00.0: Q 25 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.429158] iwlwifi 0000:3a:00.0: Q 26 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.429229] iwlwifi 0000:3a:00.0: Q 27 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.429299] iwlwifi 0000:3a:00.0: Q 28 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.429369] iwlwifi 0000:3a:00.0: Q 29 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.429440] iwlwifi 0000:3a:00.0: Q 30 is inactive and mapped to fifo 0 ra_tid 0x0000 [0,0]
[26743.429534] iwlwifi 0000:3a:00.0: Microcode SW error detected.  Restarting 0x2000000.
[26743.429539] iwlwifi 0000:3a:00.0: CSR values:
[26743.429542] iwlwifi 0000:3a:00.0: (2nd byte of CSR_INT_COALESCING is CSR_INT_PERIODIC_REG)
[26743.429558] iwlwifi 0000:3a:00.0:        CSR_HW_IF_CONFIG_REG: 0X00489008
[26743.429573] iwlwifi 0000:3a:00.0:          CSR_INT_COALESCING: 0X00000040
[26743.429588] iwlwifi 0000:3a:00.0:                     CSR_INT: 0X00000000
[26743.429603] iwlwifi 0000:3a:00.0:                CSR_INT_MASK: 0X00000000
[26743.429617] iwlwifi 0000:3a:00.0:           CSR_FH_INT_STATUS: 0X00000000
[26743.429632] iwlwifi 0000:3a:00.0:                 CSR_GPIO_IN: 0X00000019
[26743.429647] iwlwifi 0000:3a:00.0:                   CSR_RESET: 0X00000000
[26743.429662] iwlwifi 0000:3a:00.0:                CSR_GP_CNTRL: 0X08040005
[26743.429676] iwlwifi 0000:3a:00.0:                  CSR_HW_REV: 0X00000201
[26743.429691] iwlwifi 0000:3a:00.0:              CSR_EEPROM_REG: 0Xd55555d5
[26743.429706] iwlwifi 0000:3a:00.0:               CSR_EEPROM_GP: 0Xd55555d5
[26743.429720] iwlwifi 0000:3a:00.0:              CSR_OTP_GP_REG: 0Xd55555d5
[26743.429735] iwlwifi 0000:3a:00.0:                 CSR_GIO_REG: 0X001f0042
[26743.429750] iwlwifi 0000:3a:00.0:            CSR_GP_UCODE_REG: 0X00000000
[26743.429765] iwlwifi 0000:3a:00.0:           CSR_GP_DRIVER_REG: 0X00000000
[26743.429779] iwlwifi 0000:3a:00.0:           CSR_UCODE_DRV_GP1: 0X00000000
[26743.429794] iwlwifi 0000:3a:00.0:           CSR_UCODE_DRV_GP2: 0X00000000
[26743.429809] iwlwifi 0000:3a:00.0:                 CSR_LED_REG: 0X00000060
[26743.429824] iwlwifi 0000:3a:00.0:        CSR_DRAM_INT_TBL_REG: 0X8805e6a6
[26743.429838] iwlwifi 0000:3a:00.0:        CSR_GIO_CHICKEN_BITS: 0X07800200
[26743.429853] iwlwifi 0000:3a:00.0:             CSR_ANA_PLL_CFG: 0Xd55555d5
[26743.429868] iwlwifi 0000:3a:00.0:      CSR_MONITOR_STATUS_REG: 0Xc03803c0
[26743.429882] iwlwifi 0000:3a:00.0:           CSR_HW_REV_WA_REG: 0X0001001a
[26743.429897] iwlwifi 0000:3a:00.0:        CSR_DBG_HPET_MEM_REG: 0Xffff0010
[26743.429901] iwlwifi 0000:3a:00.0: FH register values:
[26743.429927] iwlwifi 0000:3a:00.0:         FH_RSCSR_CHNL0_STTS_WPTR_REG: 0X05e68c00
[26743.429953] iwlwifi 0000:3a:00.0:        FH_RSCSR_CHNL0_RBDCB_BASE_REG: 0X005db660
[26743.429979] iwlwifi 0000:3a:00.0:                  FH_RSCSR_CHNL0_WPTR: 0X00000088
[26743.430005] iwlwifi 0000:3a:00.0:         FH_MEM_RCSR_CHNL0_CONFIG_REG: 0X00801054
[26743.430031] iwlwifi 0000:3a:00.0:          FH_MEM_RSSR_SHARED_CTRL_REG: 0X000000fc
[26743.430057] iwlwifi 0000:3a:00.0:            FH_MEM_RSSR_RX_STATUS_REG: 0X03230000
[26743.430083] iwlwifi 0000:3a:00.0:    FH_MEM_RSSR_RX_ENABLE_ERR_IRQ2DRV: 0X00000000
[26743.430110] iwlwifi 0000:3a:00.0:                FH_TSSR_TX_STATUS_REG: 0X07ff0001
[26743.430136] iwlwifi 0000:3a:00.0:                 FH_TSSR_TX_ERROR_REG: 0X00000000
[26743.430273] iwlwifi 0000:3a:00.0: Start IWL Error Log Dump:
[26743.430277] iwlwifi 0000:3a:00.0: Status: 0x00000000, count: 6
[26743.430281] iwlwifi 0000:3a:00.0: Loaded firmware version: 16.242414.0
[26743.430286] iwlwifi 0000:3a:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
[26743.430289] iwlwifi 0000:3a:00.0: 0x00A00220 | uPc
[26743.430293] iwlwifi 0000:3a:00.0: 0x00000000 | branchlink1
[26743.430296] iwlwifi 0000:3a:00.0: 0x00000BF0 | branchlink2
[26743.430299] iwlwifi 0000:3a:00.0: 0x00022B90 | interruptlink1
[26743.430303] iwlwifi 0000:3a:00.0: 0x0002EB22 | interruptlink2
[26743.430306] iwlwifi 0000:3a:00.0: 0x00000000 | data1
[26743.430309] iwlwifi 0000:3a:00.0: 0x00000080 | data2
[26743.430313] iwlwifi 0000:3a:00.0: 0x07A30000 | data3
[26743.430316] iwlwifi 0000:3a:00.0: 0x22807604 | beacon time
[26743.430320] iwlwifi 0000:3a:00.0: 0xE50A89FF | tsf low
[26743.430323] iwlwifi 0000:3a:00.0: 0x00000041 | tsf hi
[26743.430326] iwlwifi 0000:3a:00.0: 0x00000000 | time gp1
[26743.430329] iwlwifi 0000:3a:00.0: 0x3A0F453D | time gp2
[26743.430333] iwlwifi 0000:3a:00.0: 0x00000000 | time gp3
[26743.430336] iwlwifi 0000:3a:00.0: 0x00000010 | uCode version major
[26743.430339] iwlwifi 0000:3a:00.0: 0x0003B2EE | uCode version minor
[26743.430343] iwlwifi 0000:3a:00.0: 0x00000201 | hw version
[26743.430346] iwlwifi 0000:3a:00.0: 0x00489008 | board version
[26743.430349] iwlwifi 0000:3a:00.0: 0x103B001C | hcmd
[26743.430353] iwlwifi 0000:3a:00.0: 0x24022002 | isr0
[26743.430356] iwlwifi 0000:3a:00.0: 0x00800000 | isr1
[26743.430359] iwlwifi 0000:3a:00.0: 0x0800180A | isr2
[26743.430362] iwlwifi 0000:3a:00.0: 0x004174C0 | isr3
[26743.430366] iwlwifi 0000:3a:00.0: 0x00000000 | isr4
[26743.430369] iwlwifi 0000:3a:00.0: 0x00000110 | isr_pref
[26743.430372] iwlwifi 0000:3a:00.0: 0x00000000 | wait_event
[26743.430375] iwlwifi 0000:3a:00.0: 0x00000080 | l2p_control
[26743.430379] iwlwifi 0000:3a:00.0: 0x00018030 | l2p_duration
[26743.430382] iwlwifi 0000:3a:00.0: 0x0000003F | l2p_mhvalid
[26743.430385] iwlwifi 0000:3a:00.0: 0x000000CE | l2p_addr_match
[26743.430389] iwlwifi 0000:3a:00.0: 0x0000000D | lmpm_pmg_sel
[26743.430392] iwlwifi 0000:3a:00.0: 0x22121936 | timestamp
[26743.430395] iwlwifi 0000:3a:00.0: 0x00348898 | flow_handler
[26743.430472] iwlwifi 0000:3a:00.0: Start IWL Error Log Dump:
[26743.430475] iwlwifi 0000:3a:00.0: Status: 0x00000000, count: 7
[26743.430479] iwlwifi 0000:3a:00.0: 0x00000070 | ADVANCED_SYSASSERT
[26743.430482] iwlwifi 0000:3a:00.0: 0x00000000 | umac branchlink1
[26743.430486] iwlwifi 0000:3a:00.0: 0xC00817F8 | umac branchlink2
[26743.430489] iwlwifi 0000:3a:00.0: 0xC0081510 | umac interruptlink1
[26743.430492] iwlwifi 0000:3a:00.0: 0xC0081510 | umac interruptlink2
[26743.430496] iwlwifi 0000:3a:00.0: 0x00000800 | umac data1
[26743.430499] iwlwifi 0000:3a:00.0: 0xC0081510 | umac data2
[26743.430502] iwlwifi 0000:3a:00.0: 0xDEADBEEF | umac data3
[26743.430505] iwlwifi 0000:3a:00.0: 0x00000010 | umac major
[26743.430509] iwlwifi 0000:3a:00.0: 0x0003B2EE | umac minor
[26743.430512] iwlwifi 0000:3a:00.0: 0xC0887F80 | frame pointer
[26743.430515] iwlwifi 0000:3a:00.0: 0xC0887F80 | stack pointer
[26743.430519] iwlwifi 0000:3a:00.0: 0x0944004E | last host cmd
[26743.430522] iwlwifi 0000:3a:00.0: 0x00000000 | isr status reg
[26743.430529] ieee80211 phy0: Hardware restart was requested
[26743.942663] iwlwifi 0000:3a:00.0: L1 Enabled - LTR Disabled
[26743.942927] iwlwifi 0000:3a:00.0: L1 Enabled - LTR Disabled
[26743.943566] iwlwifi 0000:3a:00.0: can't access the RSA semaphore it is write protected
[26744.087505] iwlwifi 0000:3a:00.0: L1 Enabled - LTR Disabled
[26744.087794] iwlwifi 0000:3a:00.0: L1 Enabled - LTR Disabled
[26744.088564] iwlwifi 0000:3a:00.0: can't access the RSA semaphore it is write protected

Some other information:

# lspci -v
...
3a:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
	Subsystem: Intel Corporation Dual Band Wireless-AC 8260
	Flags: bus master, fast devsel, latency 0, IRQ 283
	Memory at dc200000 (64-bit, non-prefetchable) [size=8K]
	Capabilities: <access denied>
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi
...

Previously in the boot-phase the dmesg write me this (I have the kernel 4.4.3-1):

# dmesg
...
Intel(R) Wireless WiFi driver for Linux
[    2.894577] Copyright(c) 2003- 2015 Intel Corporation
[    2.894722] iwlwifi 0000:3a:00.0: enabling device (0000 -> 0002)
[    2.897576] iwlwifi 0000:3a:00.0: Unsupported splx structure
[    2.898865] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2
[    2.898882] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2
[    2.898898] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2
[    2.903117] iwlwifi 0000:3a:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm
...

Where is the problem?
How I can resolve it?
Thanks

Sorry for my BAD english but I'm a very Italian goat student!
Sorry for my poor information on Arch system but..... I'm a very Italian goat student! smile

[Hardware] = XPS13 (9350) - intel i5-6200U - 8GB Ram - Intel 8260 wifi - FHD - 256SSD Nvme  ||  [DE] = Gnome

Offline

#2 2016-03-01 08:23:33

skioda86
Member
Registered: 2015-05-19
Posts: 13

Re: Intel 8260 connection drop down with dmesg errors

up

Sorry for my BAD english but I'm a very Italian goat student!
Sorry for my poor information on Arch system but..... I'm a very Italian goat student! smile

[Hardware] = XPS13 (9350) - intel i5-6200U - 8GB Ram - Intel 8260 wifi - FHD - 256SSD Nvme  ||  [DE] = Gnome

Offline

#3 2016-03-01 09:09:55

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: Intel 8260 connection drop down with dmesg errors

skioda86 wrote:

up

What the hell does this mean? If you were intending to bump, then please note that bumping is forbidden.

https://wiki.archlinux.org/index.php/Fo … te#Bumping

Offline

#4 2016-03-01 10:42:35

skioda86
Member
Registered: 2015-05-19
Posts: 13

Re: Intel 8260 connection drop down with dmesg errors

Sorry...I did't know this...

Sorry for my BAD english but I'm a very Italian goat student!
Sorry for my poor information on Arch system but..... I'm a very Italian goat student! smile

[Hardware] = XPS13 (9350) - intel i5-6200U - 8GB Ram - Intel 8260 wifi - FHD - 256SSD Nvme  ||  [DE] = Gnome

Offline

#5 2016-03-05 18:37:39

pigiron
Member
From: USA
Registered: 2009-07-14
Posts: 150

Re: Intel 8260 connection drop down with dmesg errors

[26743.426917] iwlwifi 0000:3a:00.0: Queue 2 stuck for 10000 ms.

That error message is saying that the device driver found that no packets have been transmitted for the last 10 seconds. If the device driver is doing it's job correctly, this usually/sometimes means that the adapter hardware/firmware is stopped/stuck for some reason. The driver then dumped the contents of the hardware registers inside the adapter along with other information. About the only folks that can decipher that register info would be the Intel hardware/firmware developers.

When you couple that with the following messages:

[    2.898865] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2
[    2.898882] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2
[    2.898898] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2
[    2.903117] iwlwifi 0000:3a:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm

That's saying that the device driver tried to load iwlwifi-8000C-[19 through 17].ucode but it couldn't find those firmware files in /lib/firmware/. It finally found the iwlwifi-8000C-16.ucode file and loaded that firmware version.

If this was my problem, I would go here:

http://git.kernel.org/cgit/linux/kernel … .git/tree/

and download the iwlwifi-8000C-19.ucode file into /lib/firmware/ and see if that newer firmware version helps (or not).

Be aware that if you try that, your Arch setup is now unique. I'm not sure, but it may cause future upgrade problems when Arch eventually ships that file. You should also loudly proclaim your unique setup in any future posts to the forum when asking about this device.

Offline

#6 2016-03-05 23:05:00

jeremy31
Member
Registered: 2015-11-01
Posts: 149

Re: Intel 8260 connection drop down with dmesg errors

pigiron wrote:

[26743.426917] iwlwifi 0000:3a:00.0: Queue 2 stuck for 10000 ms.

That error message is saying that the device driver found that no packets have been transmitted for the last 10 seconds. If the device driver is doing it's job correctly, this usually/sometimes means that the adapter hardware/firmware is stopped/stuck for some reason. The driver then dumped the contents of the hardware registers inside the adapter along with other information. About the only folks that can decipher that register info would be the Intel hardware/firmware developers.

When you couple that with the following messages:

[    2.898865] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2
[    2.898882] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2
[    2.898898] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2
[    2.903117] iwlwifi 0000:3a:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm

That's saying that the device driver tried to load iwlwifi-8000C-[19 through 17].ucode but it couldn't find those firmware files in /lib/firmware/. It finally found the iwlwifi-8000C-16.ucode file and loaded that firmware version.

If this was my problem, I would go here:

http://git.kernel.org/cgit/linux/kernel … .git/tree/

and download the iwlwifi-8000C-19.ucode file into /lib/firmware/ and see if that newer firmware version helps (or not).

Be aware that if you try that, your Arch setup is now unique. I'm not sure, but it may cause future upgrade problems when Arch eventually ships that file. You should also loudly proclaim your unique setup in any future posts to the forum when asking about this device.

Or they could rename the iwlwifi-8000C-16.ucode and see if the same problems occur with an older firmware version after a reboot and it might be worth sending the error log to the linux people at intel linuxwifi@intel.com

Offline

#7 2016-03-30 22:04:32

skioda86
Member
Registered: 2015-05-19
Posts: 13

Re: Intel 8260 connection drop down with dmesg errors

thanks very much to everybody!!!!!

Sorry for my BAD english but I'm a very Italian goat student!
Sorry for my poor information on Arch system but..... I'm a very Italian goat student! smile

[Hardware] = XPS13 (9350) - intel i5-6200U - 8GB Ram - Intel 8260 wifi - FHD - 256SSD Nvme  ||  [DE] = Gnome

Offline

#8 2016-03-31 05:56:11

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: Intel 8260 connection drop down with dmesg errors

@skioda86, if you managed to solve your problem then please mention the details here and mark the thread as solved.

https://wiki.archlinux.org/index.php/Fo … way_street

Offline

#9 2016-08-31 14:33:32

DakotaTheGiraffe
Member
Registered: 2014-09-29
Posts: 4

Re: Intel 8260 connection drop down with dmesg errors

pigiron wrote:

[26743.426917] iwlwifi 0000:3a:00.0: Queue 2 stuck for 10000 ms.

That error message is saying that the device driver found that no packets have been transmitted for the last 10 seconds. If the device driver is doing it's job correctly, this usually/sometimes means that the adapter hardware/firmware is stopped/stuck for some reason. The driver then dumped the contents of the hardware registers inside the adapter along with other information. About the only folks that can decipher that register info would be the Intel hardware/firmware developers.

When you couple that with the following messages:

[    2.898865] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2
[    2.898882] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2
[    2.898898] iwlwifi 0000:3a:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2
[    2.903117] iwlwifi 0000:3a:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm

That's saying that the device driver tried to load iwlwifi-8000C-[19 through 17].ucode but it couldn't find those firmware files in /lib/firmware/. It finally found the iwlwifi-8000C-16.ucode file and loaded that firmware version.

If this was my problem, I would go here:

http://git.kernel.org/cgit/linux/kernel … .git/tree/

and download the iwlwifi-8000C-19.ucode file into /lib/firmware/ and see if that newer firmware version helps (or not).

Be aware that if you try that, your Arch setup is now unique. I'm not sure, but it may cause future upgrade problems when Arch eventually ships that file. You should also loudly proclaim your unique setup in any future posts to the forum when asking about this device.

I have the same wireless module and downloading the -19.ucode and placing it in /lib/firmware fixed this issue. I think it's safe to say that this is how to resolve the issue. I've seen a couple other posts with the same module and issue.

Anyone with the Intel AC 8260 random wifi disconnect issue should be redirected here and this post needs to be marked as solved.

EDIT: Nvm, it appears that this only made the wifi connect for a longer period of time and has not solved this issue for me. Extremely frustrating.

Last edited by DakotaTheGiraffe (2016-08-31 14:38:16)

Offline

#10 2016-09-01 11:33:42

x33a
Forum Fellow
Registered: 2009-08-15
Posts: 4,587

Re: Intel 8260 connection drop down with dmesg errors

Since the OP didn't care to post the solution to this problem, I will close this thread from being bumped any further.

Offline

Pages: 1

Topic closed

Board footer

Powered by FluxBB