From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 5F35933ED for ; Tue, 4 Oct 2022 13:44:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1664891080; x=1696427080; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=eSBe9smtoV7qkYQconvXq2pg50vA/fg0vgTMB4G1NN8=; b=eKkuqxAPUL6LL8X0+3Vwonr9FHQeTrOOii9nwMBcsrHRz3EvsOnD6sGd coq1zDkDbTZbr0zadsM0wMYJIwVuqiW398dwmQM5Bfldw9ix1kN8SzwI1 mDh0c2VqV8l8K6nfOuV4/maHksIym3tBoc+rKTE403twdKHRgrum1ocuv 0lk/ymS1nM64Mx1TxR6bB2w5eJ5Awhb9S742+US+l7ssUHejQn066Lzg9 uGxlisV1jPhIVJBiCZvbUn68IzHGeAZE+39OYlMaDTbQTsSmv2v+TPaS3 t8vHptH4JcZarRQ8opqnClmaF0790uXDusEMw3PN/dRPHQ+9y2tFO34U3 g==; X-IronPort-AV: E=McAfee;i="6500,9779,10490"; a="304454670" X-IronPort-AV: E=Sophos;i="5.95,158,1661842800"; d="scan'208";a="304454670" Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Oct 2022 06:44:39 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10490"; a="713013640" X-IronPort-AV: E=Sophos;i="5.95,158,1661842800"; d="scan'208";a="713013640" Received: from stinkpipe.fi.intel.com (HELO stinkbox) ([10.237.72.191]) by FMSMGA003.fm.intel.com with SMTP; 04 Oct 2022 06:44:36 -0700 Received: by stinkbox (sSMTP sendmail emulation); Tue, 04 Oct 2022 16:44:35 +0300 Date: Tue, 4 Oct 2022 16:44:35 +0300 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= To: Greg Kroah-Hartman Cc: David Matthew Mattli , Thorsten Leemhuis , stable@vger.kernel.org, regressions@lists.linux.dev, Slade Watkins , Jerry Ling , intel-gfx@lists.freedesktop.org Subject: Re: Regression on 5.19.12, display flickering on Framework laptop Message-ID: References: <03147889-B21C-449B-B110-7E504C8B0EF4@sladewatkins.net> <714903fa-16c8-4247-d69d-74af6ef50bfa@leemhuis.info> <9aae6b15-265a-4ef9-87c1-83dfe5094378@smtp-relay.sendinblue.com> Precedence: bulk X-Mailing-List: regressions@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Patchwork-Hint: comment On Tue, Oct 04, 2022 at 03:40:55PM +0200, Greg Kroah-Hartman wrote: > On Tue, Oct 04, 2022 at 06:46:10AM -0500, David Matthew Mattli wrote: > > Thorsten Leemhuis writes: > > > > > On 03.10.22 19:48, Ville Syrjälä wrote: > > >> On Mon, Oct 03, 2022 at 08:45:18PM +0300, Ville Syrjälä wrote: > > >>> On Sat, Oct 01, 2022 at 12:07:39PM +0200, Thorsten Leemhuis wrote: > > >>>> On 30.09.22 14:26, Jerry Ling wrote: > > >>>>> > > >>>>> looks like someone has done it: > > >>>>> https://bbs.archlinux.org/viewtopic.php?pid=2059823#p2059823 > > >>>>> > > >>>>> and the bisect points to: > > >>>>> > > >>>>> |# first bad commit: [fc6aff984b1c63d6b9e54f5eff9cc5ac5840bc8c] > > >>>>> drm/i915/bios: Split VBT data into per-panel vs. global parts Best, Jerry > > | > > >>>> > > >>>> FWIW, that's 3cf050762534 in mainline. Adding Ville, its author to the > > >>>> list of recipients. > > >>> > > >>> I definitely had no plans to backport any of that stuff, > > >>> but I guess the automagics did it anyway. > > >>> > > >>> Looks like stable is at least missing this pile of stuff: > > >>> 50759c13735d drm/i915/pps: Keep VDD enabled during eDP probe > > >>> 67090801489d drm/i915/pps: Reinit PPS delays after VBT has been fully > > parsed > > >>> 8e75e8f573e1 drm/i915/pps: Split PPS init+sanitize in two > > >>> 586294c3c186 drm/i915/pps: Stash away original BIOS programmed PPS delays > > >>> 89fcdf430599 drm/i915/pps: Don't apply quirks/etc. to the VBT PPS > > >>> delays if they haven't been initialized > > >>> 60b02a09598f drm/i915/pps: Introduce pps_delays_valid() > > >>> > > >>> But dunno if even that is enough. > > > > > > If you need testers: David (now CCed) apparently has a affected machine > > > and offered to test patches in a different subthread of this thread. > > > > > > > I cherry-picked the six commits Thorsten listed onto 5.19.12 and it > > resolved the issue on my Framework laptop. > > Thanks for testing, but I'm just going to revert the offending commits > as they probably shouldn't all be added to 5.19.y Yeah, revert seems the safer route. Thanks. -- Ville Syrjälä Intel