log in

Posts by dhh

1) Message boards : Questions/Problems/Bugs : SIGSEGV: segmentation violation (Message 1905)
Posted 6 Jul 2018 by dhh
Post:
Configure the bootloader to use the kernel parameter "vsyscall=emulate"


Thank you very much!! That is solving my problem with NFS@Home too :-)!
2) Message boards : Questions/Problems/Bugs : SIGSEGV: segmentation violation (Message 1903)
Posted 6 Jul 2018 by dhh
Post:
Maybe there is an issue with kernels 4.16 and later?


Yes that might be! As an update: I can process NFS@Home WUs under Ubuntu 18.04 LTS on the same hardware without problems. Software-wise that is a system fairly equivalent to Debian 10. However the kernel is version 4.15.0-20.
3) Message boards : Questions/Problems/Bugs : SIGSEGV: segmentation violation (Message 1900)
Posted 5 Jul 2018 by dhh
Post:
I have just started running NFS@HOME WUs, and I am having problems with instant application crashes. This is on a debian linux 10 system, that is kernel 4.16.0-1. The system is a Ryzen 2700X with 32GB of RAM. In general this system processes all other BOINC-projects I have tried without problems, however this might be too new for NFS@HOME?
So I'd be happy about some feedback, either from anyone having similar problems or even better from anyone knowing a fix for the problem.

All showing the following message in the STDERR log for the task:

<core_client_version>7.10.3</core_client_version>
<![CDATA[
<message>
process got signal 11</message>
<stderr_txt>
SIGSEGV: segmentation violation

</stderr_txt>
]]>


Since is a segmentation violation, i.e. the code performing illegal I/O access, I checked the syslog and all runs leave messages of the type

lasievee_1.10_x[4301] vsyscall attempted with vsyscall=none ip:ffffffffff600000 cs:33 sp:7ffc569592d8 ax:ffffffffff600000 si:0 di:7ffc569592f0





Home | My Account | Message Boards