View All Attachments for Bug 93091

Attachment #120097
output of "valgrind clinfo"	text/plain	2015-11-24 22:33:23 UTC	3.44 KB	no flags	Details

Attachment #120098
gdb output and backtrace for clinfo	text/plain	2015-11-24 22:34:07 UTC	5.28 KB	no flags	Details

Attachment #120146
attachment-27601-0.html	text/html	2015-11-26 14:30:35 UTC	2.27 KB	no flags	Details

<p dir="ltr">well FWIW it fixed it for me, no more crashes and clinfo and tests works. might be hw specific or a different bug.</p>
<div class="gmail_quote">On Nov 26, 2015 11:02,  &lt;<a href="mailto:bugzilla-daemon@freedesktop.org">bugzilla-daemon@freedesktop.org</a>&gt; wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
    
      
    
    <div>
      <p>
        <div>
            <b><a title="NEW - [opencl] segfault when running any opencl programs (like clinfo)" href="https://bugs.freedesktop.org/show_bug.cgi?id=93091#c9" target="_blank">Comment # 9</a>
              on <a title="NEW - [opencl] segfault when running any opencl programs (like clinfo)" href="https://bugs.freedesktop.org/show_bug.cgi?id=93091" target="_blank">bug 93091</a>
              from <span><a href="mailto:emil.l.velikov@gmail.com" title="Emil Velikov &lt;emil.l.velikov@gmail.com&gt;" target="_blank"> <span>Emil Velikov</span></a>
</span></b>
        <pre>(In reply to Samuel Pitoiset from <a href="https://bugs.freedesktop.org/show_bug.cgi?id=93091#c8" target="_blank">comment #8</a>)
<span>&gt; This segfault still happens for me using mesa git, commit
&gt; ca976e6900dc8ff457ed9dba661d037c616abc59.
&gt; 
&gt; OpenGL renderer string: Gallium 0.4 on NVE7
&gt; OpenGL core profile version string: 4.1 (Core Profile) Mesa 11.2.0-devel
&gt; (git-ca976e6)
&gt; 
&gt; #0  pipe_loader_create_screen (dev=0x0) at pipe_loader.c:79</span>

Strange... I wonder if we&#39;re getting hit by the issue pointed out to Tom -
namely we should cap the ldevs iteration in platform::platform() to the value
returned by the second call to pipe_loader_probe. Reason being that second call
to pipe_loader_probe() may return smaller count (device has gone missing,
enomem, other).

Alternatively can someone pin-point the commit that causes this (note you might
need to cherry-pick patch in <a href="https://bugs.freedesktop.org/show_bug.cgi?id=93091#c1" target="_blank">comment 1</a> to fixup commit ff9cd8a67ca).

Thanks</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You reported the bug.</li>
      </ul>
    </div>

</blockquote></div>

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.