Forum > Linux
More trouble with X/K/Ubuntu 9.04 64bit
Urs Echternacht:
--- Quote from: michael37 on 03 May 2009, 02:00:33 pm ---Opened a launchpad bug
https://bugs.launchpad.net/ubuntu/+source/boinc-app-seti/+bug/371337
I hint there that the problem is in libpthread since this library is prominently featured in all stack traces. It would be nice to be more specific and more direct.
--- End quote ---
Could you modify the bug report a bit so it gets clearer that there are different 64bit applications in different 64bit versions are failing to work ?
i.e. optimized astropulse was not seen to fail on other than "Merom" cores, but optimized seti@home seems to fail on other Core 2 cpu's as well.
michael37:
--- Quote from: Urs Echternacht on 03 May 2009, 02:10:28 pm ---Could you modify the bug report a bit so it gets clearer that there are different 64bit applications in different 64bit versions are failing to work ?
i.e. optimized astropulse was not seen to fail on other than "Merom" cores, but optimized seti@home seems to fail on other Core 2 cpu's as well.
--- End quote ---
We know that neither every mb workunit nor every ap workunit fails with optimized application. Are we sure there isn't a workunit that fails on non-Merom Core 2 Duos? I don't want to mislead the developers.
Urs Echternacht:
--- Quote from: michael37 on 03 May 2009, 09:37:56 pm ---
--- Quote from: Urs Echternacht on 03 May 2009, 02:10:28 pm ---Could you modify the bug report a bit so it gets clearer that there are different 64bit applications in different 64bit versions are failing to work ?
i.e. optimized astropulse was not seen to fail on other than "Merom" cores, but optimized seti@home seems to fail on other Core 2 cpu's as well.
--- End quote ---
We know that neither every mb workunit nor every ap workunit fails with optimized application. Are we sure there isn't a workunit that fails on non-Merom Core 2 Duos? I don't want to mislead the developers.
--- End quote ---
Of course, up until the new reports by DeMus, jwalton and others in the seti@home Numbercrunching section (thread now moved to Questions&Answers:Unix/Linux section), there were only your reports and my repros of the problem. It seems now much more wide spread than a few days ago. But that is good for purposes of interpreting where the problem could be found and it is definitly not the cpu's. Tthe combination OS/application is producing this problem. As there were none of these problems reported before the release of Jaunty Jackalope the application (as is) is o.k., the culprit has come with the OS update.
edit: @michael37 Just saw you updated bug reports with some more info.
Jason G:
--- Quote from: Urs Echternacht on 05 May 2009, 07:45:18 am ---...As there were none of these problems reported before the release of Jaunty Jackalope the application (as is) is o.k., the culprit has come with the OS update.
--- End quote ---
Just to report, I was having a conversation with a gentleman yesterday at school, who runs multiple flavours of Linux, under vmWare Vm's hosted under 64 bit Fedora. It seems the same Ubuntu flavours are also having issues in that weird environment, that is without even running Seti@Home applications. He seemed to be of the opinion that there was some ongoing issue with the particular kernel build involved, though I don't know enough about it myself to gauge if there's relevance here to this problem.
Jason
Navigation
[0] Message Index
[*] Previous page
Go to full version