1814:3290 [HP ProBook 455 G1 Notebook PC] rt2800pci doesn't work after upgrading to 13.10

Bug #1265151 reported by Jarl
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
High
Unassigned

Bug Description

After upgrading to 13.10 wifi no longer works for rt2800pci (RT3290)

To me it looks like this problem:
http://www.spinics.net/lists/linux-wireless/msg113047.html

$ lsb_releasee -rd
Description: Ubuntu 13.10
Release: 13.10

$ apt-cache policy linux
linux:
  Installeret: (ingen)
  Kandidat: 3.11.0.14.15
  Versionstabel:
     3.11.0.14.15 0
        500 http://dk.archive.ubuntu.com/ubuntu/ saucy-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu/ saucy-security/main amd64 Packages
     3.11.0.12.13 0
        500 http://dk.archive.ubuntu.com/ubuntu/ saucy/main amd64 Packages

I expected wifi to work as in 13.04, but it is unstable and in is deactivated after some time.

I can reproduce the problem with
$ sudo rmmod rt2800pci
$ sudo modprobe rt2800pci

after that WIFI works for some seconds or minutes, then it is disconnected.

the dmesg output is like this but it varies a bit...

[ 360.455741] rt2800pci 0000:04:00.0: irq 56 for MSI/MSI-X
[ 360.455823] ieee80211 phy2: rt2x00_set_rt: Info - RT chipset 3290, rev 0015 detected
[ 360.459348] ieee80211 phy2: rt2x00_set_rf: Info - RF chipset 3290 detected
[ 360.459674] ieee80211 phy2: Selected rate control algorithm 'minstrel_ht'
[ 360.471808] ieee80211 phy2: rt2x00lib_request_firmware: Info - Loading firmware file 'rt3290.bin'
[ 360.471870] ieee80211 phy2: rt2x00lib_request_firmware: Info - Firmware detected - version: 0.37
[ 360.517677] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 360.518267] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 362.601583] wlan0: authenticate with 00:18:e7:8a:55:2b
[ 362.616562] wlan0: send auth to 00:18:e7:8a:55:2b (try 1/3)
[ 362.617959] wlan0: authenticated
[ 362.620409] wlan0: associate with 00:18:e7:8a:55:2b (try 1/3)
[ 362.624016] wlan0: RX AssocResp from 00:18:e7:8a:55:2b (capab=0x431 status=0 aid=2)
[ 362.624103] wlan0: associated
[ 362.624156] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 446.156373] r8169 0000:02:00.0 eth0: link down
[ 476.091171] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 476.251186] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 476.639219] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 476.799146] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 476.807303] cfg80211: Calling CRDA to update world regulatory domain
[ 476.813452] cfg80211: World regulatory domain updated:
[ 476.813459] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 476.813464] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 476.813468] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 476.813472] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[ 476.813475] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 476.813478] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[ 477.059262] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 477.219205] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 477.379126] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 477.539122] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 478.759324] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 478.919410] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 483.755832] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 483.915844] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[ 484.075688] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 0 failed to flush
[ 484.235771] ieee80211 phy2: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: linux-image-3.11.0-14-generic 3.11.0-14.21
ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
Uname: Linux 3.11.0-14-generic x86_64
NonfreeKernelModules: fglrx
ApportVersion: 2.12.5-0ubuntu2.2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: jarl 1860 F.... pulseaudio
 /dev/snd/controlC0: jarl 1860 F.... pulseaudio
Date: Tue Dec 31 09:11:38 2013
HibernationDevice: RESUME=UUID=92f3c741-1bd3-4762-a2c1-59d27eef756c
InstallationDate: Installed on 2013-12-28 (2 days ago)
InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Hewlett-Packard HP ProBook 455 G1
MarkForUpload: True
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-14-generic root=UUID=3f5bd5b6-65b8-4ea5-bf33-4a8a7bf79b52 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.11.0-14-generic N/A
 linux-backports-modules-3.11.0-14-generic N/A
 linux-firmware 1.116
RfKill:
 4: phy4: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68CPE Ver. F.02
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 194E
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 91.0B
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68CPEVer.F.02:bd04/26/2013:svnHewlett-Packard:pnHPProBook455G1:pvrA2019DD203:rvnHewlett-Packard:rn194E:rvrKBCVersion91.0B:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP ProBook 455 G1
dmi.product.version: A2019DD203
dmi.sys.vendor: Hewlett-Packard

Revision history for this message
Jarl (jarl-dk) 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
Revision history for this message
Jarl (jarl-dk) wrote : Re: rt2800pci doesn't work after upgrading to 13.10

Sometimes I also see lines like this in dmesg:
[ 2130.023591] ieee80211 phy5: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0
[ 2130.023591] Please file bug report to http://rt2x00.serialmonkey.com
[ 2131.111559] ieee80211 phy5: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0
[ 2131.111559] Please file bug report to http://rt2x00.serialmonkey.com
[ 2137.168250] ieee80211 phy5: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0
[ 2137.168250] Please file bug report to http://rt2x00.serialmonkey.com
[ 2143.224765] ieee80211 phy5: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0
[ 2143.224765] Please file bug report to http://rt2x00.serialmonkey.com

Revision history for this message
Ivo Sieben (meltedpianoman) wrote :

I think this bug is a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245819

It seems to be an issue introduced with the 3.11 kernel, and it is solved in the 3.12 kernel. For me the solution was to update my Ubuntu to 3.12 kernel. I used the following guide on how to update the kernel:

http://ubuntuhandbook.org/index.php/2013/11/linux-kernel-3-12-released-install-ubuntu-or-linux-mint/

penalvch (penalvch)
Changed in linux (Ubuntu):
importance: Undecided → High
status: Confirmed → Incomplete
summary: - rt2800pci doesn't work after upgrading to 13.10
+ 1814:3290 [HP ProBook 455 G1 Notebook PC] rt2800pci doesn't work after
+ upgrading to 13.10
Revision history for this message
Jarl (jarl-dk) wrote :

Thanks a lot for the verify specific links, especially https://help.ubuntu.com/community/BiosUpdate, I didn't know. I will update the BIOS later today and get back.

Revision history for this message
Jarl (jarl-dk) wrote :

I updated the BIOS, it doesn't help...

After BIOS update:
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
68CPE Ver. F.24
10/18/2013

The problem seems to be introduced in kernel 3.11 and solved in 3.12. Are there any plans on updating ubuntu official kernel to 3.12?

Jarl

Revision history for this message
Jarl (jarl-dk) wrote :

Should I change status to "New" now that I have provided the requested info?

Revision history for this message
penalvch (penalvch) wrote :

Jarl, thank you for updating your BIOS. Could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, please just make a comment to this.

tags: added: latest-bios-f.24
Revision history for this message
Jarl (jarl-dk) wrote :

I have update to the latest kernel using the steps in http://ubuntuhandbook.org/index.php/2013/11/linux-kernel-3-12-released-install-ubuntu-or-linux-mint/ (Thanks Ivo)

That solved my problem.

Christopher, Are you serious? you are asking me to completely wipe my ubuntu installation and reinstall from scratch the daily CD image to see if that solves the problem.

It has been confirmed now by three sources that kernel 3.12 solves the problem, isn't that sufficient information? I trust that if daily CD has kernel 3.11 the problem is there, if it has kernel 3.12 the problem is not there.

Jarl

Revision history for this message
Jarl (jarl-dk) wrote :

I tend to agree with Ivo, this bug report is a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1245819 (though it is a slightly different computer model)

Revision history for this message
Pascal Fares (pfares) wrote :

Have exactly the same problem, very difficult to fix

Revision history for this message
Pascal Fares (pfares) wrote :

I istalled the latest kernel I have update to the latest kernel using the steps in http://ubuntuhandbook.org/index.php/2013/11/linux-kernel-3-12-released-install-ubuntu-or-linux-mint/ it seem to work well. I am using it now!

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
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.