stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Matthew Mattli <dmm@mattli.us>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Jerry Ling <jiling@cern.ch>,
	Thorsten Leemhuis <regressions@leemhuis.info>,
	stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: Regression on 5.19.12, display flickering on Framework laptop
Date: Mon, 03 Oct 2022 11:42:25 -0500	[thread overview]
Message-ID: <87y1twkgem.fsf@mattli.us> (raw)
In-Reply-To: <YzcE/YEKcUDzuES/@kroah.com> (Greg KH's message of "Fri, 30 Sep 2022 17:02:21 +0200")

Greg KH <gregkh@linuxfoundation.org> writes:

> On Fri, Sep 30, 2022 at 09:05:31AM -0400, Jerry Ling wrote:
>> > If it is, simply starting with "i915.enable_psr=0" might already help.
>> 
>> unfortunately this didn't help.
>
> Ick.  Ok, can you test your own kernel build out?  If I provide a patch
> that reverts the what I think are offending commits, can you test it?
>
> Also, does 6.0-rc7 also have this same problem?  That should be tested
> first here, and if that's a problem, then we can get the i915 developers
> involved.

5.19.11 and 6.0 work fine on my 12th gen Framework. 5.19.12 has the
flickering problem that's unaffected by "i915.enable_psr=0".

I'm also available to test patches if needed.

>
> thanks,
>
> greg k-h

thanks,

David Mattli

      reply	other threads:[~2022-10-03 16:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-30  2:26 Regression on 5.19.12, display flickering on Framework laptop Jerry Ling
2022-09-30  4:37 ` Greg KH
2022-09-30  5:59   ` Greg KH
2022-09-30 11:11     ` Slade Watkins
2022-09-30 11:22       ` Greg Kroah-Hartman
2022-09-30 11:56         ` Slade Watkins
2022-09-30 12:26       ` Jerry Ling
2022-09-30 12:49         ` Slade Watkins
2022-10-01 10:07         ` Thorsten Leemhuis
2022-10-01 12:34           ` Hans de Goede
2022-10-03 17:45           ` Ville Syrjälä
2022-10-03 17:48             ` Ville Syrjälä
2022-10-03 18:28               ` Thorsten Leemhuis
2022-10-04 12:35                 ` Ville Syrjälä
2022-10-04 12:57                   ` Greg Kroah-Hartman
     [not found]                 ` <9aae6b15-265a-4ef9-87c1-83dfe5094378@smtp-relay.sendinblue.com>
2022-10-04 13:40                   ` Greg Kroah-Hartman
2022-10-04 13:44                     ` Ville Syrjälä
2022-10-04 14:28                       ` Greg Kroah-Hartman
2022-09-30  5:10 ` Thorsten Leemhuis
2022-09-30 13:05   ` Jerry Ling
2022-09-30 15:02     ` Greg KH
2022-10-03 16:42       ` David Matthew Mattli [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87y1twkgem.fsf@mattli.us \
    --to=dmm@mattli.us \
    --cc=gregkh@linuxfoundation.org \
    --cc=jiling@cern.ch \
    --cc=regressions@leemhuis.info \
    --cc=regressions@lists.linux.dev \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).