From owner-freebsd-current@freebsd.org Tue May 8 08:16:59 2018 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 51C6EFACF16 for ; Tue, 8 May 2018 08:16:59 +0000 (UTC) (envelope-from rum1cro@yandex.ru) Received: from forward101o.mail.yandex.net (forward101o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::601]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "forwards.mail.yandex.net", Issuer "Yandex CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BFEFC6B13E for ; Tue, 8 May 2018 08:16:58 +0000 (UTC) (envelope-from rum1cro@yandex.ru) Received: from mxback10o.mail.yandex.net (mxback10o.mail.yandex.net [IPv6:2a02:6b8:0:1a2d::24]) by forward101o.mail.yandex.net (Yandex) with ESMTP id 1113D1342A4B; Tue, 8 May 2018 11:16:56 +0300 (MSK) Received: from smtp4j.mail.yandex.net (smtp4j.mail.yandex.net [2a02:6b8:0:1619::15:6]) by mxback10o.mail.yandex.net (nwsmtp/Yandex) with ESMTP id 0rAq7HagVT-GtYqxXJC; Tue, 08 May 2018 11:16:56 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1525767416; bh=rbt78/A5IUEagqQHl4O7omU8um0Q0vP77aHpA9X8FJQ=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=C0Xw1pjGJQCCeZExL8xEr/LD3P1mSJqHp4BavGDlnKabQIh4RvMPHcR5Hm1HLvXUQ QKTo2Vt30VzVUoZeCXbEiDlk3lb98/a/M/DV4GHkW8e9Uw1LJwJdU0o8iluTxam7Nc UJ2WG+L5xc7ORCj5vF5ciuIf0Y+dphFf+bEoolXM= Received: by smtp4j.mail.yandex.net (nwsmtp/Yandex) with ESMTPSA id krgfR4hrNa-GsCCTUte; Tue, 08 May 2018 11:16:54 +0300 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client certificate not present) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1525767414; bh=rbt78/A5IUEagqQHl4O7omU8um0Q0vP77aHpA9X8FJQ=; h=Subject:To:References:From:Message-ID:Date:In-Reply-To; b=SWmE/ioXtmWDQiZeB9DfuTAPjCFevnvFI37r3VUkNhJYwgqnirym5h3XLHe7r7Qe3 Crgn4qH1QlkGGF2/kD+wOsPydE9LuM6dEiJVeTOiu798g7xWK9n3zUwtZ0YOdtd2vH ASIEbk0tNBk2VZgiF934Qy5UMXqL8Q06r8c1OPGU= Authentication-Results: smtp4j.mail.yandex.net; dkim=pass header.i=@yandex.ru Subject: Re: Regression Resume Lenovo T450 To: =?UTF-8?Q?Manuel_St=c3=bchn?= , freebsd-current@freebsd.org References: <20180504060717.GA88565@freebsd-t450.fritz.box> <20180506072835.GA87831@freebsd-t450.fritz.box> From: "Ilya A. Arkhipov" Message-ID: <2d6ae48a-d4fe-bca6-761c-00f3ceb1e35e@yandex.ru> Date: Tue, 8 May 2018 11:16:48 +0300 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180506072835.GA87831@freebsd-t450.fritz.box> Content-Type: text/plain; charset=iso-8859-15; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 08 May 2018 08:16:59 -0000 On 06.05.2018 10:28, Manuel Stühn wrote: > On Fri, May 04, 2018 at 08:07:17AM +0200, Manuel Stühn wrote: >> >> Since some time now CURRENT runs very smoothly on my Lenovo T450 in >> conjunction with drm-stable-kmod installed. WLAN, Suspense&Resume worked >> out of the box (at least ... until now). Due to pkg(8) complaining about >> wrong ABI of packages, I've made an update from r332385 (1200061) to >> r333091 (1200062), and now the T450 does not resume anymore; i have to >> hold the power button for some time to power it down. The >> ZFS-Boot-Environment I've made beforehand updating is still capable of >> resuming. >> >> I tried to find out which commit broke the resume for me by installing >> older kernels, but even installing r332385 kernel (into the actual >> r333091 userland) does not restore its capability to resume. >> > > Some more testing has happened: > > Since I have a BootEnvironment capable of suspend/resume, I've tried > some combinations of kernels (in fact, whole boot-folders) and > unserlands. I copied the boot-folder from the BE r332385 (which works) > into the current BE and restarted. This combination was NOT able to > resume. But the other way around is (current boot-folder (r333091) in > the r332385 based BootEnvironment) > > It seems to me, that not the kernel but either some change in userland > or package broke the resume somehow. But I do not have a clue, which > of those even can impact the resume procedure at all. Two packages > came to my mind: > > 1. graphics/drm-stable-kmod, but the installed packages are identical > for both, the "old" and the current BE. (both packages are installed > from ports along with the respective buildworld+buildkernel) > > 2. The firmwares used by sysutils/cpupdate, but after replacing the > firmware files with the firmwares from the old BE resume still doesn't > work. > > Any ideas? > > -- > Manuel > > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to > "freebsd-current-unsubscribe@freebsd.org" Hi, I have same issue (thinkpad T450s) after resume notebook cant wake up but on:  FreeBSD 12.0-CURRENT #0 r332796: Fri Apr 20 00:42:44 UTC 2018 root@releng3.nyi.freebsd.org:/usr/obj/usr/src/amd64.amd64/sys/GENERIC amd64 with: drm-next-kmod-4.11.g20180224 gpu-firmware-kmod-g20180206_1 # sysctl debug.bootverbose=1 # sysctl debug.acpi.suspend_bounce=1 In log (I think it related): May  8 01:05:06 m1cro kernel: vgapci0: child drmn0 requested pci_set_powerstate May  8 01:05:06 m1cro kernel: pci0:0:2:0: Transition from D0 to D3 May  8 01:05:06 m1cro kernel: pci0: set ACPI power state D3 on \_SB_.PCI0.VID_ May  8 01:05:06 m1cro kernel: pci0: failed to set ACPI power state D3 on \_SB_.PCI0.VID_: AE_BAD_PARAMETER where pci0:0:2:0: vgapci0@pci0:0:2:0:     class=0x030000 card=0x503617aa chip=0x16168086 rev=0x09 hdr=0x00     vendor     = 'Intel Corporation'     device     = 'HD Graphics 5500'     class      = display     subclass   = VGA