Linux segfault

Anybody ever seen fahcore segfaulting? I'm getting this all over syslog lately.

Feb 27 06:03:17 host01 kernel: FahCore_a4[20416] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7f1f87852d88 ax:ffffffffff600400 si:7f1f87852c36 di:7f1f87852dc8
Feb 27 06:03:17 host01 kernel: FahCore_a4[20416]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007f1f87852d88 error 15

petteyg359 said:

Anybody ever seen fahcore segfaulting? I'm getting this all over syslog lately.

Feb 27 06:03:17 host01 kernel: FahCore_a4[20416] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7f1f87852d88 ax:ffffffffff600400 si:7f1f87852c36 di:7f1f87852dc8
Feb 27 06:03:17 host01 kernel: FahCore_a4[20416]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007f1f87852d88 error 15

Click to expand...

Segfaults are typically hardware issues -- things like memory going bad, overclocked too much, etc. I do remember some issues back in the day with a certain WU causing these errors though, so its possible this isn't something terrible.

I'd start with a memtest86, if this isn't a memory fault, then it could be some update has changed how this works with your OS. Maybe even boot from an ubuntu live cd and toss in the latest fah client, just to rule out an OS issue.

Found the issue. My kernel has vsyscall disabled (which is the only sane option these days). I realize F@H may not have a massive IT budget, but vsyscall has been ill-advised for a long time (https://sourceware.org/ml/libc-alpha/2011-08/msg00121.html - 2011-8-24).