[Mesa-dev] What branch to get patch 47790

Kenneth Graunke kenneth at whitecape.org
Tue Jun 16 16:56:02 PDT 2015

On Tuesday, June 16, 2015 11:34:17 PM Meng, David wrote:
> Hi Ken:
> Thank you very much for your quick response.
> I have been developing a GPU driver for VMware ESXi kernel.  ESXi kernel is a virtualized hypervisor and our GPU driver provides graphics support for that kernel. We used Mesa libraries in the user space.  The kernel driver and Mesa library work fine on HSW and IVB systems.  But we found that the Mesa (10.4.0) hits the unreachable code when we launching VM on the BDW system.  Launching a VM is equivalent to starting a 3D graphics application on Linux system.
> The assert happens in following function:
> brw_blorp_exec(struct brw_context *brw, const brw_blorp_params *params)

BLORP should never be used on Gen8, currently.  Could you post a
backtrace (in gdb, run 'bt') that shows what's calling it?

Alternatively, do you have additional patches to your Mesa tree that
might cause it to be called?  brw_blorp_exec should never be called with
upstream Mesa.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.freedesktop.org/archives/mesa-dev/attachments/20150616/10260710/attachment.sig>

More information about the mesa-dev mailing list