Bug 1321615 - Realtek RTL8821AE loses connection
Summary: Realtek RTL8821AE loses connection
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 23
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-28 15:45 UTC by Talha Khan
Modified: 2018-03-28 21:38 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-10-26 16:51:05 UTC
Type: Bug


Attachments (Terms of Use)

Description Talha Khan 2016-03-28 15:45:27 UTC
Description of problem:

Laptop with Realtek RTL8821AE WiFi loses connection quickly to gateway. Sometimes loses connection to WiFi network.

Version-Release number of selected component (if applicable):

4.4.6-300.fc23.x86_64

How reproducible:

Every time

Steps to Reproduce:
1. Connect to Wifi SSID
2. Wait a few minutes
3. Ping gateway


Actual results:

Cannot ping gateway or get message "sendmsg: no buffer space available"
Cannot access anywhere with wireless connection as a result

Expected results:

Can ping gateway and should be able to connect using wireless. No issues in Windows 10


Additional info:

Laptop: Asus A555DG

from lspci:

01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE 802.11ac PCIe Wireless Network Adapter

 uname -a
Linux viper 4.4.6-300.fc23.x86_64 #1 SMP Wed Mar 16 22:10:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    600    0        0 wlp1s0
192.168.1.0     0.0.0.0         255.255.255.0   U     600    0        0 wlp1s0

ifconfig -a
enp2s0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        ether 2c:56:dc:12:f2:36  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1  (Local Loopback)
        RX packets 961  bytes 84136 (82.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 961  bytes 84136 (82.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlp1s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.1.9  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 fe80::b2c0:90ff:fe0f:6bb  prefixlen 64  scopeid 0x20<link>
        ether b0:c0:90:0f:06:bb  txqueuelen 1000  (Ethernet)
        RX packets 54192  bytes 70330506 (67.0 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 24406  bytes 2786288 (2.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
ping: sendmsg: No buffer space available
^C
--- 192.168.1.1 ping statistics ---
19 packets transmitted, 0 received, 100% packet loss, time 37005ms

ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
From 192.168.1.9 icmp_seq=1 Destination Host Unreachable
From 192.168.1.9 icmp_seq=2 Destination Host Unreachable
From 192.168.1.9 icmp_seq=3 Destination Host Unreachable
From 192.168.1.9 icmp_seq=4 Destination Host Unreachable
From 192.168.1.9 icmp_seq=5 Destination Host Unreachable
From 192.168.1.9 icmp_seq=6 Destination Host Unreachable
From 192.168.1.9 icmp_seq=7 Destination Host Unreachable
From 192.168.1.9 icmp_seq=8 Destination Host Unreachable
From 192.168.1.9 icmp_seq=9 Destination Host Unreachable
From 192.168.1.9 icmp_seq=10 Destination Host Unreachable
From 192.168.1.9 icmp_seq=11 Destination Host Unreachable
From 192.168.1.9 icmp_seq=12 Destination Host Unreachable
From 192.168.1.9 icmp_seq=13 Destination Host Unreachable
^C
--- 192.168.1.1 ping statistics ---
14 packets transmitted, 0 received, +13 errors, 100% packet loss, time 13002ms
pipe 4

Comment 1 Talha Khan 2016-03-28 15:46:55 UTC
Please reassign to another component if incorrect. I am assuming the driver may be the cause.

Comment 2 Laura Abbott 2016-09-23 19:39:08 UTC
*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs.
 
Fedora 23 has now been rebased to 4.7.4-100.fc23.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.
 
If you have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25.
 
If you experience different issues, please open a new bug report for those.

Comment 3 Laura Abbott 2016-10-26 16:51:05 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 4 Talha Khan 2018-03-28 21:38:32 UTC
I don't seem to have be having this issue anymore so I will like to confirm the close of this ticket.


Note You need to log in before you can comment on or make changes to this bug.