Cross posting to the linux-acpi and linux-pci list for help. Summary: After an Ivy Bridge laptop is resumed from S3 and the USB 3.0 host controller is in D3, under Xen, the host controller will never come out of D3 to report a USB device connection. The same laptop with a standard Ubuntu install with the same 3.2.11 kernel works fine. I'm not sure what to make of the ACPI details about wakeup events being routed to e1000e instead of the xHCI host. Can someone help out here? On Thu, Mar 15, 2012 at 04:25:45PM -0400, Tom Goetz wrote: > On Mar 15, 2012, at 10:35 AM, Tom Goetz wrote: > > On Mar 14, 2012, at 1:46 PM, Tom Goetz wrote: > >> On Mar 14, 2012, at 12:57 PM, Sarah Sharp wrote: > >>> On Wed, Mar 14, 2012 at 09:52:28AM -0400, Tom Goetz wrote: > >>>>> Why were you posting there in particular? You're much more > >>>>> likely to get your USB questions answered on this mailing list. > >>>>> :) > >>>> > >>>> I'm concerned that this may be a bug in the Xen PVOPs MSI code. > >>>> To that end I've posted updates on xen-devel here: > >>>> > >>>> http://lists.xen.org/archives/html/xen-devel/2012-03/msg00904.html > >>>> http://lists.xen.org/archives/html/xen-devel/2012-03/msg00727.html > >>>> http://lists.xen.org/archives/html/xen-devel/2012-03/msg00978.html > >>> > >>> Does the xHCI host work fine without Xen? I.e. running Linux > >>> directly as the host OS, suspending, resuming, and then plugging > >>> in a device? > >> > >> It works in Ubuntu 12.04 Beta 1 with Linux 3.2.0. So it's either > >> broken between 3.2.0 and 3.2.5 or it's broken in Xen. I haven't > >> made a direct comparison yet. I'm putting Ubuntu on my SDP now to > >> test that. > > > > xHCI wakes up from D3 on the SDP with Ubuntu 12.04 Beta 1 and > > 3.2.11. This fails with the same 3.2.11 kernel and Xen. So the > > problem is Xen related. > > Another update. > > On the Ivybridge laptop, xHCI is not waking up because when I plug a > device into a xHCI port the ACPI wakeup events are going to the > e1000e. Pre S3, it eventually gets a interrupt from the device that > wakes it up. Post S3 it never gets an interrupt from the device. > > On the SDP, I get ACPI wake up calls for the xHCI before S3, but not > after. Both cases work with out Xen. I'm assuming Xen/PVOPs is leaving > the device in a state the causes the ACPI wake up events to be masked. > Can you tell me what what state that could be? I can look at > decompiling the ASL to find out, but that's not my first choice. > Toggling the power policy (auto->on->auto) does not fix delivery of > ACPI wake up events for this device. I am still getting ACPI wake ups > for the e1000e, so it's not all wake ups that are blocked. > > Thanks for any help. > > -Tom-- To unsubscribe from this list: send the line "unsubscribe > linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More > majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
