From: Thorsten Leemhuis <firstname.lastname@example.org>
To: Harald Dunkel <email@example.com>,
Javier Martinez Canillas <firstname.lastname@example.org>
Cc: Kernel Mailing List <email@example.com>,
Thomas Zimmermann <firstname.lastname@example.org>,
Subject: Re: 5.15 regression: CONFIG_SYSFB_SIMPLEFB breaks console scrolling
Date: Thu, 25 Nov 2021 13:00:11 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
On 21.11.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.
Javier, I'd be interested in your option on this.
Harald, did you have CONFIG_X86_SYSFB enabled in earlier kernel versions
(and did console scrolling work then)? The answer would help me to
decide if this a regression, as those ideally should be fixed as quickly
> TWIMC: To be sure this issue doesn't fall through the cracks unnoticed,
> I'm adding it to regzbot, my Linux kernel regression tracking bot:
> #regzbot ^introduced 8633ef82f101c040427b57d4df7b706261420b94
> #regzbot title CONFIG_SYSFB_SIMPLEFB breaks console scrolling
> #regzbot ignore-activity
> Ciao, Thorsten, your Linux kernel regression tracker.
> P.S.: If you want to know more about regzbot, check out its
> web-interface, the getting start guide, and/or the references documentation:
> The last two documents will explain how you can interact with regzbot
> yourself if your want to.
> Hint for the reporter: when reporting a regression it's in your interest
> to tell #regzbot about it in the report, as that will ensure the
> regression gets on the radar of regzbot and the regression tracker.
> That's in your interest, as they will make sure the report won't fall
> through the cracks unnoticed.
> Hint for developers: you normally don't need to care about regzbot, just
> fix the issue as you normally would. Just remember to include a 'Link:'
> tag to the report in the commit message, as explained in
> That aspect was recently was made more explicit in commit 1f57bd42b77c:
#regzbot title drm: CONFIG_SYSFB_SIMPLEFB breaks console scrolling
next prev parent reply other threads:[~2021-11-25 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <firstname.lastname@example.org>
2021-11-21 11:47 ` 5.15 regression: CONFIG_SYSFB_SIMPLEFB breaks console scrolling Thorsten Leemhuis
2021-11-25 12:00 ` Thorsten Leemhuis [this message]
2021-12-03 10:40 ` Thorsten Leemhuis
2021-12-03 11:20 ` Javier Martinez Canillas
2021-12-05 6:56 ` Thorsten Leemhuis
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).