From: Sarah Sharp <sarah.a.sharp@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: "Bjørn Mork" <bjorn@mork.no>,
"Ulrich Eckhardt" <usb@uli-eckhardt.de>,
"Andrew Lutomirski" <luto@mit.edu>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"Alan Stern" <stern@rowland.harvard.edu>,
"Ming Lei" <ming.lei@canonical.com>,
"Bjorn Helgaas" <bhelgaas@google.com>,
linux-pci@vger.kernel.org, "Huang Ying" <ying.huang@intel.com>
Subject: Re: Unreliable USB3 with NEC uPD720200 and Delock Cardreader
Date: Thu, 6 Dec 2012 16:28:08 -0800 [thread overview]
Message-ID: <20121207002808.GG5324@xanatos> (raw)
In-Reply-To: <1962497.aG1sFtYjJG@vostro.rjw.lan>
On Thu, Dec 06, 2012 at 01:43:32AM +0100, Rafael J. Wysocki wrote:
> On Wednesday, December 05, 2012 04:33:44 PM Sarah Sharp wrote:
> > Wakeup from D3 works fine on the 3.5.0 kernel, but fails on 3.6.2. I
> > haven't fully bisected yet.
> >
> > In debugging, I found that if you only enable runtime suspend for the
> > NEC host controller, the host successfully comes out of D3 when you plug
> > in a USB device. However, if you enable runtime PM for the parent PCIe root
> > port, it stops working. Disabling D3cold for both devices did not help.
> >
> > It looks like a PCI issue, so what sort of debugging info do you need
> > from me?
>
> It looks like this is related to one of the following commits:
> Generally, please try to bisect changes in drivers/pci between v3.5 and v3.6.
Ok, I ran git bisect with only the drivers/pci directory as a target.
> ee85f54 ACPI/PM: specify lowest allowed state for device sleep state
git bisect ended up identifying this as the bad patch, although
reverting just that patch after the bisect finished didn't seem to help.
However, it does make sense that this would be the culprit patch, if
Huang Ying's theory about the PME polling is correct.
Sarah Sharp
next prev parent reply other threads:[~2012-12-07 0:28 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121126191002.GE6504@xanatos>
2012-11-26 21:48 ` Unreliable USB3 with NEC uPD720200 and Delock Cardreader Bjørn Mork
2012-11-28 22:54 ` Sarah Sharp
2012-12-06 0:33 ` Sarah Sharp
2012-12-06 0:43 ` Rafael J. Wysocki
2012-12-07 0:28 ` Sarah Sharp [this message]
2012-12-07 21:00 ` Rafael J. Wysocki
2012-12-12 2:32 ` Huang Ying
2012-12-12 2:34 ` Andrew Lutomirski
2012-12-12 3:18 ` huang ying
2012-12-13 19:53 ` Sarah Sharp
2012-12-06 7:17 ` Huang Ying
2012-12-06 12:43 ` Rafael J. Wysocki
[not found] <50841CCC.9030809@uli-eckhardt.de>
2012-10-22 23:40 ` Sarah Sharp
2012-10-23 13:54 ` Bjorn Helgaas
2012-10-23 17:14 ` Ulrich Eckhardt
2012-10-24 20:18 ` Bjorn Helgaas
2012-10-24 21:10 ` Rafael J. Wysocki
2012-10-24 21:13 ` Bjorn Helgaas
2012-10-24 21:31 ` Rafael J. Wysocki
2012-10-25 1:24 ` Ming Lei
2012-10-25 13:33 ` Bjorn Helgaas
2012-10-25 17:43 ` Ulrich Eckhardt
2012-10-25 18:19 ` Alan Stern
2012-10-27 13:02 ` Ulrich Eckhardt
2012-10-25 17:15 ` Ulrich Eckhardt
2012-10-25 20:11 ` Rafael J. Wysocki
2012-10-26 16:41 ` Ulrich Eckhardt
2012-10-25 20:09 ` Rafael J. Wysocki
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=20121207002808.GG5324@xanatos \
--to=sarah.a.sharp@linux.intel.com \
--cc=bhelgaas@google.com \
--cc=bjorn@mork.no \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=luto@mit.edu \
--cc=ming.lei@canonical.com \
--cc=rjw@sisk.pl \
--cc=stern@rowland.harvard.edu \
--cc=usb@uli-eckhardt.de \
--cc=ying.huang@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).