From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 23 15:52:12 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 976D98DD for ; Mon, 23 Jun 2014 15:52:12 +0000 (UTC) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 71659263D for ; Mon, 23 Jun 2014 15:52:12 +0000 (UTC) Received: from jhbbsd.localnet (unknown [209.249.190.124]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id 7F397B95D; Mon, 23 Jun 2014 11:52:10 -0400 (EDT) From: John Baldwin To: freebsd-acpi@freebsd.org Subject: Re: ACPI error messages on Lenovo W540 Date: Mon, 23 Jun 2014 09:53:16 -0400 User-Agent: KMail/1.13.5 (FreeBSD/8.4-CBSD-20140415; KDE/4.5.5; amd64; ; ) References: <53A048B1.1080108@metricspace.net> In-Reply-To: <53A048B1.1080108@metricspace.net> MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <201406230953.16496.jhb@freebsd.org> X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Mon, 23 Jun 2014 11:52:10 -0400 (EDT) X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 23 Jun 2014 15:52:12 -0000 On Tuesday, June 17, 2014 9:54:57 am Eric McCorkle wrote: > Hello, > > 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 think these are harmless and you can ignore them. Probably these devices only support D0 (on) and D3 (off) and not D2 (low power). > 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. Does it not work in general, or does it not work after resume? > 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) That is a very different error, but it might explain nvidia driver problems. The ACPI spec explains how _DSM works (there's an example method in section 9 of the 5.0 spec which you can get from acpi.info). In this case the warning is complaining that the return type is incorrect. Of course, the spec says that this function should return a Buffer, but ACPICA seems to think it should return a Package. It would be good to track down which specific arguments were passed to _DSM and then examine the acpidump to see which path that would take. -- John Baldwin