From: Stanislaw Gruszka <stf_xl@wp.pl>
To: Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Stanislaw Gruszka <sgruszka@redhat.com>,
linux-wireless@vger.kernel.org,
Helmut Schaa <helmut.schaa@googlemail.com>,
regressions@lists.linux.dev, Kalle Valo <kvalo@codeaurora.org>,
Exuvo <exuvo@exuvo.se>
Subject: Re: rt2x00 regression
Date: Tue, 9 Nov 2021 08:31:27 +0100 [thread overview]
Message-ID: <20211109073127.GA109212@wp.pl> (raw)
In-Reply-To: <7d353dd2-2ffb-6d5e-9983-f983c8b4f6da@leemhuis.info>
On Mon, Nov 08, 2021 at 07:00:20PM +0100, Thorsten Leemhuis wrote:
> Sending this again, but this time also to Stanislaw's email address
> currently found in MAINTAINERS.
>
> Stanislaw, can you help with this regression?
Yes.
I'll check on mail archives what is the status and what can be done.
Stanislaw
> 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 <exuvo@exuvo.se> 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 <sgruszka@redhat.com>
> >>>>>>>>> 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
next prev parent reply other threads:[~2021-11-09 7:38 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bff7d309-a816-6a75-51b6-5928ef4f7a8c@exuvo.se>
[not found] ` <20190927080303.GA7667@redhat.com>
[not found] ` <CA+GwT0B5SyRZnGLqwqOeuJK4CWMVc=dKaWre9VN8KQC6kBzKGw@mail.gmail.com>
[not found] ` <20191203075736.GA701@redhat.com>
[not found] ` <d74dab51-3a84-9035-d89e-ea8f63e89198@exuvo.se>
[not found] ` <a8eeb0bc-95da-291a-7fb9-5d15d1174c27@exuvo.se>
[not found] ` <c22673af-40e0-3af2-5ab7-69b23fc03598@exuvo.se>
[not found] ` <f935dc15-08bd-2e28-fc1b-b27634c618be@exuvo.se>
2021-10-01 6:56 ` rt2x00 regression Kalle Valo
2021-10-01 8:24 ` Thorsten Leemhuis
2021-11-30 9:16 ` rt2x00 regression #forregzbot Thorsten Leemhuis
2021-11-05 13:25 ` rt2x00 regression Thorsten Leemhuis
2021-11-08 18:00 ` Thorsten Leemhuis
[not found] ` <20211109073127.ga109212@wp.pl>
2021-11-09 7:31 ` Stanislaw Gruszka [this message]
2021-11-09 12:07 ` Stanislaw Gruszka
2021-11-09 15:22 ` Exuvo
[not found] ` <cc85b4e8a038417b865069c6578acf50@grupawp.pl>
2021-11-10 6:59 ` Kalle Valo
2021-11-10 8:01 ` Stanislaw Gruszka
2021-11-11 10:54 ` Exuvo
2021-11-11 14:10 ` [PATCH] rt2x00: do not mark device gone on EPROTO errors during start Stanislaw Gruszka
2021-11-18 6:16 ` Thorsten Leemhuis
2021-11-19 14:19 ` Kalle Valo
2021-11-29 10:54 ` Kalle Valo
[not found] <ca+gwt0b5syrznglqwqoeujk4cwmvc=dkawre9vn8kqc6kbzkgw@mail.gmail.com>
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=20211109073127.GA109212@wp.pl \
--to=stf_xl@wp.pl \
--cc=exuvo@exuvo.se \
--cc=helmut.schaa@googlemail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=sgruszka@redhat.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).