From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Lorenzo Bianconi <lorenzo.bianconi@redhat.com>
Cc: eduardoabinader@gmail.com,
linux-wireless <linux-wireless@vger.kernel.org>,
Felix Fietkau <nbd@nbd.name>
Subject: Re: [PATCH] mt76: handle protocol error to proper deinit rx_tasklet
Date: Mon, 26 Nov 2018 10:59:36 +0100 [thread overview]
Message-ID: <20181126095935.GA5710@redhat.com> (raw)
In-Reply-To: <CAJ0CqmV5byNc+Tmxh5rjHHv9TML31vSWToXq=Fb7aV7JwdJPBw@mail.gmail.com>
On Sat, Nov 24, 2018 at 10:25:52AM +0100, Lorenzo Bianconi wrote:
> > During removal of usb dongle, noticed many unhandled rx urb
> > below. This this patch, make it possible and early completion
> > of the rx tasklet.
> >
> > mt76x2u 1-3.4.3.1.2:1.0: rx urb failed: -71
> > mt76x2u 1-3.4.3.1.2:1.0: rx urb failed: -71
> > mt76x2u 1-3.4.3.1.2:1.0: rx urb failed: -71
> > mt76x2u 1-3.4.3.1.2:1.0: rx urb failed: -71
If problem here is just printing errors, I think we are ok. If problem
is some hung or infinity loop, it should be fixed.
> Hi Eduardo,
>
> I think EPROTO is a more general error (it is not strictly related to
> device removal)
> and it could happen even during normal operation. In this case I guess we should
> reinsert the urb to usb-core.
Some (out of tree) usb host drivers returns EPROTO all the time
in some error conditions. On rt2x00 resubmitting urb resulted in
infinity loop:
https://marc.info/?t=153375128700002&r=1&w=2
Fix I proposed for that was counting EPROTO errors and
mark device as removed if 10 of them happened in row:
https://marc.info/?l=linux-wireless&m=153441755529960&w=2
Thanks
Stanislaw
next prev parent reply other threads:[~2018-11-26 9:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-23 21:37 [PATCH] mt76: handle protocol error to proper deinit rx_tasklet Eduardo Abinader
2018-11-24 9:25 ` Lorenzo Bianconi
2018-11-26 9:59 ` Stanislaw Gruszka [this message]
2018-11-26 21:15 ` Eduardo Abinader
2018-11-26 21:31 ` Lorenzo Bianconi
2018-11-26 21:37 ` Eduardo Abinader
2018-11-26 21:58 ` Lorenzo Bianconi
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=20181126095935.GA5710@redhat.com \
--to=sgruszka@redhat.com \
--cc=eduardoabinader@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=lorenzo.bianconi@redhat.com \
--cc=nbd@nbd.name \
/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