-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Segmentation fault on MacPro5,1 #4
Comments
Interesting, it seems to crash after reading the configuration file. Can you try running with gdb? |
Is this still an issue @b-? |
I'll have to try it again, but I can make a point of doing so and let you know. |
Sorry for the late reply, the past few weeks have been busy. I just compiled and installed fresh on Proxmox 8.1.3 which is basically just Debian Bookworm with a Linux 6.5.11-7 kernel. I'm still getting the same behavior. I'm happy to try with gdb, but I honestly don't really know how to use it. EDIT: Okay, actually I got some information out of gdb more easily than I expected: (gdb) r -n
Starting program: /root/macfand/macfand -n
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Loading profile for model: macpro5,1
dbug: opening profile /usr/local/macfand/machines/macpro5,1.conf
Program received signal SIGSEGV, Segmentation fault.
__memcpy_sse2_unaligned_erms () at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:341
341 ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S: No such file or directory.
(gdb) |
macpro5,1.conf has values for CPUA and CPUB, could it be possible that this is a profile only for dual tray models? |
I don't think this should be an issue, as my machine does have two sockets. |
Running on Proxmox VE (basically Debian bullseye), compiled from source with completely default configuration (apart from #3). I’m running on a MacPro5,1.
Transcript:
the profile exists and is being read:
The text was updated successfully, but these errors were encountered: