View Issue Details

IDProjectCategoryView StatusLast Update
0003835Kali LinuxGeneral Bugpublic2018-03-12 13:34
Reporterrfrogman Assigned Tosbrun  
PrioritynormalSeveritycrashReproducibilityalways
Status resolvedResolutionfixed 
Product Version2016.2 
Summary0003835: hashcat v3.20 clGetDeviceIDs(): CL_DEVICE_NOT_FOUND Segmentation fault
Description

Hashcat fails after last last apt-get dist-upgrade. Hashcat v3.10 was working correctly. Hashcat v3.20 fails with the following errors:

root@kali:~# hashcat -b
hashcat (v3.20) starting in benchmark mode...

clGetDeviceIDs(): CL_DEVICE_NOT_FOUND

  • Device 0000001: Old CUDA chipset 3.0 detected, OpenCL performance is reduced.
    For ideal hashcat performance on NVIDIA GPU you need Shader Model 5.0 or higher
    clGetDeviceIDs(): CL_DEVICE_NOT_FOUND

Segmentation fault


cudaHashcat64.bin is working fine on same laptop

Steps To Reproduce

hashcat -b

Additional Information

This is the response from cudaHashcat64:

root@kali:~/Desktop/cudaHashcat-2.01# ./cudaHashcat64.bin -b
cudaHashcat v2.01 starting in benchmark-mode...

Device 0000001: Quadro K3100M, 4035MB, 705Mhz, 4MCU

Hashtype: MD4
Workload: 1024 loops, 256 accel

Speed.GPU.0000001.: 1638.8 MH/s

.......

I have verified the following installs:

root@kali:~# apt-get install nvidia-opencl-icd
Reading package lists... Done
Building dependency tree
Reading state information... Done
nvidia-opencl-icd is already the newest version (375.26-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

root@kali:~# apt-get install opencl-headers
Reading package lists... Done
Building dependency tree
Reading state information... Done
opencl-headers is already the newest version (2.1-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

root@kali:~# lspci -v | grep nvidia
Kernel driver in use: nvidia
Kernel modules: nvidia

root@kali:~# glxinfo | grep -i "direct rendering"
direct rendering: Yes

nvidia-driver 375.26-1 amd64

Activities

sbrun

sbrun

2017-02-13 14:48

manager   ~0006376

If the package mesa-opencl-icd is installed, please try to remove it (apt remove mesa-opencl-icd).
It seems that the latest version of the package generates issues when co-installed with other *-opencl-icd.

rfrogman

rfrogman

2017-02-13 15:27

reporter   ~0006378

mesa-opencl-id was not installed. Hashcat has been update through apt-get to v3.30 and same result.

root@kali:~# hashcat -b -m 1000
hashcat (v3.30) starting in benchmark mode...

  • Device 0000001: Old CUDA compute capability 3.0 detected, OpenCL performance is reduced.
    For ideal hashcat performance on NVIDIA GPU you need CUDA compute capability 5.0 or higher (Maxwell)
    Segmentation fault
    root@kali:~# apt remove mesa-opencl-icd
    Reading package lists... Done
    Building dependency tree
    Reading state information... Done
    Package 'mesa-opencl-icd' is not installed, so not removed
    0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
    root@kali:~# hashcat -b -m 1000
    hashcat (v3.30) starting in benchmark mode...

  • Device 0000001: Old CUDA compute capability 3.0 detected, OpenCL performance is reduced.
    For ideal hashcat performance on NVIDIA GPU you need CUDA compute capability 5.0 or higher (Maxwell)
    Segmentation fault
    root@kali:~#

rhertzog

rhertzog

2017-02-13 20:50

administrator   ~0006397

Is your system fully up-to-date? (apt update && apt full-upgrade)

Can you try to install http://debug.mirrors.debian.org/debian-debug/pool/main/h/hashcat/hashcat-dbgsym_3.30-1_amd64.deb and run hashcat in gdb to get a backtrace of the segfault ?

rfrogman

rfrogman

2017-02-14 21:23

reporter   ~0006402

Yes my system is fully up-to-date.

Here is gdb results:

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7b62484 in hm_NVML_nvmlDeviceGetPowerManagementLimit (
limit=0x7fffffffdfcc, device=0x0, hashcat_ctx=0x555555759010)
at src/hwmon.c:1012
1012 src/hwmon.c: No such file or directory.

rhertzog

rhertzog

2017-02-15 08:46

administrator   ~0006403

At this point in gdb you need to type "bt" to get a backtrace. Thank you!

But we should continue this conversation upstream, I opened a ticket here:
https://github.com/hashcat/hashcat/issues/1101

Please paste the full backtrace to both places.

rfrogman

rfrogman

2017-02-15 13:10

reporter   ~0006405

my bad! here you go...

hashcat (v3.30) starting in benchmark mode...

  • Device 0000001: Old CUDA compute capability 3.0 detected, OpenCL performance is reduced.
    For ideal hashcat performance on NVIDIA GPU you need CUDA compute capability 5.0 or higher (Maxwell)

Program received signal SIGSEGV, Segmentation fault.
0x00007ffff7b62484 in hm_NVML_nvmlDeviceGetPowerManagementLimit (
limit=0x7fffffffdfdc, device=0x0, hashcat_ctx=0x555555759010)
at src/hwmon.c:1012
1012 src/hwmon.c: No such file or directory.
(gdb) bt
#0 0x00007ffff7b62484 in hm_NVML_nvmlDeviceGetPowerManagementLimit (
limit=0x7fffffffdfdc, device=0x0, hashcat_ctx=0x555555759010)
at src/hwmon.c:1012
0000001 hwmon_ctx_init (hashcat_ctx=hashcat_ctx@entry=0x555555759010)
at src/hwmon.c:3894
#2 0x00007ffff7b5b504 in hashcat_session_init (hashcat_ctx=0x555555759010,
install_folder=0x5555555565c6 "/usr/bin",
shared_folder=0x5555555565b3 "/usr/share/hashcat", argc=4,
argv=0x7fffffffe2a8, comptime=1484845219) at src/hashcat.c:1025
#3 0x0000555555555203 in main (argc=4, argv=0x7fffffffe2a8) at src/main.c:975
(gdb)

rhertzog

rhertzog

2017-02-15 22:04

administrator   ~0006406

Can you have a look at the upstream ticket? They ask you to test an updated version...

Also they say that this segfault would likely be fixed by installing the "libnvidia-ml1" package.

rfrogman

rfrogman

2017-02-16 13:42

reporter   ~0006412

Yes I installed hashcat-dbgsym_3.30-1_amd64.deb......
dpkg -i hashcat-dbgsym_3.30-1_amd64.deb

libnvidia-ml1 is already installed.

root@kali:~# apt-get install libnvidia-ml1
Reading package lists... Done
Building dependency tree
Reading state information... Done
libnvidia-ml1 is already the newest version (375.26-2).
libnvidia-ml1 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

rhertzog

rhertzog

2017-02-16 14:38

administrator   ~0006413

hashcat-dbgsym is not a new version of hashcat, it's just the debugging symbols required to provide a meaningful backtrace for the version of hashcat that we have in Kali.

Upstream committed a possible fix to git, so either you build a custom version out of git to try it out, or you test with a pre-built binary that they provide here:
https://hashcat.net/beta/

cf https://github.com/hashcat/hashcat/issues/1101#issuecomment-280102444

rfrogman

rfrogman

2017-02-17 14:58

reporter   ~0006426

root@kali:~/Downloads/betahashcat# ./hashcat64.bin -b -m 1000
hashcat (v3.30-316-gbbb4c74) starting in benchmark mode...

clGetDeviceIDs(): CL_DEVICE_NOT_FOUND

  • Device 0000001: Old CUDA compute capability 3.0 detected, OpenCL performance is reduced.
    For ideal hashcat performance on NVIDIA GPU you need CUDA compute capability 5.0 or higher (Maxwell)
    clGetDeviceIDs(): CL_DEVICE_NOT_FOUND

OpenCL Platform 0000001: NVIDIA Corporation

  • Device 0000001: Quadro K3100M, 1008/4035 MB allocatable, 4MCU

OpenCL Platform #2: Mesa, skipped or no OpenCL compatible devices found

Hashtype: NTLM

inc_cipher_aes.cl: No such file or directory

Started: Fri Feb 17 08:52:16 2017
Stopped: Fri Feb 17 08:52:17 2017

rfrogman

rfrogman

2017-02-17 15:05

reporter   ~0006427

root@kali:~# ldd /usr/bin/hashcat
linux-vdso.so.1 (0x00007ffe3d6c4000)
libhashcat.so => /usr/lib/hashcat/libhashcat.so (0x00007ff437197000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007ff436f55000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007ff436d51000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ff4369b3000)
/lib64/ld-linux-x86-64.so.2 (0x0000561154b79000)

alhashcatfan

alhashcatfan

2017-02-19 15:45

reporter   ~0006433

Geforce GT 710B
Kali 2.0 just upgraded:

hashcat (v3.30) starting...

clGetDeviceIDs(): CL_DEVICE_NOT_FOUND

clGetDeviceIDs(): CL_DEVICE_NOT_FOUND

No devices found/left


Regards
A.

sbrun

sbrun

2018-03-12 13:34

manager   ~0008905

hashcat has been updated to version 4.0.1-1
I don't reproduce the error with this version.
If you still have issue, please open a new bug report.

Issue History

Date Modified Username Field Change
2017-01-16 16:54 rfrogman New Issue
2017-02-13 14:48 sbrun Assigned To => sbrun
2017-02-13 14:48 sbrun Status new => assigned
2017-02-13 14:48 sbrun Note Added: 0006376
2017-02-13 15:27 rfrogman Note Added: 0006378
2017-02-13 20:50 rhertzog Note Added: 0006397
2017-02-14 21:23 rfrogman Note Added: 0006402
2017-02-15 08:46 rhertzog Note Added: 0006403
2017-02-15 13:10 rfrogman Note Added: 0006405
2017-02-15 22:04 rhertzog Note Added: 0006406
2017-02-16 13:42 rfrogman Note Added: 0006412
2017-02-16 14:38 rhertzog Note Added: 0006413
2017-02-17 14:58 rfrogman Note Added: 0006426
2017-02-17 15:05 rfrogman Note Added: 0006427
2017-02-19 15:45 alhashcatfan Note Added: 0006433
2018-03-12 13:34 sbrun Status assigned => resolved
2018-03-12 13:34 sbrun Resolution open => fixed
2018-03-12 13:34 sbrun Note Added: 0008905