On Tue, 17 Jun 2014 09:54:57 -0400, Eric McCorkle wrote:

 > I'm trying to set up on a lenovo W540 mobile workstation I recently
 > purchased.  Things work well for the most part (including suspend/resume),
 > however there's some error messages that I suspect are at the root of why the
 > nvidia Xorg driver doesn't work, and possibly also at the root of why USB 3.0
 > won't work either.
 > 
 > At suspend/resume, the following error messages show up:
 > 
 > 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.EXP3:
 > AE_BAD_PARAMETER
 > pci0: failed to set ACPI power state D2 on \134_SB_.PCI0.EXP5:
 > AE_BAD_PARAMETER
 > 
 > I suspect these might have something to do with the USB 3.0 system not
 > working, though I don't have experience with either the ACPI or USB
 > subsystems.
 > 
 > Also, the nvidia Xorg driver fails to work, and causes a similar error
 > message:
 > 
 > ACPI Warning: \134_SB_.PCI0.PEG_.VID_._DSM: Argument #4 type mismatch -
 > Found [Buffer], APCI requires [Package] (20130823/nsarguments-97)
 > (the same message gets repeated about 10 times)
 > 
 > Again, I don't have any experience with ACPI, but this looks to me like a
 > vendor-specific quirk.
 > 
 > Any advice on how to go about fixing/working around this?

Hi Eric,

I refer you to freebsd-mobile@ archives for May re these 'failed to set 
ACPI power state D2' messages, in thread 'Thinkpad T410: resume broken'.
I'm also cross-posting this back there.

These appear on the suspend path on (AFAICT) all modern Lenovos; X2xx, 
T4xx and T5xx at least, though I get similar messages for the Cardbus 
bridges on my old T23s.  The EXPn messages at least do appear to be 
harmless though they keep causing your sort of concern, and it would be 
good in the long run to find out why attempts are being made to set 
state D2 on devices that (should indicate that they) don't support it.

John Baldwin (cc'd) explains in that thread that the EXPn devices are 
"probably PCI-PCI bridges that represent the downstream ports of your 
PCI-e root complex)" though I can't say I understand what that means .. 
with verbose boot messages you may also see that these are initialised 
back into D0 state twice, unlike the other devices.

The PEG_ message seems to appear on the more recent ones with integrated 
graphics.  I don't know if that message represents a problem or not, 
though the later warnings re \134_SB_.PCI0.PEG_.VID_._DSM seem ominous.

It would be good to know if your USB3 issues are connected to the more 
generic issue all these Lenovos appear to have of USB failing entirely, 
only on the external ports, after - depending on model - one or two 
suspend/resume cycles.  There's not even any 5V on these ports, whether 
or not the BIOS has been set to provide 5V on these ports in suspend or 
power-off states.  Does that also happen on yours?

cheers, Ian
_______________________________________________
freebsd-acpi@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-acpi
To unsubscribe, send any mail to "freebsd-acpi-unsubscr...@freebsd.org"

Reply via email to