Questions and Answers :
Unix/Linux :
[Debian 10]No new tasks
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
Radjin Send message Joined: 2 May 00 Posts: 105 Credit: 14,928,529 RAC: 102 |
Well I see I typoed. But you don't do anything other than put VSYSCALL=EMULATE in between the already existing GRUB_CMDLINE_LINUX_DEFAULT="" line in between the existing "" sudo update-grub Generating grub configuration file ... Found linux image: /boot/vmlinuz-4.19.0-6-amd64 Found initrd image: /boot/initrd.img-4.19.0-6-amd64 Found linux image: /boot/vmlinuz-4.19.0-5-amd64 Found initrd image: /boot/initrd.img-4.19.0-5-amd64 Found memtest86+ image: /boot/memtest86+.bin Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin doneThat seemed to go ok. cat /usr/src/linux-headers-$(uname -r)/.config | grep cat: /usr/src/linux-headers-4.19.0-6-amd64/.config: No such file or directoryFor some reason I don’t get the confirmation of the emulation mode. Radjin~ |
Radjin Send message Joined: 2 May 00 Posts: 105 Credit: 14,928,529 RAC: 102 |
I was perusing my computers for the past 30 days an realized that I was running seti@home prior to upgrading the memory and CPU, hence there is the i5 in the list with 16GB of ram. It also received the same error. Just an observation that it may not be hardware. Radjin~ |
rob smith Send message Joined: 7 Mar 03 Posts: 22190 Credit: 416,307,556 RAC: 380 |
OK. You say you upgraded from an i5 to an i7 and added some more memory at the same time. Prior to the upgrade you had at least one task fail with a SIGSEGV error - I've grabbed the stderr file for that one so others can see if there is anything significant in it. With this not being a "new" error, what remains of the "old" i5 computer? And what exactly have you changed? (As SIGSEGV errors are rare it is more likely to be something at your end off the chain than at the server end - if it were a data-related error we would be seeing a number of other users showing the same problem. There was such an event a few years back where hundreds of tasks were mal-formed and were causing a vast number of errors, the project staff stepped in and pulled the batch) Task 8031699442 Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
Radjin Send message Joined: 2 May 00 Posts: 105 Credit: 14,928,529 RAC: 102 |
OK. You say you upgraded from an i5 to an i7 and added some more memory at the same time. The only change was the CPU and Memory. I did upgrade the CPU cooler to where it maintains temperatures in the mid 30's idle and under 60 when pushed to 100%. The i5 became the I7. Radjin~ |
rob smith Send message Joined: 7 Mar 03 Posts: 22190 Credit: 416,307,556 RAC: 380 |
We may now be getting closer to a solution, and I'll admit now these are not the ones I first thought of :-( A motherboard fault - not unknown, but could well lead to the error you are seeing. BUT Second question - did you swap out al the memory or just "add a couple more sticks"? Third question - Am I right in assuming you are using the same hard disk and haven't done any software update or repair operation in recent weeks? (Outside chance that there is an issue with the disk having a minor corruption, but that would probably be flagged up during boot or as part of Linux's continuous health checking) (I think we can safely lay an issue with the CPU to one side as you've installed a new one of a different type, and the probability of having two faulty is quite remote) Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
Keith Myers Send message Joined: 29 Apr 01 Posts: 13164 Credit: 1,160,866,277 RAC: 1,873 |
Well I see I typoed. But you don't do anything other than put VSYSCALL=EMULATE in between the already existing GRUB_CMDLINE_LINUX_DEFAULT="" line in between the existing "" Again, I suspect your distro is simply ignoring it since the default has been to use emulate by default for many years now. No point in turning something on that is already on. Seti@Home classic workunits:20,676 CPU time:74,226 hours A proud member of the OFA (Old Farts Association) |
TBar Send message Joined: 22 May 99 Posts: 5204 Credit: 840,779,836 RAC: 2,768 |
Actually, there are a few others with this Error, https://setiathome.berkeley.edu/results.php?hostid=8780534&state=6 Also, back during WOW it was noted the Cloud machine was producing quite a few SIGSEGV errors. They all have one common theme, they are using the Stock SETI CPU App. I don't remember seeing anyone running a different CPU App have this problem, except maybe TomM, who has had all sorts of errors. Maybe try a different App and see if this machine has the same errors? |
Radjin Send message Joined: 2 May 00 Posts: 105 Credit: 14,928,529 RAC: 102 |
Actually, there are a few others with this Error, https://setiathome.berkeley.edu/results.php?hostid=8780534&state=6 Also, back during WOW it was noted the Cloud machine was producing quite a few SIGSEGV errors. They all have one common theme, they are using the Stock SETI CPU App. I don't remember seeing anyone running a different CPU App have this problem, except maybe TomM, who has had all sorts of errors. Maybe try a different App and see if this machine has the same errors? Well at least I am not delusional... I did try running a version from here http://www.arkayn.us/lunatics/BOINC.7z that gave me the same errors. I also get the same errors after upgrading the CPU and memory, hence the i5 computer in my 30 day list. Radjin~ |
rob smith Send message Joined: 7 Mar 03 Posts: 22190 Credit: 416,307,556 RAC: 380 |
Since this error has been with you for a few weeks and you have tried an alternative application I have to say - read my previous post about hardware faults. Bob Smith Member of Seti PIPPS (Pluto is a Planet Protest Society) Somewhere in the (un)known Universe? |
Radjin Send message Joined: 2 May 00 Posts: 105 Credit: 14,928,529 RAC: 102 |
It has started crunching WU’s. I did nothing but fly out for a couple of days. Thanks for all the tips and suggestions. Radjin~ Radjin~ |
Justin Turner Arthur Send message Joined: 20 Oct 03 Posts: 12 Credit: 3,929,052 RAC: 2 |
I just started seeing this after upgrading from Linux 5.0.0 to 5.3.8 and a glibc upgrade. Like with others, setiathome_8.05_i686-pc-linux-gnu and GPU runners work great but setiathome_8.00_x86_64-pc-linux-gnu gives the segfault and signal 11. strace shows it happening after trying to stat init_data.xml (which doesn't exist in my stock project dir). Maybe stat-ing the missing file failed more gracefully in older kernels or older glibc? execve("./setiathome_8.00_x86_64-pc-linux-gnu", ["./setiathome_8.00_x86_64-pc-linu"...], 0x7ffc29b602e0 /* 31 vars */) = 0 uname({sysname="Linux", nodename="allspice", ...}) = 0 brk(NULL) = 0x22fa000 brk(0x22fb1a0) = 0x22fb1a0 arch_prctl(ARCH_SET_FS, 0x22fa880) = 0 set_tid_address(0x22fab50) = 13077 set_robust_list(0x22fab60, 24) = 0 futex(0x7ffd823c5adc, FUTEX_WAKE_PRIVATE, 1) = 0 futex(0x7ffd823c5adc, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, NULL, 0x22fa880) = -1 EAGAIN (Resource temporarily unavailable) rt_sigaction(SIGRTMIN, {sa_handler=0x6ec380, sa_mask=[], sa_flags=SA_RESTORER|SA_SIGINFO, sa_restorer=0x6f5930}, NULL, 8) = 0 rt_sigaction(SIGRT_1, {sa_handler=0x6ec2b0, sa_mask=[], sa_flags=SA_RESTORER|SA_RESTART|SA_SIGINFO, sa_restorer=0x6f5930}, NULL, 8) = 0 rt_sigprocmask(SIG_UNBLOCK, [RTMIN RT_1], NULL, 8) = 0 getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM64_INFINITY}) = 0 brk(0x231c1a0) = 0x231c1a0 brk(0x231d000) = 0x231d000 futex(0xadc168, FUTEX_WAKE_PRIVATE, 2147483647) = 0 stat("stderr.txt", 0x7ffd823c4820) = -1 ENOENT (No such file or directory) close(2) = 0 open("stderr.txt", O_WRONLY|O_CREAT|O_APPEND, 0666) = 2 fstat(2, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x7ff9436d7000 fstat(2, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0 lseek(2, 0, SEEK_SET) = 0 munmap(0x7ff9436d7000, 4096) = 0 rt_sigaction(SIGILL, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0 rt_sigaction(SIGILL, {sa_handler=0x4ca1cc, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x6f5930}, NULL, 8) = 0 rt_sigaction(SIGABRT, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0 rt_sigaction(SIGABRT, {sa_handler=0x4ca1cc, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x6f5930}, NULL, 8) = 0 rt_sigaction(SIGBUS, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0 rt_sigaction(SIGBUS, {sa_handler=0x4ca1cc, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x6f5930}, NULL, 8) = 0 rt_sigaction(SIGSEGV, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0 rt_sigaction(SIGSEGV, {sa_handler=0x4ca1cc, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x6f5930}, NULL, 8) = 0 rt_sigaction(SIGSYS, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0 rt_sigaction(SIGSYS, {sa_handler=0x4ca1cc, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x6f5930}, NULL, 8) = 0 rt_sigaction(SIGPIPE, NULL, {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0 rt_sigaction(SIGPIPE, {sa_handler=0x4ca1cc, sa_mask=[], sa_flags=SA_RESTORER, sa_restorer=0x6f5930}, NULL, 8) = 0 open("init_data.xml", O_RDONLY) = -1 ENOENT (No such file or directory) stat("init_data.xml", 0x7ffd823c58b0) = -1 ENOENT (No such file or directory) --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xffffffffff600400} --- write(2, "SIGSEGV: segmentation violation\n", 32) = 32 brk(0x2348000) = 0x2348000 brk(0x233a000) = 0x233a000 futex(0xaef4b0, FUTEX_WAKE_PRIVATE, 2147483647) = 0 --- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0xffffffffff600400} --- +++ killed by SIGSEGV +++ Segmentation fault |
Justin Turner Arthur Send message Joined: 20 Oct 03 Posts: 12 Credit: 3,929,052 RAC: 2 |
Looks like I was in the same boat as most and just needed to enable vsyscall emulation. In newer kernels, it's disabled by default and there is no longer a native mode option. If you've opted to enable it via the Linux kernel command line (e.g. in grub) instead of compiling with the config flag, you can see if your current kernel was launched correctly with: $ cat /proc/cmdline BOOT_IMAGE=/kernel-genkernel-x86_64-5.3.8-gentoo root=UUID=abcdefg-1234-5678-fedc-ba9876543210 ro vsyscall=emulate My strace output is not helpful as it doesn't show these old syscalls; it likely had nothing to do with that stat() line. |
HankB Send message Joined: 1 Dec 04 Posts: 12 Credit: 6,115,914 RAC: 1 |
Hi folks, I'm trying to get going with SETI again and I'm running into this: BOINC log: Wed 11 Dec 2019 05:52:38 PM CST | SETI@home | Starting task 31au13ab.6429.3748.14.41.148.vlar_0 Wed 11 Dec 2019 05:52:39 PM CST | SETI@home | Computation for task 31au13ab.6429.3748.14.41.148.vlar_0 finished Wed 11 Dec 2019 05:52:39 PM CST | SETI@home | Output file 31au13ab.6429.3748.14.41.148.vlar_0_r219480302_0 for task 31au13ab.6429.3748.14.41.148.vlar_0 absent Wed 11 Dec 2019 06:08:33 PM CST | SETI@home | project suspended by user I see pretty much the same for all 79 downloaded jobs. :( Status on the web page is "In progress" because nothing is sent back. I find the executable setiathome_8.00_x86_64-pc-linux-gnuand find difficulty running it (except for -help and -version options.) root@olive:/var/lib/boinc-client/projects/setiathome.berkeley.edu# ./setiathome_8.00_x86_64-pc-linux-gnu -version SETI@home client. Version: 8.00 SETI@home is sponsored by individual donors around the world. If you'd like to contribute to the project, please visit the SETI@home web site at http://setiathome.ssl.berkeley.edu. The project is also sponsored by the Planetary Society, the University of California, Sun Microsystems, Paramount Pictures, Fujifilm Computer Products, Informix, Engineering Design Team Inc, The Santa Cruz Operation (SCO), Intel, Quantum Corporation, and the SETI Institute. SETI@home was developed by David Gedye (Founder), David Anderson (Director), Dan Werthimer (Chief Scientist), Hiram Clawson, Jeff Cobb, Charlie Fenton, Eric Heien, Eric Korpela, Matt Lebofsky, Tetsuji 'Maverick' Rai and Rom Walton root@olive:/var/lib/boinc-client/projects/setiathome.berkeley.edu# ./setiathome_8.00_x86_64-pc-linux-gnu -help bad arg: -help options: -nographics run without graphics -notranspose do not transpose data for pulse and gaussian searches -default_functions use the safe unoptimized default functions -standalone (implies -nographics) -version show version info -verbose print running status root@olive:/var/lib/boinc-client/projects/setiathome.berkeley.edu# But root@olive:/var/lib/boinc-client/projects/setiathome.berkeley.edu# ./setiathome_8.00_x86_64-pc-linux-gnu Segmentation fault (core dumped) root@olive:/var/lib/boinc-client/projects/setiathome.berkeley.edu# ./setiathome_8.00_x86_64-pc-linux-gnu -default_functions Segmentation fault (core dumped) root@olive:/var/lib/boinc-client/projects/setiathome.berkeley.edu# ./setiathome_8.00_x86_64-pc-linux-gnu -verbose Segmentation fault (core dumped) root@olive:/var/lib/boinc-client/projects/setiathome.berkeley.edu# Error file tells me what I already know. root@olive:/var/lib/boinc-client/projects/setiathome.berkeley.edu# cat stderr.txt SIGSEGV: segmentation violation SIGSEGV: segmentation violation SIGSEGV: segmentation violation SIGSEGV: segmentation violation SIGSEGV: segmentation violation SIGSEGV: segmentation violation root@olive:/var/lib/boinc-client/projects/setiathome.berkeley.edu# An I dealing with the same problem and if so, should I continue on this thread or should I start another thread (or is there another resource I should be looking at.) Thanks! Edit: I forgot to mention that I'm on Debian Linux and running a 5.3 kernel. I've run both Rosetta and Folding at Home on this PC with no apparent problems. |
Mariusz A. Przeklasa Send message Joined: 9 Mar 02 Posts: 1 Credit: 2,509,359 RAC: 3 |
Were you able to find a solution to this problem (Debian 10 buster & SETI@home problem)? <message> |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.