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 64472C433FE for ; Mon, 3 Oct 2022 18:12:43 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229674AbiJCSMk (ORCPT ); Mon, 3 Oct 2022 14:12:40 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56826 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230010AbiJCSMi (ORCPT ); Mon, 3 Oct 2022 14:12:38 -0400 Received: from mga18.intel.com (mga18.intel.com [134.134.136.126]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 044473743A for ; Mon, 3 Oct 2022 11:12:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1664820756; x=1696356756; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=/pXCfP6FdVNBhKTPRNvFzyvMpsR1lB5zHpZEUGiHdqs=; b=Myi4IxkQ1diuvGyAttPDX0rWvOxtGJX9LV5RJVhECQBLBkWVmZxdiKJC NIQllD3wO32JMVSyJ8CFdAxMS2dokVkrM9/+Z+tPXuh1Aez38wsmsuFKn /b2PSBzdvArStwD9wivXRxrCYxwKT/5L4EBLCHstxFGBjKkYNT8/RtubY QfR+ccDqDAidpqjR8v7EdegRgBZEMJga4ez+Gt1n+biZShuziq9Xpwjb1 5fc227b/9dn1yl8rLJV9hM/j25/DKZlT/DvmtKLPG4036EBB8BFsH+TsY JFaUmUMvnOWNaDpabT4r35AziN0cl4crMlIz2ZrpyhSEJbWil1ksfZBmp w==; X-IronPort-AV: E=McAfee;i="6500,9779,10489"; a="285891991" X-IronPort-AV: E=Sophos;i="5.93,366,1654585200"; d="scan'208";a="285891991" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga106.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 03 Oct 2022 10:48:46 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10489"; a="766020930" X-IronPort-AV: E=Sophos;i="5.93,366,1654585200"; d="scan'208";a="766020930" Received: from stinkpipe.fi.intel.com (HELO stinkbox) ([10.237.72.191]) by fmsmga001.fm.intel.com with SMTP; 03 Oct 2022 10:48:42 -0700 Received: by stinkbox (sSMTP sendmail emulation); Mon, 03 Oct 2022 20:48:41 +0300 Date: Mon, 3 Oct 2022 20:48:41 +0300 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= To: Thorsten Leemhuis Cc: stable@vger.kernel.org, regressions@lists.linux.dev, Greg Kroah-Hartman , Slade Watkins , Jerry Ling , intel-gfx@lists.freedesktop.org Subject: Re: Regression on 5.19.12, display flickering on Framework laptop Message-ID: References: <55905860-adf9-312c-69cc-491ac8ce1a8b@cern.ch> <03147889-B21C-449B-B110-7E504C8B0EF4@sladewatkins.net> 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 Precedence: bulk List-ID: X-Mailing-List: stable@vger.kernel.org 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. > > This bug report is probably the same thing: > https://gitlab.freedesktop.org/drm/intel/-/issues/7013 Also cc intel-gfx... > > > > > Did anyone check if a revert on top of 5.19.12 works easily and solves > > the problem? > > > > And does anybody known if mainline affected, too? > > > > Ciao, Thorsten > > > > > > > On 9/30/22 07:11, Slade Watkins wrote: > > >> Hey Greg, > > >> > > >>> On Sep 30, 2022, at 1:59 AM, Greg KH wrote: > > >>> > > >>> On Fri, Sep 30, 2022 at 06:37:48AM +0200, Greg KH wrote: > > >>>> On Thu, Sep 29, 2022 at 10:26:25PM -0400, Jerry Ling wrote: > > >>>>> Hi, > > >>>>> > > >>>>> It has been reported by multiple users across a handful of distros > > >>>>> that > > >>>>> there seems to be regression on Framework laptop (which presumably > > >>>>> is not > > >>>>> that special in terms of mobo and display) > > >>>>> > > >>>>> Ref: > > >>>>> https://community.frame.work/t/psa-dont-upgrade-to-linux-kernel-5-19-12-arch1-1-on-arch-linux-gen-11-model/23171 > > >>>> Can anyone do a 'git bisect' to find the offending commit? > > >>> Also, this works for me on a gen 12 framework laptop: > > >>>     $ uname -a > > >>>     Linux frame 5.19.12 #68 SMP PREEMPT_DYNAMIC Fri Sep 30 07:02:33 > > >>> CEST 2022 x86_64 GNU/Linux > > >>> > > >>> so there's something odd with the older hardware? > > >>> > > >>> greg k-h > > >> Could be. Running git bisect for 5.19.11 and 5.19.12 (as suggested by > > >> the linked forum thread) returned nothing on gen 11 for me. > > >> > > >> This is very odd, > > >> -srw > > > > > > > > -- > Ville Syrjälä > Intel -- Ville Syrjälä Intel