"Firmware Crash" (but not with "live-session" or UBUNTU!)

Questions about WIFI networks and devices
Forum rules
Before you post please read how to get help
Post Reply
McJigger
Level 1
Level 1
Posts: 4
Joined: Tue Feb 20, 2018 6:25 am

"Firmware Crash" (but not with "live-session" or UBUNTU!)

Post by McJigger » Tue Feb 20, 2018 6:33 am

Hello!

There's a problem I have with the Wifi connection on my Acer-Aspire-E5-575G-Laptop with the newest Mint (18.3). I randomly get disconnected. Then I have to switch Wifi off and on again via control panel in order to have it work correctly afterwards until a new boot. I noticed that this always happens when the computer automatically "changes bandwith" (why???), see below. I only hope some Linux Mint expert can solve this problem. Thanks in advance!

Additional info:
There's no such problem when I run Mint from a "Live-USB-Stick" or under UBUNTU (which Mint derives from)!
Can anybody tell me please why that is?

Code: Select all

Feb 12 13:20:48 acer kernel: [  329.632874] wlp3s0: AP 9c:c7:a6:96:e7:ab changed bandwidth, new config is 2412 MHz, width 2 (2422/0 MHz)
Feb 12 13:20:48 acer kernel: [  329.668385] ath10k_pci 0000:03:00.0: firmware crashed! (uuid b26d690f-eaa3-4b4a-b8e5-8850fefe9b88)
Feb 12 13:20:48 acer kernel: [  329.668400] ath10k_pci 0000:03:00.0: qca9377 hw1.1 target 0x05020001 chip_id 0x003821ff sub 11ad:08a6
Feb 12 13:20:48 acer kernel: [  329.668403] ath10k_pci 0000:03:00.0: kconfig debug 0 debugfs 1 tracing 1 dfs 0 testmode 0
Feb 12 13:20:48 acer kernel: [  329.668981] ath10k_pci 0000:03:00.0: firmware ver WLAN.TF.1.0-00267-1 api 5 features ignore-otp crc32 79cea2c7
Feb 12 13:20:48 acer kernel: [  329.669380] ath10k_pci 0000:03:00.0: board_file api 2 bmi_id N/A crc32 93da0176
Feb 12 13:20:48 acer kernel: [  329.669388] ath10k_pci 0000:03:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
Feb 12 13:20:48 acer kernel: [  329.671391] ath10k_pci 0000:03:00.0: firmware register dump:
Feb 12 13:20:48 acer kernel: [  329.671397] ath10k_pci 0000:03:00.0: [00]: 0x05020001 0x000015B3 0x00985B3A 0x00955B31
Feb 12 13:20:48 acer kernel: [  329.671400] ath10k_pci 0000:03:00.0: [04]: 0x00985B3A 0x00060730 0x00000004 0x00000000
Feb 12 13:20:48 acer kernel: [  329.671403] ath10k_pci 0000:03:00.0: [08]: 0x00955A00 0x00438830 0x00450888 0x00420970
Feb 12 13:20:48 acer kernel: [  329.671405] ath10k_pci 0000:03:00.0: [12]: 0x00000009 0x00000000 0x00952CD0 0x00952CE6
Feb 12 13:20:48 acer kernel: [  329.671408] ath10k_pci 0000:03:00.0: [16]: 0x00952CC4 0x0091080D 0x00000000 0x0091080D
Feb 12 13:20:48 acer kernel: [  329.671410] ath10k_pci 0000:03:00.0: [20]: 0x40985B3A 0x0040E788 0x00400000 0x00421888
Feb 12 13:20:48 acer kernel: [  329.671412] ath10k_pci 0000:03:00.0: [24]: 0x809BF546 0x0040E7E8 0x00426470 0xC0985B3A
Feb 12 13:20:48 acer kernel: [  329.671415] ath10k_pci 0000:03:00.0: [28]: 0x809B90D8 0x0040E958 0x00000018 0x0042EA0C
Feb 12 13:20:48 acer kernel: [  329.671417] ath10k_pci 0000:03:00.0: [32]: 0x809B859A 0x0040E9A8 0x0040E9CC 0x00428D74
Feb 12 13:20:48 acer kernel: [  329.671420] ath10k_pci 0000:03:00.0: [36]: 0x8091D252 0x0040E9C8 0x00000000 0x00000001
Feb 12 13:20:48 acer kernel: [  329.671422] ath10k_pci 0000:03:00.0: [40]: 0x809EDD7B 0x0040EA78 0x00437544 0x00429428
Feb 12 13:20:48 acer kernel: [  329.671424] ath10k_pci 0000:03:00.0: [44]: 0x809EB6A6 0x0040EA98 0x00437544 0x00000001
Feb 12 13:20:48 acer kernel: [  329.671427] ath10k_pci 0000:03:00.0: [48]: 0x80911210 0x0040EAE8 0x00000010 0x004041D0
Feb 12 13:20:48 acer kernel: [  329.671429] ath10k_pci 0000:03:00.0: [52]: 0x80911154 0x0040EB28 0x00400000 0x00000000
Feb 12 13:20:48 acer kernel: [  329.671431] ath10k_pci 0000:03:00.0: [56]: 0x8091122D 0x0040EB48 0x00000000 0x00400600
Feb 12 13:20:48 acer kernel: [  329.671434] ath10k_pci 0000:03:00.0: Copy Engine register dump:
Feb 12 13:20:48 acer kernel: [  329.671444] ath10k_pci 0000:03:00.0: [00]: 0x00034400   5   5   3   3
Feb 12 13:20:48 acer kernel: [  329.671455] ath10k_pci 0000:03:00.0: [01]: 0x00034800  30  30 107 108
Feb 12 13:20:48 acer kernel: [  329.671466] ath10k_pci 0000:03:00.0: [02]: 0x00034c00  26  26  25  26
Feb 12 13:20:48 acer kernel: [  329.671475] ath10k_pci 0000:03:00.0: [03]: 0x00035000  21  21  22  21
Feb 12 13:20:48 acer kernel: [  329.671485] ath10k_pci 0000:03:00.0: [04]: 0x00035400 1385 1385 246 182
Feb 12 13:20:48 acer kernel: [  329.671496] ath10k_pci 0000:03:00.0: [05]: 0x00035800   0   0   0   0
Feb 12 13:20:48 acer kernel: [  329.671507] ath10k_pci 0000:03:00.0: [06]: 0x00035c00   9   9   9   9
Feb 12 13:20:48 acer kernel: [  329.671519] ath10k_pci 0000:03:00.0: [07]: 0x00036000   1   1   1   1
Feb 12 13:20:48 acer kernel: [  329.701019] ieee80211 phy0: Hardware restart was requested
Feb 12 13:20:48 acer kernel: [  329.701198] pcieport 0000:00:1d.2: AER: Multiple Corrected error received: id=00ea
Feb 12 13:20:48 acer kernel: [  329.701206] pcieport 0000:00:1d.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ea(Receiver ID)
Feb 12 13:20:48 acer kernel: [  329.701210] pcieport 0000:00:1d.2:   device [8086:9d1a] error status/mask=00000001/00002000
Feb 12 13:20:48 acer kernel: [  329.701214] pcieport 0000:00:1d.2:    [ 0] Receiver Error         (First)
Feb 12 13:20:48 acer kernel: [  329.701218] pcieport 0000:00:1d.2: AER: Multiple Corrected error received: id=00ea
Feb 12 13:20:48 acer kernel: [  329.701224] pcieport 0000:00:1d.2: can't find device of ID00ea
Feb 12 13:20:48 acer kernel: [  329.701225] pcieport 0000:00:1d.2: AER: Multiple Corrected error received: id=00ea
Feb 12 13:20:48 acer kernel: [  329.701230] pcieport 0000:00:1d.2: can't find device of ID00ea
Feb 12 13:20:48 acer kernel: [  329.701232] pcieport 0000:00:1d.2: AER: Multiple Corrected error received: id=00ea
Feb 12 13:20:48 acer kernel: [  329.701237] pcieport 0000:00:1d.2: can't find device of ID00ea
Feb 12 13:20:48 acer kernel: [  329.740654] pcieport 0000:00:1d.2: AER: Multiple Corrected error received: id=00ea
Feb 12 13:20:48 acer kernel: [  329.740662] pcieport 0000:00:1d.2: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00ea(Receiver ID)
Feb 12 13:20:48 acer kernel: [  329.740666] pcieport 0000:00:1d.2:   device [8086:9d1a] error status/mask=00000041/00002000
Feb 12 13:20:48 acer kernel: [  329.740668] pcieport 0000:00:1d.2:    [ 0] Receiver Error         (First)
Feb 12 13:20:48 acer kernel: [  329.740670] pcieport 0000:00:1d.2:    [ 6] Bad TLP
Last edited by McJigger on Sun Mar 04, 2018 5:33 pm, edited 3 times in total.

JeremyB
Level 18
Level 18
Posts: 8379
Joined: Fri Feb 21, 2014 8:17 am

Re: "Firmware Crash"

Post by JeremyB » Tue Feb 20, 2018 6:59 am

Is the wifi router set to a fixed channel and channel width rather than auto?

McJigger
Level 1
Level 1
Posts: 4
Joined: Tue Feb 20, 2018 6:25 am

Re: "Firmware Crash"

Post by McJigger » Fri Feb 23, 2018 10:46 am

The router is set "auto".

User avatar
Pjotr
Level 20
Level 20
Posts: 10208
Joined: Mon Mar 07, 2011 10:18 am
Location: The Netherlands (Holland)
Contact:

Re: "Firmware Crash"

Post by Pjotr » Fri Feb 23, 2018 10:50 am

McJigger wrote:
Fri Feb 23, 2018 10:46 am
The router is set "auto".
Then try a fixed channel.
Tip: 10 things to do after installing Linux Mint 19 Tara
Keep your Linux Mint healthy: Avoid these 10 fatal mistakes
Twitter: twitter.com/easylinuxtips
All in all, horse sense simply makes sense.

McJigger
Level 1
Level 1
Posts: 4
Joined: Tue Feb 20, 2018 6:25 am

Re: "Firmware Crash"

Post by McJigger » Fri Feb 23, 2018 10:57 am

Ok, I tried a fixed channel (though the router recommends "auto") and first thought it would work, but it doesn't. So I switched the router setting back to "auto". Besides, OS X and Windows don't bother about "auto" at all... ;-)
So what else can I/we do?

JeremyB
Level 18
Level 18
Posts: 8379
Joined: Fri Feb 21, 2014 8:17 am

Re: "Firmware Crash"

Post by JeremyB » Sat Feb 24, 2018 8:34 am

The Qualcomm Atheros people just released a new firmware version 9 days ago that we can try

Code: Select all

cd /lib/firmware/ath10k/QCA9377/hw1.0/
sudo mv firmware-5.bin firmware-5.bin.bak
sudo wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/ath10k/QCA9377/hw1.0/firmware-5.bin
Reboot

McJigger
Level 1
Level 1
Posts: 4
Joined: Tue Feb 20, 2018 6:25 am

Re: "Firmware Crash"

Post by McJigger » Sun Feb 25, 2018 5:15 pm

It sounded too good...
Unfortunately still "changing bandwidth" and "crashing firmware" :-(
Should I post the complete output of the "wireless script" here or is the syslog-info above sufficient?

Post Reply

Return to “Wireless”