Error code 193 for nearly all WUs on Linux 2.6

Message boards : Number crunching : Error code 193 for nearly all WUs on Linux 2.6

To post messages, you must log in.

AuthorMessage
root

Send message
Joined: 16 Feb 09
Posts: 6
Credit: 24,387
RAC: 0
Message 59918 - Posted: 2 Mar 2009, 11:34:45 UTC

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?
ID: 59918 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
root

Send message
Joined: 16 Feb 09
Posts: 6
Credit: 24,387
RAC: 0
Message 60029 - Posted: 8 Mar 2009, 23:28:12 UTC - in response to Message 59918.  

Nobody has this problem?
ID: 60029 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
th3
Avatar

Send message
Joined: 20 Jun 06
Posts: 11
Credit: 540,609
RAC: 0
Message 60030 - Posted: 8 Mar 2009, 23:38:38 UTC - in response to Message 60029.  
Last modified: 8 Mar 2009, 23:39:30 UTC

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)
ID: 60030 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Path7

Send message
Joined: 25 Aug 07
Posts: 128
Credit: 61,751
RAC: 0
Message 60031 - Posted: 9 Mar 2009, 0:02:20 UTC - in response to Message 60029.  

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.
ID: 60031 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
root

Send message
Joined: 16 Feb 09
Posts: 6
Credit: 24,387
RAC: 0
Message 60137 - Posted: 13 Mar 2009, 17:29:24 UTC

@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?
ID: 60137 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
root

Send message
Joined: 16 Feb 09
Posts: 6
Credit: 24,387
RAC: 0
Message 60138 - Posted: 13 Mar 2009, 17:30:43 UTC

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...)?
ID: 60138 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mod.Sense
Volunteer moderator

Send message
Joined: 22 Aug 06
Posts: 4018
Credit: 0
RAC: 0
Message 60142 - Posted: 13 Mar 2009, 19:05:38 UTC

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
ID: 60142 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
root

Send message
Joined: 16 Feb 09
Posts: 6
Credit: 24,387
RAC: 0
Message 60155 - Posted: 13 Mar 2009, 23:43:00 UTC - in response to Message 60142.  

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?
ID: 60155 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote
Mod.Sense
Volunteer moderator

Send message
Joined: 22 Aug 06
Posts: 4018
Credit: 0
RAC: 0
Message 60160 - Posted: 14 Mar 2009, 18:02:02 UTC

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
ID: 60160 · Rating: 0 · rate: Rate + / Rate - Report as offensive    Reply Quote

Message boards : Number crunching : Error code 193 for nearly all WUs on Linux 2.6



©2024 University of Washington
https://www.bakerlab.org