Tasks abort with Status 11 (0xb) |
Message boards : Unix/Linux : Tasks abort with Status 11 (0xb)
Author | Message |
---|---|
Hi, |
|
ID: 8510 | Rating: 0 | rate: / | |
Hi, I looked everywhere and the only thing I found was when someone was switching from Seti to Rosetta and back their machine would hang and give the same error message you are getting. One thing to check then would be to see if you are keeping the old unit in memory when switching to the new one. This setting is under Your Account, Computing Preferences and then look for "Leave applications in memory while suspended? (suspended applications will consume swap space if 'yes')". If it is not already set to yes, change it and see if that helps. ____________ |
|
ID: 8514 | Rating: 0 | rate: / | |
Hi, First, a small correction to your report... your tasks are receiving Signal 11, not exiting with Status 11 as you stated. There is a difference. Anyway, BOINC FAQ Service says this about Signal 11. You also have a problem with the network connection. I doubt the Signal 11 is caused by the network connection problem because it's the malariacontrol app that gets the Signal 11. The malariacontrol app does not (at least it should not) be using the network connection. Are you getting the "BOINC can't access Internet - check network connection or proxy configuration" just after you reboot? That does happen to some Linux systems that don't get the network up and running before BOINC starts or else the computer switches to a new connection after BOINC starts. That might be what is causing your network problem or it might not. See Slow network startup at the official BOINC wiki for more info. |
|
ID: 8518 | Rating: 0 | rate: / | |
I may be wrong, but I think I recall signal 11 combined with network problems being related to a missing localhost entry in /etc/hosts file. |
|
ID: 8532 | Rating: 0 | rate: / | |
Message boards : Unix/Linux : Tasks abort with Status 11 (0xb)