From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Slade Watkins <srw@sladewatkins.net>
Cc: Jerry Ling <jiling@cern.ch>,
stable@vger.kernel.org, regressions@lists.linux.dev
Subject: Re: Regression on 5.19.12, display flickering on Framework laptop
Date: Fri, 30 Sep 2022 13:22:27 +0200 [thread overview]
Message-ID: <YzbRcyi6Evu2RrNt@kroah.com> (raw)
In-Reply-To: <03147889-B21C-449B-B110-7E504C8B0EF4@sladewatkins.net>
On Fri, Sep 30, 2022 at 07:11:19AM -0400, Slade Watkins wrote:
> Hey Greg,
>
> > On Sep 30, 2022, at 1:59 AM, Greg KH <gregkh@linuxfoundation.org> 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,
So 5.19.11 works for you, but 5.19.12 does not?
Or is it just the arch packaged kernel that does not work for you?
confused,
greg k-h
next prev parent reply other threads:[~2022-09-30 11:32 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 [this message]
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
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=YzbRcyi6Evu2RrNt@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=jiling@cern.ch \
--cc=regressions@lists.linux.dev \
--cc=srw@sladewatkins.net \
--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).