Bug 101485

Summary:	Compiling Darktable kernel leads to segfault
Product:	Beignet	Reporter:	Bruno Pagani <bruno.n.pagani>
Component:	Beignet	Assignee:	Zhigang Gong <zhigang.gong>
Status:	RESOLVED MOVED	QA Contact:
Severity:	normal
Priority:	medium	CC:	bruno.n.pagani, xiuli.pan, yan.wang
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Bruno Pagani 2017-06-17 20:02:53 UTC

Trying to start Darktable (https://www.darktable.org/, with OpenCL forcibly enabled through opencl_disable_drivers_blacklist=true in .config/darktable/darktablerc since it’s now blacklisted) results in segfault.

There is a report at https://bugs.archlinux.org/task/54399, and another at https://bugzilla.redhat.com/show_bug.cgi?id=1460400#c10, both provide backtraces.

Please tell if you need more infos, trying more debugging steps, etc.

Comment 1 Bruno Pagani 2017-10-27 16:01:28 UTC

This bug goes away when compiling Beignet 1.3.1 with LLVM 3.9 (I was testing with 1.3.1 + LLVM 4.0 before).

I cannot test it under Beignet 1.3.2 compiled with either LLVM 3.9 or LLVM 5.0 because I get this instead:

Beignet: self-test failed: (3, 7, 5) + (5, 7, 3) returned (6, 7, 5)
See README.md or http://www.freedesktop.org/wiki/Software/Beignet/
Beignet: disabling non-working device

Comment 2 Rebecca Palmer 2018-01-04 22:46:17 UTC

The "self-test failed" message in 1.3.2 is probably https://bugs.freedesktop.org/show_bug.cgi?id=102137 - see there for a fix.

Comment 3 Bruno Pagani 2018-01-06 14:17:47 UTC

Adding this fix results in Darktable crashing again…

Comment 4 GitLab Migration User 2018-10-12 21:26:23 UTC

-- 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/beignet/beignet/issues/60.

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.