public inbox for linux-wireless@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Mancini <Jason.Mancini@amd.com>
To: Tony Chuang <yhchuang@realtek.com>,
	Kalle Valo <kvalo@codeaurora.org>,
	Randy Dunlap <rdunlap@infradead.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: v5.5-rc1 and beyond insta-kills some Comcast wifi routers
Date: Wed, 4 Mar 2020 23:06:58 -0800	[thread overview]
Message-ID: <ed6e071d-00c0-fb4d-4bbe-1f3668a0c140@amd.com> (raw)
In-Reply-To: <c185b1f27e4a4b66941b50697dba006c@realtek.com>

On 3/4/20 2:41 AM, Tony Chuang wrote:
> Unfortunately, no, there's no flag to turn off this.
> But, from your experiments, if you applied that patch,
> ("rtw88: disable TX-AMSDU on 2.4G band") connect to AP on 2.4G, and still crash
> the Comcast AP, then it looks like it's not TX-AMSDU to be blamed.
>
> Assume the return value you mentioned is max_rc_amsdu_len, if you always
> return 1, it will just disable all of the AMSDU process.
> You can try it, and to see if sending AMSDU will crash the router or not.
>
> Yen-Hsuan

(Specifically, this Comcast router is "Arris TG1682G" firmware 10.1.27B.SIP.PC20.CT hardware version 9.0)

I re-tested tonight, here are the results, from *unpatched* kernels:

(1) 2.4G only w/5G disabled via router control panel: kernel 5.5/5.6 seemingly doesn't upset router.
(2) 5G only w/2.4G disabled via router control panel: kernel 5.5/5.6 definitely kill router wifi.
(3) 5G only w/2.4G disabled via router control panel: plus get_max_amsdu_len forced to return 1: kernel 5.6-rc4 seemingly doesn't upset router.

As you can see, the suggested patch isn't going to help result (2), and apparently isn't needed for (1).  And this router's 5G seems
allergic to amsdu per (3), so somehow amsdu is involved it seems.

Well, I'll just work around it with (3) custom kernels, or (1) leave the router in 2.4G mode.  But be aware that apparently there's at least
one common buggy wifi router that's going to puke on 5G + amsdu.

Jason


      reply	other threads:[~2020-03-05  7:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DM6PR12MB4331FD3C4EF86E6AF2B3EBC7E5E50@DM6PR12MB4331.namprd12.prod.outlook.com>
     [not found] ` <4e2a1fc1-4c14-733d-74e2-750ef1f81bf6@infradead.org>
2020-03-04  5:05   ` v5.5-rc1 and beyond insta-kills some Comcast wifi routers Kalle Valo
2020-03-04  5:16     ` Tony Chuang
2020-03-04  9:03       ` Mancini, Jason
2020-03-04 10:41         ` Tony Chuang
2020-03-05  7:06           ` Jason Mancini [this message]

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=ed6e071d-00c0-fb4d-4bbe-1f3668a0c140@amd.com \
    --to=jason.mancini@amd.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=yhchuang@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