]> git.proxmox.com Git - mirror_ubuntu-jammy-kernel.git/commit
rt2x00: do not mark device gone on EPROTO errors during start
authorStanislaw Gruszka <stf_xl@wp.pl>
Thu, 11 Nov 2021 14:10:03 +0000 (15:10 +0100)
committerPaolo Pisati <paolo.pisati@canonical.com>
Thu, 9 Dec 2021 10:10:35 +0000 (11:10 +0100)
commit326c10d0c2e69923069c6cdaad0c97d979875675
tree4054fd91b6cc9905ef0857b9a9f630c655a42f54
parentf8a4ae6697d79ca5d3ff6227af553c3178b2a8f7
rt2x00: do not mark device gone on EPROTO errors during start

BugLink: https://bugs.launchpad.net/bugs/1953731
commit ed53ae75693096f1c10b4561edd31a07b631bd72 upstream.

As reported by Exuvo is possible that we have lot's of EPROTO errors
during device start i.e. firmware load. But after that device works
correctly. Hence marking device gone by few EPROTO errors done by
commit e383c70474db ("rt2x00: check number of EPROTO errors") caused
regression - Exuvo device stop working after kernel update. To fix
disable the check during device start.

Link: https://lore.kernel.org/linux-wireless/bff7d309-a816-6a75-51b6-5928ef4f7a8c@exuvo.se/
Reported-and-tested-by: Exuvo <exuvo@exuvo.se>
Fixes: e383c70474db ("rt2x00: check number of EPROTO errors")
Cc: stable@vger.kernel.org
Signed-off-by: Stanislaw Gruszka <stf_xl@wp.pl>
Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Link: https://lore.kernel.org/r/20211111141003.GA134627@wp.pl
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Signed-off-by: Paolo Pisati <paolo.pisati@canonical.com>
drivers/net/wireless/ralink/rt2x00/rt2x00usb.c