From: Nik Nyby <nikolas@gnu.org>
To: Larry Finger <Larry.Finger@lwfinger.net>,
linux-wireless@vger.kernel.org, pkshih@realtek.com
Subject: Re: rtl8821ae dbi read question
Date: Sun, 5 Nov 2017 15:53:06 -0500 [thread overview]
Message-ID: <6155a30b-ca6d-e27d-701e-9e1876a982ff@gnu.org> (raw)
In-Reply-To: <695fe947-7b0d-ef4b-5e90-ff503df6a08b@lwfinger.net>
On 11/05/2017 11:50 AM, Larry Finger wrote:
>
> If you read the commit message for commit b8b8b16352cd, you will find
> that we do not understand why using a byte read causes failure, but
> reverting the change so that it is a word read made it function again.
> The "fix" was found by a user doing bisection, and verified on my
> system, where the RTL8821AE has stable connections. The transfer rates
> take wild swings, but the connection is not dropped.
>
> If you NIC behaves differently, then you will need to help us debug the
> problem. If you had a kernel that worked, then you might try bisection.
I just tested on kernels 4.12 and 4.13 - my connection gets dropped on
those kernels as well. Right now I'm using 4.14-rc7.
> If that is not possible, you might try various combinations of module
> parameters aspm, int_clear, and msi
Thanks for these suggestions. Disabling ASPM solves my connection
dropping issue! Previously, I was getting disconnected around 10 seconds
after starting "git clone" on a large git repository. Now, I haven't
seen the connection drop once.
I can help debug the issue. I'm using a Lenovo Ideapad 320-15ABR laptop.
Here's the lspci -vv info for my NIC:
01:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8821AE
802.11ac PCIe Wireless Network Adapter
Subsystem: Lenovo RTL8821AE 802.11ac PCIe Wireless Network Adapter
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx+
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Latency: 0, Cache Line Size: 32 bytes
Interrupt: pin A routed to IRQ 33
Region 0: I/O ports at 2000 [size=256]
Region 2: Memory at f0b00000 (64-bit, non-prefetchable) [size=16K]
Capabilities: <access denied>
Kernel driver in use: rtl8821ae
next prev parent reply other threads:[~2017-11-05 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-04 23:27 rtl8821ae dbi read question Nik Nyby
2017-11-05 16:50 ` Larry Finger
2017-11-05 20:53 ` Nik Nyby [this message]
2017-11-06 1:46 ` Larry Finger
2017-11-05 21:15 ` Nik Nyby
2017-11-05 21:29 ` James Cameron
2017-11-06 2:09 ` Larry Finger
2017-11-06 4:09 ` Nik Nyby
2017-11-06 13:52 ` Larry Finger
2017-11-19 0:39 ` Nik Nyby
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6155a30b-ca6d-e27d-701e-9e1876a982ff@gnu.org \
--to=nikolas@gnu.org \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pkshih@realtek.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).