From owner-freebsd-current@freebsd.org Mon May 14 08:45:36 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 DEED2FE1ABC for ; Mon, 14 May 2018 08:45:35 +0000 (UTC) (envelope-from mikael.urankar@gmail.com) Received: from mail-pl0-x22b.google.com (mail-pl0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 59B4184EAB; Mon, 14 May 2018 08:45:35 +0000 (UTC) (envelope-from mikael.urankar@gmail.com) Received: by mail-pl0-x22b.google.com with SMTP id e6-v6so6945536plt.11; Mon, 14 May 2018 01:45:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Id8tBbzf6ZxBkj6FCC6/VLRTo1SDpBlUH2JfeQQzA+o=; b=ctdIzuoCP20gVhWXSodIhNiwLlh0PKYvSqfFCQgpttiif53Dist78InVD8pid07kgt ck4EEQeXR2/7IiPlFuhIR7e1DmwN9yxKWhMzGF4t+v4BWxVt5e+0+/eLIUSJk/5gzpSx lWVUWlJsFp1fAcHbIu1dF+dfpaB1k6XOXvu+p3MzJ+Len+lkcK2xnCKGFO6taku78agD gJTMuzDTpjVNsl0Bx7Kp8inxLwztCryuE5G7zZ+9PQUnZ+wS9m75OstwcLjZd1nblnf3 x2g7gL1R/sqjM/u5LFMGBu+VPO61ZNBdKF/kUfBAaCRhh8CAaIku03fZi4DxNYtaq3+6 9QFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Id8tBbzf6ZxBkj6FCC6/VLRTo1SDpBlUH2JfeQQzA+o=; b=HEfomiv4S0uBhSFsYhgzcHdxvqrFg41TECHmYT8C1DCG/8DKLNQNnbPASS9Rhqbwm0 OBSKWGqZjZCRSv6C2NEMUqDI4EGwn2ac/CR4mf++OQAKaUhEw9tWXaBh1XdbpnRjidv3 /GqpeVdOu80VISzHOzlJQMWBDgtcrF/58d9RwAwOSnetqJPhz5V8hxvebSK5Wb2VfYqU KW0Mq6Q/+J3AEuA0S0qB/Mhx6RU9ZqQ9pRaRXbp2NP+yDvesamDTt37E57peQRUYqo9B kXkWO98MYXlC8jHVQWWa27Gxpf86IWIsKfpev9hgodlrQ42oStbVjFYDHwP9vX2+X83Z rw8w== X-Gm-Message-State: ALKqPwfZ0F3xbd8zU/ZkOPIcZJEbCLsIBA1UhW0L8aoTVgA1TVX41riG LOchNkPk0QgtERpa99SP22imCQtxddAMYFmiRdQ= X-Google-Smtp-Source: AB8JxZqEZJ/4G5ofl60A8WhUOaxLBAy+rU7DpgjDq8h2jOZxFInRHDkEZl2E5vyfhQGfE44qiQdQfjG5YQoy4AFjuck= X-Received: by 2002:a17:902:2f84:: with SMTP id t4-v6mr9210559plb.24.1526287534467; Mon, 14 May 2018 01:45:34 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a17:90a:20ab:0:0:0:0 with HTTP; Mon, 14 May 2018 01:44:54 -0700 (PDT) In-Reply-To: References: <1e608109-fcdd-d794-b03a-2e417300b95a@nomadlogic.org> <3488a8a4-8cad-d6a8-0852-3bbbdd971c7f@gmail.com> <26f5ec31-3994-eac9-0c43-6d2458c35ad0@nomadlogic.org> <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> <20180514080604.GA2006@brick> From: =?UTF-8?Q?Mika=C3=ABl_Urankar?= Date: Mon, 14 May 2018 10:44:54 +0200 Message-ID: Subject: Re: suspend/resume regression To: Niclas Zeising Cc: Pete Wright , Theron , Andriy Gapon , FreeBSD Current Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.26 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:45:36 -0000 2018-05-14 10:27 GMT+02:00 Niclas Zeising : > On 05/14/18 10:06, Edward Tomasz Napiera=C5=82a wrote: > >> On 0513T1244, Pete Wright wrote: >> >>> >>> >>> 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=3D1" 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 see= ms >>> to be a freebsd issue unfortunately. i guess next step is to attempt t= o >>> find a working CURRENT snapshot that does suspend/resume without issue >>> then start looking at commits? >>> >> >> FWIW, I'm seeing the same - sluggishness after resume - with stock >> 12-CURRENT, without drm-next, just vanilla i915kms.ko, on T420. >> >> TBH I'm not entirely sure it's X11 problem - as I'm writing it now, >> under vt(4), it seems somewhat slow too. >> >> > It's not impossible that there are two different regressions, one causing > sluggishness and one causing graphics corruption, or that they are > intertwined. I have a Kaby Lake system which I run these tests on. I also > have a window where the regression seem to have happened. r333269 to > r333340, so once I have time I'll start bisecting. > > Hopefully I can test on older systems as well. Could it be the same problem described here? https://lists.freebsd.org/pipermail/freebsd-hackers/2018-May/052778.html