From owner-freebsd-current@freebsd.org Sun May 13 19:44:31 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 519A0FCEF0F for ; Sun, 13 May 2018 19:44:31 +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 B88E374589; Sun, 13 May 2018 19:44:30 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from [192.168.2.9] (cpe-23-243-163-13.socal.res.rr.com [23.243.163.13]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 3fedb49e TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Sun, 13 May 2018 12:44:27 -0700 (PDT) Subject: Re: suspend/resume regression From: Pete Wright To: Theron , Niclas Zeising , Andriy Gapon , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> Message-ID: <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> Date: Sun, 13 May 2018 12:44:26 -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: <26f5ec31-3994-eac9-0c43-6d2458c35ad0@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.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 19:44:31 -0000 On 05/13/2018 10:27, Pete Wright wrote: > > > On 05/13/2018 08:58, Theron wrote: >>> 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 >> Hi Niclas, >> I used drm-next on Skylake with issues which sound similar. Resuming >> from suspend, or simply switching the laptop display output off and >> on from xrandr, resulted in graphics sluggishness (drop to 30fps in >> glxgears) and graphical corruption in Xorg apps, which persisted even >> after restarting these apps. Switching to drm-stable made the >> problems go away; I haven't had time to figure out what -next is >> doing differently to cause them. >> >> Pete's issue sounds more severe, and unrelated as it happens without >> drm loaded.  My kernel is two weeks out of date (r333093), so I need >> to check whether the more recent changes affect my system as well. >> > so i've done a bit more debugging on my end.  i've even installed the > 11.2-BETA branch last night since 11-STABLE worked without issues > about a month or so ago. > > i've set "debug.acpi.resume_beep=1" and when resuming after entering > an S3 sleep state the bell rings and does not stop until i do a hard > reset (both with i915kms loaded and unloaded). > > kinda at a loss as to how this could break both CURRENT and basically > 11-STABLE.  i'm going to make a ubuntu live image and test that, my > laptop is a System76 laptop that shipped with ubuntu originally.  if > that is broken as well then i guess this could be a hardware issue. > ubuntu live image suspends/resumes without issue so this certainly seems to be a freebsd issue unfortunately.  i guess next step is to attempt to find a working CURRENT snapshot that does suspend/resume without issue then start looking at commits? -pete -- Pete Wright pete@nomadlogic.org @nomadlogicLA