Summary: | libdrm 2.4.94-1 causes blender to crash on opencl | ||
---|---|---|---|
Product: | DRI | Reporter: | Mowley <yachtsoma> |
Component: | libdrm | Assignee: | Default DRI bug account <dri-devel> |
Status: | RESOLVED MOVED | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | ckoenig.leichtzumerken |
Version: | XOrg git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Mowley
2018-09-14 17:37:08 UTC
can provide more info if required but was unsure as to what specifically I should attach in order to help. Can you bisect? Please attach the Xorg log file and the output of dmesg and xrandr. I've found the commit that introduces this bug: 7aa1a511336dd7cb26dafef81d76edd6978a6cdf (In reply to Augusto Fraga Giachero from comment #4) > I've found the commit that introduces this bug: > 7aa1a511336dd7cb26dafef81d76edd6978a6cdf I'm guessing that my XOrg log file would now be superfluous? (In reply to Mowley from comment #5) > I'm guessing that my XOrg log file would now be superfluous? Yeah, actually comment 3 was intended for another bug report, sorry. Christian, any idea how the commit below could cause this? commit 7aa1a511336dd7cb26dafef81d76edd6978a6cdf Author: Christian König <christian.koenig@amd.com> Date: Wed Aug 1 20:44:44 2018 +0200 amdgpu: stop using the hash table for fd_tab (In reply to Michel Dänzer from comment #6) > Christian, any idea how the commit below could cause this? -EBADF means the file descriptor number is already closed. So maybe the application is trying to open/close the device multiple times and we have a bug in amdgpu_device_free_internal? Christian. -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/drm/issues/22. |
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.