13b1:002f Cisco Linksys AE1000 rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0500 with error -71

Bug #1501876 reported by Jonathan Brier
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Triaged
High
Unassigned

Bug Description

With my USB adapter Linksys AE1000, on the University of Maryland College Park campus I am experiencing wifi connectivity issues where I get an initial connection, but it will drop frequently and have difficulty reconnecting to this secured wifi. This is at multiple locations on campus, but not off campus that I've found at this time. My Android Phone and Tablet do not have wifi issues connecting. It was working for a while until it lost connection. After the loss of connection I saw a repeated:
ieee80211 phy1: rt2x00usb_regbusy_read: Error - Indirect register access failed: offset=0x00000500, value=0xffff8804

ieee80211 phy1: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0500 with error -71

Before the wifi connection loss I saw repeated:
ieee80211 phy1: rt2800usb_tx_sta_fifo_read_completed: Warning - TX status read failed -71

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-30-generic 3.19.0-30.33
ProcVersionSignature: Ubuntu 3.19.0-30.33-generic 3.19.8-ckt6
Uname: Linux 3.19.0-30-generic x86_64
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jonathan 2145 F.... pulseaudio
 /dev/snd/controlC0: jonathan 2145 F.... pulseaudio
CurrentDesktop: Unity
Date: Thu Oct 1 15:10:34 2015
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-01-29 (244 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20141015)
MachineType: Hewlett-Packard HP ENVY TS 15 Notebook PC
ProcFB:
 0 radeondrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-30-generic.efi.signed root=UUID=1cc26cb0-3476-4abf-a12e-acac53ba8537 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-30-generic N/A
 linux-backports-modules-3.19.0-30-generic N/A
 linux-firmware 1.143.3
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-04-06 (177 days ago)
dmi.bios.date: 01/26/2015
dmi.bios.vendor: Insyde
dmi.bios.version: F.19
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 198A
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 03.14
dmi.chassis.asset.tag: 5CG32129MN
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.19:bd01/26/2015:svnHewlett-Packard:pnHPENVYTS15NotebookPC:pvr0888100000305B00000320000:rvnHewlett-Packard:rn198A:rvrKBCVersion03.14:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP ENVY TS 15 Notebook PC
dmi.product.version: 0888100000305B00000320000
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Jonathan Brier (brierjon) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: Confirmed → Incomplete
Revision history for this message
Jonathan Brier (brierjon) wrote :

The model number is: E1R45AV
Model Description: HP ENVY 15Z-J100 NOTEBOOK PC

Revision history for this message
penalvch (penalvch) wrote :

Jonathan Brier, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: latest-bios-f.19
Changed in linux (Ubuntu):
importance: Low → Medium
Revision history for this message
Jonathan Brier (brierjon) wrote :

I ran into the same issue with the latest mainline kernel 4.3.0-040300rc3-generic.

tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.3.0-040300rc3 kernel-bug-exists-upstream-kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Jonathan Brier (brierjon) wrote :

Tested again with 4.3.0-040300rv4 issue still present.

tags: added: kernel-bug-exists-upstream-4.3.0-040300rc4
removed: kernel-bug-exists-upstream-4.3.0-040300rc3
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
description: updated
penalvch (penalvch)
tags: added: kernel-bug-exists-upstream-4.3-c4
removed: kernel-bug-exists-upstream-4.3.0-040300rc4 kernel-bug-exists-upstream-kernel-bug-exists-upstream
Revision history for this message
penalvch (penalvch) wrote :

Jonathan Brier, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate venue (linux-wireless CC Stanislaw Gruszka and Helmut Schaa)?

Please provide a direct URL to your newly made report when it becomes available so that it may be tracked.

Thank you for your understanding.

Changed in linux (Ubuntu):
importance: Medium → High
status: Confirmed → Triaged
summary: - Cisco Linksys AE1000 rt2x00usb_vendor_request: Error - Vendor Request
- 0x07 failed for offset 0x0500 with error -71
+ 13b1:002f Cisco Linksys AE1000 rt2x00usb_vendor_request: Error - Vendor
+ Request 0x07 failed for offset 0x0500 with error -71
Revision history for this message
penalvch (penalvch) wrote :

Jonathan Brier, I wanted to clarify that the scope of this report is your Cisco Linksys device, not the built-in WiFi. This is as dealing with each device separately in their own reports is preferred both upstream and downstream. Hence, to scope a different report regarding your built-in WiFi, please file a report about it via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.