From owner-freebsd-mobile@FreeBSD.ORG Thu Nov 13 22:04:58 2014 Return-Path: Delivered-To: freebsd-mobile@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DE633EE7 for ; Thu, 13 Nov 2014 22:04:58 +0000 (UTC) Received: from mail.metricspace.net (mail.metricspace.net [IPv6:2001:470:1f11:617::103]) by mx1.freebsd.org (Postfix) with ESMTP id AA4FBCF2 for ; Thu, 13 Nov 2014 22:04:58 +0000 (UTC) Received: from [172.16.0.75] (unknown [172.16.0.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: eric) by mail.metricspace.net (Postfix) with ESMTPSA id CD7291C37 for ; Thu, 13 Nov 2014 22:04:57 +0000 (UTC) Message-ID: <54652B09.3000004@metricspace.net> Date: Thu, 13 Nov 2014 17:04:57 -0500 From: Eric McCorkle User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.2.0 MIME-Version: 1.0 To: freebsd-mobile@freebsd.org Subject: Re: ThinkPad support References: <20140916213835.GA4575@localhost.localdomain> <20140917193232.K61666@sola.nimnet.asn.au> In-Reply-To: <20140917193232.K61666@sola.nimnet.asn.au> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 13 Nov 2014 22:04:59 -0000 On 09/17/2014 06:09, Ian Smith wrote: > On Tue, 16 Sep 2014 22:38:35 +0100, isdtor wrote: > > [.. I can't comment on your devd issue/s ..] > > > Sep 16 21:48:23 host kernel: pci0: failed to set ACPI power state D2 on > > \_SB_.PCI0.EXP1: AE_BAD_PARAMETER > > This appears to be common to all Thinkpads for the last 6 years or so, > when booting with verbose messages. This message is emitted late on the > suspend path, and seems to indicate some device that has advertised D2 > as an available state, where D2 isn't apparently really supported. Chiming in late here... I see this on mine. I had thought it was the source of some problems, but I traced examined ACPI debugging traces (at a very high debugging level), and found that it doesn't seem to be causing any problems. The ACPI methods execute and finish without errors. > > On the resume path, not much later in the messages sequence, you should > see power being set back to D0 state, successfully. Perhaps - as in the > case of my X200 - twice in a row, for devices \_SB_.PCI0.EXP0 thru .EXP3 > > I don't know if this failure means that the device was left in D0 state > (run) or in D3 state (off) when power was removed in S3 suspend state. > > I never have been able to connect the dots between these .EXPn devices > and particular PCI devices in dmesg. So far they appear to be harmless. > > cheers, Ian > _______________________________________________ > freebsd-mobile@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-mobile > To unsubscribe, send any mail to "freebsd-mobile-unsubscribe@freebsd.org" >