Folding Forum

Posted: **Wed Feb 28, 2018 6:52 pm**

beer wrote:Hi
I think I have the same situration:
viewtopic.php?f=72&t=30654&start=15

I am a bit of a linux newbie. I have tried to google how/where to enter "vsyscall=emulate" on a debian system. But without no good results. Can you point me in the right directions (I am running Debian testing)

Sure, you can edit your kernel paramters by editing

Code: Select all

/etc/default/grub

and find the line

Code: Select all

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

and add

Code: Select all

vsyscall=emulate

withing the quotes, then run (requires sudo)

Code: Select all

grub-mkconfig -o /boot/grub/grub.cfg

and restart.

Source: https://wiki.archlinux.org/index.php/kernel_parameters

Posted: **Wed Feb 28, 2018 9:13 pm**

Interestingly enough rosetta@home had the same problem:

https://boinc.bakerlab.org/rosetta/foru ... hp?id=6886

Posted: **Thu Mar 01, 2018 6:37 am**

#butc8 It dont seems to work on my computer.

Code: Select all

beer@debian:~$ cat /usr/src/linux-headers-$(uname -r)/.config | grep VSYSCALL
CONFIG_GENERIC_TIME_VSYSCALL=y
CONFIG_X86_VSYSCALL_EMULATION=y
# CONFIG_LEGACY_VSYSCALL_NATIVE is not set
# CONFIG_LEGACY_VSYSCALL_EMULATE is not set
CONFIG_LEGACY_VSYSCALL_NONE=y

Code: Select all

beer@debian:~$ cat /etc/default/grub
# If you change this file, run 'update-grub' afterwards to update
# /boot/grub/grub.cfg.
# For full documentation of the options in this file, see:
#   info -f grub -n 'Simple configuration'

GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet vsyscall=emulate"
GRUB_CMDLINE_LINUX=""

# Uncomment to enable BadRAM filtering, modify to suit your needs
# This works with Linux (no patch required) and with any kernel that obtains
# the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
#GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"

# Uncomment to disable graphical terminal (grub-pc only)
#GRUB_TERMINAL=console

# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command `vbeinfo'
#GRUB_GFXMODE=640x480

# Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
#GRUB_DISABLE_LINUX_UUID=true

# Uncomment to disable generation of recovery mode menu entries
#GRUB_DISABLE_RECOVERY="true"

# Uncomment to get a beep at grub start
#GRUB_INIT_TUNE="480 440 1"

And I did run grub-mkconfig -o /boot/grub/grub.cfg after edding the file with no error messages and I still got crashing A4 but not A7

Posted: **Thu Mar 01, 2018 6:06 pm**

I have exactly the same kernel config, so perhaps it is a different problem?

You can check by running an a4 core and having it fail and see if there is any relevant output when you run

Code: Select all

dmesg

when it was error'ing out on me I was seeing these types of messages

Code: Select all

[ 7290.795572] FahCore_a4[5393]: segfault at ffffffffff600400 ip ffffffffff600400 sp 00007f316fa83d88 error 15
[ 7350.913653] FahCore_a4[5626] vsyscall attempted with vsyscall=none ip:ffffffffff600400 cs:33 sp:7f395887bd88 ax:ffffffffff600400 si:7f395887bc2a di:7f395887bdc8

Posted: **Fri Mar 02, 2018 6:37 am**

hi
I dont know exactly what happend. but there was a a couple of updates yesterdaty to debian (including grub with a new /etc/default/grub) and now A4 runs as it should on my mashine

Folding Forum

Cannot fold A4 cpu but can fold A7

Re: Core a4 WUs segfaulting on kernel 4.15

Re: Core a4 WUs segfaulting on kernel 4.15

Re: Core a4 WUs segfaulting on kernel 4.15

Re: Core a4 WUs segfaulting on kernel 4.15

Re: Core a4 WUs segfaulting on kernel 4.15