You are not logged in.
Pages: 1
For the past few days, my wifi has repeatedly been disconnecting every few minutes, then reconnecting within a few seconds.
The output of dmesg -H
[Dec31 15:57] wlp0s18f2u1: authenticate with 80:2a:a8:1a:f7:6e
[ +0.258399] wlp0s18f2u1: send auth to 80:2a:a8:1a:f7:6e (try 1/3)
[ +0.008343] wlp0s18f2u1: authenticated
[ +0.002578] wlp0s18f2u1: associate with 80:2a:a8:1a:f7:6e (try 1/3)
[ +0.004516] wlp0s18f2u1: RX AssocResp from 80:2a:a8:1a:f7:6e (capab=0x431 status=0 aid=2)
[ +0.006676] wlp0s18f2u1: associatedjournalctl -x
Dec 31 15:57:37 ozymandias dhcpcd[583]: wlp0s18f2u1: carrier lost
Dec 31 15:57:37 ozymandias dhcpcd[583]: wlp0s18f2u1: deleting default route via 192.168.1.1
Dec 31 15:57:37 ozymandias dhcpcd[583]: wlp0s18f2u1: deleting route to 192.168.1.0/24
Dec 31 15:57:37 ozymandias avahi-daemon[335]: Withdrawing address record for 192.168.1.19 on wlp0s18f2u1.
Dec 31 15:57:37 ozymandias avahi-daemon[335]: Leaving mDNS multicast group on interface wlp0s18f2u1.IPv4 with address 192.168.1.19.
Dec 31 15:57:38 ozymandias avahi-daemon[335]: Interface wlp0s18f2u1.IPv4 no longer relevant for mDNS.
Dec 31 15:57:39 ozymandias kernel: wlp0s18f2u1: authenticate with 80:2a:a8:1a:f7:6e
Dec 31 15:57:39 ozymandias kernel: wlp0s18f2u1: send auth to 80:2a:a8:1a:f7:6e (try 1/3)
Dec 31 15:57:39 ozymandias kernel: wlp0s18f2u1: authenticated
Dec 31 15:57:39 ozymandias kernel: wlp0s18f2u1: associate with 80:2a:a8:1a:f7:6e (try 1/3)
Dec 31 15:57:39 ozymandias kernel: wlp0s18f2u1: RX AssocResp from 80:2a:a8:1a:f7:6e (capab=0x431 status=0 aid=2)
Dec 31 15:57:39 ozymandias kernel: wlp0s18f2u1: associated
Dec 31 15:57:40 ozymandias dhcpcd[583]: wlp0s18f2u1: carrier acquired
Dec 31 15:57:40 ozymandias dhcpcd[583]: wlp0s18f2u1: IAID 11:63:25:63
Dec 31 15:57:40 ozymandias dhcpcd[583]: wlp0s18f2u1: rebinding lease of 192.168.1.19
Dec 31 15:57:40 ozymandias dhcpcd[583]: wlp0s18f2u1: probing address 192.168.1.19/24
Dec 31 15:57:46 ozymandias dhcpcd[583]: wlp0s18f2u1: leased 192.168.1.19 for 86400 seconds
Dec 31 15:57:46 ozymandias avahi-daemon[335]: Joining mDNS multicast group on interface wlp0s18f2u1.IPv4 with address 192.168.1.19.
Dec 31 15:57:46 ozymandias avahi-daemon[335]: New relevant interface wlp0s18f2u1.IPv4 for mDNS.
Dec 31 15:57:46 ozymandias dhcpcd[583]: wlp0s18f2u1: adding route to 192.168.1.0/24
Dec 31 15:57:46 ozymandias avahi-daemon[335]: Registering new address record for 192.168.1.19 on wlp0s18f2u1.IPv4.
Dec 31 15:57:46 ozymandias dhcpcd[583]: wlp0s18f2u1: adding default route via 192.168.1.1In both cases, the same output repeats every time the connection is lost.
Offline
Please paste the output of `systemctl list-unit-files --state=enabled` and full details of your card and driver.
Offline
systemctl list-unit-files --state=enabled
UNIT FILE STATE
org.cups.cupsd.path enabled
autovt@.service enabled
avahi-daemon.service enabled
dbus-org.freedesktop.Avahi.service enabled
display-manager.service enabled
getty@.service enabled
lightdm.service enabled
netctl@home.service enabled
org.cups.cupsd.service enabled
avahi-daemon.socket enabled
org.cups.cupsd.socket enabled
remote-fs.target enabledlsusb -v
Bus 001 Device 002: ID 0cf3:7015 Qualcomm Atheros Communications TP-Link TL-WN821N v3 / TL-WN822N v2 802.11n [Atheros AR7010+AR9287]
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
idVendor 0x0cf3 Qualcomm Atheros Communications
idProduct 0x7015 TP-Link TL-WN821N v3 / TL-WN822N v2 802.11n [Atheros AR7010+AR9287]
bcdDevice 2.02
iManufacturer 16 ATHEROS
iProduct 32 USB WLAN
iSerial 48 12345
bNumConfigurations 1
Configuration Descriptor:
bLength 9
bDescriptorType 2
wTotalLength 60
bNumInterfaces 1
bConfigurationValue 1
iConfiguration 0
bmAttributes 0x80
(Bus Powered)
MaxPower 500mA
Interface Descriptor:
bLength 9
bDescriptorType 4
bInterfaceNumber 0
bAlternateSetting 0
bNumEndpoints 6
bInterfaceClass 255 Vendor Specific Class
bInterfaceSubClass 0
bInterfaceProtocol 0
iInterface 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x01 EP 1 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x82 EP 2 IN
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x83 EP 3 IN
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x04 EP 4 OUT
bmAttributes 3
Transfer Type Interrupt
Synch Type None
Usage Type Data
wMaxPacketSize 0x0040 1x 64 bytes
bInterval 1
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x05 EP 5 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Endpoint Descriptor:
bLength 7
bDescriptorType 5
bEndpointAddress 0x06 EP 6 OUT
bmAttributes 2
Transfer Type Bulk
Synch Type None
Usage Type Data
wMaxPacketSize 0x0200 1x 512 bytes
bInterval 0
Device Qualifier (for other device speed):
bLength 10
bDescriptorType 6
bcdUSB 2.00
bDeviceClass 255 Vendor Specific Class
bDeviceSubClass 255 Vendor Specific Subclass
bDeviceProtocol 255 Vendor Specific Protocol
bMaxPacketSize0 64
bNumConfigurations 1
can't get debug descriptor: Resource temporarily unavailable
Device Status: 0x0000
(Bus Powered)lshw -C Network
*-network
description: Wireless interface
physical id: 1
bus info: usb@1:1
logical name: wlp0s18f2u1
serial: f8:d1:11:63:25:63
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=ath9k_htc driverversion=4.14.9-1-ARCH firmware=1.4 ip=192.168.1.19 link=yes multicast=yes wireless=IEEE 802.11Offline
How frequent are those losses (I mean, are the timeframes between the losses pretty much eqally long?)
Tried "ps_enable=0"?
Do you have TLP, laptop-mode-tools or powertop installed or just enabled usb autosuspend directly?
Offline
Anywhere from a few seconds to a few minutes between losses, which goes on for about an hour before it begins working regularly again for a day or so.
Power saving is disabled
$ iw dev wlp0s18f2u1 get power_save
Power save: offI do not have any of those installed and have never enabled usb autosuspend.
Last edited by atloomis (2017-12-31 23:11:16)
Offline
Pages: 1