[Bug 215001] Regression in 5.15, Firmware-initialized graphics console selects FB_VGA16, screen corruption

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Fri Jan 7 11:31:49 UTC 2022


https://bugzilla.kernel.org/show_bug.cgi?id=215001

--- Comment #9 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions at leemhuis.info) ---
(In reply to Kris Karas from comment #7)
> 
> ... I filed this bug nearly 2 months ago with the "Regression = Y" metadata
> clearly set; but the various kernel regression trackers

Which trackers? Humans or software? I'm running a bot, but that is still in the
early stages -- and has no bugzilla integration as of now (but it's on the todo
list, but only in the middle), as the kernel's docs discourage from using it
most of the time. See
https://www.kernel.org/doc/html/latest/admin-guide/reporting-issues.html
(written by yours truly). See also the last section of that document.

> What's the best way to get a bugzilla report
> for a regression tracked so that it doesn't get forgotten or lost in the
> shuffle?

Docs on that are in the work:
https://lore.kernel.org/linux-doc/cover.1641203216.git.linux@leemhuis.info/

>  For example, bug 199533 was filed back in 2018, with a proper
> bisect even, but hasn't garnered even so much as a single comment. 
> (Probably ought to be closed as I no longer have the hardware to test a fix
> :-)

There are many things wrt kernel bug/regression reporting that IMHO need to be
fixed or improved. I'm working on this, but I'm mostly doing it in my spare
time (except for the regzbot, for which I found external funding).

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are on the CC list for the bug.


More information about the dri-devel mailing list