Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp719574ybi; Fri, 12 Jul 2019 03:35:43 -0700 (PDT) X-Google-Smtp-Source: APXvYqyPA8FxrE9qeQ/Rji2CpGGrCBNPGdKU9HhWvOhtzXJYqU5KDL3K3huHjkWkFfVluDHkoqYL X-Received: by 2002:a17:90a:77c5:: with SMTP id e5mr9547168pjs.109.1562927743286; Fri, 12 Jul 2019 03:35:43 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1562927743; cv=none; d=google.com; s=arc-20160816; b=gkv33Oe6YCmzTv1zLeu92MCDw786kGM+QKEMZ7s4g3VpEmleV0DVTJGkDwTAY/5Z4P HavEfs48b3oobSQQUcgeEXn7/TC8Szqg1NCENyRPd/yszj5TThuKaNALyui33hAbxSCU 5nYAArtt8tF8ZyqkHGx5MXUFjQZ/mbEf8INbHctOOCNjq8tQ/ljiGo1xIJoKy96JHgdj Bah+Uug/yMqA8Dg5qI0vB1wTNRGSypMRrytSTEWIXAidHYpoVaQ4DVwb19/x2YE0GEtZ G9Mdq/ascEO2WdpBD1/aSk2fkXNVud7hEW3TjC45qGHijTLhKQo11Ys338mLAqvLQ0+m N9hA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=6kGIIa9r9y4zPbHUl26pNYJyXwHAmwRixVYKRDvZ4dY=; b=BQU+2EGQRc8wG6Bk/CLDqbYK+0Rkw53X/d1yVyTKEiSOKU0J4mcR1ZLfzmOgWAA1+o BjXGXZ1uSKZtIkSQzQbx/Vq87b6qKPG33hUhHYdHepmIP/ChEcfRh8sI4GK61+s2NKEE 9Akdln3EJSCYeBUBSh3eMMAfWzVvEEIkgVE4n0ZgWBP2yoGOuWmaSVWmnn2pEsExo1a2 xYRKsz5haHJ2n+JWxToSnnbFazqSkeT6s2cxDoBWfExtlCf2OrSuQo0e/in8LXZjN3+G grnnXOTL3615k1IKZCuVriBPNaAaz32WR705GoldIYo2t9gtG6livyD0RStJ6p4lxv8e K/hQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=tiscali.nl Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c137si8329124pga.80.2019.07.12.03.35.27; Fri, 12 Jul 2019 03:35:43 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=tiscali.nl Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726462AbfGLKdD (ORCPT + 99 others); Fri, 12 Jul 2019 06:33:03 -0400 Received: from lb1-smtp-cloud8.xs4all.net ([194.109.24.21]:40135 "EHLO lb1-smtp-cloud8.xs4all.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726091AbfGLKdC (ORCPT ); Fri, 12 Jul 2019 06:33:02 -0400 Received: from xps13 ([83.160.161.190]) by smtp-cloud8.xs4all.net with ESMTPSA id lsrDhP6COHOZUlsrGhbQVQ; Fri, 12 Jul 2019 12:33:01 +0200 Message-ID: Subject: Re: screen freeze with 5.2-rc6 Dell XPS-13 skylake i915 From: Paul Bolle To: Chris Wilson , James Bottomley , intel-gfx@lists.freedesktop.org Cc: linux-kernel Date: Fri, 12 Jul 2019 12:32:45 +0200 In-Reply-To: <9a8ed0f8e880e1a7387db00c74a9b71210ce6aff.camel@tiscali.nl> References: <1561834612.3071.6.camel@HansenPartnership.com> <156283735757.12757.8954391372130933707@skylake-alporthouse-com> <9a8ed0f8e880e1a7387db00c74a9b71210ce6aff.camel@tiscali.nl> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.3 (3.32.3-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfLaRbaES6HfwrzMNSFf3CXWwhvICM4kUP0lrUQX2EC2KOFCdmhd99TIO807yAvQL5IL1KDhcislGjxi3g+Wo9W91bdNcXlP4RKJaVQlDTrvx2kBEmgkr A6cbPM/5KpT15ST7HsbnQN7fPkqx8NUc8kJwU+P7BBRFcd1qRiAYu7IibvuuYjQMriAQaQGVIx0J0NqmyDqfMoTbYkD4h6l35gudeX0kvPqut95hSQQK2xvi pe6ivjWD0ZOjElm+SZCCcVdsHzW/hJ5CLuxFNkO3xW8Mmff+U04/drYmwJz9uNiNWXvXPlUj+CgtW8EWEHzUHg== Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Paul Bolle schreef op do 11-07-2019 om 13:20 [+0200]: > Chris Wilson schreef op do 11-07-2019 om 10:29 [+0100]: > > Temporary workaround would be to set i915.enable_psr=0 > > That workaround seems to work for me. Over an hour of uptime without any > screen freezes. May or may not be related: 24 hours into that session I had the machine lock up hard. Screen frozen, no input possible, etc. I had to power cycle it (after half an hour, behaving very patient). But the screen freeze that we're focusing on here never occurred during this session. Paul Bolle