dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Kaiwan N Billimoria <kaiwan.billimoria@gmail.com>, zackr@vmware.com
Cc: airlied@linux.ie, hdegoede@redhat.com,
	Linux-graphics-maintainer@vmware.com, javierm@redhat.com,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/vmwgfx: Fix passing partly uninitialized drm_mode_fb_cmd2 struct
Date: Wed, 21 Dec 2022 11:15:11 +0100	[thread overview]
Message-ID: <8bcf04de-47eb-cb3c-4589-ba5a67477977@leemhuis.info> (raw)
In-Reply-To: <CAPDLWs_7331QyD_Mnb9k1LrBsYopeVVbd9zDM_2R-xCoG272PA@mail.gmail.com>

Hi, this is your Linux kernel regression tracker. The relevant code here
is not my area of expertise, nevertheless a few questions:

On 21.12.22 03:23, Kaiwan N Billimoria wrote:
> [REGRESSION] ?

> Testing with 6.1, I find the same issue - VirtualBox VMs seem to hang
> on boot, though the kernel has this patch applied of course...

Maybe I'm missing something, but what made you assume that it's the same
issue? The fix for that issue talked about "garbage" in some structures
that "can cause random failures during the bringup of the fbcon." Yeah,
maybe that ca result in a hang, but I didn't see it that thread (but
maybe I missed)

> Am running VirtualBox 7.0.4 on an x86_64 Linux (Ubuntu 22.04.1) host;
> the system hangs on boot with the screen
> going blank.

A bit more details would be helpful. For example: is anything printed at
all before the system hangs? What's the last kernel that worked for you
(and is the newer kernel using a similar build configuration)? Which
graphics adapater did you configure in VirtualBox?

Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)

P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.

  reply	other threads:[~2022-12-21 10:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-21  2:23 [PATCH] drm/vmwgfx: Fix passing partly uninitialized drm_mode_fb_cmd2 struct Kaiwan N Billimoria
2022-12-21 10:15 ` Thorsten Leemhuis [this message]
2022-12-21 14:31   ` Kaiwan N Billimoria
2022-12-22 11:04 ` [PATCH] drm/vmwgfx: Fix passing partly uninitialized drm_mode_fb_cmd2 struct #forregzbot Thorsten Leemhuis
  -- strict thread matches above, loose matches on Subject: below --
2022-05-09 11:04 [PATCH] drm/vmwgfx: Fix passing partly uninitialized drm_mode_fb_cmd2 struct Hans de Goede
2022-05-09 11:52 ` Javier Martinez Canillas
2022-05-09 11:55   ` Hans de Goede
2022-05-09 12:02     ` Javier Martinez Canillas
2022-05-13  7:43       ` Thorsten Leemhuis
2022-05-13 13:25         ` Zack Rusin
2022-05-13 13:47           ` Thorsten Leemhuis
2022-05-13 14:18           ` Hans de Goede
2022-05-13 15:00             ` Zack Rusin

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=8bcf04de-47eb-cb3c-4589-ba5a67477977@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=Linux-graphics-maintainer@vmware.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=hdegoede@redhat.com \
    --cc=javierm@redhat.com \
    --cc=kaiwan.billimoria@gmail.com \
    --cc=zackr@vmware.com \
    /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;
as well as URLs for NNTP newsgroup(s).