Date: Thu, 18 Feb 2016 09:51:08 -0800 From: John Baldwin <jhb@freebsd.org> To: Alexey Dokuchaev <danfe@nsu.ru> Cc: Jan Henrik Sylvester <me@janh.de>, Hans Petter Selasky <hps@selasky.org>, Adrian Chadd <adrian@freebsd.org>, "current@freebsd.org" <current@freebsd.org>, Stefan Ehmann <shoesoft@gmx.net>, "freebsd-mobile@freebsd.org" <freebsd-mobile@freebsd.org>, Kevin Oberman <rkoberman@gmail.com> Subject: Re: Thinkpad T410: resume broken Message-ID: <3029262.DlAcg8ENfU@ralph.baldwin.cx> In-Reply-To: <20160218165629.GA64990@regency.nsu.ru> References: <53762216.8020205@gmx.net> <1519677.qimO7W0WJL@ralph.baldwin.cx> <20160218165629.GA64990@regency.nsu.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thursday, February 18, 2016 10:56:29 PM Alexey Dokuchaev wrote:
> On Thu, Feb 18, 2016 at 06:55:03AM -0800, John Baldwin wrote:
> > On Thursday, February 18, 2016 08:37:38 PM Alexey Dokuchaev wrote:
> > > I've started to observe similar lines in the logs after updating to
> > > fresh -CURRENT, upon resume (on a different laptop though, not T410):
> > >
> > > pcib0: failed to set ACPI power state D2 on \_SB_.PCI0: AE_BAD_PARAMETER
> > > acpi0: cleared fixed power button status
> > >
> > > If these messages are legit, I'm wondering why I didn't see them on 8.4,
> > > and if it might affect suspend/resume sequence (broken right now)?
> >
> > [...] Your BIOS said "please put this device in D2 during suspend" and your
> > device's capabilities said "I don't support D2". You can confirm this by
> > looking up the _S3 method of your _SB_.PCIO device to find out what state is
> > requested during suspend and then looking at 'pciconf -lc pci0:0:0' to see
> > what D states are listed as supported.
>
> This?:
>
> Scope (\_SB)
> {
> Name (ECOK, 0x00)
> Device (PCI0)
> {
> Method (_S3D, 0, NotSerialized) // _S3D: S3 Device State
> {
> Return (0x02)
> }
> ...
Yes, this says "please use D2 when going to S3".
> # pciconf -lc pci0:0:0
> hostb0@pci0:0:0:0: class=0x060000 card=0x83191033 chip=0x25908086 rev=0x04 hdr=0x00
> cap 09[e0] = vendor (length 9) Intel cap 2 version 1
Humm, perhaps PCI0 is not at 0:0. Can you find the _ADR method for _SB_.PCI0?
That contains the "slot" and "function" as two words, e.g. 0x10002 would
correspond to the 'pci0:1:2' device (or possibly pci0:2:1, don't recall the
order off the top of my head).
--
John Baldwin
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3029262.DlAcg8ENfU>