Message boards : Number crunching : Error code 193 for nearly all WUs on Linux 2.6
Author | Message |
---|---|
root Send message Joined: 16 Feb 09 Posts: 6 Credit: 24,387 RAC: 0 |
I'm getting this same error for nearly all WUs on two Linux boxes running FC8 and FC9 with kernel 2.6.23.1-42.fc8 and 2.6.25.14-108.fc9.x86_64; resp. In addition, I have a third Linux laptop running FC9 with no problems whatsoever. All 3 machines are running with leave_apps_in_memory=0. <core_client_version>6.4.5</core_client_version> <![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> Any ideas? |
root Send message Joined: 16 Feb 09 Posts: 6 Credit: 24,387 RAC: 0 |
Nobody has this problem? |
th3 Send message Joined: 20 Jun 06 Posts: 11 Credit: 540,609 RAC: 0 |
Nobody has this problem? Not on rosetta and not that error code. I did however have all WUs fail on 2 other projects with newer kernels. I think the problem was nvidia chipset for Intel processors, the other PCs, with Intel chipsets and the same kernel, had no problems. Maybe yours are not nvidia but thats all i got, sorry. Edit: to be more specific, it was nvidia chipsets with integrated graphics (nf630i/gf7100) |
Path7 Send message Joined: 25 Aug 07 Posts: 128 Credit: 61,751 RAC: 0 |
Nobody has this problem? Hello Root, Haven't seen this error on Ubuntu 8.04 (kernel 2.6.24-23-generic). The BOINC FAQ Service gives this answer: process exited with code 193 (0xc1) Good luck, Path7. |
root Send message Joined: 16 Feb 09 Posts: 6 Credit: 24,387 RAC: 0 |
@th3: Thanks for the input. An nvidia chipset is indeed present on one of the non-working machines, but that machine is the AMD64 one. The other machine has an Intel chipset.In summary: kernel 2.6.23.1-42.fc8 on Intel Q6600 with Intel G31 chipset kernel 2.6.25.14-108.fc9.x86_64 on AMD 64 X2 4000+ with Nvidia chipset (don't recall exact one right now). @path7: Yeah, I know that the code denotes a segmentation violation, but what am I supposed to do about that? |
root Send message Joined: 16 Feb 09 Posts: 6 Credit: 24,387 RAC: 0 |
Does Rosetta provide any guidance or hints as to what kernels work well and what can be done to prevent crashes on the newer kernels (I like my cutting edge features...)? |
Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0 |
No guidance. But, if the kernel is stable, BOINC should work on the machine. Your machines (and results) are hidden. How frequently are you see segmentation violations as compared to successful results? Rosetta Moderator: Mod.Sense |
root Send message Joined: 16 Feb 09 Posts: 6 Credit: 24,387 RAC: 0 |
No guidance. But, if the kernel is stable, BOINC should work on the machine. Your machines (and results) are hidden. How frequently are you see segmentation violations as compared to successful results? On the two aforementioned machines - always. Nearly without exception (maybe one or two successful WU). Admittedly the number of available issues to fail on has decreased as I have been bumping my very low daily quota (from all those compute errors). These are segmentation faults in minirosetta, not BOINC btw. BOINC is rock solid and I have yet to see it break on any of my machines. Do you have any ideas on the glibc error? |
Mod.Sense Volunteer moderator Send message Joined: 22 Aug 06 Posts: 4018 Credit: 0 RAC: 0 |
No ideas. I am not a Rosetta programmer. Suggest you post to the "problems with..." thread for the Rosetta version showing the problems. The programmers focus on monitoring that. Rosetta Moderator: Mod.Sense |
Message boards :
Number crunching :
Error code 193 for nearly all WUs on Linux 2.6
©2024 University of Washington
https://www.bakerlab.org