summaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/sched-migration.py
diff options
context:
space:
mode:
authorRichard Genoud <richard.genoud@gmail.com>2014-04-03 16:48:56 +0200
committerJohn W. Linville <linville@tuxdriver.com>2014-05-22 14:04:36 -0400
commit2ad69ac5976191e9bb7dc4044204a504653ad1bb (patch)
tree6e1fbd031771038fd1b862dfd545aad1c2cb9945 /tools/perf/scripts/python/sched-migration.py
parent5c2b6078ce02c3e81eb0aa2f07bf59ba67461ce2 (diff)
rt2x00: Endless loop on hub port power down
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) Signed-off-by: Richard Genoud <richard.genoud@gmail.com> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'tools/perf/scripts/python/sched-migration.py')
0 files changed, 0 insertions, 0 deletions