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 Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id A0FFBCDB465 for ; Thu, 19 Oct 2023 14:50:07 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 277C610E501; Thu, 19 Oct 2023 14:50:07 +0000 (UTC) Received: from mgamail.intel.com (mgamail.intel.com [134.134.136.31]) by gabe.freedesktop.org (Postfix) with ESMTPS id 9FBE210E501 for ; Thu, 19 Oct 2023 14:50:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1697727005; x=1729263005; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=NNZmvC+zXRLx22jFJ658GUE7dl+wod3UYkxR9sfDMGw=; b=Yy5Q0W1yz6JUroumf6boMoYTm11hqV/VQHDIaujDpdCBhtyb3U5BtnBa qEIYrFCLOv7GB+AqkF0NkVAI1OJkCkzf1HXCFcizt8Y+hN5XHy/wzmpv1 TaGN15V34lcdwRyA9G2tP21HM0Hn7W8LSz0m28/3Fj1jFpIiuIGY6yFiP LRWGw0i7XncMiXoHktzTArF0AniG6+o8lNVXqnVgaXZKgP58Qc6qNX4Py YzDcA6uO7omdeACRmc31t+zARniD6ij5EV/q+ejLaYc/bIiI/G/BxC5aP dkG2to1rUbmO9xUcdbalerch4i5FWMgc0TQC0gIwEdCf6oulQF8tiiVYI g==; X-IronPort-AV: E=McAfee;i="6600,9927,10868"; a="450492246" X-IronPort-AV: E=Sophos;i="6.03,237,1694761200"; d="scan'208";a="450492246" Received: from orviesa001.jf.intel.com ([10.64.159.141]) by orsmga104.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Oct 2023 07:50:05 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.03,237,1694761200"; d="scan'208";a="4774103" Received: from tiamfooc-mobl.gar.corp.intel.com (HELO intel.com) ([10.214.147.77]) by smtpauth.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 19 Oct 2023 07:48:52 -0700 Date: Thu, 19 Oct 2023 16:49:50 +0200 From: Andi Shyti To: Tvrtko Ursulin Message-ID: References: <20231017195309.2476088-1-vinay.belgaumkar@intel.com> <169759328299.15109.5802304051647309440@emeril.freedesktop.org> <22223706-fdcc-d9d7-80e8-bdeb847bc8ef@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <22223706-fdcc-d9d7-80e8-bdeb847bc8ef@linux.intel.com> Subject: Re: [Intel-gfx] =?utf-8?b?4pyXIEZpLkNJLklHVDogZmFpbHVyZSBmb3IgZHJt?= =?utf-8?q?/i915/mtl=3A_Don=27t_set_PIPE=5FCONTROL=5FFLUSH=5FL3_=28rev5=29?= X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: intel-gfx@lists.freedesktop.org Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" On Thu, Oct 19, 2023 at 09:14:13AM +0100, Tvrtko Ursulin wrote: > > On 18/10/2023 17:43, Andi Shyti wrote: > > Hi Vinay, > > > > > Possible regressions > > > > > > • igt@gem_exec_nop@basic-series: > > > > > > □ shard-glk: PASS -> INCOMPLETE +1 other test incomplete > > > • igt@kms_big_fb@4-tiled-max-hw-stride-64bpp-rotate-0-hflip-async-flip: > > > > > > □ shard-dg2: PASS -> TIMEOUT > > > • igt@kms_cursor_crc@cursor-onscreen-64x21@pipe-d-hdmi-a-1: > > > > > > □ shard-tglu: PASS -> INCOMPLETE > > > • igt@kms_psr@psr2_suspend: > > > > > > □ shard-mtlp: NOTRUN -> FAIL > > > > these failures look unrelated and besides they are not related to > > MTL. > > There is something new on the shards which _seems_ to be implicating this patch. > > This previously all green test started failing in a bad way: > > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_13775/shard-mtlp-6/igt@sysfs_preempt_timeout@timeout@vecs0.html > > <5> [97.816201] Fence expiration time out i915-0000:00:02.0:sysfs_preempt_t[1166]:2! > <3> [187.682308] INFO: task kworker/0:3:165 blocked for more than 61 seconds. > <3> [187.689294] Tainted: G W 6.6.0-rc6-CI_DRM_13775-ge69e078f7bef+ #1 > <3> [187.697375] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. > <6> [187.705354] task:kworker/0:3 state:D stack:13504 pid:165 ppid:2 flags:0x00004000 > <6> [187.705375] Workqueue: i915-unordered intel_gt_watchdog_work [i915] > <6> [187.705671] Call Trace: > <6> [187.705675] > <6> [187.705683] __schedule+0x3a0/0xd70 > <6> [187.705704] schedule+0x5c/0xd0 > <6> [187.705713] guc_context_cancel_request+0x45e/0x9f0 [i915] > <6> [187.706078] ? __pfx_autoremove_wake_function+0x10/0x10 > <6> [187.706091] ? intel_gt_watchdog_work+0x20/0x260 [i915] > <6> [187.706377] intel_gt_watchdog_work+0xd1/0x260 [i915] > <6> [187.706624] ? process_scheduled_works+0x264/0x530 > <6> [187.706635] process_scheduled_works+0x2db/0x530 > <6> [187.706650] ? __pfx_worker_thread+0x10/0x10 > <6> [187.706656] worker_thread+0x18c/0x350 > <6> [187.706664] ? __pfx_worker_thread+0x10/0x10 > <6> [187.706670] kthread+0xfe/0x130 > <6> [187.706678] ? __pfx_kthread+0x10/0x10 > <6> [187.706687] ret_from_fork+0x2c/0x50 > <6> [187.706696] ? __pfx_kthread+0x10/0x10 > <6> [187.706704] ret_from_fork_asm+0x1b/0x30 > <6> [187.706724] > > I am not claiming it is at fault but the transition from green to timing out looks clear. This looks an unrelated failure to me... Before merging this patch I did consult with Vinay. Vinay, could you please double check here? Andi