[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87h7z4r9p5.fsf@kamboji.qca.qualcomm.com>
Date: Wed, 04 Mar 2020 07:05:42 +0200
From: Kalle Valo <kvalo@...eaurora.org>
To: Randy Dunlap <rdunlap@...radead.org>
Cc: "Mancini\, Jason" <Jason.Mancini@....com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev\@vger.kernel.org" <netdev@...r.kernel.org>,
Yan-Hsuan Chuang <yhchuang@...ltek.com>,
linux-wireless@...r.kernel.org
Subject: Re: v5.5-rc1 and beyond insta-kills some Comcast wifi routers
Randy Dunlap <rdunlap@...radead.org> writes:
> [add netdev mailing list + 2 patch signers]
Adding also linux-wireless. It's always best to send questions about any
wireless issues to linux-wireless
> On 3/3/20 7:34 PM, Mancini, Jason wrote:
>> [I can't seem to access the linux-net ml per kernel.org faq, apology
>> in advance.]
>>
>> This change, which I think first appeared for v5.5-rc1, basically
>> within seconds, knocks out our [apparently buggy] Comcast wifi for
>> about 2-3 minutes. Is there a boot option (or similar) where I can
>> achieve prior kernel behavior? Otherwise I am stuck on kernel 5.4
>> (or Win10) it seems, or forever compiling custom kernels for my
>> choice of distribution [as I don't have physical access to the router
>> in question.]
>> Thanks!
>> Jason
>>
>> ================
>>
>> 127eef1d46f80056fe9f18406c6eab38778d8a06 is the first bad commit
>> commit 127eef1d46f80056fe9f18406c6eab38778d8a06
>> Author: Yan-Hsuan Chuang <yhchuang@...ltek.com>
>> Date: Wed Oct 2 14:35:23 2019 +0800
Can you try if this fixes it:
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/wireless-drivers-next.git/commit/?id=74c3d72cc13401f9eb3e3c712855e9f8f2d2682b
--
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Powered by blists - more mailing lists