kernel-packages team mailing list archive

[Kim Tyler <1383555@xxxxxxxxxxxxxxxxxx>]

This was NOT happening in precise, and WAS happening with early versions
of trusty.  I had a test partition with trusty to check it, prior to
fresh install of trusty.  It was clear that this was happening with
trusty from boot.  I filed a bug report for trusty, along with upstream
kernels that were checked.  The newest upstream kernels did not show
that errors from boot.  When trusty was updated some time later, and
this error did not present from boot, I took the opportunity to fresh
install trusty, and use that full time.  I reported that the error
seemed to be fixed, and you closed the report. (Bug 1318837 )

(my comment from bug 1318837 follows) :-

have tried many kernels from mainline kernels
kernels from current, up to and including 3.14.0-rc2 exhibit error as described above.
kernels 3.14.0-rc3 and above DO NOT exhibit error as descibed above.
I have looked at changes log for for 3.14.0-rc3 for obvious changes that may be implicated, and found following candidate (search on "phy") (this may or may not be the solution)

Andrew Lunn (3):
      drivers: phy: Make NULL a valid phy reference
      drivers: phy: Add support for optional phys
      ata: sata_mv: Fix probe failures with optional phys

-- 
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/1383555

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

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Doesn't happen immediately after kernel reboot.  Will eventually cause
  wireless connection to fail, and cause computer to lock up.  Need to
  use <ALT-SYSREQ>REISUB to reboot, as all other method frozen.  Fills
  up logs with above messages many times per minute.  Originally
  happened with precise pangolin repeatedly from boot, but I did fresh
  install of trusty, and now is happening after a while from reboot.
  (this particular instance was 1 day or so after reboot)

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: linux-image-3.13.0-37-generic 3.13.0-37.64
  ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
  Uname: Linux 3.13.0-37-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC0:  kit284     2730 F.... pulseaudio
   /dev/snd/controlC2:  kit284     2730 F.... pulseaudio
  CurrentDesktop: Unity
  Date: Tue Oct 21 14:35:46 2014
  HibernationDevice: RESUME=UUID=8bc3362d-e136-453f-bb6c-284013a5dd11
  InstallationDate: Installed on 2014-10-01 (20 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: CLEVO D900K
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=7f8ca46f-0efa-4971-b7fc-9b787d5b660f ro quiet splash
  RelatedPackageVersions:
   linux-restricted-modules-3.13.0-37-generic N/A
   linux-backports-modules-3.13.0-37-generic  N/A
   linux-firmware                             1.127.7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/06/2005
  dmi.bios.vendor: Phoenix
  dmi.bios.version: 4.06CJ15
  dmi.board.name: D900K
  dmi.board.vendor: CLEVO
  dmi.board.version: VT8341B
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 1
  dmi.chassis.vendor: No Enclosure
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnPhoenix:bvr4.06CJ15:bd12/06/2005:svnCLEVO:pnD900K:pvrVT8341B:rvnCLEVO:rnD900K:rvrVT8341B:cvnNoEnclosure:ct1:cvrN/A:
  dmi.product.name: D900K
  dmi.product.version: VT8341B
  dmi.sys.vendor: CLEVO

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