Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CPU-X isn't starting anymore; Segmentation fault #258

Closed
kkhkkh1 opened this issue Dec 6, 2022 · 5 comments
Closed

CPU-X isn't starting anymore; Segmentation fault #258

kkhkkh1 opened this issue Dec 6, 2022 · 5 comments
Assignees
Labels

Comments

@kkhkkh1
Copy link

kkhkkh1 commented Dec 6, 2022

Hello,

tried to run CPU-X today which was always working before, now its not starting.

Describe the bug/Expected behavior

Additional information

  • Operating system name and version:
  • Slackware-15-64Bit.
  • CPU-X installation type:
  • Built from source.

cpu-x.log is attached.
Thanks for any help.

Terminal puts out the same error as in the logfile.

Your GPU user mode driver is unknown: 4.6.0 NVIDIA 515.76

�[1;31mOops, something was wrong! CPU-X has received signal 11 (Segmentation fault) and has crashed.�[0m
========================= Backtrace =========================
CPU-X 4.3.1 (Oct 14 2022 22:02:37, Linux x86_64, GNU 11.2.0)
# 1 /lib64/libc.so.6(+0x3b8d0) [0x7ff0f4bac8d0]
# 2 /usr/lib64/gallium-pipe/pipe_iris.so(+0x5d15b9) [0x7ff0d93165b9]
# 3 /usr/lib64/gallium-pipe/pipe_iris.so(+0x1b590e) [0x7ff0d8efa90e]
# 4 /usr/lib64/gallium-pipe/pipe_iris.so(+0x1b5613) [0x7ff0d8efa613]
# 5 /usr/lib64/gallium-pipe/pipe_iris.so(+0x13eaf7) [0x7ff0d8e83af7]
# 6 /usr/lib64/libMesaOpenCL.so.1(+0x6582b) [0x7ff0f04a682b]
# 7 /usr/lib64/libMesaOpenCL.so.1(+0x5407c) [0x7ff0f049507c]
# 8 /usr/lib64/libMesaOpenCL.so.1(+0x601e8) [0x7ff0f04a11e8]
# 9 /usr/lib64/libMesaOpenCL.so.1(+0x327fb) [0x7ff0f04737fb]
#10 /lib64/ld-linux-x86-64.so.2(+0x1138e) [0x7ff0f602138e]
#11 /lib64/ld-linux-x86-64.so.2(+0x11470) [0x7ff0f6021470]
#12 /lib64/libc.so.6(_dl_catch_exception+0xad) [0x7ff0f4cb87dd]
#13 /lib64/ld-linux-x86-64.so.2(+0x15984) [0x7ff0f6025984]
#14 /lib64/libc.so.6(_dl_catch_exception+0x65) [0x7ff0f4cb8795]
#15 /lib64/ld-linux-x86-64.so.2(+0x14f28) [0x7ff0f6024f28]
======================== End Backtrace =======================

cpu-x.log

@kkhkkh1 kkhkkh1 changed the title CPU-X isn't starting anymore CPU-X isn't starting anymore; Segmentation fault Dec 6, 2022
@TheTumultuousUnicornOfDarkness
Copy link
Owner

It looks like #246. It was fixed in v4.5.1.
You can try with the latest AppImage to see if this bug is fixed: https://github.com/TheTumultuousUnicornOfDarkness/CPU-X/releases/latest

@kkhkkh1
Copy link
Author

kkhkkh1 commented Dec 7, 2022

Hey,
I just updated CPU-X to Version 4.5.2. It's still not starting, but now I'm getting a different Error:

Your GPU user mode driver is unknown: 4.6.0 NVIDIA 515.76
MESA-INTEL: warning: Performance support disabled, consider sysctl dev.i915.perf_stream_paranoid=0


Oops, something was wrong! CPU-X has received signal 11 (Segmentation fault) and has crashed.
========================= Backtrace =========================
CPU-X 4.5.2 (Dec  7 2022 16:44:43, Linux x86_64, GNU 11.2.0)
# 1 /lib64/libc.so.6(+0x3b8d0) [0x7f37791268d0]
# 2 /usr/lib64/gallium-pipe/pipe_iris.so(+0x5d15b9) [0x7f375ebbf5b9]
# 3 /usr/lib64/gallium-pipe/pipe_iris.so(+0x1b590e) [0x7f375e7a390e]
# 4 /usr/lib64/gallium-pipe/pipe_iris.so(+0x1b5613) [0x7f375e7a3613]
# 5 /usr/lib64/gallium-pipe/pipe_iris.so(+0x13eaf7) [0x7f375e72caf7]
# 6 /usr/lib64/libMesaOpenCL.so.1(+0x6582b) [0x7f376eef182b]
# 7 /usr/lib64/libMesaOpenCL.so.1(+0x5407c) [0x7f376eee007c]
# 8 /usr/lib64/libMesaOpenCL.so.1(+0x601e8) [0x7f376eeec1e8]
# 9 /usr/lib64/libMesaOpenCL.so.1(+0x327fb) [0x7f376eebe7fb]e
#10 /lib64/ld-linux-x86-64.so.2(+0x1138e) [0x7f377a60538e]
#11 /lib64/ld-linux-x86-64.so.2(+0x11470) [0x7f377a605470]
#12 /lib64/libc.so.6(_dl_catch_exception+0xad) [0x7f37792327dd]
#13 /lib64/ld-linux-x86-64.so.2(+0x15984) [0x7f377a609984]
#14 /lib64/libc.so.6(_dl_catch_exception+0x65) [0x7f3779232795]
#15 /lib64/ld-linux-x86-64.so.2(+0x14f28) [0x7f377a608f28]
======================== End Backtrace =======================

I also tried the AppImage as suggested, there I'm getting a total different Error:

/tmp/.mount_CPU-X-YrLIzT/AppRun.wrapped: error while loading shared libraries: libthai.so.0: cannot open shared object file: No such file or directory

Thanks for your help.

@TheTumultuousUnicornOfDarkness
Copy link
Owner

I do not get it. You have a NVIDIA graphic card and you are using the Intel Iris OpenCL driver?
Can you told us what hardware you have and which GPU is supposed to run OpenCL?
Also, please provide the clinfo command output.

@kkhkkh1
Copy link
Author

kkhkkh1 commented Dec 27, 2022

Sorry for the late answer,
the System which I'm using currently is a Notebook with intergrated Intel Card + NVIDIA. NVIDIA is set as primary GPU, I don't know what's about the Intel drivers, since everything else uses NVIDIA driver's and is working as expected.
clinfo 's output is "Segmentation Fault". That's all it show's.
greetings

@TheTumultuousUnicornOfDarkness
Copy link
Owner

Ok, because according to the backtrace, it is loading the Intel (Iris) OpenCL driver.
If clinfo is also crashing, something is not configured properly on your system. I can suggest to remove the mesa package on your system, or rebuild CPU-X without OpenCL support (cmake -DWITH_OPENCL=0).
But there is nothing I can do here.

@TheTumultuousUnicornOfDarkness TheTumultuousUnicornOfDarkness closed this as not planned Won't fix, can't repro, duplicate, stale Dec 28, 2022
TheTumultuousUnicornOfDarkness added a commit that referenced this issue Jan 11, 2023
We face numerous issues related to OpenCL (#238, #258, #264).
OpenCL drivers are in bad shape in Linux.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants