From: Paul Rolland <rol@witbe.net>
To: Christian Heusel <christian@heusel.eu>
Cc: Zack Rusin <zack.rusin@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Martin Krastev <martin.krastev@broadcom.com>,
Maaz Mombasawala <maaz.mombasawala@broadcom.com>,
dri-devel@lists.freedesktop.org,
Brad Spengler <spender@grsecurity.net>,
rdkehn@gmail.com, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev, rol@witbe.net
Subject: Re: [REGRESSION][BISECTED] vmwgfx crashes with command buffer error after update
Date: Mon, 19 Aug 2024 19:49:11 +0200 [thread overview]
Message-ID: <20240819194911.7999bec1@riri> (raw)
In-Reply-To: <0d0330f3-2ac0-4cd5-8075-7f1cbaf72a8e@heusel.eu>
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
Hello,
On Thu, 15 Aug 2024 19:48:47 +0200
Christian Heusel <christian@heusel.eu> wrote:
> While we were still debugging the issue Brad (also CC'ed) messaged me
> that they were seeing similar failures in their ESXi based test
> pipelines except for one box that was running on legacy BIOS (so maybe
> that is relevant). They noticed this because they had set panic_on_warn.
I have the same problem at home using ESXi and UEFI Bios with my VMs:
kernel 6.10.4 and 6.10.5 are showing an error with vmwgfx while booting and
there is no console available, though it's still possible to remotely
access the VMs using SSH.
Reverting to 6.10.3 solves the problem.
Regards,
Paul
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
next prev parent reply other threads:[~2024-08-19 17:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 17:48 [REGRESSION][BISECTED] vmwgfx crashes with command buffer error after update Christian Heusel
2024-08-15 17:51 ` Brad Spengler
2024-08-15 18:40 ` Zack Rusin
2024-08-15 20:30 ` Andreas Piesk
2024-08-16 18:56 ` Zack Rusin
2024-08-16 20:23 ` Andreas Piesk
2024-09-02 8:34 ` Paul Rolland
2024-09-02 8:42 ` Christian Heusel
2024-09-05 7:54 ` Paul Rolland
2024-08-19 17:49 ` Paul Rolland [this message]
2024-08-19 22:48 ` Doug Kehn
2024-08-20 10:14 ` Paul Rolland
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=20240819194911.7999bec1@riri \
--to=rol@witbe.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=christian@heusel.eu \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maaz.mombasawala@broadcom.com \
--cc=martin.krastev@broadcom.com \
--cc=rdkehn@gmail.com \
--cc=regressions@lists.linux.dev \
--cc=spender@grsecurity.net \
--cc=zack.rusin@broadcom.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