From owner-freebsd-current@freebsd.org Mon May 14 08:06:09 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 527A1FDFA45 for ; Mon, 14 May 2018 08:06:09 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: from mail-wr0-x22e.google.com (mail-wr0-x22e.google.com [IPv6:2a00:1450:400c:c0c::22e]) (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 B5F81791FC; Mon, 14 May 2018 08:06:08 +0000 (UTC) (envelope-from etnapierala@gmail.com) Received: by mail-wr0-x22e.google.com with SMTP id 94-v6so11228272wrf.5; Mon, 14 May 2018 01:06:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=25bZsCsYRtVzBSXuq4yusu6ubWgwk2pGd5KM5YgvQEk=; b=h/jFJx7ZQOhnSDqCoBUAU122mXCpmjMdjDO4DBrq8NJ55GIRIFse+98xrZMumIqECv pP+xxtZLitYinqFdeWJ+cpC7FgVd3KO2cxKVC7iLc1GHICvNIn18EH+36qso9QzhNKps gMCAwuEtCnqF9hIYXwF7g8eJId1FThdyyisDyhRFpHRiKUtpRvh2+LfGEIUAYRqA3NV4 TYy4KzGd+/FtU4bwiFSamnYRxXIhujZwjSlFVBfBFBDVoo3z4LQYnDcDQUVBjmpqGfQx Ja3UAH3wh8DrxvaytduHstIckmY5zxLgEUvkgHzkLGkTUjDCc6WBDmlZfvUO/NW4gcCp BBcg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=25bZsCsYRtVzBSXuq4yusu6ubWgwk2pGd5KM5YgvQEk=; b=Qu8ZZmkVLX603iOq+4P0epxZxrMO4zRK1aLhfRBGB8W6NVl7tALLwtjJY+R6aJXxjt SywQ+ZkaJU6NjS2WnL13pUO3PcICDZ/YHhwiOlYvOK+hwuA88uUV8TammmL30qTAr6VR ZMR0Z09xX1hD4TT5r8y4r072vPixq2dMwhAEbWfGm+cQ9xCH1M60Yd3h/GHJUARc9O7P 6TKBBV2oEwkGbwuVWJALJEvrcoJdj4UwMB5IYG18ycBcJ8QyNslsBL/PdRqRNmWHdj/a mxsHrWpWOEM12OXeIbTq3fXTrI+hcokdg/B7ZDrv9NfRz5N6pej9nRdKmBEiLlkW23yJ fUNA== X-Gm-Message-State: ALKqPwfJYN6ij4UV98Ze51I46lQu8F894usFbDpxe4u0mxbm9FTqt96w YpFSeLZTOlg2ON4NU1oNbwY= X-Google-Smtp-Source: AB8JxZqWSWD/fnLYN06Vg9Yw3JGg1s5w5Op0As39lv9POqrjcm9ReN5NJKJik7jRXpM59LIqT+CbvQ== X-Received: by 2002:adf:ab0a:: with SMTP id q10-v6mr6036156wrc.239.1526285167577; Mon, 14 May 2018 01:06:07 -0700 (PDT) Received: from brick (cpc92302-cmbg19-2-0-cust461.5-4.cable.virginm.net. [82.1.209.206]) by smtp.gmail.com with ESMTPSA id q2-v6sm11098349wrj.57.2018.05.14.01.06.06 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 May 2018 01:06:06 -0700 (PDT) Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= Date: Mon, 14 May 2018 09:06:04 +0100 From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= To: Pete Wright Cc: Theron , Niclas Zeising , Andriy Gapon , FreeBSD Current Subject: Re: suspend/resume regression Message-ID: <20180514080604.GA2006@brick> Mail-Followup-To: Pete Wright , 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> <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <9f7fcdaa-99ea-98f4-8ef3-c8da6060542e@nomadlogic.org> User-Agent: Mutt/1.9.5 (2018-04-13) 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:06:09 -0000 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=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? 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.