From: Jens Axboe <axboe@kernel.dk>
To: LKML <linux-kernel@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
avier Martinez Canillas <javierm@redhat.com>,
Helge Deller <deller@gmx.de>
Subject: REGRESSION: no console on current -git
Date: Fri, 19 Jan 2024 11:39:20 -0700 [thread overview]
Message-ID: <05ea3233-20dd-4af7-86cc-de11ad2efe84@kernel.dk> (raw)
Hi,
My trusty R7525 test box is failing to show a console, or in fact anything,
on current -git. There's no output after:
Loading Linux 6.7.0+ ...
Loading initial ramdisk ...
and I don't get a console up. I went through the bisection pain and
found this was the culprit:
commit df67699c9cb0ceb70f6cc60630ca938c06773eda
Author: Thomas Zimmermann <tzimmermann@suse.de>
Date: Wed Jan 3 11:15:11 2024 +0100
firmware/sysfb: Clear screen_info state after consuming it
Reverting this commit, and everything is fine. Looking at dmesg with a
buggy kernel, I get no frame or fb messages. On a good kernel, it looks
ilke this:
[ 1.416486] efifb: probing for efifb
[ 1.416602] efifb: framebuffer at 0xde000000, using 3072k, total 3072k
[ 1.416605] efifb: mode is 1024x768x32, linelength=4096, pages=1
[ 1.416607] efifb: scrolling: redraw
[ 1.416608] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 1.449746] fb0: EFI VGA frame buffer device
Happy to test a fix, or barring that, can someone just revert this
commit please?
--
Jens Axboe
next reply other threads:[~2024-01-19 18:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 18:39 Jens Axboe [this message]
2024-01-19 20:55 ` REGRESSION: no console on current -git Helge Deller
2024-01-19 21:01 ` Jens Axboe
2024-01-19 21:14 ` Helge Deller
2024-01-19 21:22 ` Jens Axboe
2024-01-20 0:27 ` Helge Deller
2024-01-20 0:32 ` Jens Axboe
2024-01-20 18:11 ` Mirsad Todorovac
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=05ea3233-20dd-4af7-86cc-de11ad2efe84@kernel.dk \
--to=axboe@kernel.dk \
--cc=deller@gmx.de \
--cc=javierm@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=tzimmermann@suse.de \
/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