You are not logged in.

#1 2017-12-24 07:15:17

ideaman924
Member
Registered: 2017-12-24
Posts: 3

Laptop not going to sleep, Wi-Fi problems and more

Hoping somebody can help me out here. I have a Samsung laptop (NT500R5H-Y53L) with a Qualcomm Atheros QCA6174 wireless card.

When I boot up, everything runs well - the Wi-Fi connects through GNOME automatically, the Internet is working, yada yada. Suspend also works - the power indicator light shuts off to let me know the system is sleeping.

Sometimes, after I leave the laptop unattended for a while, when I come back the Wi-Fi is "dead". This behavior is also observed (sometimes) when I plug in the Ethernet port, use the laptop for a bit, then disconnect the wire to move somewhere else, and then notice that Wi-Fi isn't working. Firefox cannot connect to any webpages, the GNOME applet shows a Wi-Fi icon but it says it's not "connected", and doesn't show any networks in the popup menu. (I have not yet tried turned Wi-Fi off and on again, but the next time the crash comes back I certainly will and post here)

dmesg shows "Firmware Crashed" for the ath10k_pci driver. I would've posted logs if it hadn't been wiped because of a forced reboot. Running 'ip link' results in a frozen Terminal - aka the cursor will blink, it will still grab my commands but the escape signal (Ctrl-C) will just register as ^C on the console and it will not be killed.

When the Wi-Fi problems occur, the computer will not go to sleep. The power indicator LED will stay blue to show me that the system isn't shutting down. Sometimes, the screen will stay black, but sometimes the screen will turn on and say "Failed to freeze tasks after 20.01 sec" or something along the lines. Then the suspend service (I believe this is the systemd thing that suspends my computer) crashes, and sends me to GDM where I can log back into GNOME. Checking journalctl showed that dhcpcd was to blame, but there wasn't any more information other than a core dump.

The computer will not shut down when the Wi-Fi problems occur - sometimes showing "There's a stop task for ...." and cycles through the culprit programs. Sometimes it's dhcpcd, sometimes it's NetworkManager.

If you've been reading through here and thinking "Jeez, @ideaman924 keeps using the word 'sometimes'" it's because the crashes and freeze-ups and no-suspend symptoms are sporadic. Sometimes it happens, sometimes it doesn't, sometimes the computer will trundle on fine, unaware of any issue that lurks ahead.

Any advice on how to get suspend working on this baby will be appreciated.  (And the WiFi driver not crashing) Thanks in advance.

Offline

#2 2017-12-24 07:42:36

ooo
Member
Registered: 2013-04-10
Posts: 1,479

Re: Laptop not going to sleep, Wi-Fi problems and more

I'd imagine your laptop isn't suspending because of your wifi firmware crashed, so you should focus on the latter issue.

Next time this happens, get the error from logs, and look up if anyone else has solved the same issue. Searching for arh10k on the forums found at least this that could be related, and has potential solution posted at the end.

If you can't find a solution, post the error from logs, and preferably link to full dmesg/journal.

Offline

#3 2017-12-24 17:46:22

ideaman924
Member
Registered: 2017-12-24
Posts: 3

Re: Laptop not going to sleep, Wi-Fi problems and more

ooo wrote:

I'd imagine your laptop isn't suspending because of your wifi firmware crashed, so you should focus on the latter issue.

Next time this happens, get the error from logs, and look up if anyone else has solved the same issue. Searching for arh10k on the forums found at least this that could be related, and has potential solution posted at the end.

If you can't find a solution, post the error from logs, and preferably link to full dmesg/journal.

Not sure what changed but I'm having hell of a time reproducing the issue right now. (Lol, bugs always disappear when I actively look for them...)

I will post the logs when the thing craps its pants again. Until then this problem will need further verification.

Can I keep this thread open, or is it better to open a new one when the problems return and I have a proper log? And also, if I reply in like, say, two weeks or so, does the thread bump back up? (just in case it gets buried and forgotten)

Sorry about this, I assumed the bug would be pretty trivial to locate.


EDIT: Firmware crashed a couple times but the laptop remained stable and a couple minutes later the firmware rebooted back on its own, no reboots or instabilities. The Wi-Fi was cut for the duration of the reboot but otherwise it started working again. Really strange. Here's a link to the logs if anybody is up to some sleuthing: https://gist.github.com/anonymous/890dc … bebe3c0417

EDIT2: Decided to do some checking out of the logs too, just in case I could spot anything that could help you guys. First firmware crash in dmesg.log starts at line 759:

[  127.457699] wlp1s0: deauthenticating from 00:07:89:41:51:d6 by local choice (Reason: 3=DEAUTH_LEAVING)
[  127.475444] ath10k_pci 0000:01:00.0: firmware crashed! (guid 0b18ac17-cfa7-485f-93f5-09b9a5a229bb)
[  127.475451] ath10k_pci 0000:01:00.0: qca6174 hw2.1 target 0x05010000 chip_id 0x003405ff sub 144d:4125
[  127.475453] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[  127.475849] ath10k_pci 0000:01:00.0: firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features ignore-otp,no-4addr-pad crc32 10bf8e08
[  127.476065] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id N/A crc32 ae2e275a
[  127.476067] ath10k_pci 0000:01:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[  127.478094] ath10k_pci 0000:01:00.0: firmware register dump:
[  127.478100] ath10k_pci 0000:01:00.0: [00]: 0x05010000 0x00000000 0x0092E4DC 0x8FC53A2E
[  127.478103] ath10k_pci 0000:01:00.0: [04]: 0x0092E4DC 0x00060130 0x00000018 0x0041A760
[  127.478106] ath10k_pci 0000:01:00.0: [08]: 0x8FC53A1A 0x00400000 0x00000000 0x000A5C88
[  127.478108] ath10k_pci 0000:01:00.0: [12]: 0x00000009 0x00000000 0x0096C09C 0x0096C0A7
[  127.478111] ath10k_pci 0000:01:00.0: [16]: 0x0096BDBC 0x009287BD 0x00000000 0x009287BD
[  127.478113] ath10k_pci 0000:01:00.0: [20]: 0x4092E4DC 0x0041A710 0x00000000 0x0F000000
[  127.478116] ath10k_pci 0000:01:00.0: [24]: 0x809432A7 0x0041A770 0x0040D400 0xC092E4DC
[  127.478118] ath10k_pci 0000:01:00.0: [28]: 0x80942BC4 0x0041A790 0x8FC53A1A 0x00400000
[  127.478121] ath10k_pci 0000:01:00.0: [32]: 0x80947BA7 0x0041A7B0 0x00404D88 0x0040E074
[  127.478123] ath10k_pci 0000:01:00.0: [36]: 0x809BDECC 0x0041A7D0 0x00404D88 0x0040E074
[  127.478125] ath10k_pci 0000:01:00.0: [40]: 0x8099638C 0x0041A7F0 0x00404D88 0x00000000
[  127.478128] ath10k_pci 0000:01:00.0: [44]: 0x80992076 0x0041A810 0x0044FD68 0x0046FFE8
[  127.478130] ath10k_pci 0000:01:00.0: [48]: 0x80996BD3 0x0041A830 0x0044FD68 0x00000000
[  127.478132] ath10k_pci 0000:01:00.0: [52]: 0x800B4405 0x0041A850 0x00422318 0x00005002
[  127.478135] ath10k_pci 0000:01:00.0: [56]: 0x809A6C34 0x0041A8E0 0x0042932C 0x0042CA20
[  127.478137] ath10k_pci 0000:01:00.0: Copy Engine register dump:
[  127.478146] ath10k_pci 0000:01:00.0: [00]: 0x00034400   1   1   3   3
[  127.478155] ath10k_pci 0000:01:00.0: [01]: 0x00034800  18  18 277 278
[  127.478164] ath10k_pci 0000:01:00.0: [02]: 0x00034c00  50  50 113 114
[  127.478172] ath10k_pci 0000:01:00.0: [03]: 0x00035000   4   4   5   4
[  127.478181] ath10k_pci 0000:01:00.0: [04]: 0x00035400 6243 6243 115  51
[  127.478189] ath10k_pci 0000:01:00.0: [05]: 0x00035800   0   0   0   0
[  127.478198] ath10k_pci 0000:01:00.0: [06]: 0x00035c00   9   9   9   9
[  127.478206] ath10k_pci 0000:01:00.0: [07]: 0x00036000   1   1   1   1
[  127.478249] ath10k_pci 0000:01:00.0: failed to create WMI vdev 0: -108
[  127.566887] ieee80211 phy0: Hardware restart was requested
[ 128.886806] ath10k_pci 0000:01:00.0: device successfully recovered

Looks like a deauth crashes the Wi-Fi driver, strange? The same thing starts up again at line 871. Then at line 1131, something interesting happens. The module fails to remove a "key" from the device, and the firmware crashes:

[ 5233.803936] wlp1s0: deauthenticating from f4:f2:6d:b3:74:c3 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 5237.017118] ath10k_pci 0000:01:00.0: failed to install key for vdev 0 peer f4:f2:6d:b3:74:c3: -110
[ 5237.017124] wlp1s0: failed to remove key (0, f4:f2:6d:b3:74:c3) from hardware (-110)
[ 5237.021842] ath10k_pci 0000:01:00.0: firmware crashed! (guid e140cdc0-e185-4932-98ff-bb6206e23d65)
[ 5237.021857] ath10k_pci 0000:01:00.0: qca6174 hw2.1 target 0x05010000 chip_id 0x003405ff sub 144d:4125
[ 5237.021861] ath10k_pci 0000:01:00.0: kconfig debug 0 debugfs 1 tracing 0 dfs 0 testmode 0
[ 5237.022980] ath10k_pci 0000:01:00.0: firmware ver SW_RM.1.1.1-00157-QCARMSWPZ-1 api 5 features ignore-otp,no-4addr-pad crc32 10bf8e08
[ 5237.023572] ath10k_pci 0000:01:00.0: board_file api 2 bmi_id N/A crc32 ae2e275a
[ 5237.023577] ath10k_pci 0000:01:00.0: htt-ver 3.1 wmi-op 4 htt-op 3 cal otp max-sta 32 raw 0 hwcrypto 1
[ 5237.025838] ath10k_pci 0000:01:00.0: firmware register dump:
[ 5237.025846] ath10k_pci 0000:01:00.0: [00]: 0x05010000 0x00000000 0x0092E4DC 0xE4E5889E
[ 5237.025851] ath10k_pci 0000:01:00.0: [04]: 0x0092E4DC 0x00060130 0x00000018 0x0041A760
[ 5237.025855] ath10k_pci 0000:01:00.0: [08]: 0xE4E5888A 0x00400000 0x00000000 0x000A5C88
[ 5237.025860] ath10k_pci 0000:01:00.0: [12]: 0x00000009 0x00000000 0x0096C09C 0x0096C0A7
[ 5237.025864] ath10k_pci 0000:01:00.0: [16]: 0x0096BDBC 0x009287BD 0x00000000 0x009287BD
[ 5237.025868] ath10k_pci 0000:01:00.0: [20]: 0x4092E4DC 0x0041A710 0x00000000 0x0F000000
[ 5237.025873] ath10k_pci 0000:01:00.0: [24]: 0x809432A7 0x0041A770 0x0040D400 0xC092E4DC
[ 5237.025877] ath10k_pci 0000:01:00.0: [28]: 0x80942BC4 0x0041A790 0xE4E5888A 0x00400000
[ 5237.025881] ath10k_pci 0000:01:00.0: [32]: 0x80947BA7 0x0041A7B0 0x004050A8 0x0040E074
[ 5237.025885] ath10k_pci 0000:01:00.0: [36]: 0x809BDECC 0x0041A7D0 0x004050A8 0x0040E074
[ 5237.025889] ath10k_pci 0000:01:00.0: [40]: 0x8099638C 0x0041A7F0 0x004050A8 0x00000000
[ 5237.025894] ath10k_pci 0000:01:00.0: [44]: 0x80992076 0x0041A810 0x0044FD68 0x0046FFE8
[ 5237.025898] ath10k_pci 0000:01:00.0: [48]: 0x80996BD3 0x0041A830 0x0044FD68 0x00000000
[ 5237.025902] ath10k_pci 0000:01:00.0: [52]: 0x800B4405 0x0041A850 0x00422318 0x00005002
[ 5237.025906] ath10k_pci 0000:01:00.0: [56]: 0x809A6C34 0x0041A8E0 0x0042932C 0x0042CA44
[ 5237.025910] ath10k_pci 0000:01:00.0: Copy Engine register dump:
[ 5237.025922] ath10k_pci 0000:01:00.0: [00]: 0x00034400   1   1   3   3
[ 5237.025933] ath10k_pci 0000:01:00.0: [01]: 0x00034800   2   2 389 390
[ 5237.025944] ath10k_pci 0000:01:00.0: [02]: 0x00034c00  24  24  23  24
[ 5237.025955] ath10k_pci 0000:01:00.0: [03]: 0x00035000  31  31   0  31
[ 5237.025967] ath10k_pci 0000:01:00.0: [04]: 0x00035400 2509 2509  40 232
[ 5237.025978] ath10k_pci 0000:01:00.0: [05]: 0x00035800   0   0   0   0
[ 5237.025989] ath10k_pci 0000:01:00.0: [06]: 0x00035c00  16  16  16  16
[ 5237.025999] ath10k_pci 0000:01:00.0: [07]: 0x00036000   1   1   1   1
[ 5237.026096] ath10k_pci 0000:01:00.0: failed to create WMI vdev 0: -108
[ 5237.098331] PM: suspend entry (deep)
[ 5237.098334] PM: Syncing filesystems ... 
[ 5237.108325] ieee80211 phy0: Hardware restart was requested
[ 5237.117303] done.
[ 5237.377059] Freezing user space processes ... 
[ 5238.425305] ath10k_pci 0000:01:00.0: device successfully recovered

I think this was the time when I used the power button to suspend the system, you can see the last few lines mentioning freezing user space processes. Then at line 1259, it fails to "install" the "key":

[ 9622.942776] wlp1s0: deauthenticating from f4:f2:6d:b3:74:c3 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 9625.966637] ath10k_pci 0000:01:00.0: failed to install key for vdev 0 peer f4:f2:6d:b3:74:c3: -110
[ 9625.966642] wlp1s0: failed to remove key (0, f4:f2:6d:b3:74:c3) from hardware (-110)
[ 9628.096713] PM: suspend entry (deep)
[ 9628.096716] PM: Syncing filesystems ... done.
[ 9628.552189] Freezing user space processes ... 
[ 9629.166617] ath10k_pci 0000:01:00.0: failed to create WMI vdev 0: -11
[ 9629.170280] (elapsed 0.618 seconds) done.
[ 9629.170289] OOM killer disabled.
[ 9629.170291] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
[ 9629.172016] Suspending console(s) (use no_console_suspend to debug)
[ 9629.176194] sd 1:0:0:0: [sdb] Synchronizing SCSI cache
[ 9629.176309] sd 1:0:0:0: [sdb] Stopping disk
[ 9629.176343] sd 0:0:0:0: [sda] Synchronizing SCSI cache
[ 9629.179052] sd 0:0:0:0: [sda] Stopping disk
[ 9632.366616] ath10k_pci 0000:01:00.0: failed to delete WMI vdev 1: -11
[ 9638.766580] ath10k_pci 0000:01:00.0: could not suspend target (-11)

Then from line 1323 onwards, it keeps saying the "line" isn't ready. This was the part where I got the "Not connected" message from GNOME (but otherwise it scanned some networks near me):

[ 9640.903257] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9641.112982] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
[ 9641.116208] ata2.00: configured for UDMA/100
[ 9642.223000] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9642.288293] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9647.190131] wlp1s0: authenticate with f4:f2:6d:b3:74:c3
[ 9647.235121] wlp1s0: send auth to f4:f2:6d:b3:74:c3 (try 1/3)
[ 9647.236844] wlp1s0: authenticated
[ 9647.242928] wlp1s0: associate with f4:f2:6d:b3:74:c3 (try 1/3)
[ 9647.247008] wlp1s0: RX AssocResp from f4:f2:6d:b3:74:c3 (capab=0x411 status=0 aid=3)
[ 9647.249624] wlp1s0: associated
[ 9647.249697] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 9664.042968] r8169 0000:02:00.0 enp2s0: link up
[ 9664.042982] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
[ 9673.286352] wlp1s0: deauthenticating from f4:f2:6d:b3:74:c3 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 9679.516174] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 9682.249055] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9682.323033] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9684.708075] r8169 0000:02:00.0 enp2s0: link down
[ 9687.183384] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9692.074239] wlp1s0: authenticate with f4:f2:6d:b3:74:c3
[ 9692.116930] wlp1s0: send auth to f4:f2:6d:b3:74:c3 (try 1/3)
[ 9692.118508] wlp1s0: authenticated
[ 9692.119609] wlp1s0: associate with f4:f2:6d:b3:74:c3 (try 1/3)
[ 9692.128576] wlp1s0: RX AssocResp from f4:f2:6d:b3:74:c3 (capab=0x411 status=0 aid=3)
[ 9692.131096] wlp1s0: associated
[ 9692.131135] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready
[ 9889.313005] wlp1s0: deauthenticating from f4:f2:6d:b3:74:c3 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 9895.620414] ath10k_pci 0000:01:00.0: could not suspend target (-11)
[ 9913.842709] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9913.909246] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9918.767516] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9921.191241] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9921.199246] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9921.210338] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9931.099637] wlp1s0: authenticate with f4:f2:6d:b3:74:c3
[ 9931.141925] wlp1s0: send auth to f4:f2:6d:b3:74:c3 (try 1/3)
[ 9931.144097] wlp1s0: authenticated
[ 9936.142510] wlp1s0: aborting authentication with f4:f2:6d:b3:74:c3 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 9941.082879] wlp1s0: authenticate with f4:f2:6d:b3:74:c3
[ 9941.124096] wlp1s0: send auth to f4:f2:6d:b3:74:c3 (try 1/3)
[ 9941.127288] wlp1s0: authenticated
[ 9946.124671] wlp1s0: aborting authentication with f4:f2:6d:b3:74:c3 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 9946.252906] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9946.266301] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9951.160690] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9953.287861] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9953.297742] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9953.310544] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9963.207492] wlp1s0: authenticate with f4:f2:6d:b3:74:c3
[ 9963.249265] wlp1s0: send auth to f4:f2:6d:b3:74:c3 (try 1/3)
[ 9963.251177] wlp1s0: authenticated
[ 9974.090655] wlp1s0: authenticate with f4:f2:6d:b3:74:c3
[ 9974.132056] wlp1s0: send auth to f4:f2:6d:b3:74:c3 (try 1/3)
[ 9974.137113] wlp1s0: authenticated
[ 9978.248943] wlp1s0: aborting authentication with f4:f2:6d:b3:74:c3 by local choice (Reason: 3=DEAUTH_LEAVING)
[ 9978.256461] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9978.261429] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9983.182360] IPv6: ADDRCONF(NETDEV_UP): wlp1s0: link is not ready
[ 9988.074301] wlp1s0: authenticate with f4:f2:6d:b3:74:c3
[ 9988.116310] wlp1s0: send auth to f4:f2:6d:b3:74:c3 (try 1/3)
[ 9988.117896] wlp1s0: authenticated
[ 9988.118955] wlp1s0: associate with f4:f2:6d:b3:74:c3 (try 1/3)
[ 9988.123100] wlp1s0: RX AssocResp from f4:f2:6d:b3:74:c3 (capab=0x411 status=0 aid=3)
[ 9988.126525] wlp1s0: associated
[ 9988.126568] IPv6: ADDRCONF(NETDEV_CHANGE): wlp1s0: link becomes ready

That's the end of the file, and at that point I was able to use the Internet normally. I assume this was when the firmware was "recovering" from the crash.

I am presuming the firmware concerned here is really, really messy. Or either, it's actually the chip design and they were "designed" to segfault or whatever and crash, and the Windows drivers just cover it up very well by power cycling the chips and forcing the "keys" or whatever out of them.

Going to need to find more clues to this puzzle... Ugh I hate Wi-Fi so much...

Last edited by ideaman924 (2017-12-24 18:05:17)

Offline

#4 2017-12-25 07:45:36

ideaman924
Member
Registered: 2017-12-24
Posts: 3

Re: Laptop not going to sleep, Wi-Fi problems and more

Hey, @ooo, I just managed to reproduce the issue. Finally!

So the permanent firmware crash wasn't triggered by manual suspends - i.e. me shutting the laptop lid or pressing the power button. The firmware crashed, permanently, if I kept the computer on for an extended period of time *without* touching the mouse or keyboard. The screen dimmed, but when it should've suspended itself five minutes later, it didn't and the power indicator light still remained on.

When I touched the mouse, the computer resumed from the dimmed mode, but I noticed the Wi-Fi indicator went to a transparent state, and the text that would normally show next to the icon, like "Connected to WiFiName" or "Not connected" did not show.

Attempting to turn off the Wi-Fi did not work. Going to System Settings, the Wi-Fi menu showed "Sorry, there was a problem. NetworkManager needs to be running..." something along these lines.

These are the crash logs. https://gist.github.com/anonymous/7e840 … f6026e62cc

Notice dmesg, line 1519. I think that's when the firmware crashes, permanently, and never comes back on. Interestingly, it's the same "cannot remove key from device" error.

Thoughts? This is driving me up the wazoo.

EDIT: Forgot to mention some important things. 1. Running "ps aux | grep NetworkManager" showed a hung process running under root. Using "kill -9 {PID}" resulted in a frozen Terminal, with the same (^C) escape sequences showing on the Terminal but otherwise not doing anything. Running "sudo reboot" caused the same behavior (what in the world) and running "reboot" finally dropped me to a shell. And then it started running the stop jobs, so I pressed Ctrl-Alt-Del seven times, and the stop jobs terminated running. The computer should've rebooted then, but it didn't with the "watchdog didn't stop" message, and just hung there until I force rebooted it. I'm out of hints... dunno what's going on...

Last edited by ideaman924 (2017-12-25 07:48:00)

Offline

#5 2017-12-25 09:08:09

ooo
Member
Registered: 2013-04-10
Posts: 1,479

Re: Laptop not going to sleep, Wi-Fi problems and more

Again, If you search for ath10k on these forums, there appears to be plenty of threads about similar issues. I even linked one on my previous message. There are also many of possible solutions. According to this thread, the issue is caused by bug in ath10k firware and has been reported to developers.

I'm quite sure all your other issues are caused by the ath10k bug. If you resolve the wi-fi issue and other problems persist after that, open a new thread.

Also, I know nothing about this issue, other than what I gathered from 5min of searching. Please put some effort to search for solution yourself. I can't really help you much further than this, unless you need help applying some specific possible fix or workaround.

Offline

Board footer

Powered by FluxBB