From owner-freebsd-current@freebsd.org Mon May 14 08:23:45 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 3F8B5FE09A6 for ; Mon, 14 May 2018 08:23:45 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from mail.daemonic.se (mail.daemonic.se [176.58.89.161]) (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 CF5B27EFAE; Mon, 14 May 2018 08:23:44 +0000 (UTC) (envelope-from zeising+freebsd@daemonic.se) Received: from cid.daemonic.se (localhost [IPv6:::1]) by mail.daemonic.se (Postfix) with ESMTP id 40kty75NyyzDhS4; Mon, 14 May 2018 08:23:43 +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=1526286223; bh=KZLn+GJLCNstcDb4z0ajpHte +blqXSfpuHE+PbMGztY=; b=i3fBw/7rn8xktXTJcusXGY+EscSp3Q+XsudlCeCw bwpaHW7LxWeq8apLWhtlWmsX8blLnXjPQpuFWTcv0OvEUXgZN9I+eKJi3IUdGA9p 08aZKkdQHKiYt5wEzmCRR0UCWa/xozoZe47tkMx1YMpMiuzEeoLoHcEr17OIUFiW DIA= X-Virus-Scanned: amavisd-new at daemonic.se Received: from mail.daemonic.se ([IPv6:::1]) (using TLS with cipher ECDHE-RSA-AES128-GCM-SHA256) by cid.daemonic.se (mailscanner.daemonic.se [IPv6:::1]) (amavisd-new, port 10587) with ESMTPS id QlBUko7o3Smv; Mon, 14 May 2018 08:23:43 +0000 (UTC) Received: from garnet.daemonic.se (host-95-192-250-89.mobileonline.telia.com [95.192.250.89]) by mail.daemonic.se (Postfix) with ESMTPSA id 40kty66YyqzDhBg; Mon, 14 May 2018 08:23:42 +0000 (UTC) Subject: Re: suspend/resume regression To: Theron , Andriy Gapon , Pete Wright , FreeBSD Current References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> From: Niclas Zeising Message-ID: <4725b2ef-37c7-85eb-a2fa-8dd96d1d9ad6@daemonic.se> Date: Mon, 14 May 2018 10:23:42 +0200 User-Agent: Mutt/1.5.21 MIME-Version: 1.0 In-Reply-To: <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: quoted-printable 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: Mon, 14 May 2018 08:23:45 -0000 On 05/13/18 17:58, Theron wrote: >> Hi! >> I'm also seeing issues, not as severe as Pete, but after I resume=20 >> (which works, with drm-next and DMC firmware), the system becomes=20 >> sluggish.=C2=A0 It feels like I/O takes more time, and graphics are=20 >> sluggish (very sientific, I know, but for instance git operations are=20 >> much slower after a resume).=C2=A0 I know there's been an update to ac= pica=20 >> between my system updates, when this started to happen, but I haven't=20 >> had time to revert that update and test again.=C2=A0 I will try to do = that=20 >> and report back. >> Regards > Hi Niclas, > I used drm-next on Skylake with issues which sound similar. Resuming=20 > from suspend, or simply switching the laptop display output off and on=20 > from xrandr, resulted in graphics sluggishness (drop to 30fps in=20 > glxgears) and graphical corruption in Xorg apps, which persisted even=20 > after restarting these apps.=C2=A0 Switching to drm-stable made the pro= blems=20 > go away; I haven't had time to figure out what -next is doing=20 > differently to cause them. >=20 > Pete's issue sounds more severe, and unrelated as it happens without dr= m=20 > loaded.=C2=A0 My kernel is two weeks out of date (r333093), so I need t= o=20 > check whether the more recent changes affect my system as well. >=20 I have a Kaby Lake system. I haven't tried switching outputs with=20 xrandr, I have to do that as well. What versions of drm-next and=20 drm-stable have you tested? Regards --=20 Niclas