hashcat Forum

Full Version: LUKS clGetEventProfilingInfo(): CL_UNKNOWN_ERROR
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
(This setup has been stable for several years, never had any problems with hashcat before)


Code:
hashcat64.bin -a 0 -m 14600 LUKS.hash rockyou.txt

hashcat (v5.1.0) starting...

OpenCL Platform #1: Intel(R) Corporation
========================================
* Device #1: Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz, skipped.

OpenCL Platform #2: NVIDIA Corporation
======================================
* Device #2: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #3: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #4: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #5: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #6: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #7: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #8: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #9: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU

Then I get several errors like:
clGetEventProfilingInfo(): CL_UNKNOWN_ERROR
clEnqueueReadBuffer(): CL_OUT_OF_RESOURCES


However, if I manually specify the same devices everything works just fine:


Code:
hashcat64.bin -a 0 -m 14600 -d 2,3,4,5,6,7,8,9 LUKS.hash rockyou.txt

hashcat (v5.1.0) starting...

OpenCL Platform #1: Intel(R) Corporation
========================================
* Device #1: Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz, skipped.

OpenCL Platform #2: NVIDIA Corporation
======================================
* Device #2: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #3: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #4: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #5: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #6: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #7: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #8: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #9: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU

Using the same syntax for NTLM works fine:


Code:
hashcat64.bin -m 1000 -a 0 ntlm.hash rockyou.txt

hashcat (v5.1.0) starting...

OpenCL Platform #1: Intel(R) Corporation
========================================
* Device #1: Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz, skipped.

OpenCL Platform #2: NVIDIA Corporation
======================================
* Device #2: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #3: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #4: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #5: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #6: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #7: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #8: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU
* Device #9: GeForce GTX 1080, 2028/8114 MB allocatable, 20MCU

Any idea what is happening here, and how can I debug this further?
why are you so sure that this has anything to do with LUKS ? Did you test by running the benchmarks or even --benchmark --benchmark-all ?

did you try to use the beta from https://hashcat.net/beta/

I assume you are using linux and the most recent nvidia driver, but please always mention important info like this
Strange thing.... The original attack now works just fine.

Maybe the reboot worked.