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: Fri, 22 Sep 2017 15:35:58 +1000 [thread overview]
Message-ID: <20170922053558.GK12195@us.netrek.org> (raw)
In-Reply-To: <abff13d3-4115-4935-6546-b0fd8c860124@lwfinger.net>
On Thu, Sep 21, 2017 at 09:40:14AM -0500, Larry Finger wrote:
> On 09/21/2017 03:07 AM, James Cameron wrote:
> >My test kernel "-qb" was write_readback = false in sw.c, with 8-bit
> >read of REG_DBI_RDATA, and has been stable for four hours. I'll
> >focus on some more testing of this one. It is a surprise.
> >
> >http://dev.laptop.org/~quozl/z/1dutXk.txt (dmesg)
> >
> >Observe how REG_DBI_FLAG+0 is briefly seen as 1, which doesn't
> >happen with write_readback = true.
>
> Again, thanks for your efforts.
>
> At this point, my system has been up over 17 hours without a single
> drop. As a result, I will leave the reversion of commit 40b368af4b75
> in place. It seems safer than turning off write_readback. After we
> get more testing, that could still be an option.
Thanks for the reversion commit, I'll point others to it.
My apologies for sloppy work, the test kernel features got swapped!
"-qb" above was with write_readback off, and 16-bit read of
REG_DBI_RDATA, not 8-bit. Verified with objdump. It has run for 24
hours without a drop.
So at conclusion;
- the 16-bit read is good with or without write_readback.
- the 8-bit read is bad with or without write_readback, and tends to
lose connection much quicker without write_readback.
Been a pleasure working with you. Back to lurk mode.
--
James Cameron
http://quozl.netrek.org/
next prev parent reply other threads:[~2017-09-22 5: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
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 [this message]
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=20170922053558.GK12195@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).