Strange, how come we never, ever managed to trigger that in the beta test? Wrong kinds of system? I mean, I know for sure I rebooted my box (it shows up clearly in the result, too) and it didn't crash. Not even a single little error message. Did all the other "evil" stuff, too, like forcing an update or pausing and resuming 5 times in a row. Rock solid on my box. And I think we had a few X2s on the beta test, too, which got all WUs crunched allright. Ideas, anyone?
Well, as I wrote initially, "It fixes one possible source of the SIGABRT problem". Knowing that this happens when the machine is rebooted is useful. Is there anything in the system logs that might be relevant, such as "process xy doesn't respond, sending ABORT signal"?
No idea here.
I started and stopped BOINC pretty often(manual: 'boinc_cmd --quit' or through my init scripts), no problems at all. I can start the graphics, stop them and start them again. Tested so far 2 of 3 systems with X11 installed, one Athlon XP with an old Matrox PCI GK(software rendering/Knoppix 5.2) and my X2 with nvidia openGL(SuSE 10.1). Both work fine.
All my systems run BOINC under a special user account. My X2 runs WinXP pro and Linux in dual boot. The two Linux VMs(OpenSuSE 10.2), that do the crunching under WinXP, don't have X11 installed and must be kept "untouched" or they will not stay at low priority.
@Bernd: Is there hope, that the performance problem for AMD/Win systems gets fixed?
Strange, how come we never, ever managed to trigger that in the beta test? Wrong kinds of system? I mean, I know for sure I rebooted my box (it shows up clearly in the result, too) and it didn't crash. Not even a single little error message. Did all the other "evil" stuff, too, like forcing an update or pausing and resuming 5 times in a row. Rock solid on my box. And I think we had a few X2s on the beta test, too, which got all WUs crunched allright. Ideas, anyone?
Same here. I updated a lot, used kill -TERM several times, had E@H run alongside other projects quite a lot, all without any problem in the beta app. I think it's fair to say that 4.21 runs more stable than the previous linux versions. It might not be perfect (what software is?) but it's an improvement.
@Bernd: Is there hope, that the performance problem for AMD/Win systems gets fixed?
It definitely will. However my first quick shots addressing this (e.g. compiling the relevant code for Windows with the same compiler I used for Linux) didn't yield anything useful (i.e. linking in the above example) yet. I'll continue to work on this.
I am still getting
)
I am still getting :
process got signal 11
called
SIGABRT: abort called
on my AMD x2 when ever I re-boot the machine.
http://einsteinathome.org/task/84134043
Did you use the beta app? If
)
Did you use the beta app?
If not, the problems are hopefully fixed now because BOINC will automaticaly download the new app.
cu,
Michael
ziege', looking at the result
)
ziege', looking at the result shows he's running latest and greatest 4.21
RE: ziege', looking at the
)
Oh, I see. I have overlooked that last position, because I'm used to look at the top of the stderr.txt file.
cu,
Michael
Strange, how come we never,
)
Strange, how come we never, ever managed to trigger that in the beta test? Wrong kinds of system? I mean, I know for sure I rebooted my box (it shows up clearly in the result, too) and it didn't crash. Not even a single little error message. Did all the other "evil" stuff, too, like forcing an update or pausing and resuming 5 times in a row. Rock solid on my box. And I think we had a few X2s on the beta test, too, which got all WUs crunched allright. Ideas, anyone?
Well, as I wrote initially,
)
Well, as I wrote initially, "It fixes one possible source of the SIGABRT problem". Knowing that this happens when the machine is rebooted is useful. Is there anything in the system logs that might be relevant, such as "process xy doesn't respond, sending ABORT signal"?
BM
BM
No idea here. I started and
)
No idea here.
I started and stopped BOINC pretty often(manual: 'boinc_cmd --quit' or through my init scripts), no problems at all. I can start the graphics, stop them and start them again. Tested so far 2 of 3 systems with X11 installed, one Athlon XP with an old Matrox PCI GK(software rendering/Knoppix 5.2) and my X2 with nvidia openGL(SuSE 10.1). Both work fine.
All my systems run BOINC under a special user account. My X2 runs WinXP pro and Linux in dual boot. The two Linux VMs(OpenSuSE 10.2), that do the crunching under WinXP, don't have X11 installed and must be kept "untouched" or they will not stay at low priority.
@Bernd: Is there hope, that the performance problem for AMD/Win systems gets fixed?
cu,
Michael
RE: Strange, how come we
)
Same here. I updated a lot, used kill -TERM several times, had E@H run alongside other projects quite a lot, all without any problem in the beta app. I think it's fair to say that 4.21 runs more stable than the previous linux versions. It might not be perfect (what software is?) but it's an improvement.
CU
BRM
RE: @Bernd: Is there hope,
)
It definitely will. However my first quick shots addressing this (e.g. compiling the relevant code for Windows with the same compiler I used for Linux) didn't yield anything useful (i.e. linking in the above example) yet. I'll continue to work on this.
BM
BM
Just ask if you need another
)
Just ask if you need another beta test ;-) I can run Windows, too.