You are not logged in.

#1 2019-10-16 09:01:11

pawggers
Member
Registered: 2019-04-30
Posts: 7

[SOLVED] Issues with network after booting into windows 10

Hello,

I have a dual boot setup with Windows 10 and ArchLinux. I was playing games with Windows 10 and when I switched back to ArchLinux my network and overall performance was shitty AF. My network speed went from 350mbps to 10kb/s and pages would not load. Under full load the computer would lock up and I had to restart due to the freeze. I remember looking at the logs and it said something about a queue being full and the driver crashed.

I rolled back linux-firmware thinking it was a bad update but the problem persisted. The issue only happened when I used Windows 10 and went back to Arch.

One day the problem resolved after I did a big update and everything was performing flawlessly on Arch. Network was back to 350mbps and things were great. Today one of the games I wanted to play (Archeage Unchained) made me log back into Windows 10. After my session I went back to Arch and my computer was fucked up again. The network is trash and I lock up after doing a speed test at fast.com.

At this point I ran

mkinitcpio -p linux

thinking it was something with that and it didn't fix anything.

As I'm typing this right now the problem persists.


dmesg | grep -i iwl
[   47.252535] iwlwifi 0000:03:00.0: Found debug destination: EXTERNAL_DRAM
[   47.252536] iwlwifi 0000:03:00.0: Found debug configuration: 0
[   47.252818] iwlwifi 0000:03:00.0: loaded firmware version 46.6bf1df06.0 op_mode iwlmvm
[   47.630854] iwlwifi 0000:03:00.0: Detected Intel(R) Wireless-AC 9260 160MHz, REV=0x324
[   47.637988] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[   47.638119] iwlwifi 0000:03:00.0: Allocated 0x00400000 bytes for firmware monitor.
[   47.677773] iwlwifi 0000:03:00.0: base HW address: a4:c3:f0:86:7d:1a
[   47.746094] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[   47.747382] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
[   48.082975] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[   48.198039] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[   48.262415] iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring
[   48.489666] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[   48.604254] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[   48.667107] iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring
[  213.934270] iwlwifi 0000:03:00.0: Error sending STATISTICS_CMD: time out after 2000ms.
[  213.934274] iwlwifi 0000:03:00.0: Current CMD queue read_ptr 220 write_ptr 221
[  213.935393] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[  213.935396] iwlwifi 0000:03:00.0: Status: 0x00000080, count: 6
[  213.935398] iwlwifi 0000:03:00.0: Loaded firmware version: 46.6bf1df06.0
[  213.935400] iwlwifi 0000:03:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
[  213.935402] iwlwifi 0000:03:00.0: 0x008022F2 | trm_hw_status0
[  213.935403] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
[  213.935405] iwlwifi 0000:03:00.0: 0x0048853E | branchlink2
[  213.935407] iwlwifi 0000:03:00.0: 0x00479392 | interruptlink1
[  213.935408] iwlwifi 0000:03:00.0: 0x00006908 | interruptlink2
[  213.935410] iwlwifi 0000:03:00.0: 0x0001A9E8 | data1
[  213.935411] iwlwifi 0000:03:00.0: 0xFF000000 | data2
[  213.935413] iwlwifi 0000:03:00.0: 0x4000000C | data3
[  213.935415] iwlwifi 0000:03:00.0: 0x6E4178D2 | beacon time
[  213.935416] iwlwifi 0000:03:00.0: 0x47AE15AE | tsf low
[  213.935418] iwlwifi 0000:03:00.0: 0x0000060E | tsf hi
[  213.935420] iwlwifi 0000:03:00.0: 0x000FFF4C | time gp1
[  213.935421] iwlwifi 0000:03:00.0: 0x09DA2DC0 | time gp2
[  213.935423] iwlwifi 0000:03:00.0: 0x00000001 | uCode revision type
[  213.935425] iwlwifi 0000:03:00.0: 0x0000002E | uCode version major
[  213.935426] iwlwifi 0000:03:00.0: 0x6BF1DF06 | uCode version minor
[  213.935428] iwlwifi 0000:03:00.0: 0x00000321 | hw version
[  213.935430] iwlwifi 0000:03:00.0: 0x18C89004 | board version
[  213.935431] iwlwifi 0000:03:00.0: 0x0000001C | hcmd
[  213.935433] iwlwifi 0000:03:00.0: 0x00013040 | isr0
[  213.935435] iwlwifi 0000:03:00.0: 0x0004E000 | isr1
[  213.935436] iwlwifi 0000:03:00.0: 0x00001802 | isr2
[  213.935438] iwlwifi 0000:03:00.0: 0x0041D4C0 | isr3
[  213.935439] iwlwifi 0000:03:00.0: 0x00000000 | isr4
[  213.935441] iwlwifi 0000:03:00.0: 0x00DB0502 | last cmd Id
[  213.935443] iwlwifi 0000:03:00.0: 0x0001A9E8 | wait_event
[  213.935444] iwlwifi 0000:03:00.0: 0x00000084 | l2p_control
[  213.935446] iwlwifi 0000:03:00.0: 0x00001402 | l2p_duration
[  213.935447] iwlwifi 0000:03:00.0: 0x0000000F | l2p_mhvalid
[  213.935449] iwlwifi 0000:03:00.0: 0x00000085 | l2p_addr_match
[  213.935451] iwlwifi 0000:03:00.0: 0x0000000F | lmpm_pmg_sel
[  213.935452] iwlwifi 0000:03:00.0: 0x08081424 | timestamp
[  213.935454] iwlwifi 0000:03:00.0: 0x14F83830 | flow_handler
[  213.935496] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[  213.935498] iwlwifi 0000:03:00.0: Status: 0x00000080, count: 7
[  213.935500] iwlwifi 0000:03:00.0: 0x20000066 | NMI_INTERRUPT_HOST
[  213.935501] iwlwifi 0000:03:00.0: 0x00000000 | umac branchlink1
[  213.935503] iwlwifi 0000:03:00.0: 0xC008888E | umac branchlink2
[  213.935505] iwlwifi 0000:03:00.0: 0xC0084414 | umac interruptlink1
[  213.935506] iwlwifi 0000:03:00.0: 0xC0084414 | umac interruptlink2
[  213.935508] iwlwifi 0000:03:00.0: 0x01000000 | umac data1
[  213.935510] iwlwifi 0000:03:00.0: 0xC0084414 | umac data2
[  213.935511] iwlwifi 0000:03:00.0: 0xDEADBEEF | umac data3
[  213.935513] iwlwifi 0000:03:00.0: 0x0000002E | umac major
[  213.935515] iwlwifi 0000:03:00.0: 0x6BF1DF06 | umac minor
[  213.935516] iwlwifi 0000:03:00.0: 0x09DA2DB1 | frame pointer
[  213.935518] iwlwifi 0000:03:00.0: 0xC088627C | stack pointer
[  213.935519] iwlwifi 0000:03:00.0: 0x00DB0502 | last host cmd
[  213.935521] iwlwifi 0000:03:00.0: 0x00000000 | isr status reg
[  213.935530] iwlwifi 0000:03:00.0: Fseq Registers:
[  213.935535] iwlwifi 0000:03:00.0: 0xEEF91C80 | FSEQ_ERROR_CODE
[  213.935540] iwlwifi 0000:03:00.0: 0x00000000 | FSEQ_TOP_INIT_VERSION
[  213.935545] iwlwifi 0000:03:00.0: 0xFDCB74BE | FSEQ_CNVIO_INIT_VERSION
[  213.935550] iwlwifi 0000:03:00.0: 0x0000A371 | FSEQ_OTP_VERSION
[  213.935555] iwlwifi 0000:03:00.0: 0x4E6363AC | FSEQ_TOP_CONTENT_VERSION
[  213.935559] iwlwifi 0000:03:00.0: 0xF6891989 | FSEQ_ALIVE_TOKEN
[  213.935564] iwlwifi 0000:03:00.0: 0xE08F7E8D | FSEQ_CNVI_ID
[  213.935569] iwlwifi 0000:03:00.0: 0x65B58802 | FSEQ_CNVR_ID
[  213.935574] iwlwifi 0000:03:00.0: 0x01000200 | CNVI_AUX_MISC_CHIP
[  213.935581] iwlwifi 0000:03:00.0: 0x01300202 | CNVR_AUX_MISC_CHIP
[  213.935588] iwlwifi 0000:03:00.0: 0x0000485B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[  213.935646] iwlwifi 0000:03:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[  213.935652] iwlwifi 0000:03:00.0: Collecting data: trigger 2 fired.
[  214.736501] iwlwifi 0000:03:00.0: Queue 0 is active on fifo 7 and stuck for 2500 ms. SW [220, 221] HW [220, 221] FH TRB=0x07000dc
[  214.758591] iwlwifi 0000:03:00.0: Failing on timeout while stopping DMA channel 8 [0x077f0000]
[  214.780372] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[  214.894328] iwlwifi 0000:03:00.0: Applying debug destination EXTERNAL_DRAM
[  214.957647] iwlwifi 0000:03:00.0: FW already configured (0) - re-configuring

Last edited by pawggers (2019-10-17 22:17:31)

Offline

#2 2019-10-16 11:00:22

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 7,771

Re: [SOLVED] Issues with network after booting into windows 10

You need to disable fast-startup in Windows: https://wiki.archlinux.org/index.php/Du … t_Start-Up

Offline

#3 2019-10-17 22:01:33

pawggers
Member
Registered: 2019-04-30
Posts: 7

Re: [SOLVED] Issues with network after booting into windows 10

V1del wrote:

You need to disable fast-startup in Windows: https://wiki.archlinux.org/index.php/Du … t_Start-Up

Thank you so much omg this fixed it!

Offline

#4 2019-10-17 22:13:25

2ManyDogs
Forum Moderator
Registered: 2012-01-15
Posts: 2,787

Re: [SOLVED] Issues with network after booting into windows 10

Please remember to mark your thread [SOLVED] (edit the title of your first post).

Offline

#5 2019-10-18 08:02:17

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 7,771

Re: [SOLVED] Issues with network after booting into windows 10

Be wary that on big Windows updates the functionality might be reenabled, so look out for that.

Offline

#6 2019-10-25 20:34:17

pawggers
Member
Registered: 2019-04-30
Posts: 7

Re: [SOLVED] Issues with network after booting into windows 10

So the problem actually came back.

I think the linux-firmware package is fine and instead it was probably something with the kernel. Instead of downgrading the kernel I decided to replace it entirely and install linux-lts. So far everything is flawless again. No more studdering and lock ups under network load.

I think I updated my system and while I was rebooting I just so happen to play on windows. When I came back to my new kernel on Arch it must have been the culprit. I think Windows had nothing to do with this problem.

This is most likely related: https://bbs.archlinux.org/viewtopic.php?id=249605

Last edited by pawggers (2019-10-25 20:43:54)

Offline

Board footer

Powered by FluxBB