← Back to team overview

kernel-packages team mailing list archive

[Bug 1168255] Re: Enabling wakeup on the USB Root Controller prevents computer from suspending

 

Sparhawk, thank you for reporting this bug to Ubuntu. Quantal reached EOL on May 16, 2014.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this reproducible in the latest release of Ubuntu via
http://cdimage.ubuntu.com/daily-live/current/ ?

If so, please execute the following via a terminal in order for the necessary debugging information to be attached:
apport-collect 1168255

** Package changed: pm-utils (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Importance: Undecided => Low

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

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

Title:
  Enabling wakeup on the USB Root Controller prevents computer from
  suspending

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  Steps to reproduce:
  1) As root: # echo enabled > /sys/bus/usb/devices/2-1/power/wakeup
  2) Attempt to suspend computer.

  Expected results:
  Computer should suspend.

  Observed results
  Computer goes into suspend then immediately wakes up. There is nothing informative in /var/log/pm-suspend.log

  Background:
  This bug was discovered by a udev script that I wrote to allow waking my computer up from suspension by attached USB devices. This is the script:
  ACTION=="add", SUBSYSTEM=="usb", ATTRS{idVendor}=="15d9", ATTRS{idProduct}=="0a4d" RUN+="/bin/sh -c 'echo enabled > /sys$env{DEVPATH}/../power/wakeup'"

  A recent regression meant that this now prevents the computer from
  suspending as above. This script now writes "enabled" to both
  /sys/bus/usb/devices/2-1/power/wakeup and
  /sys/bus/usb/devices/2-1/2-1.1/power/wakeup . I'm not sure if the
  regression was that it now writes to the former as well as the latter,
  or if it always has written to both, and a regression in pm-suspend
  now cannot deal with the former. If I write "disabled" to the former,
  I can suspend as normal.

  More information:
  $ lsusb -t
   /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci_hcd/2p, 480M
      |__ Port 1: Dev 2, If 0, Class=hub, Driver=hub/8p, 480M
          |__ Port 1: Dev 5, If 0, Class=HID, Driver=usbhid, 1.5M
          |__ Port 5: Dev 3, If 0, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M
          |__ Port 5: Dev 3, If 1, Class='bInterfaceClass 0xe0 not yet handled', Driver=btusb, 12M

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: pm-utils 1.4.1-9
  ProcVersionSignature: Ubuntu 3.5.0-27.46-generic 3.5.7.7
  Uname: Linux 3.5.0-27-generic x86_64
  ApportVersion: 2.6.1-0ubuntu10
  Architecture: amd64
  Date: Fri Apr 12 16:32:39 2013
  InstallationDate: Installed on 2012-12-16 (116 days ago)
  InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: Upgraded to quantal on 2013-01-31 (71 days ago)

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