From: Paul Rolland <rol@witbe.net>
To: Zack Rusin <zack.rusin@broadcom.com>
Cc: Doug Kehn <rdkehn@gmail.com>,
Christian Heusel <christian@heusel.eu>,
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>,
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: Tue, 20 Aug 2024 12:14:26 +0200 [thread overview]
Message-ID: <20240820121426.5d0fa1ee@riri> (raw)
In-Reply-To: <CAKrfnYfNsLnyWHYmjZOFMKcncGc_ewFFAoYg4GQwd3cBkTNymA@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 220 bytes --]
Hello,
On Mon, 19 Aug 2024 17:48:45 -0500
Doug Kehn <rdkehn@gmail.com> wrote:
> Attached is a log from a BIOS system.
And a log from a UEFI VM, this test was done with 6.10.6 from el-repo.
Regards,
Paul
[-- Attachment #1.2: dmesg-6106-vmwgfx-crash.log.gz --]
[-- Type: application/gzip, Size: 26201 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2024-08-20 10:14 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
2024-08-19 22:48 ` Doug Kehn
2024-08-20 10:14 ` Paul Rolland [this message]
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=20240820121426.5d0fa1ee@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 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.