From: Jerry Ling <email@example.com>
To: Thorsten Leemhuis <firstname.lastname@example.org>, <email@example.com>
Subject: Re: Regression on 5.19.12, display flickering on Framework laptop
Date: Fri, 30 Sep 2022 09:05:31 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
>If it is, simply starting with "i915.enable_psr=0" might already help.
unfortunately this didn't help.
On 9/30/22 01:10, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker.
> On 30.09.22 04:26, Jerry Ling wrote:
>> 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)
> A bisect would be good, as Greg already mentioned.
> Not my area of expertise, so it's a wild guess, but display flickering
> made me wonder if this change is the culprit:
> If it is, simply starting with "i915.enable_psr=0" might already help.
> but as I said, just a wild guess after briefly looking into the problem.
> Anyway, for the rest of this mail:
> [TLDR: I'm adding this regression report to the list of tracked
> regressions; all text from me you find below is based on a few templates
> paragraphs you might have encountered already already in similar form.]
> Thanks for the report. To be sure below issue doesn't fall through the
> cracks unnoticed, I'm adding it to regzbot, my Linux kernel regression
> tracking bot:
> #regzbot ^introduced v5.19.11..v5.19.12
> #regzbot title Display flickering on Framework laptop
> #regzbot ignore-activity
> This isn't a regression? This issue or a fix for it are already
> discussed somewhere else? It was fixed already? You want to clarify when
> the regression started to happen? Or point out I got the title or
> something else totally wrong? Then just reply -- ideally with also
> telling regzbot about it, as explained here:
> Reminder for developers: When fixing the issue, add 'Link:' tags
> pointing to the report (the mail this one replies to), as explained for
> in the Linux kernel's documentation; above webpage explains why this is
> important for tracked regressions.
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
> P.S.: As the Linux kernel's regression tracker I deal with a lot of
> reports and sometimes miss something important when writing mails like
> this. If that's the case here, don't hesitate to tell me in a public
> reply, it's in everyone's interest to set the public record straight.
next prev parent reply other threads:[~2022-09-30 13:06 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] ` <email@example.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 [this message]
2022-09-30 15:02 ` Greg KH
2022-10-03 16:42 ` David Matthew Mattli
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).