From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 215001] Regression in 5.15, Firmware-initialized graphics console selects FB_VGA16, screen corruption
Date: Fri, 07 Jan 2022 11:31:49 +0000 [thread overview]
Message-ID: <bug-215001-2300-6SLWZVJdvs@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-215001-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=215001
--- Comment #9 from The Linux kernel's regression tracker (Thorsten Leemhuis) (regressions@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.
next prev parent reply other threads:[~2022-01-07 11:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-215001-2300@https.bugzilla.kernel.org/>
2021-11-16 9:56 ` [Bug 215001] Regression in 5.15, Firmware-initialized graphics console selects FB_VGA16, screen corruption bugzilla-daemon
2021-11-16 9:57 ` bugzilla-daemon
2022-01-06 2:39 ` bugzilla-daemon
2022-01-06 15:16 ` bugzilla-daemon
2022-01-07 2:16 ` bugzilla-daemon
2022-01-07 2:24 ` bugzilla-daemon
2022-01-07 7:52 ` bugzilla-daemon
2022-01-07 11:13 ` bugzilla-daemon
2022-01-07 11:31 ` bugzilla-daemon [this message]
2022-01-07 23:12 ` bugzilla-daemon
2022-01-08 11:16 ` bugzilla-daemon
2022-01-11 9:50 ` bugzilla-daemon
2022-01-12 2:14 ` bugzilla-daemon
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=bug-215001-2300-6SLWZVJdvs@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/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