From owner-freebsd-current@freebsd.org Thu May 17 18:14:08 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 D3128EDBF60 for ; Thu, 17 May 2018 18:14:08 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (mail.nomadlogic.org [IPv6:2607:f2f8:a098::2]) (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 557316E3C4 for ; Thu, 17 May 2018 18:14:08 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.1.223] (cpe-75-82-194-8.socal.res.rr.com [75.82.194.8]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id c6563bcf TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO for ; Thu, 17 May 2018 11:14:07 -0700 (PDT) Subject: Re: suspend/resume regression From: Pete Wright To: FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> Message-ID: Date: Thu, 17 May 2018 11:14:06 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 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: Thu, 17 May 2018 18:14:09 -0000 On 05/12/2018 19: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. > Closing the loop on this thread.  Git commit 4e99d4e797ba9cea01897b6909b061db841f855a fixes this issue on my end.  For more info there is a thread on this list named "Lag after resume culprit found" that has details. -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA