From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932527AbdJ3UD6 (ORCPT ); Mon, 30 Oct 2017 16:03:58 -0400 Received: from mga06.intel.com ([134.134.136.31]:15933 "EHLO mga06.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932083AbdJ3UDy (ORCPT ); Mon, 30 Oct 2017 16:03:54 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,320,1505804400"; d="scan'208";a="167008235" Date: Mon, 30 Oct 2017 13:03:51 -0700 From: Rodrigo Vivi To: Linus Torvalds Cc: Fengguang Wu , Daniel Vetter , intel-gfx , Linux Kernel Mailing List , Jani Nikula Subject: Re: [Intel-gfx] [haswell_crtc_enable] WARNING: CPU: 3 PID: 109 at drivers/gpu/drm/drm_vblank.c:1066 drm_wait_one_vblank+0x18f/0x1a0 [drm] Message-ID: <20171030200351.5b7ox7kposnbk3q5@intel.com> References: <20171029225155.qcum5i75awrt5tzm@wfg-t540p.sh.intel.com> <20171030070044.eibo4y43plbc2vbk@wfg-t540p.sh.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: NeoMutt/20170912 (1.9.0) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Oct 30, 2017 at 07:10:11PM +0000, Linus Torvalds wrote: > On Mon, Oct 30, 2017 at 12:00 AM, Fengguang Wu wrote: > > CC intel-gfx. > > Thanks, these are all interesting (even if some of them seem to be > from random kernels). > > Fengguang, is this a new script that you started running? Because I'm > *hoping* it's not that rc6 suddenly seems so flaky, and it's really > that you now have a nice new script that started reporting these > things better, even though many of them may be old? yep, on our side there isn't anything on 4.14-rc6 from i915 that could justify this issues. I hope... Well, on the other hand it would be easier to bisect if this is a 4.14-rc6 thing since we just got one patch for i915 and few patches for gvt for this -rc6. > > This particular one I will have to leave to the intel gfx people to comment on. why is the bisect hard on this case in particularly? random? Is is reported anywhere where we could have access to full logs? I couldn't find any related open issue on our side. Nothing like this on our CI apparently as well. Other related cases that I saw with vblank time out like this, something else on CPU/GPU had already died before that hence the vblank never recieved. So I'd like to see more logs to have a better idea. Thanks, Rodrigo. > > Linus > _______________________________________________ > Intel-gfx mailing list > Intel-gfx@lists.freedesktop.org > https://lists.freedesktop.org/mailman/listinfo/intel-gfx