From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.0 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 95E7AC3A5A7 for ; Wed, 4 Sep 2019 08:37:53 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 692222339D for ; Wed, 4 Sep 2019 08:37:53 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=ffwll.ch header.i=@ffwll.ch header.b="U9+zEmr/" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728598AbfIDIhw (ORCPT ); Wed, 4 Sep 2019 04:37:52 -0400 Received: from mail-ed1-f51.google.com ([209.85.208.51]:38254 "EHLO mail-ed1-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725267AbfIDIhw (ORCPT ); Wed, 4 Sep 2019 04:37:52 -0400 Received: by mail-ed1-f51.google.com with SMTP id r12so21636536edo.5 for ; Wed, 04 Sep 2019 01:37:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ffwll.ch; s=google; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=aVdFPGsO99fAHb0fDhq0jDs2yUdP0q6E5B82ILny3Mw=; b=U9+zEmr/e91kEhC0hkj435zZ0gbXQfHEM0gCZI0xxo4dfi1ycr946w8RBp5Vp6dYmo 1jYryGWSSRgZGuKaXNbE87tsfEGHFZfP6KOuyMa/Vdl33wxKSdAn9aKG1BA0LvniT9DL gKWayI2hSfYejDicvfILxoqr37c/e1/IqH6js= 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 :in-reply-to:user-agent; bh=aVdFPGsO99fAHb0fDhq0jDs2yUdP0q6E5B82ILny3Mw=; b=Zu5cKzcdGaJeOk46QL7y9+k1dfvr9yBK2YRKwusac+io1TyiyiKa8knZZ7D/XrHCOT Z2g7cBQcBKRX4wcB5WUliNt4/6ZyeQHsWFnNo6+z69J+2tWVGykGO0P81U7v06gmnWzO tUzrSd7XRmubh6Id6YulHM+KP9VSX4dxv5xCiu5yOCPRmbx+cYFiXn67YNfIOLlVrmn5 KWJpc8OTbC3lM07VFzxUsrZ3rrxlcu4UigTzWytVX8uep75jhYU2woNOkAO+6AS4Stqy 3JQtTlWQ1Co9+6N5p2U9Hw7z19FVW6IVLeR61vVhlupTXC6quw8nZhX18O0Xn+SSsdnj NO3A== X-Gm-Message-State: APjAAAUlFi0Qtm7oVvkw3HK0MXUSCWQfMs+Q2EP9G60wIW13f8d49Hbx 4BbaCcEw1w8NiP0WSzjqYKWbvg== X-Google-Smtp-Source: APXvYqz0ChI/C22nVFm32NQ+8BGIvxKJ90yP02BZdljqxcx7QVaEp8goV21yUaH/pz+vZNJPQFlB9A== X-Received: by 2002:a17:906:7c55:: with SMTP id g21mr1482880ejp.177.1567586270115; Wed, 04 Sep 2019 01:37:50 -0700 (PDT) Received: from phenom.ffwll.local (212-51-149-96.fiber7.init7.net. [212.51.149.96]) by smtp.gmail.com with ESMTPSA id t16sm2638378ejj.48.2019.09.04.01.37.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 04 Sep 2019 01:37:49 -0700 (PDT) Date: Wed, 4 Sep 2019 10:37:47 +0200 From: Daniel Vetter To: Hillf Danton Cc: Daniel Vetter , Mikhail Gavrilov , dri-devel , amd-gfx list , Linux kernel , Alex Deucher , Harry Wentland Subject: Re: gnome-shell stuck because of amdgpu driver [5.3 RC5] Message-ID: <20190904083747.GE2112@phenom.ffwll.local> Mail-Followup-To: Hillf Danton , Mikhail Gavrilov , dri-devel , amd-gfx list , Linux kernel , Alex Deucher , Harry Wentland References: <20190830032948.13516-1-hdanton@sina.com> <5d6e2298.1c69fb81.b5532.8395SMTPIN_ADDED_MISSING@mx.google.com> <5d6f10a6.1c69fb81.6b104.af73SMTPIN_ADDED_MISSING@mx.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5d6f10a6.1c69fb81.6b104.af73SMTPIN_ADDED_MISSING@mx.google.com> X-Operating-System: Linux phenom 5.2.0-2-amd64 User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 04, 2019 at 09:17:16AM +0800, Hillf Danton wrote: > Daniel Vetter > >> > >> Now 11:01pm and "gnome shell stuck warning" not appear since 19:17. So > >> looks like issue happens only when computer blocked and monitor in > >> power save mode. > > > > I'd bet on runtime pm or some other power saving feature in amdgpu > > shutting the interrupt handling down before we've handled all the > > interrupts. That would then result in a stuck fence. > > > > Do we already know which fence is stuck? > > It is welcomed to shed a thread of light on how to collect/print that info. > Say line:xxx-yyy in path/to/amdgpu/zzz.c Extend your backtrac warning slightly like WARN(r, "we're stuck on fence %pS\n", fence->ops); Also adding Harry and Alex, I'm not really working on amdgpu ... -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch