Skip to content

Instantly share code, notes, and snippets.

@dsprenkels
Created February 27, 2018 13:07
Show Gist options
  • Star 1 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save dsprenkels/eb1c7095385fe16ee9b128ab0834be21 to your computer and use it in GitHub Desktop.
Save dsprenkels/eb1c7095385fe16ee9b128ab0834be21 to your computer and use it in GitHub Desktop.
Feb 27 13:40:26 aang kernel: ath10k_pci 0000:02:00.0: Unknown eventid: 118809
Feb 27 13:40:26 aang kernel: ath10k_pci 0000:02:00.0: Unknown eventid: 90118
Feb 27 13:40:26 aang kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
Feb 27 13:40:26 aang NetworkManager[583]: <info> [1519735226.8008] device (wlp2s0): set-hw-addr: set MAC address to 82:2E:08:61:F6:7F (scanning)
Feb 27 13:40:28 aang kernel: ath10k_pci 0000:02:00.0: failed to receive control response completion, polling..
Feb 27 13:40:28 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000001 at 0x00034430: -110
Feb 27 13:40:28 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x00034444: -110
Feb 27 13:40:28 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000001e at 0x00034430: -110
Feb 27 13:40:28 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000001 at 0x00034830: -110
Feb 27 13:40:28 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000001 at 0x00035430: -110
Feb 27 13:40:28 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x00035444: -110
Feb 27 13:40:28 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0000001e at 0x00035430: -110
Feb 27 13:40:30 aang kernel: ath10k_pci 0000:02:00.0: ctl_resp never came in (-110)
Feb 27 13:40:30 aang kernel: ath10k_pci 0000:02:00.0: failed to connect to HTC: -110
Feb 27 13:40:31 aang kernel: ath10k_warn: 59 callbacks suppressed
Feb 27 13:40:31 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x00036034: -110
Feb 27 13:40:31 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0xfffff81f at 0x00036034: -110
Feb 27 13:40:31 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003602c: -110
Feb 27 13:40:31 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0xffffffe1 at 0x0003602c: -110
Feb 27 13:40:31 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x00000000 at 0x0003a008: -110
Feb 27 13:40:31 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0x0007fc00 at 0x0003a014: -110
Feb 27 13:40:31 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a008: -110
Feb 27 13:40:31 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a000: -110
Feb 27 13:40:31 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for write32 of 0xfffff7ff at 0x0003a000: -110
Feb 27 13:40:31 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x00000800: -110
Feb 27 13:40:36 aang kernel: ath10k_warn: 143 callbacks suppressed
Feb 27 13:40:36 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:36 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:36 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:36 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:36 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:36 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:36 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:36 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:36 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:37 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:38 aang kernel: ath10k_pci 0000:02:00.0: failed to read device register, device is gone
Feb 27 13:40:41 aang kernel: ath10k_warn: 143 callbacks suppressed
Feb 27 13:40:41 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:41 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:41 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:41 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:41 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:41 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:41 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:41 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:41 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:42 aang kernel: ath10k_pci 0000:02:00.0: failed to wake target for read32 at 0x0003a028: -110
Feb 27 13:40:44 aang kernel: ath10k_pci 0000:02:00.0: failed to read device register, device is gone
Feb 27 13:40:45 aang NetworkManager[583]: <warn> [1519735245.7375] platform-linux: do-change-link[2]: failure changing link: failure 110 (Connection timed out)
Feb 27 13:40:45 aang kernel: ath10k_pci 0000:02:00.0: Could not init core: -110
Feb 27 13:40:45 aang NetworkManager[583]: <info> [1519735245.7382] manager: NetworkManager state is now DISCONNECTED
@dsprenkels
Copy link
Author

A friend of mine also seems to have problems still, and he has a recent linux version afaik.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment