(adding regressions list for easier tracking) Exuvo <exuvo@xxxxxxxx> 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@xxxxxxxxxx> >>>>>>> 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. -- https://patchwork.kernel.org/project/linux-wireless/list/ https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
