From owner-freebsd-mobile@freebsd.org Thu Feb 18 16:55:43 2016 Return-Path: Delivered-To: freebsd-mobile@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 4D537AAC0E3; Thu, 18 Feb 2016 16:55:43 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from mx.nsu.ru (mx.nsu.ru [84.237.50.39]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EBB0E789; Thu, 18 Feb 2016 16:55:42 +0000 (UTC) (envelope-from danfe@regency.nsu.ru) Received: from regency.nsu.ru ([193.124.210.26]) by mx.nsu.ru with esmtp (Exim 4.72) (envelope-from ) id 1aWRrY-0003U6-9s; Thu, 18 Feb 2016 22:55:33 +0600 Received: from regency.nsu.ru (localhost [127.0.0.1]) by regency.nsu.ru (8.14.2/8.14.2) with ESMTP id u1IGuYwV072968; Thu, 18 Feb 2016 22:56:34 +0600 (NOVT) (envelope-from danfe@regency.nsu.ru) Received: (from danfe@localhost) by regency.nsu.ru (8.14.2/8.14.2/Submit) id u1IGuTOF072930; Thu, 18 Feb 2016 22:56:29 +0600 (NOVT) (envelope-from danfe) Date: Thu, 18 Feb 2016 22:56:29 +0600 From: Alexey Dokuchaev To: John Baldwin Cc: Jan Henrik Sylvester , Hans Petter Selasky , Adrian Chadd , "current@freebsd.org" , Stefan Ehmann , "freebsd-mobile@freebsd.org" , Kevin Oberman Subject: Re: Thinkpad T410: resume broken Message-ID: <20160218165629.GA64990@regency.nsu.ru> References: <53762216.8020205@gmx.net> <201405231000.30861.jhb@freebsd.org> <20160218143738.GA38066@regency.nsu.ru> <1519677.qimO7W0WJL@ralph.baldwin.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1519677.qimO7W0WJL@ralph.baldwin.cx> User-Agent: Mutt/1.4.2.1i X-KLMS-Rule-ID: 1 X-KLMS-Message-Action: clean X-KLMS-AntiSpam-Lua-Profiles: 91515 [Feb 18 2016] X-KLMS-AntiSpam-Version: 5.5.9.33 X-KLMS-AntiSpam-Envelope-From: danfe@regency.nsu.ru X-KLMS-AntiSpam-Rate: 0 X-KLMS-AntiSpam-Status: not_detected X-KLMS-AntiSpam-Method: none X-KLMS-AntiSpam-Moebius-Timestamps: 3970137, 3970161, 3969585 X-KLMS-AntiSpam-Info: LuaCore: 414 414 652141367f63b6038f5642fa97308d3a9d2edb46, 127.0.0.200:7.1.3; regency.nsu.ru:7.1.1; 193.124.210.26:7.1.3,7.1.2,7.3.4; nsu.ru:7.1.1; 127.0.0.199:7.1.2; d41d8cd98f00b204e9800998ecf8427e.com:7.1.1 X-KLMS-AntiSpam-Interceptor-Info: scan successful X-KLMS-AntiPhishing: Clean, 2016/02/18 13:06:53 X-KLMS-AntiVirus: Kaspersky Security 8.0 for Linux Mail Server, version 8.0.1.705, not scanned, license restriction X-BeenThere: freebsd-mobile@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Mobile computing with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Feb 2016 16:55:43 -0000 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) } ... # 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 # pciconf -rb pci0:0:0 0xe0:0xff 09 00 09 21 02 a2 8b 90 0a 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 05 00 10 00 00 00 > There's not much we can do if your BIOS lies to us. As long as we can patch ACPI tables, lying BIOS should not be a problem, no? ./danfe