On Fri, Mar 29, 2013 at 5:27 AM, Rafael J. Wysocki <rjw@xxxxxxx> wrote: > On Thursday, March 28, 2013 07:31:58 PM Martin Mokrejs wrote: >> Hi Bjorn, >> >> Bjorn Helgaas wrote: >> > On Thu, Mar 28, 2013 at 11:26 AM, Martin Mokrejs >> > <mmokrejs@xxxxxxxxxxxxxxxxxx> wrote: >> >> >> >> >> >> Rafael J. Wysocki wrote: >> >>> On Thursday, March 28, 2013 10:46:10 AM Bjorn Helgaas wrote: >> >>>> On Thu, Mar 28, 2013 at 10:41 AM, Rafael J. Wysocki <rjw@xxxxxxx> wrote: >> >>>>> On Thursday, March 28, 2013 10:21:30 AM Bjorn Helgaas wrote: >> >>>>>> On Thu, Mar 28, 2013 at 6:57 AM, Rafael J. Wysocki <rjw@xxxxxxx> wrote: >> >>>>>>> Hi Bjorn, >> >>>>>>> >> >>>>>>> I wonder what you think about the patch below? >> >>>>>> >> >>>>>> Seems fine to me (I'm trusting your and Matthew's judgment here since >> >>>>>> I don't know much about it). Why don't you resend it with Matthew's >> >>>>>> ack and the appropriate stable tags, and I'll put it in. >> >>>>> >> >>>>> I will, thanks! >> >>>>> >> >>>>>> If you have >> >>>>>> a URL for a bugzilla or mailing list report of the original problem, >> >>>>>> that would be good, too. It'd be nice if users and distros could >> >>>>>> match problem reports with this solution, but I can't tell what the >> >>>>>> user-visible issue was. I assume that Sarah tested this (or somebody >> >>>>>> else reproduced the problem and tested the fix)? >> >>>>> >> >>>>> Sarah reported it to me privately and I'm afraid I don't have any pointers >> >>>>> to publicly available mailing list archives etc. >> >>>> >> >>>> Do you at least have a description of how a user could determine >> >>>> whether he is seeing the problem fixed by this patch? >> >>> >> >>> Yeah. For example, when the problem is visible on a USB controller and that >> >>> controller is runtime-suspended, then plugging a new USB device into one >> >>> of the controller's ports won't wake the controller up without the patch. >> >> >> >> Hi, >> >> I am wondering for a week or two why nobody answered any of my bug reports, >> >> not even Sarah who asked for more details. I am think the fix is about my report >> >> under thread "Re: 3.8.2: xhci port is dead until pcieport PME# goes to disabled" >> >> and I really wonder why I wasn't Cc:ed and listed as a reporter provided it is >> >> about my report. But I should better wait what Sarah says. ;-) Hi, Martin, Sorry for late. Just found your bug report. That seems related with PCIe port runtime PM support. Can you try the debug patch attached? And send me back the dmesg? Sorry I use gmail web client, so I can only send patch as attachment. Best Regards, Huang Ying
Attachment:
port_wake_dbg.patch
Description: Binary data
