Arch Linux

twol

Member

Registered: 2020-06-06

Posts: 2

Laptop Troubleshooting advice

I've been happily running arch on multiple machines for the last year or so and recently I've been in the process of converting what used to be my main laptop before I ran linux.

The laptop is an Acer Aspire R5-571t and I have several problems

The first problem that I want to tackle is the network card which is apparently the infamous Qualcomm Atheros QCA6174

the problem being that it will work fine for a random amount of time and then, usually in the middle of moderate network usage, all the sudden it stops, spits out a bunch of "... ath10k_pci 0000:01:00.0: failed to wake target for write32 ..." and when I try to restart my computer it cannot kill the network process and I have to force the power off.

I've read a lot about people with similar issues some saying it is an issue with networkmanager's power managment but I use systemd-networkd and iwd, Ive also tried using iwd alone and networkmanager all with the same results. Some found their solution in manually installing the firmware from the kvalo github, I did not, infact I think the wifi would stop working even quicker when I did that. The only other thing I think I've seen suggested is updating the bios, something which I don't understand how it effects comunication with the wifi card, so if it does lmk.

By the looks of the other answers on all of the forums I have browsed it I'm not sure if anyone will just happen to have the answer to the problem I am having. I'm not expecting to have this issue solved right away, so what I would like to know is if it's possible to revover from this issue more gracefully. When I try killing/restarting all the relevant sevices or running `sudo modprobe -r ath10k_pci && sudo modprobe ath10k_pci` the command hangs. what should I try next?

Last edited by twol (2021-01-08 17:43:47)

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 25,353

Re: Laptop Troubleshooting advice

Have you tried using wpa_supplicant instead of iwd ? (Might be implied by the "tried to use networkmanager" but maybe you're set on using iwd and configured NM that way)

Can you post the actual messages you receive? Best would be the complete context of a

sudo journalctl -b

when the issue happens so we can check what the general state is.

FWIW, though this doesn't help you for now, I don't have any such issues (...anymore...) on my own Aspire V5 with the same chipset, so either there are wild variations with the same designations around or it's something in the surrounding stack.

twol

Member

Registered: 2020-06-06

Posts: 2

Re: Laptop Troubleshooting advice

ok, well... haha this is kind of funny. I'll admit this laptop has taken a beating or two in its day and may or may not have some damage to a structural mount point for one of the screws.

I was in the middlle of watching three videos at the same time to see if i could trigger the issue while running

journalctl -f

I had to get up for a second and I had headphones in so I picked my laptop up from the corner with the loose screw, and all the sudden this pops up

Jan 08 13:09:59 lappy2 kernel: pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:00:1d.0
Jan 08 13:09:59 lappy2 kernel: pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jan 08 13:09:59 lappy2 kernel: pcieport 0000:00:1d.0:   device [8086:9d1b] error status/mask=00000001/00002000
Jan 08 13:09:59 lappy2 kernel: pcieport 0000:00:1d.0:    [ 0] RxErr                  (First)
Jan 08 13:09:59 lappy2 kernel: pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:00:1d.0
Jan 08 13:09:59 lappy2 kernel: pcieport 0000:00:1d.0: AER: can't find device of ID00e8
Jan 08 13:10:01 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x00001439 at 0x0003543c: -110
Jan 08 13:10:01 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x0000143b at 0x0003543c: -110
Jan 08 13:10:02 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x0000143d at 0x0003543c: -110
Jan 08 13:10:02 lappy2 kernel: pcieport 0000:00:1d.0: AER: Multiple Corrected error received: 0000:00:1d.0
Jan 08 13:10:02 lappy2 kernel: pcieport 0000:00:1d.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID)
Jan 08 13:10:02 lappy2 kernel: pcieport 0000:00:1d.0:   device [8086:9d1b] error status/mask=00000001/00002000
Jan 08 13:10:02 lappy2 kernel: pcieport 0000:00:1d.0:    [ 0] RxErr                  (First)
Jan 08 13:10:09 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x0000143f at 0x0003543c: -110
Jan 08 13:10:10 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x00001441 at 0x0003543c: -110
Jan 08 13:10:10 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x00001443 at 0x0003543c: -110
Jan 08 13:10:10 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x00001445 at 0x0003543c: -110
Jan 08 13:10:10 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x00001447 at 0x0003543c: -110
Jan 08 13:10:10 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x00001449 at 0x0003543c: -110
Jan 08 13:10:10 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x0000144b at 0x0003543c: -110
Jan 08 13:10:10 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x0000144d at 0x0003543c: -110
Jan 08 13:10:10 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x0000144f at 0x0003543c: -110
Jan 08 13:10:10 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x00001451 at 0x0003543c: -110
Jan 08 13:10:14 lappy2 kernel: ath10k_warn: 13 callbacks suppressed
Jan 08 13:10:14 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x0000146d at 0x0003543c: -110
Jan 08 13:10:15 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x0000146f at 0x0003543c: -110
Jan 08 13:10:15 lappy2 kernel: ath10k_pci 0000:01:00.0: failed to wake target for write32 of 0x00001471 at 0x0003543c: -110

Ive done a coulple tests and can confirm that physical stress is causing the problem.
at least I know what the cause might be now. whoops.

hopefully its nothing a little epoxy can't fix. now I just need to test whether this is also somehow the cause of my gpu randomly hanging while using krita or blender

Last edited by twol (2021-01-08 23:05:09)