From owner-freebsd-current@freebsd.org Sun May 13 09:54:49 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 520BCFD1FCA for ; Sun, 13 May 2018 09:54:49 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [IPv6:2607:f740:d:20::25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C367F78E3E; Sun, 13 May 2018 09:54:48 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40kK1f6YXMzDhG6; Sun, 13 May 2018 09:54:46 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=daemonic.se; h= content-transfer-encoding:content-language:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=20151023; t=1526205286; bh=J5S73eMsJ1GWjULibBlDs3q8 mv72teaGx881Yt0chiU=; b=ugL2yL6BwQzrDtjYz8vYVuTPn6PfwqVIW2sHEbTr l+/a8buC2YDzpoewO4ZYuvOtlUdavpuspXpliBWctFph7fpkW0p9nrfcXP4AdfAc hqaQtQTvleQ9Pf/GmFGqzKuqqaaKXMhqluAVuKN21zKOshSNnArZcLM3HkW4kbQa 4BI= X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([127.0.0.1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [127.0.0.1]) (amavisd-new, port 10587) with ESMTPS id 3k76arAYYKDW; Sun, 13 May 2018 09:54:46 +0000 (UTC) Received: from celes.daemonic.se (celes.daemonic.se [IPv6:2001:470:dca9:2::3]) by mail.daemonic.se (Postfix) with ESMTPSA id 40kK1f1xFwzDhBg; Sun, 13 May 2018 09:54:46 +0000 (UTC) Subject: Re: suspend/resume regression To: Andriy Gapon , Pete Wright , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> From: Niclas Zeising Message-ID: Date: Sun, 13 May 2018 11:54:45 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit 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: Sun, 13 May 2018 09:54:49 -0000 On 05/13/18 09:48, Andriy Gapon wrote: > On 13/05/2018 05:25, Pete Wright wrote: >> hi there - i have an amd64 laptop that's been running CURRENT for a while using >> both drm-next and drm-stable for graphics. during the past week or so i've run >> into issues with suspend resume...well technically resume has stopped working. >> i've tested a couple configurations and none have allowed my system to resume >> successfully: >> >> - drm-next installed with DMC firmware loaded >> - drm-next installed without DMC firmware loaded (worked previously) >> - drm-stable with DMC >> - drm-stable without DMC >> - no drm modules loaded. >> >> I've also tested these configs with the following sysctl set to 0 and 1: >> hw.acpi.reset_video >> >> at this point i'd like to help find what the regression i'm running into is, so >> any pointers on how i can help? the system seems to boot and i'm pretty sure i >> can ssh into it most times, just not sure what info i should grab to help. >> nothing of interest in messages or dmesg buffer either. > > Did you do any OS upgrades what was last working version and what is the current > version (svn revision number)? > Or any other notable changes before resume stopped working... > Hi! I'm also seeing issues, not as severe as Pete, but after I resume (which works, with drm-next and DMC firmware), the system becomes sluggish. It feels like I/O takes more time, and graphics are sluggish (very sientific, I know, but for instance git operations are much slower after a resume). I know there's been an update to acpica between my system updates, when this started to happen, but I haven't had time to revert that update and test again. I will try to do that and report back. Regards -- Niclas