Date: Thu, 13 Nov 2014 14:12:39 -0800 From: Adrian Chadd <adrian@freebsd.org> To: Eric McCorkle <eric@metricspace.net> Cc: "freebsd-mobile@freebsd.org" <freebsd-mobile@freebsd.org> Subject: Re: ThinkPad support Message-ID: <CAJ-Vmo=vX8xxw=sEQR6jzEpGiCrPXODT5qAN0tm9oM4BLqzFQw@mail.gmail.com> In-Reply-To: <54652B09.3000004@metricspace.net> References: <CAAupw%2BLLtHKUUdkQ9GWo8Pge7wFMwqvnP-CXr7W1H__pwomVHA@mail.gmail.com> <CAN6yY1uqYr4PL23DmQFsGXKkV_Taob7W9B_23crsdjaBvvZ1YA@mail.gmail.com> <20140916213835.GA4575@localhost.localdomain> <20140917193232.K61666@sola.nimnet.asn.au> <54652B09.3000004@metricspace.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Please update to the latest -HEAD and re-try. We found some issues with the suspend path and which device was being checked when deciding what power state to enter. -adrian On 13 November 2014 14:04, Eric McCorkle <eric@metricspace.net> wrote: > 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" >> > _______________________________________________ > 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo=vX8xxw=sEQR6jzEpGiCrPXODT5qAN0tm9oM4BLqzFQw>