From: Roosen Henri <Henri.Roosen@ginzinger.com>
To: "deller@gmx.de" <deller@gmx.de>, "sashal@kernel.org" <sashal@kernel.org>
Cc: Kepplinger-Novakovic Martin
<Martin.Kepplinger-Novakovic@ginzinger.com>,
"simona@ffwll.ch" <simona@ffwll.ch>,
"tzimmermann@suse.de" <tzimmermann@suse.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"icb@fastmail.org" <icb@fastmail.org>,
"a.vatoropin@crpt.ru" <a.vatoropin@crpt.ru>,
"linux-fbdev@vger.kernel.org" <linux-fbdev@vger.kernel.org>,
"dri-devel@lists.freedesktop.org"
<dri-devel@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: BUG: Linux kernel regression: full screen logo
Date: Wed, 18 Nov 2026 14:23:54 +0000 [thread overview]
Message-ID: <074e66817a069dca965d9c258606f23fbcb2e1a3.camel@ginzinger.com> (raw)
Hello Helge, hello Sasha,
I have been bisecting the linux kernel for a regression, were a white
stripe occurs at the bottom of the display, when showing the bootlogo.
The bisect ended up at commit-582a89109ad9 ("fbcon: Fix KASAN slab-out-
of-bounds Read in fbcon_prepare_logo") on a v6.18.x kernel, [ Upstream
commit 94e6a058b16820e02f25e1221a4c4e713ba23550 ].
We use a custom bootlogo exactly full-screen. With your commit we get a
white bar at the bottom, which i think is about the size of the font-
height.
Our logo file has 800x480:
file logo_clut224.ppm
logo_clut224.ppm: Netpbm image data, size = 800 x 480, pixmap, ASCII
text
And the target framebuffer has the same 800x480 size:
# cat /sys/class/graphics/fb0/virtual_size
800,480
The logo does not exceed the screen size, still your patch introduces
this regression.
I'm happy to test a possible solution.
Kind regards,
Henri
next reply other threads:[~2026-11-18 14:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-18 14:23 Roosen Henri [this message]
2026-11-18 18:04 ` BUG: Linux kernel regression: full screen logo Helge Deller
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=074e66817a069dca965d9c258606f23fbcb2e1a3.camel@ginzinger.com \
--to=henri.roosen@ginzinger.com \
--cc=Martin.Kepplinger-Novakovic@ginzinger.com \
--cc=a.vatoropin@crpt.ru \
--cc=deller@gmx.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=gregkh@linuxfoundation.org \
--cc=icb@fastmail.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=simona@ffwll.ch \
--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