Ubuntu
linux package

Wifi Adapter Fails to come up after restart. after power off works fine

Bug #1584542 reported by hussain
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

I just installed Ubuntu Gnome 16.04 on my Laptop and I have noticed that Wifi somtimes doesn't work. after observing the problem I have come to the conclusion that it doesn't work after a reboot. I need to power it off and then back on to get the WiFi adapter working. my laptop is HP Pavilion and using a Ralink RT3290 Wireless adapter.

this is the dmesg output when it's working:
[ 12.190373] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected
[ 12.198413] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 3290 detected
[ 12.230518] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 22.490620] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin'
[ 22.566482] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37

this is when it's not working:
[ 12.434107] ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected
[ 12.437567] ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 3290 detected
[ 12.453872] ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
[ 22.603249] ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin'
[ 22.634727] ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37
[ 24.250054] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[ 25.850083] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[ 25.851000] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)
[ 27.994185] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[ 29.594240] ieee80211 phy0: rt2800_wait_wpdma_ready: Error - WPDMA TX/RX busy [0x00000068]
[ 29.595203] ieee80211 phy0: rt2800pci_set_device_state: Error - Device failed to enter state 4 (-5)

____________________________________________________________________________

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-22-generic 4.4.0-22.40
ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: hussain 2002 F.... pulseaudio
 /dev/snd/controlC0: hussain 2002 F.... pulseaudio
CurrentDesktop: GNOME
Date: Mon May 23 00:52:12 2016
HibernationDevice: RESUME=UUID=50a78741-d9a5-4656-a841-0c17259a4155
InstallationDate: Installed on 2016-05-22 (0 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 (20160421)
MachineType: Hewlett-Packard HP Pavilion 15 Notebook PC
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic.efi.signed root=UUID=69cc5799-74c4-41f7-b65d-5f9dafb54f43 ro
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-22-generic N/A
 linux-backports-modules-4.4.0-22-generic N/A
 linux-firmware 1.157
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/08/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.21
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2166
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 29.23
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrF.21:bd08/08/2013:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr0897100000304100000610100:rvnHewlett-Packard:rn2166:rvr29.23:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion 15 Notebook PC
dmi.product.version: 0897100000304100000610100
dmi.sys.vendor: Hewlett-Packard

See original description
Revision history for this message
hussain (abuznb195) wrote :
hussain (abuznb195)
description: updated
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
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
hussain (abuznb195)
tags: added: kernel-bug-exists-upstream
tags: removed: amd64 apport-bug xenial
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
hussain (abuznb195) wrote :

The bug happened right after installing Ubuntu Gnome 16.04, clean install. a while ago I upgraded from ubuntu 15.10 to 16.04 but the problem didn't occur.

Tested with 4.6 kernel. problem still exists.

penalvch (penalvch)
tags: added: amd64 apport-bug xenial
penalvch (penalvch)
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
hussain (abuznb195) wrote :

The model is 15-n034se

description: updated
Revision history for this message
penalvch (penalvch) wrote :

hussain, could you please test the latest mainline kernel (4.7-rc2) and advise to the results?

tags: added: bios-outdated-f.68
tags: added: regression-release
Revision history for this message
hussain (abuznb195) wrote :

Tested with latest kernel (4.7-rc5) and the problem still persists. sorry for the delay.

Revision history for this message
penalvch (penalvch) wrote :

hussain, as per http://support.hp.com/us-en/drivers/selfservice/hp-pavilion-15-n000-notebook-pc-series/5401225/model/5442795#Z7_3054ICK0K8UDA0AQC11TA930O2 an update to your computer's buggy, insecure, and outdated BIOS is available (F.69). When you update to this following https://help.ubuntu.com/community/BIOSUpdate how does this improve the situation?

For more on BIOS updates and linux, please see https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette .

Please note your current BIOS is already in the Bug Description, so posting this on the old BIOS would not be helpful.

Also, you don't have to create a new bug report.

Once the BIOS is updated, if the problem is still reproducible:
1) Please provide the output of the following terminal command (not perform an apport-collect):
sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
2) Please make a comment specifically advising on if there was an improvement or not.
3) Please mark this report Status Confirmed.

If it's not reproducible, please mark this as Invalid.

Thank you for your help.

tags: added: kernel-bug-exists-upstream-4.7-rc5
tags: added: bios-outdated-f.69
removed: bios-outdated-f.68
Revision history for this message
hussain (abuznb195) wrote :

I checked the link and there doesn't seem to be a BIOS update for my laptop. Are you certain there was an update for it ?!

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
penalvch (penalvch)
tags: added: bios-outdated-f.70
removed: bios-outdated-f.69
Revision history for this message
Aficionado (aficionadodesu) wrote :

Sorry. I know that was closed a year ago, but this bug is still present now.

I've updated my BIOS to the latest available version with no luck.

I'm on Debian. I think that's not directly related to Ubuntu. It may be a bug in the kernel driver or maybe a hardware problem (let's hope it is the first).

I'm not sure on how to proceed. How can I debug it? Can I file a bug to module developers? ( ?_?)

Also, I've noticed that, after a restart, you can make it work by suspending and waking up the computer.

Revision history for this message
Aficionado (aficionadodesu) wrote :

I found a workaround. Maybe someone find it useful.

In kernel source, file:

drivers/net/wireless/ralink/rt2x00/rt2800lib.c

function:

int rt2800_wait_wpdma_ready(struct rt2x00_dev *rt2x00dev)

replace:

return -EACCES;

by:

return 0;

That forces the code to continue even if the card seems to be busy. But it works for me. Maybe is not really busy... Who knows.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Maybe change the sleep time from 10 to an even larger number? See commit 08e5310028359.

Revision history for this message
Aficionado (aficionadodesu) wrote :

Yes, I saw the timeout message and tried with a 100, but no luck.

Revision history for this message
Aficionado (aficionadodesu) wrote :

Just saw a message in January 2017 about a fix (well, it seemed to me just another workaround). Maybe it is fixed in 4.9.6 or 7. I"ll try.

Revision history for this message
Aficionado (aficionadodesu) wrote :

Yes, bug is "solved" in Debian's unstable (linux image 4.11), but still present in the Debian's stable branch (linux image 4.9.0).

Revision history for this message
robb990099 (rebrown) wrote :

FWIW Still present also in 4.10.0-40-generic.

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

Other bug subscribers

Remote bug watches

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