From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107940] libdrm 2.4.94-1 causes blender to crash on opencl
Date: Mon, 24 Sep 2018 09:10:00 +0000 [thread overview]
Message-ID: <bug-107940-502-W1gyuvncO5@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-107940-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 945 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107940
Michel Dänzer <michel@daenzer.net> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |ckoenig.leichtzumerken@gmai
| |l.com
--- Comment #6 from Michel Dänzer <michel@daenzer.net> ---
(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
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2396 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-09-24 9:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-14 17:37 [Bug 107940] libdrm 2.4.94-1 causes blender to crash on opencl bugzilla-daemon
2018-09-14 17:38 ` bugzilla-daemon
2018-09-17 9:44 ` bugzilla-daemon
2018-09-17 9:58 ` bugzilla-daemon
2018-09-22 13:56 ` bugzilla-daemon
2018-09-22 20:58 ` bugzilla-daemon
2018-09-24 9:10 ` bugzilla-daemon [this message]
2018-09-24 9:53 ` bugzilla-daemon
2019-09-24 17:09 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-107940-502-W1gyuvncO5@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox