All of lore.kernel.org
 help / color / mirror / Atom feed
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 23:12:41 +0000	[thread overview]
Message-ID: <bug-215001-2300-cnkDCf3rNZ@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 #10 from Kris Karas (bugs-a21@moonlit-rail.com) ---
Hi Thorsten -

Thanks for the helpful pointer on bug reporting (comment 9).  I've been so used
to dealing with LKML and Bugzilla (since 1993) that I'd rather forgotten about
Lore.  :-)

I didn't know whether the regression trackers were a real "bot" sort of thing,
or just folks pitching in to try to keep track by hand.  Good to know that it's
still human-powered.

I've got another bug to file now, multiple flavors of OOPSen showing up on boot
in _kmalloc due to creation/manipulation of network devices (bridges, veth),
perhaps as a result of the "igb" patches in 5.15 as it seems hardware-specific.
 I'll try to cc those lists when I have it bisected or narrowed down a bit...

Kris

-- 
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.

  parent reply	other threads:[~2022-01-07 23:12 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
2022-01-07 23:12 ` bugzilla-daemon [this message]
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-cnkDCf3rNZ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.