From owner-freebsd-acpi@FreeBSD.ORG Mon Jun 23 22:42:32 2014 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 3FE27C25; Mon, 23 Jun 2014 22:42:32 +0000 (UTC) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::103]) by mx1.freebsd.org (Postfix) with ESMTP id 145162D92; Mon, 23 Jun 2014 22:42:32 +0000 (UTC) Received: from [172.16.1.182] (unknown [172.16.1.182]) (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id E710E25077; Mon, 23 Jun 2014 22:42:30 +0000 (UTC) Message-ID: <53A8AD54.8040908@metricspace.net> Date: Mon, 23 Jun 2014 18:42:28 -0400 From: Eric McCorkle User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0 MIME-Version: 1.0 To: John Baldwin , freebsd-acpi@freebsd.org Subject: Re: ACPI error messages on Lenovo W540 References: <53A048B1.1080108@metricspace.net> <201406230953.16496.jhb@freebsd.org> In-Reply-To: <201406230953.16496.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 22:42:32 -0000 On 06/23/2014 09:53, John Baldwin wrote: > 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). That makes sense. It'd be nice if we could quiet the messages, but that wouldn't even be a second-order concern for me at this point. > >> 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? Actually, USB seems to be working quite well. It even detects an already plugged-in mouse during the ith resume. The sign of trouble are some messages that show up during resume: usb_alloc_device: device init 2 failed (USB_ERR_IOERROR, ignored) ugen0.2: at usbus2 (disconnected) uhub_reattach_port: could not allocate new device There had been some timeout messages, which googling seemed to implicate was a USB 3.0 issue with lenovos, but those seem to have disappeared (I did do a kernel update). Maybe I should test USB 3.0-specific features to see if they are working. Unfortunately, I'm not that familiar with the gritty details of USB. Any ideas for how to do that? > >> 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. I looked at acpidump, and I was able to find the definition of _DSM. Is there a way to get better ACPI debugging info out of the kernel (aside from adding debug messages directly)?