On Friday, February 22, 2013 10:51:58 PM Fabio Baltieri wrote: > On Fri, Feb 22, 2013 at 03:59:54AM -0500, Dave Jones wrote: > > On Thu, Feb 21, 2013 at 10:40:10AM -0800, Greg KH wrote: > > > > > USB patches for 3.9-rc1 > > > > > > Here's the big USB merge for 3.9-rc1 > > > > > > Nothing major, lots of gadget fixes, and of course, xhci stuff. > > > > I get no USB devices recognised when I insert them any more, which > > I think is pretty major. I suspect it has something to do with this ? > > > > > Lan Tianyu (12): > > > usb: add runtime pm support for usb port device > > > usb: add usb port auto power off mechanism > > > > It looks like every port on my laptop is powered down, as I can't > > even charge devices with it. > > Hi Dave, > > I have the same problem (and almost the same laptop, Thinkpad T430 > here), all external USB ports without power - even the always-on one > :-). > > The bug seems to be ACPI related, I bisected it down to this patch: > > f95988d ACPI / scan: Treat power resources in a special way > > In the dmesg I have some error like these: > > ACPI: Power Resource [PUBS] (on) > ... > pci 0000:00:14.0: System wakeup disabled by ACPI They aren't errors in fact, just info messages. > for the USB controllers in the broken kernel, there are some in your > dmesg too. I'll try to come up with a fix for current mainline, but all > the acpi stuff is quite obscure to me and the patch does not revert > cleanly, maybe Rafael (in CC) has some idea! It won't revert, there's more stuff on top of it. And it is a fix, so reverting it is not really a good idea anyway. I suspect that the USB controllers are put into low-power states at one point and they don't generate wakeup events. I'm not sure, though, why this is related to power resources. Can you please send a dmesg boot log and the output of acpidump from the affected machine? Rafael -- I speak only for myself. Rafael J. Wysocki, Intel Open Source Technology Center. -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
