lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKnqPui5XSBgxPA0Jh9UEv72aVr1uvFqoNeON6RB-YZUj+Fr=g@mail.gmail.com>
Date: Thu, 15 Aug 2024 13:51:22 -0400
From: Brad Spengler <spender@...ecurity.net>
To: Christian Heusel <christian@...sel.eu>
Cc: Zack Rusin <zack.rusin@...adcom.com>, 
	Broadcom internal kernel review list <bcm-kernel-feedback-list@...adcom.com>, 
	Martin Krastev <martin.krastev@...adcom.com>, 
	Maaz Mombasawala <maaz.mombasawala@...adcom.com>, dri-devel@...ts.freedesktop.org, 
	rdkehn@...il.com, linux-kernel@...r.kernel.org, regressions@...ts.linux.dev
Subject: Re: [REGRESSION][BISECTED] vmwgfx crashes with command buffer error
 after update

Hi all,

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

Just to clarify, it was actually the inverse: all the legacy
BIOS-booting systems triggered the warning, and the UEFI one did not.

Thanks for the report!

-Brad

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ