Apparently triggered by: a6a38a038bd62e6d9558905f00bef81b5e7e6fcc Author: Grazvydas Ignotas <notasas@gmail.com> Commit: Matt Turner <mattst88@gmail.com> util/u_atomic: provide 64bit atomics where they're missing There are still some distributions trying to support unfortunate people with old or exotic CPUs that don't have 64bit atomic operations. When compiling for such a machine, gcc conveniently inserts a library call to a helper, but it's implementation is missing and we get a linker error. This allows us to provide our own implementation, which is marked weak to prefer a better implementation, should one exist. v2: changed copyright, some style adjustments v3: [mattst88] Print results with AC_MSG_CHECKING/AC_MSG_RESULT Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=93089 Signed-off-by: Grazvydas Ignotas <notasas@gmail.com> Reviewed-by: Matt Turner <mattst88@gmail.com>
I don't think this patch is at fault. The md5sum of i965_dri.so does not change with it applied.
Hi. Mark, could you please re-check this test? I tried it locally, output below. Also there are no GPU hangs at all. den@den-HP-ZBook-14u-G4:~/repositories/piglit/bin$ ./glsl-max-varyings -auto Vertical axis: Increasing numbers of varyings. Horizontal axis: Which of the varyings contains the color. GL_MAX_VARYING_FLOATS = 128 PIGLIT: {"result": "pass" } Tested on 3 different PC's with the similar setup (all with 2 monitors, laptop+additional): Ubuntu 16.04 Mesa 18.3.0-git (from 03.09), Mesa 18.0.5 (release) KBL HSW _______________________ Interesting, that on another distros test fails in different ways (but also without the hang): 1. Ubuntu 18.04 Mesa 18.3.0-git KBL 3 monitors connected Test is failing on the laptop's monitor only. If you run test on connected display - it passes. 2. Antergos Mesa 18.3.0-git (debug) KBL 2 monitors connected - fails on both of them
This test was re-enabled a while ago, and does indeed pass reliably. The bug report was in error, or something was fixed in Mesa/Kernel in the interim.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.