[Mesa-dev] What branch to get patch 47790

[Meng, David]

Hi Ken:
Thank you very much for pointing out the issue.

We are using Mesa 10.4.0.  We will check a later Mesa version to see if we can resolve the problem.

I will check if we have a patch which results in blit_texture_to_pbo() is directly called by brw_blorp_blit_miptrees().

Regards,

David
-----Original Message-----
From: Kenneth Graunke [mailto:kenneth at whitecape.org] 
Sent: Tuesday, June 16, 2015 5:16 PM
To: Meng, David
Cc: mesa-dev at lists.freedesktop.org
Subject: Re: [Mesa-dev] What branch to get patch 47790

On Wednesday, June 17, 2015 12:05:05 AM Meng, David wrote:
> Hi Ken:
> Thank you for the help and clarification.
>  
> The back trace we got from the dump file is in blow.  The brw_blorp_exec()  is called in the thread 1. 
> 
> We do not have other major patches in the Mesa but some small patches.  I can find them if you need.
> 
> Regards,
> 
> David
> --------------back trace---------------------------------------------
> Thread 3 (Thread 38344):
> #0  0x00000000077cccac in pthread_cond_wait@@GLIBC_2.3.2 () from 
> /lib64/libpthread.so.0
> #1  0x000000000623d9c1 in ?? ()
> #2  0x00000000065d2f82 in ?? ()
> #3  0x0000000006245a38 in ?? ()
> #4  0x00000000077c8ddc in start_thread () from /lib64/libpthread.so.0
> #5  0x000000000860f12d in clone () from /lib64/libc.so.6
> 
> Thread 2 (Thread 38341):
> #0  0x000000000623c77f in ?? ()
> #1  0x000000000623c7ff in ?? ()
> #2  0x000000000623c4c4 in ?? ()
> #3  0x0000000006294047 in ?? ()
> #4  0x00000000060a2d0b in ?? ()
> #5  0x0000000006018135 in ?? ()
> #6  0x0000000006019654 in ?? ()
> #7  0x00000000060164b6 in main ()
> 
> Thread 1 (Thread 38345):
> #0  0x00000000065d5942 in ?? ()
> #1  0x0000000006018991 in ?? ()
> #2  0x00000000065d5816 in ?? ()
> #3  <signal handler called>
> #4  0x000000000857014e in raise () from /lib64/libc.so.6
> #5  0x00000000085715fb in abort () from /lib64/libc.so.6
> #6  0x0000000008568e4d in __assert_fail () from /lib64/libc.so.6
> #7  0x000000000ad1fd97 in brw_blorp_exec (brw=0x32d55360, 
> params=0x3ffc38b1270) at brw_blorp.cpp:241
> #8  0x000000000ad20c40 in brw_blorp_blit_miptrees (brw=0x32d55360, 
> src_mt=0x337b02a0, src_level=0, src_layer=1, 
> src_format=MESA_FORMAT_R8G8B8A8_SRGB, dst_mt=0x337bb4c0, dst_level=0, 
> dst_layer=0, dst_format=MESA_FORMAT_B8G8R8A8_SRGB, src_x0=0, src_y0=0, 
> src_x1=32, src_y1=32, dst_x0=0, dst_y0=0, dst_x1=32, dst_y1=32, 
> filter=9728, mirror_x=false, mirror_y=false) at brw_blorp_blit.cpp:96
> #9  0x000000000ad1cd52 in blit_texture_to_pbo (ctx=0x32d55360, 
> format=32993, type=33639, pixels=0x0, texImage=0x337b04e0) at 
> intel_tex_image.c:531
> #10 0x000000000ad1cdf2 in intel_get_tex_image (ctx=0x32d55360, 
> format=32993, type=33639, pixels=0x0, texImage=0x337b04e0) at 
> intel_tex_image.c:551
> #11 0x000000000aac5ab6 in _mesa_GetnTexImageARB (target=34070, 
> level=0, format=32993, type=33639, bufSize=2147483647, pixels=0x0) at 
> ../../src/mesa/main/texgetimage.c:949
> #12 0x000000000aac5b13 in _mesa_GetTexImage (target=34070, level=0, 
> format=32993, type=33639, pixels=0x0) at 
> ../../src/mesa/main/texgetimage.c:959
> #13 0x0000000009a4a19b in shared_dispatch_stub_281 (target=34070, 
> level=0, format=32993, type=33639, pixels=0x0) at 
> ../../src/mapi/shared-glapi/glapi_mapi_tmp.h:16289
> #14 0x00000000062d1360 in ?? ()
> #15 0x00000000062cd9fd in ?? ()
> #16 0x00000000062f8b24 in ?? ()
> #17 0x00000000062f8be3 in ?? ()
> #18 0x00000000062ac937 in ?? ()
> #19 0x0000000006294f25 in ?? ()
> #20 0x00000000062a9073 in ?? ()
> #21 0x0000000006245a38 in ?? ()
> #22 0x00000000077c8ddc in start_thread () from /lib64/libpthread.so.0
> 
> Following is the back trace we get from the dump file:

Note that blit_texture_to_pbo has been deleted in commit 779923194c65e, which was in Mesa 10.5.0.  You must be using some older version of Mesa; it may just work if you update to a newer version.

But I'm confused.  Even when it existed, blit_texture_to_pbo() never directly called brw_blorp_blit_miptrees().  It used the BLT engine.

So I'm suspicious that this is caused by a patch in your tree.

--Ken