public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dennis Gnad <dennis@xorn.org>
To: linux-kernel@vger.kernel.org
Subject: USB issues on Fujitsu T2020 since a424948dde8421089826e2f782d0efe9e565707e
Date: Wed, 13 Jun 2012 23:18:52 +0200	[thread overview]
Message-ID: <4FD903BC.3040200@xorn.org> (raw)

After commit a424948dde8421089826e2f782d0efe9e565707e (see below), and
still in Kernel 3.4.2, USB will not work at all when the power controls
of the according PCI device and in the usb subdirectory are set to "auto".
For example:
echo auto > /sys/devices/pci0000:00/0000:00:1a.7/power/control
echo auto > /sys/devices/pci0000:00/0000:00:1a.7/usb1/power/control

It only stops working when *both* are set to "auto". This is also
triggered by the tunables of the powertop program.

Tested on a Fujitsu Lifebook T2020.

If this behavior is not specific to this notebook, the commit should
maybe get reverted?

Thanks for any comment!
 -Dennis


a424948dde8421089826e2f782d0efe9e565707e is the first bad commit
commit a424948dde8421089826e2f782d0efe9e565707e
Author: Rafael J. Wysocki <rjw@sisk.pl>
Date:   Sun Nov 6 22:21:46 2011 +0100

    PCI/ACPI/PM: Avoid resuming devices that don't signal PME

    Modify pci_acpi_wake_dev() to avoid resuming PME-capable devices
    whose PME Status bits are not set, which may happen currently if
    several devices are associated with the same wakeup GPE and all
    of them are notified whenever at least one of them signals PME.

    Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
    Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>

:040000 040000 bd5d78ae9ff2b75713725ed6e16d997b0017937d
f801b576ab380baa48b8c19523323aa6cca0b8cb M      drivers

                 reply	other threads:[~2012-06-13 21:50 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FD903BC.3040200@xorn.org \
    --to=dennis@xorn.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox