Project

General

Profile

Bug #10912

DT freeze when exporting Canon G1X Mark II RAW to JPEG

Added by Michael Ertl over 3 years ago. Updated over 3 years ago.

Status:
New
Priority:
Low
Category:
General
Target version:
-
Start date:
02/11/2016
Due date:
% Done:

0%

Estimated time:
Affected Version:
2.0.1
System:
other GNU/Linux
bitness:
64-bit
hardware architecture:
amd64/x86

Description

When I export a Canon G1X Mark II RAW to JPEG with OpenCL support there always happens a "NMI watchdog: BUG: soft lockup - CPU#n stuck for xxs! Which means that DT and also the desktop freezes for quite a while. Without OpenCL support the export works fine. Attached you find some logs which are hopefully a help for you.

I don't know if this is a bug in LR or a problem with my configuration, but it is the same behavior with Antergos ARCH linux (kernel 4.4.2) and Linux Mint LMDE2 (kernel 4.2) both using the cinnamon desktop.

dt.log (18.9 KB) dt.log Michael Ertl, 02/11/2016 09:07 PM
dmesg.log (79.5 KB) dmesg.log Michael Ertl, 02/11/2016 09:07 PM
inxi.log (1.91 KB) inxi.log Michael Ertl, 02/11/2016 09:07 PM

History

#1 Updated by Roman Lebedev over 3 years ago

  • Assignee set to Ulrich Pegelow
  • Category changed from Lighttable to General

I don't know if this is a bug in LR or a problem with my configuration,

Hm? :)

I guess those logs are for upstream - nvidia.

But

[opencl_init] device 0 `Quadro FX 880M' allows GPU memory allocations of up to 255MB

tells me that you should not even try to use opencl with that card.

@Pegelow: are you sure opencl_memory_requirement should be checked against CL_DEVICE_GLOBAL_MEM_SIZE, not CL_DEVICE_MAX_MEM_ALLOC_SIZE?

#2 Updated by Ulrich Pegelow over 3 years ago

The watchdog timer in NVIDIA cards is meant to detect lockups. However, with a very slow card even ordinary kernels can take such a long time that the timeout of the watchdog is reached and the kernel gets interrupted. I guess that darktable survives this situation and continues to process on the CPU but overall it's a waste of resources. Such a slow card is not suited for darktable.

@Pegelow: are you sure opencl_memory_requirement should be checked against CL_DEVICE_GLOBAL_MEM_SIZE, not CL_DEVICE_MAX_MEM_ALLOC_SIZE?

Yes, at that place we want to avoid under-equipped graphics cards. We later check CL_DEVICE_MAX_MEM_ALLOC_SIZE when it comes to tiling. A maximum of 255MB is not an issue in itself and can be easily coped with in a tiling context.

Also available in: Atom PDF

Go to top