From: Jerry Ling <jiling@cern.ch>
To: Slade Watkins <srw@sladewatkins.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: <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 08:26:40 -0400 [thread overview]
Message-ID: <aa8b9724-50c6-ae2e-062d-3791144ac97e@cern.ch> (raw)
In-Reply-To: <03147889-B21C-449B-B110-7E504C8B0EF4@sladewatkins.net>
Hi,
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 |
On 9/30/22 07:11, 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,
> -srw
next prev parent reply other threads:[~2022-09-30 12:27 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 [this message]
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=aa8b9724-50c6-ae2e-062d-3791144ac97e@cern.ch \
--to=jiling@cern.ch \
--cc=gregkh@linuxfoundation.org \
--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).