From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jaak Ristioja <jaak@ristioja.ee>, dri-devel@lists.freedesktop.org
Cc: Huacai Chen <chenhuacai@kernel.org>,
javierm@redhat.com, Ard Biesheuvel <ardb@kernel.org>,
Hans de Goede <hdegoede@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>
Subject: Re: Blank screen on boot of Linux 6.5 and later on Lenovo ThinkPad L570
Date: Mon, 18 Sep 2023 14:40:18 +0700 [thread overview]
Message-ID: <ZQf-4r1K1Dx_LQ5t@debian.me> (raw)
In-Reply-To: <7c50e051-eba2-09fc-da9f-023d592de457@ristioja.ee>
[-- Attachment #1: Type: text/plain, Size: 710 bytes --]
On Wed, Sep 13, 2023 at 03:02:26PM +0300, Jaak Ristioja wrote:
> Hello,
>
> Upgrading to Linux 6.5 on a Lenovo ThinkPad L570 (Integrated Intel HD
> Graphics 620 (rev 02), Intel(R) Core(TM) i7-7500U) results in a blank screen
> after boot until the display manager starts... if it does start at all.
> Using the nomodeset kernel parameter seems to be a workaround.
>
> I've bisected this to commit 60aebc9559492cea6a9625f514a8041717e3a2e4
> ("drivers/firmware: Move sysfb_init() from device_initcall to
> subsys_initcall_sync").
>
Thanks for the regression report. I'm adding it to regzbot:
#regzbot ^introduced: 60aebc9559492c
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next parent reply other threads:[~2023-09-18 7:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7c50e051-eba2-09fc-da9f-023d592de457@ristioja.ee>
2023-09-18 7:40 ` Bagas Sanjaya [this message]
[not found] ` <31bdf7b1-0ed9-4217-b459-1d857e53120b@leemhuis.info>
[not found] ` <CAAhV-H7fRpykesVUEyaTpVnFiGwpP+fPbtdrp6JwfgD=bDp06Q@mail.gmail.com>
[not found] ` <CAAhV-H7XCmbgS=N4-SE8FnASAws8hnDRZsQJgXE+dwyARaqzNw@mail.gmail.com>
2023-10-09 8:45 ` Blank screen on boot of Linux 6.5 and later on Lenovo ThinkPad L570 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
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=ZQf-4r1K1Dx_LQ5t@debian.me \
--to=bagasdotme@gmail.com \
--cc=ardb@kernel.org \
--cc=chenhuacai@kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hdegoede@redhat.com \
--cc=jaak@ristioja.ee \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
/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