On Fri, May 23, 2014 at 10:00:30AM -0400, John Baldwin wrote: > On Wednesday, May 21, 2014 3:43:49 pm Jan Henrik Sylvester wrote: > > Looking through dmesg, it seems that other USB devices (build-in) are > > reappearing (Qualcomm Gobi 2000, Broadcom Bluetooth Device) after > > resume, just not the mouse. > > > > Are these lines likely related? > > > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.PEG_: > > AE_BAD_PARAMETER > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP1: > > AE_BAD_PARAMETER > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP2: > > AE_BAD_PARAMETER > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP4: > > AE_BAD_PARAMETER > > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP5: > > AE_BAD_PARAMETER > > These are probably not related. These man that your BIOS explicitly told > the OS to power down these devices (PEG_ is probably your GPU, and EXP[1-5] > are probably PCI-PCI bridges that represent the downstream ports of your > PCI-e root complex) in the D2 state when suspending, but the devices don't > actually support D2 (most PCI devices only support D0 (full on) and D3 > (full off)). I've started to observe similar lines in the logs after updating to fresh -CURRENT, upon resume (on a different laptop though, not T410): pcib0: failed to set ACPI power state D2 on \_SB_.PCI0: AE_BAD_PARAMETER acpi0: cleared fixed power button status If these messages are legit, I'm wondering why I didn't see them on 8.4, and if it might affect suspend/resume sequence (broken right now)? Thanks, ./danfeReceived on Thu Feb 18 2016 - 13:36:54 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:02 UTC