From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from wp530.webpack.hosteurope.de (wp530.webpack.hosteurope.de [80.237.130.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 2DC1E2C96 for ; Mon, 8 Nov 2021 18:00:30 +0000 (UTC) Received: from ip4d173d4a.dynamic.kabel-deutschland.de ([77.23.61.74] helo=[192.168.66.200]); authenticated by wp530.webpack.hosteurope.de running ExIM with esmtpsa (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) id 1mk8wP-0000qL-89; Mon, 08 Nov 2021 19:00:21 +0100 Message-ID: <7d353dd2-2ffb-6d5e-9983-f983c8b4f6da@leemhuis.info> Date: Mon, 8 Nov 2021 19:00:20 +0100 Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.2.0 Subject: Re: rt2x00 regression Content-Language: en-BZ From: Thorsten Leemhuis To: Stanislaw Gruszka , Stanislaw Gruszka Cc: linux-wireless@vger.kernel.org, Helmut Schaa , regressions@lists.linux.dev, Kalle Valo , Exuvo References: <20190927080303.GA7667@redhat.com> <20191203075736.GA701@redhat.com> <87czop5j33.fsf@tynnyri.adurom.net> <6366d9bd-9752-dbc2-8970-442bdc6e8eea@leemhuis.info> In-Reply-To: <6366d9bd-9752-dbc2-8970-442bdc6e8eea@leemhuis.info> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-bounce-key: webpack.hosteurope.de;regressions@leemhuis.info;1636394430;adadfe11; X-HE-SMSGID: 1mk8wP-0000qL-89 Sending this again, but this time also to Stanislaw's email address currently found in MAINTAINERS. Stanislaw, can you help with this regression? Helmut: or can you help somehow to get things rolling again? Ciao, Thorsten, your Linux kernel regression tracker On 05.11.21 14:25, Thorsten Leemhuis wrote: > Lo, this is your Linux kernel regression tracker speaking. > > On 01.10.21 08:56, Kalle Valo wrote: >> (adding regressions list for easier tracking) > > Thx for this, that's how it got on the radar of regzbot, my Linux kernel > regression tracking bot: > https://linux-regtracking.leemhuis.info/regzbot/regression/87czop5j33.fsf@tynnyri.adurom.net/ > > >> Exuvo writes: >> >>> I would like to get this resolved, is there any more information you need from me? >>> >>> I have been manually patching this all year with: >>> >>> drivers/net/wireless/ralink/rt2x00/rt2x00usb.c >>> - if (rt2x00dev->num_proto_errs > 8) >>> -    return true; >>> >>> It seems to just be some part of rt2800_load_firmware that is not >>> supported on my device and generating errors but it has been running >>> without problems in AP mode with daily usage. >> >> [...] >> >>>>>>>>> This most likely is the problem introduced by commit: >>>>>>>>> >>>>>>>>> commit e383c70474db32b9d4a3de6dfbd08784d19e6751 >>>>>>>>> Author: Stanislaw Gruszka >>>>>>>>> Date: Tue Mar 12 10:51:42 2019 +0100 >>>>>>>>> >>>>>>>>> rt2x00: check number of EPROTO errors >>>>>>>>> >>>>>>>>> Plase check below patch that increase number of EPROTO checks >>>>>>>>> before marking device removed. If it does not help, plese >>>>>>>>> check if reverting above commits helps. >> >> Should we do a revert? Can someone submit that including an explanation >> of the regression. > > Afaics nothing happened since then. Or did I miss anything? How can we > get the ball rolling again? > > Stanislaw, is there anything Exuvo (who offered to help afaics) could > test to get us closer to a fix? > > Ciao, Thorsten > > P.S.: I have no personal interest in this issue and watch it using > regzbot. Hence, feel free to exclude me on further messages in this > thread after the first reply, as I'm only posting this mail to hopefully > get a status update and things rolling again. #regzbot poke