linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mancini, Jason" <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 09:03:00 +0000	[thread overview]
Message-ID: <DM6PR12MB433132A38F2AA6A5946B75CBE5E50@DM6PR12MB4331.namprd12.prod.outlook.com> (raw)
In-Reply-To: <4bd036de86c94545af3e5d92f0920ac2@realtek.com>

[AMD Official Use Only - Internal Distribution Only]

I tested Kalle's patch.  Laptop connects via 5GHz band by default.  Comcast router still
crashed in a hurry.  I blocked (via NM.conf) the 5GHz mac of the router, and rebooted
the laptop. Checked that the router was using 2.4 for the laptop.  Still hung the router!

What I've done temporarily is change the unlimited return value from 0 to 4000.
Somewhere around 5325 the Comcast router gets cranky/weird, and at 5350 it is
resetting the wifi stack (without resetting the entire router).

So there's no boot time flag to turn the feature off currently?

Jason

  reply	other threads:[~2020-03-04  9:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-04  3:34 v5.5-rc1 and beyond insta-kills some Comcast wifi routers Mancini, Jason
2020-03-04  4:05 ` Randy Dunlap
2020-03-04  5:05   ` Kalle Valo
2020-03-04  5:16     ` Tony Chuang
2020-03-04  9:03       ` Mancini, Jason [this message]
2020-03-04 10:41         ` Tony Chuang
2020-03-05  7:06           ` Jason Mancini

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=DM6PR12MB433132A38F2AA6A5946B75CBE5E50@DM6PR12MB4331.namprd12.prod.outlook.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;
as well as URLs for NNTP newsgroup(s).