From: Stanislaw Gruszka <sgruszka@redhat.com>
To: Richard Genoud <richard.genoud@gmail.com>
Cc: Ivo van Doorn <IvDoorn@gmail.com>,
Gertjan van Wingerde <gwingerde@gmail.com>,
Helmut Schaa <helmut.schaa@googlemail.com>,
"John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rt2x00: Endless loop on hub port power down
Date: Fri, 4 Apr 2014 10:04:53 +0200 [thread overview]
Message-ID: <20140404080453.GA1448@redhat.com> (raw)
In-Reply-To: <1396536536-26423-1-git-send-email-richard.genoud@gmail.com>
On Thu, Apr 03, 2014 at 04:48:56PM +0200, Richard Genoud wrote:
> I've met an endless (or at least very long) loop if I power down the usb
> port on witch a usb wifi key is plugged.
> (Ok, it's not very smart to power down a usb port when a usb key is in
> used... but still, I think that should not lead to an endless loop).
>
> I have a lot of:
> ieee80211 phy1: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0438 with error -71
>
> (-71==-EPROTO)
>
> How to reproduce:
> - plug an usb wifi key
> - ip link set wlan0 up
> - hub-ctrl -b usb_bus -d usb_device -P usb_port -p 0
>
> hub-ctrl source: https://github.com/codazoda/hub-ctrl.c/blob/master/hub-ctrl.c
>
> The following patch prevents the endless loop, but I'm really not sure
> that The Right Way To Do It (R)
If device disappear, we should get -ENODEV status, why we get -EPROTO ?
Stanislaw
next prev parent reply other threads:[~2014-04-04 8:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-03 14:48 [PATCH] rt2x00: Endless loop on hub port power down Richard Genoud
2014-04-04 8:04 ` Stanislaw Gruszka [this message]
2014-04-04 9:58 ` Richard Genoud
2014-04-04 14:13 ` Stanislaw Gruszka
2014-04-04 15:38 ` Richard Genoud
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=20140404080453.GA1448@redhat.com \
--to=sgruszka@redhat.com \
--cc=IvDoorn@gmail.com \
--cc=gwingerde@gmail.com \
--cc=helmut.schaa@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=richard.genoud@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.