From: Thorsten Leemhuis <email@example.com>
To: Javier Martinez Canillas <firstname.lastname@example.org>,
Harald Dunkel <email@example.com>
Cc: Kernel Mailing List <firstname.lastname@example.org>,
Thomas Zimmermann <email@example.com>,
Subject: Re: 5.15 regression: CONFIG_SYSFB_SIMPLEFB breaks console scrolling
Date: Sun, 5 Dec 2021 07:56:11 +0100 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Hi, this is your Linux kernel regression tracker speaking.
On 03.12.21 12:20, Javier Martinez Canillas wrote:
> Sorry for the late reply.
> On 11/21/21 12:47, Thorsten Leemhuis wrote:
>> Hi, this is your Linux kernel regression tracker speaking.
>> On 16.11.21 05:52, Harald Dunkel wrote:
>>> if I enable CONFIG_SYSFB_SIMPLEFB in 5.15.2 and use grub's default
>>> (Debian sid amd64), then a few lines at the bottom of /dev/tty1 including
>>> login prompt are off-screen. Scrolling is broken. I can login, though.
>>> Enabling GRUB_TERMINAL=console in grub doesn't make a difference. Using
>>> the same kernel except for CONFIG_SYSFB_SIMPLEFB the problem is gone.
>>> Graphics card is a GeForce GTX 1650. I tried with both CONFIG_DRM_NOUVEAU
>>> and proprietary graphics drivers disabled.
>>> Attached you can find the config file. Please mail if I can help to track
>>> this problem down.
>> Thx for the report. I'm not totally sure if this is a regression, as
>> that's a new config option. But it might be one considered a successor
>> to an older one, hence it might count as regression. Adding two
>> developers and a mailing list to the CC, hopefully someone can clarify.
> I don't think this is a regression since enabling CONFIG_SYSFB_SIMPLEFB will
> make the simpledrm driver to be bound while disabling the option makes the
> efifb driver to be bound instead.
> Yes, it seems to be a bug in the simpledrm driver but the solution if you
> have issues with the simpledrm is to not enable CONFIG_SYSFB_SIMPLEFB and
> keep using the old fbdev driver.
Mandy thx for the answer, Javier. Harald is quiet for some time already
and didn't object so far, hence I'll remove this from regzbot:
#regzbot invalid: problem caused by a new CONFIG option
P.S.: As a Linux kernel regression tracker I'm getting a lot of reports
on my table. I can only look briefly into most of them. Unfortunately
therefore I sometimes will get things wrong or miss something important.
I hope that's not the case here; if you think it is, don't hesitate to
tell me about it in a public reply. That's in everyone's interest, as
what I wrote above might be misleading to everyone reading this; any
suggestion I gave they thus might sent someone reading this down the
wrong rabbit hole, which none of us wants.
BTW, I have no personal interest in this issue, which is tracked using
regzbot, my Linux kernel regression tracking bot
(https://linux-regtracking.leemhuis.info/regzbot/). I'm only posting
this mail to get things rolling again and hence don't need to be CC on
all further activities wrt to this regression.
prev parent reply other threads:[~2021-12-05 6:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <email@example.com>
2021-11-21 11:47 ` 5.15 regression: CONFIG_SYSFB_SIMPLEFB breaks console scrolling Thorsten Leemhuis
2021-11-25 12:00 ` Thorsten Leemhuis
2021-12-03 10:40 ` Thorsten Leemhuis
2021-12-03 11:20 ` Javier Martinez Canillas
2021-12-05 6:56 ` Thorsten Leemhuis [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).