From: Javier Martinez Canillas <javierm@redhat.com>
To: Huacai Chen <chenhuacai@kernel.org>,
Thorsten Leemhuis <regressions@leemhuis.info>
Cc: Linux regressions mailing list <regressions@lists.linux.dev>,
Thomas Zimmermann <tzimmermann@suse.de>,
Evan Preston <x.arch@epreston.net>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux DRI Development <dri-devel@lists.freedesktop.org>,
Jaak Ristioja <jaak@ristioja.ee>,
Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: Blank screen on boot of Linux 6.5 and later on Lenovo ThinkPad L570
Date: Wed, 25 Oct 2023 15:29:24 +0200 [thread overview]
Message-ID: <87v8auhlu3.fsf@minerva.mail-host-address-is-not-set> (raw)
In-Reply-To: <CAAhV-H5DH3Oj3ttSpa_k6jUdZ+0_pMwgoaqUTGGFr46j7DMXRw@mail.gmail.com>
Huacai Chen <chenhuacai@kernel.org> writes:
Hello,
> On Wed, Oct 25, 2023 at 6:08 PM Thorsten Leemhuis
> <regressions@leemhuis.info> wrote:
[...]
>>
>> This additional report makes me wonder if we should revert the culprit
>> (60aebc9559492c ("drivers/firmware: Move sysfb_init() from
>> device_initcall to subsys_initcall_sync") [v6.5-rc1]). But I guess that
>> might lead to regressions for some users? But the patch description says
>> that this is not a common configuration, so can we maybe get away with that?
> From my point of view, this is not a regression, 60aebc9559492c
> doesn't cause a problem, but exposes a problem. So we need to fix the
> real problem (SIMPLEDRM has a blank screen on some conditions). This
> needs Jaak or Evan's help.
>
I agree with this.
> Huacai
--
Best regards,
Javier Martinez Canillas
Core Platforms
Red Hat
next prev parent reply other threads:[~2023-10-25 13:29 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-13 12:02 Blank screen on boot of Linux 6.5 and later on Lenovo ThinkPad L570 Jaak Ristioja
2023-09-18 7:40 ` Bagas Sanjaya
2023-09-26 11:15 ` Linux regression tracking (Thorsten Leemhuis)
2023-09-26 14:31 ` Huacai Chen
2023-10-09 1:27 ` Huacai Chen
2023-10-09 8:45 ` Bagas Sanjaya
2023-10-09 8:54 ` Huacai Chen
2023-10-20 9:35 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-20 9:48 ` Huacai Chen
2023-10-22 22:54 ` Evan Preston
2023-10-25 10:08 ` Thorsten Leemhuis
2023-10-25 13:23 ` Huacai Chen
2023-10-25 13:29 ` Javier Martinez Canillas [this message]
2023-10-25 13:42 ` Linux regression tracking (Thorsten Leemhuis)
2023-10-25 18:49 ` Jaak Ristioja
2023-10-26 0:58 ` Huacai Chen
2023-10-28 11:06 ` Jaak Ristioja
2023-10-29 1:42 ` Huacai Chen
2023-10-31 12:17 ` Huacai Chen
2023-11-01 11:52 ` Jaak Ristioja
2023-11-02 12:38 ` Huacai Chen
2023-11-03 5:45 ` Evan Preston
2023-11-03 6:36 ` Huacai Chen
2023-11-04 2:32 ` Evan Preston
2023-11-05 12:40 ` Huacai Chen
2023-11-05 16:28 ` Jaak Ristioja
2023-11-06 2:15 ` Huacai Chen
2023-11-06 13:49 ` Jaak Ristioja
2023-11-06 14:22 ` Huacai Chen
2023-11-06 20:32 ` Evan Preston
2023-11-07 1:49 ` Huacai Chen
2023-11-07 5:39 ` Evan Preston
2023-11-08 5:23 ` Evan Preston
2023-11-08 2:52 ` Huacai Chen
2023-12-11 3:31 ` Huacai Chen
2023-11-05 21:10 ` Evan Preston
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=87v8auhlu3.fsf@minerva.mail-host-address-is-not-set \
--to=javierm@redhat.com \
--cc=bagasdotme@gmail.com \
--cc=chenhuacai@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jaak@ristioja.ee \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=tzimmermann@suse.de \
--cc=x.arch@epreston.net \
/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).