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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 51B48C001DB for ; Mon, 14 Aug 2023 14:36:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230510AbjHNOfg (ORCPT ); Mon, 14 Aug 2023 10:35:36 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33708 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230436AbjHNOfF (ORCPT ); Mon, 14 Aug 2023 10:35:05 -0400 Received: from mgamail.intel.com (mgamail.intel.com [192.55.52.115]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E5AE8E4 for ; Mon, 14 Aug 2023 07:35:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1692023704; x=1723559704; h=date:from:to:cc:subject:message-id:reply-to:references: mime-version:in-reply-to; bh=gRZPy6mHGf74LzmsrxabP7mm6fPg22EAQVGoqIlfHfk=; b=GpAFxk16Rs7qVsfDbJ/LaQIsh+H1fIP3y3V9b/PIUwag95EjzLpzwzrW AESBpntk21uVmbtlgwVozjos4AfceT0Xlz9c0qVaDI/VDb1V7Nb40rg+u UEXLocaLWKKW4Xp+If0B0/nZ4LMaEiThYL9W9XND+bd4BUoiB/zL9vuJY lIBrbipqkMramJVspWB7ixwFKmqE74mRXzv1cYRy9CReEiW97zpd597/F Sp7h6+vh7+4oEdogRnaSLZl8nRCcLFhYgd3yOkLpy0BFTMNmiJ4MrsOH5 TfGi/r98xgVjrO/oNohJFY4tw2jzjVq6Fx4x+hTEn6XiWoowPYSPl28H4 Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10802"; a="372045328" X-IronPort-AV: E=Sophos;i="6.01,172,1684825200"; d="scan'208";a="372045328" Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Aug 2023 07:35:04 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10802"; a="907259022" X-IronPort-AV: E=Sophos;i="6.01,172,1684825200"; d="scan'208";a="907259022" Received: from ideak-desk.fi.intel.com ([10.237.72.78]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Aug 2023 07:35:00 -0700 Date: Mon, 14 Aug 2023 17:35:13 +0300 From: Imre Deak To: Linux regressions mailing list , Jani Nikula Cc: Mikhail Rudenko , Thomas Zimmermann , Neil Armstrong , Dmitry Baryshkov , Maarten Lankhorst , Maxime Ripard , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org, Joonas Lahtinen , Rodrigo Vivi , Tvrtko Ursulin , David Airlie , Daniel Vetter Subject: Re: [REGRESSION] HDMI connector detection broken in 6.3 on Intel(R) Celeron(R) N3060 integrated graphics Message-ID: Reply-To: imre.deak@intel.com References: <87v8dmr6ty.fsf@gmail.com> <87il9l2ymf.fsf@gmail.com> <3df95e6d-8237-1c43-e220-a9bdb5d6e044@leemhuis.info> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3df95e6d-8237-1c43-e220-a9bdb5d6e044@leemhuis.info> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sun, Aug 13, 2023 at 03:41:30PM +0200, Linux regression tracking (Thorsten Leemhuis) wrote: Hi, > On 11.08.23 20:10, Mikhail Rudenko wrote: > > On 2023-08-11 at 08:45 +02, Thorsten Leemhuis wrote: > >> On 10.08.23 21:33, Mikhail Rudenko wrote: > >>> The following is a copy an issue I posted to drm/i915 gitlab [1] two > >>> months ago. I repost it to the mailing lists in hope that it will help > >>> the right people pay attention to it. > >> > >> Thx for your report. Wonder why Dmitry (who authored a4e771729a51) or > >> Thomas (who committed it) it didn't look into this, but maybe the i915 > >> devs didn't forward the report to them. > > For the record: they did, and Jani mentioned already. Sorry, should have > phrased this differently. > > >> Let's see if these mails help. Just wondering: does reverting > >> a4e771729a51 from 6.5-rc5 or drm-tip help as well? > > > > I've redone my tests with 6.5-rc5, and here are the results: > > (1) 6.5-rc5 -> still affected > > (2) 6.5-rc5 + revert a4e771729a51 -> not affected > > (3) 6.5-rc5 + two patches [1][2] suggested on i915 gitlab by @ideak -> not affected (!) > > > > Should we somehow tell regzbot about (3)? > > That's good to know, thx. But the more important things are: > > * When will those be merged? They are not yet in next yet afaics, so it > might take some time to mainline them, especially at this point of the > devel cycle. Imre, could you try to prod the right people so that these > are ideally upstreamed rather sooner than later, as they fix a regression? I think the patches ([1] and [2]) could be merged via the drm-intel-next (drm-intel-fixes) tree Cc'ing also stable. Jani, is this ok? > * They if possible ideally should be tagged for backporting to 6.4, as > this is a regression from the 6.3 cycle. > > But yes, let's tell regzbot that fixes are available, too: > > #regzbot fix: drm/i915: Fix HPD polling, reenabling the output poll work > as needed > > (for the record: that's the second of two patches apparently needed) > > Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat) > -- > Everything you wanna know about Linux kernel regression tracking: > https://linux-regtracking.leemhuis.info/about/#tldr > If I did something stupid, please tell me, as explained on that page. > > >> BTW, there was an earlier report about a problem with a4e771729a51 that > >> afaics was never addressed, but it might be unrelated. > >> https://lore.kernel.org/all/20230328023129.3596968-1-zhouzongmin@kylinos.cn/ > > [1] https://patchwork.freedesktop.org/patch/548590/?series=121050&rev=1 > > [2] https://patchwork.freedesktop.org/patch/548591/?series=121050&rev=1 >