On Tue, Apr 17, 2012 at 03:20:32PM -0400, Alan Stern wrote: > > Unbound: > > > > pci 0000:00:1d.0: wake-up capability enabled by ACPI > > pci 0000:00:1d.0: Refused to change power state, currently in D0 > > pci 0000:00:1d.0: cur 5 target 3 error 0 > > pci 0000:00:1a.0: wake-up capability enabled by ACPI > > pci 0000:00:1a.0: Refused to change power state, currently in D0 > > pci 0000:00:1a.0: cur 5 target 3 error 0 > > > > Bound: > > > > ehci_hcd 0000:00:1d.0: wake-up capability enabled by ACPI > > ehci_hcd 0000:00:1d.0: Refused to change power state, currently in D0 > > ehci_hcd 0000:00:1d.0: cur 5 target 3 error 0 > > ehci_hcd 0000:00:1a.0: wake-up capability enabled by ACPI > > ehci_hcd 0000:00:1a.0: Refused to change power state, currently in D0 > > ehci_hcd 0000:00:1a.0: cur 5 target 3 error 0 > > Very good. The two behaviors are the same. > > Now if you modify the patch by removing the change to hcd-pci.c, which > will leave the EHCI code exactly the same as in the vanilla kernel, and > set the pm_test value to "platform", what does the dmesg log show in > the two cases? The same for the unbound state. For the bound state, it still locks up. -- WBR, wRAR
Attachment:
signature.asc
Description: Digital signature
