← Back to team overview

kernel-packages team mailing list archive

[Bug 1443924] [NEW] 1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0 failed to flush

 

Public bug reported:

Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity
after installing 15.04 Beta.

The system did work correctly with older Ubuntu versions (like 12.04)
and had this problem show up after upgrading to Trusty (as I already
reported in bug #1318837). Using Trusty the problem went away when
switching from the stock 3.13.0-XX-generic kernel to builds of newer
kernels (like 3.14.1-031401).

Now the same problem shows up again after installing Vivid Beta. It seems to be the same problem reported for other Ubuntu releases (see bugs #1318837 and #1383555) and also the same problem of this upstream kernel bug:
    https://bugzilla.kernel.org/show_bug.cgi?id=61621

Someone on kernel's bug mentions turning off MSI interrupts and I can confirm it did change the situation:
- normally the system looses WiFi connectivity mere seconds after boot (eg. can't ping anything after boot)
- if I boot with "pci=nomsi" the system will remain connected to the WiFi for a much longer period (eg. I am able to apt-get install something after boot)

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-extra-3.19.0-13-generic 3.19.0-13.13
ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
Uname: Linux 3.19.0-13-generic i686
ApportVersion: 2.17-0ubuntu2
Architecture: i386
AudioDevicesInUse:
 USER        PID ACCESS COMMAND
 /dev/snd/controlC0:  luca       1997 F.... pulseaudio
CurrentDesktop: LXDE
Date: Tue Apr 14 14:19:19 2015
HibernationDevice: RESUME=UUID=cbd1e136-ffc4-48b9-b2aa-c15264b9b132
MachineType: Freeline Freeline Series
ProcEnviron:
 LANGUAGE=en_US:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic root=UUID=6110f881-b32b-426d-910a-c63b355c179c ro quiet splash vt.handoff=7 pci=nomsi
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-13-generic N/A
 linux-backports-modules-3.19.0-13-generic  N/A
 linux-firmware                             1.143
RfKill:
 0: phy0: Wireless LAN
 	Soft blocked: no
 	Hard blocked: no
SourcePackage: linux
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/29/2004
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: Freeline Series
dmi.board.vendor: Freeline
dmi.board.version: Ver1.0
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/29/2004:svnFreeline:pnFreelineSeries:pvrVer1.0:rvnFreeline:rnFreelineSeries:rvrVer1.0:cvn:ct3:cvr:
dmi.product.name: Freeline Series
dmi.product.version: Ver1.0
dmi.sys.vendor: Freeline

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Confirmed


** Tags: apport-bug i386 vivid

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1443924

Title:
  1814:0201 ieee80211 phy0: rt2x00queue_flush_queue:Warning - Queue 0
  failed to flush

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Philips i386 PC with rt2x00 pci is suffering loss of WiFi connectivity
  after installing 15.04 Beta.

  The system did work correctly with older Ubuntu versions (like 12.04)
  and had this problem show up after upgrading to Trusty (as I already
  reported in bug #1318837). Using Trusty the problem went away when
  switching from the stock 3.13.0-XX-generic kernel to builds of newer
  kernels (like 3.14.1-031401).

  Now the same problem shows up again after installing Vivid Beta. It seems to be the same problem reported for other Ubuntu releases (see bugs #1318837 and #1383555) and also the same problem of this upstream kernel bug:
      https://bugzilla.kernel.org/show_bug.cgi?id=61621

  Someone on kernel's bug mentions turning off MSI interrupts and I can confirm it did change the situation:
  - normally the system looses WiFi connectivity mere seconds after boot (eg. can't ping anything after boot)
  - if I boot with "pci=nomsi" the system will remain connected to the WiFi for a much longer period (eg. I am able to apt-get install something after boot)

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: linux-image-extra-3.19.0-13-generic 3.19.0-13.13
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic i686
  ApportVersion: 2.17-0ubuntu2
  Architecture: i386
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  luca       1997 F.... pulseaudio
  CurrentDesktop: LXDE
  Date: Tue Apr 14 14:19:19 2015
  HibernationDevice: RESUME=UUID=cbd1e136-ffc4-48b9-b2aa-c15264b9b132
  MachineType: Freeline Freeline Series
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-13-generic root=UUID=6110f881-b32b-426d-910a-c63b355c179c ro quiet splash vt.handoff=7 pci=nomsi
  RelatedPackageVersions:
   linux-restricted-modules-3.19.0-13-generic N/A
   linux-backports-modules-3.19.0-13-generic  N/A
   linux-firmware                             1.143
  RfKill:
   0: phy0: Wireless LAN
   	Soft blocked: no
   	Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2004
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: Freeline Series
  dmi.board.vendor: Freeline
  dmi.board.version: Ver1.0
  dmi.chassis.type: 3
  dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd10/29/2004:svnFreeline:pnFreelineSeries:pvrVer1.0:rvnFreeline:rnFreelineSeries:rvrVer1.0:cvn:ct3:cvr:
  dmi.product.name: Freeline Series
  dmi.product.version: Ver1.0
  dmi.sys.vendor: Freeline

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1443924/+subscriptions


Follow ups

References