From: James Cameron <quozl@laptop.org>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-wireless@vger.kernel.org, Ping-Ke Shih <pkshih@realtek.com>,
Kalle Valo <kvalo@codeaurora.org>
Subject: Re: rtl8821ae keep alive not set, connection lost
Date: Wed, 20 Sep 2017 19:36:33 +1000 [thread overview]
Message-ID: <20170920093633.GO9946@us.netrek.org> (raw)
In-Reply-To: <20170919094204.GR26927@us.netrek.org>
On Tue, Sep 19, 2017 at 07:42:04PM +1000, James Cameron wrote:
> On Thu, Sep 14, 2017 at 07:27:39PM +1000, James Cameron wrote:
> > On Wed, Sep 13, 2017 at 07:39:35PM -0500, Larry Finger wrote:
> > > On 09/13/2017 04:46 PM, James Cameron wrote:
> > > >
> > > >I'll give it some more testing and let you know, but it seems as
> > > >capable of keeping a connection as 4.13 plus my earlier revert.
> > > >
> >
> > Testing went well; removing the call to enable ASPM was as good as
> > changing the DBI read back to 16-bit width.
> >
> > > The change I sent earlier should be as good as reverting the change
> > > to write_byte in your reversion.
> >
> > Yes, that would be the hope.
> >
> > But with the 16-bit DBI read, the register REG_DBI_CTRL+0 is being
> > read as well, in the first read in _rtl8821ae_enable_aspm_back_door,
> > so perhaps reading that register has an unexpected side-effect.
> >
>
> I've ruled that out after testing for several days different kernels
> based on v4.13;
>
> - add an rtl_read_byte of REG_DBI_CTRL+0 in rtl8821ae_hw_init just
> after the call to enable_aspm; does not solve problem,
>
> - add an rtl_read_byte of REG_DBI_CTRL+0 at the start of
> _rtl8821ae_check_pcie_dma_hang; does not solve problem,
When the problem occurs, register 0x350 bit 25 is set, for which a
comment in _rtl8821ae_check_pcie_dma_hang says means there is an RX
hang.
So perhaps driver should call _rtl8821ae_check_pcie_dma_hang
and _rtl8821ae_reset_pcie_interface_dma.
Any ideas where to do this?
> [...]
--
James Cameron
http://quozl.netrek.org/
next prev parent reply other threads:[~2017-09-20 9:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-12 22:09 rtl8821ae keep alive not set, connection lost James Cameron
2017-09-13 15:01 ` Larry Finger
2017-09-13 21:46 ` James Cameron
2017-09-14 0:39 ` Larry Finger
2017-09-14 9:27 ` James Cameron
2017-09-19 9:42 ` James Cameron
2017-09-20 9:36 ` James Cameron [this message]
2017-09-20 21:48 ` Larry Finger
2017-09-20 23:22 ` James Cameron
2017-09-21 8:07 ` James Cameron
2017-09-21 14:40 ` Larry Finger
2017-09-22 5:35 ` James Cameron
2018-01-31 17:06 ` Larry Finger
2018-02-01 6:22 ` James Cameron
2018-02-02 7:50 ` Pkshih
2018-02-02 20:13 ` Larry Finger
2018-02-03 4:45 ` Pkshih
2018-02-04 18:18 ` Larry Finger
2018-02-02 20:27 ` Larry Finger
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=20170920093633.GO9946@us.netrek.org \
--to=quozl@laptop.org \
--cc=Larry.Finger@lwfinger.net \
--cc=kvalo@codeaurora.org \
--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).