Bug reports for charmm 5.03
Message boards : Windows : Bug reports for charmm 5.03
| Author | Message | |
|---|---|---|
suguruhirahara
Forum moderator Volunteer tester 
Joined: Sep 13 06 Posts: 282 ID: 15 Credit: 56,614 RAC: 0 |
||
|
Finally, my host experienced the error which seems worth to be reported :)
<core_client_version>5.4.11</core_client_version> This error happened suddenly when the workunit was being computed. ____________ 
I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions. |
||
ID:
930 | Rating: 0
| rate:
/
|
||
|
Andre Kerstens
Forum moderator Project tester Volunteer tester 
Joined: Sep 11 06 Posts: 749 ID: 1 Credit: 15,199 RAC: 0 |
||
|
Hi Suguruhirahara,
Finally, my host experienced the error which seems worth to be reported :) ____________ D@H the greatest project in the world... a while from now! |
||
|
ID:
935 | Rating: 0
| rate:
/
|
||
|
suguruhirahara
Forum moderator Volunteer tester
Joined: Sep 13 06 Posts: 282 ID: 15 Credit: 56,614 RAC: 0 |
||
|
Hi Andre,
I haven't seen this error yet, but see that this is the longhorn machine again. At the moment, we do not have such a machine to test our app so it will be hard to reproduce this error in the lab and find out what's going on. I think so, too. The other host which crunches D@H (winxp pro) hasn't faced that error so far. Actually I don't know what caused the error, but when I google the sentence " The program issued a command but the command length is incorrect ", there are around 270 results listed, for example, Windows Error 0x00000000 - 0x0000007F Thanks for reading, suguruhirahara ____________
I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions. |
||
|
ID:
939 | Rating: 0
| rate:
/
|
||
|
suguruhirahara
Forum moderator Volunteer tester
Joined: Sep 13 06 Posts: 282 ID: 15 Credit: 56,614 RAC: 0 |
||
|
Unusual workunit:
http://docking.utep.edu/workunit.php?wuid=8353
<core_client_version>5.4.11</core_client_version> Thanks for reading, suguruhirahara ____________
I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions. |
||
|
ID:
964 | Rating: 0
| rate:
/
|
||
|
suguruhirahara
Forum moderator Volunteer tester
Joined: Sep 13 06 Posts: 282 ID: 15 Credit: 56,614 RAC: 0 |
||
|
Add:
http://docking.utep.edu/result.php?resultid=32795 So I checked the host which crunched the workunits. This is a list of the workunits it crunched. It shows that all of them failed to be finished (even started with normal). I suppose that it's due to the system of the host. The OS of the host is Windows98 and the CPU is Pentium 1... Is it possible for Win9x to run the science application, Charmm 5.03, on itself? Thanks for reading, suguruhirahara ____________
I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions. |
||
|
ID:
965 | Rating: 0
| rate:
/
|
||
|
David Ball
Forum moderator Volunteer tester 
Joined: Sep 18 06 Posts: 274 ID: 115 Credit: 1,634,401 RAC: 0 |
||
|
Add: That computer only has 91.53 MB of memory (probably 96 MB with some used as video memory). I just checked a Charmm WU in progress on XP and the peak memory usage is about 57 MB with a Virtual Machine usage of 180 MB. The BOINC client itself takes about 10 MB. I suspect even with swapping that the machine is just too memory limited. Also, if coppermine P3's are having accuracy problems, I wonder if a plain Pentium would work? -- David |
||
|
ID:
966 | Rating: 0
| rate:
/
|
||
|
David Ball
Forum moderator Volunteer tester
Joined: Sep 18 06 Posts: 274 ID: 115 Credit: 1,634,401 RAC: 0 |
||
|
Unusual workunit: http://docking.utep.edu/workunit.php?wuid=8353 The first one is a P3, probably a coppermine, and shows up as "Validation State: Invalid" in the result (30007). Isn't there a problem with reduced floating point accuracy on P3's that they're working on? It's also running a 5.6.5 core client, but I don't know if that matters. The third one is a Vista machine and also shows "Validation State: Invalid". BTW, is that machine set to "Leave applications in memory while suspended"? I've been wondering if that makes a difference on Charmm? I have all my machines set to "Leave applications in memory while suspended" because other projects have had problems with that in the past. Regards, -- David EDIT: Fixed Quote BBCode tag |
||
|
ID:
967 | Rating: 0
| rate:
/
|
||
|
suguruhirahara
Forum moderator Volunteer tester
Joined: Sep 13 06 Posts: 282 ID: 15 Credit: 56,614 RAC: 0 |
||
|
Thanks for replying, dave
The first one is a P3, probably a coppermine, and shows up as "Validation State: Invalid" in the result (30007). Isn't there a problem with reduced floating point accuracy on P3's that they're working on? It's also running a 5.6.5 core client, but I don't know if that matters. Because the issue is due to the science application, the Manager aren't be the cause. The third one is a Vista machine and also shows "Validation State: Invalid". Thanks, I missed the point. I just saw the outcome. BTW, is that machine set to "Leave applications in memory while suspended"? I've been wondering if that makes a difference on Charmm? Yes, the host is set to leave the application in swap memory. It seems that sometimes the application has the problem in running on Vista. Thanks for reading, suguruhirahara ____________
I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions. |
||
|
ID:
968 | Rating: 0
| rate:
/
|
||
|
suguruhirahara
Forum moderator Volunteer tester
Joined: Sep 13 06 Posts: 282 ID: 15 Credit: 56,614 RAC: 0 |
||
|
Hallo again,
|
||
|
ID:
971 | Rating: 0
| rate:
/
|
||
|
Richard just started to test on a windows 98. It seems that the problem is not in the amount of memory, as somebody suggested, is seems to be related to the OS itself.
|
||
|
ID:
975 | Rating: 0
| rate:
/
|
||
|
Memo wrote:
I am working on the P3 issue and we are suspecting that it might be a problem with the way older machines handle FP operations and stores as David Ball said. I am eagerly awaiting the PIII update, as well as the automated WU generator. So glad to hear they are at the top of your list of things to do. Best of luck to you in finding quick solutions to both of these problems! ~Atomic |
||
|
ID:
1002 | Rating: 0
| rate:
/
|
||
|
Ok automatic WU generator should be working now, but we still have the problem that sometimes there are no work for a platform in the shared memory. But it is at the top of our lists. On the PIII we are working hard and making some progress but it results to be something more complicated than what we expected. I will keep you updated on the issue |
||
|
ID:
1006 | Rating: 0
| rate:
/
|
||
|
suguruhirahara
Forum moderator Volunteer tester
Joined: Sep 13 06 Posts: 282 ID: 15 Credit: 56,614 RAC: 0 |
||
|
Hello,
|
||
|
ID:
1008 | Rating: 0
| rate:
/
|
||
|
Hello, I believe it does. All my testing has been done in linux so far. The problem is that PIII give different results than P4s that is why I think that is very possible that yours are not getting validated because of the same reason. What are the specs of your processor? |
||
|
ID:
1009 | Rating: 0
| rate:
/
|
||
|
suguruhirahara
Forum moderator Volunteer tester
Joined: Sep 13 06 Posts: 282 ID: 15 Credit: 56,614 RAC: 0 |
||
|
Hi memo,
I suspect there is a problem with this host . All of the results it crunched failed to be validated. what is due to this problem? Actually it isn't a host of mine, but one which I found when referring pending results. The host has "GenuineIntel x86 Family 6 Model 8 Stepping 6 996MHz", which is PIII(?). The CPUs which my hosts have are PentiumD(Presler) and PentiumM(Dothan). ____________
I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions. |
||
|
ID:
1010 | Rating: 0
| rate:
/
|
||
|
Memo wrote:
So is this P3 problem happening on Linux too? Or just Windows? I was thinking about installing Linux on mine, to see if it would make a difference in crunching speed and possibly get validated results (and also help pick away at the unbalanced OS specfic workload!) But if it's purely a hardware issue then I will wait. @Suguru: this host of mine is actually an old emachine Celeron 600, but in projects, it displays as a GenuineIntel x86 Family 6 Model 8 Stepping 3 631MHz. I have seen these types of systems, including my own, referred to by devs on the message boards as "P3's". I just went along with it without asking why, as I figured they had a better idea of what they were talking about than I did and was more concerned with getting whatever issue I had solved - but I am glad you asked because I am still kind of curious myself. |
||
|
ID:
1015 | Rating: 0
| rate:
/
|
||
|
Yes is a hardware issue. Linux boxes are having the same problem. |
||
|
ID:
1018 | Rating: 0
| rate:
/
|
||
|
suguruhirahara
Forum moderator Volunteer tester
Joined: Sep 13 06 Posts: 282 ID: 15 Credit: 56,614 RAC: 0 |
||
|
Here is a invalid result of mine.
|
||
|
ID:
1050 | Rating: 0
| rate:
/
|
||
|
David Ball
Forum moderator Volunteer tester
Joined: Sep 18 06 Posts: 274 ID: 115 Credit: 1,634,401 RAC: 0 |
||
|
Celeron is the budget line of Intel Pentium ?s. Yours is basically a P3 with less cache memory on the CPU. It probably also has a 100 MHz FSB memory interface while regular P3's moved on to a 133 MHz memory interface. BTW, if you ever try to upgrade the CPU in that system, it's probably a P3 coppermine core versus the later P3 tualatin(sp?) core. The tualatin required a different motherboard, although they were both called Socket 370. Later P4 based Celerons are basically a P4 with less cache, no hyperthreading, and a 400 MHz memory interface while the regular P4 line moved on to 533 MHz and higher memory interfaces. IIRC, Celeron D is one of the 64 bit P4's with less cache, no hyperthreading, and a 533 MHz memory interface while the P4 moved on to higher speed memory interfaces. Celeron D are not currently Dual Core, but the Celeron D 352 and 356 are based on the P4 Preslar core so they have 512KB cache and lower power requirements due to being built on the 65 nm manufacturing process instead of the 90 nm manufacturing process (P4 Prescott core) that used so much power and produced so much heat. I don't know what the future plans are for the Celeron line. They might change the name completely when they produce a budget Core 2 processor next year. BTW, Sempron is the current budget line of AMD Athlon processors. Back in the time of the P3, the budget Athlon was called a Duron. Note to technical readers, I just called it a memory interface instead of going into the "Intel FSB" versus AMD's "On CPU" memory interfaces. I also left out a lot of other technical details such as varying voltages, Socket 478 and 775 for Intel, Socket A and 754 and 939 and 940 and AM2 for AMD, SDRAM versus RDRAM versus DDR versus DDR2, etc. Note to upgraders: Check with an expert before changing the CPU or memory in a system. Just because the new CPU fits the socket doesn't mean it will work. In some cases it is even likely to fry itself and/or the motherboard if you get the wrong combination of CPU and motherboard. There are similar problems with RAM memory and DIMMs that will fit but won't work because the motherboard doesn't support the proper voltage requirements, etc. Always check with an expert before upgrading. -- David |
||
|
ID:
1051 | Rating: 0
| rate:
/
|
||
|
Thanks for the explanation David! |
||
|
ID:
1052 | Rating: 0
| rate:
/
|
||
|
suguruhirahara
Forum moderator Volunteer tester
Joined: Sep 13 06 Posts: 282 ID: 15 Credit: 56,614 RAC: 0 |
||
|
I found this unusual result, although I'm no sure whether it's due to the science application or not.
<core_client_version>5.4.9</core_client_version> here is an unofficial reference. ____________
I'm a volunteer participant; my views are not necessarily those of Docking@Home or its participating institutions. |
||
|
ID:
1164 | Rating: 0
| rate:
/
|
||
|
We will look into that.
|
||
|
ID:
1169 | Rating: 0
| rate:
/
|
||
|
suguruhirahara
Forum moderator Volunteer tester
Joined: Sep 13 06 Posts: 282 ID: 15 Credit: 56,614 RAC: 0 |
||
|
Error detected:
http://docking.utep.edu/result.php?resultid=42971
<core_client_version>5.4.11</core_client_version> |
||
|
ID:
1232 | Rating: 0
| rate:
/
|
||
|
suguruhirahara
Forum moderator Volunteer tester
Joined: Sep 13 06 Posts: 282 ID: 15 Credit: 56,614 RAC: 0 |
||
|
The same error as above detected:
http://docking.utep.edu/result.php?resultid=42512
|
||
|
ID:
1237 | Rating: 0
| rate:
/
|
||
|
Andre Kerstens
Forum moderator Project tester Volunteer tester
Joined: Sep 11 06 Posts: 749 ID: 1 Credit: 15,199 RAC: 0 |
||
|
I've put this in our bug database and Richard will be looking at it.
The same error as above detected: http://docking.utep.edu/result.php?resultid=42512 ____________ D@H the greatest project in the world... a while from now! |
||
|
ID:
1238 | Rating: 0
| rate:
/
|
||
|
suguruhirahara
Forum moderator Volunteer tester
Joined: Sep 13 06 Posts: 282 ID: 15 Credit: 56,614 RAC: 0 |
||
|
Since 5.03 isn't available for mac/linux yet, I moved this thread to "Windows"
|
||
|
ID:
1321 | Rating: 0
| rate:
/
|
||
Message boards : Windows : Bug reports for charmm 5.03
Database Error: The MySQL server is running with the --read-only option so it cannot execute this statement
array(3) {
[0]=>
array(7) {
["file"]=>
string(47) "/boinc/projects/docking/html_v2/inc/db_conn.inc"
["line"]=>
int(97)
["function"]=>
string(8) "do_query"
["class"]=>
string(6) "DbConn"
["object"]=>
object(DbConn)#31 (2) {
["db_conn"]=>
resource(78) of type (mysql link persistent)
["db_name"]=>
string(7) "docking"
}
["type"]=>
string(2) "->"
["args"]=>
array(1) {
[0]=>
&string(50) "update DBNAME.thread set views=views+1 where id=77"
}
}
[1]=>
array(7) {
["file"]=>
string(48) "/boinc/projects/docking/html_v2/inc/forum_db.inc"
["line"]=>
int(60)
["function"]=>
string(6) "update"
["class"]=>
string(6) "DbConn"
["object"]=>
object(DbConn)#31 (2) {
["db_conn"]=>
resource(78) of type (mysql link persistent)
["db_name"]=>
string(7) "docking"
}
["type"]=>
string(2) "->"
["args"]=>
array(3) {
[0]=>
object(BoincThread)#3 (16) {
["id"]=>
string(2) "77"
["forum"]=>
string(1) "5"
["owner"]=>
string(2) "15"
["status"]=>
string(1) "0"
["title"]=>
string(27) "Bug reports for charmm 5.03"
["timestamp"]=>
string(10) "1163000212"
["views"]=>
string(4) "1977"
["replies"]=>
string(2) "25"
["activity"]=>
string(20) "1.6767435786541e-128"
["sufferers"]=>
string(1) "0"
["score"]=>
string(1) "0"
["votes"]=>
string(1) "0"
["create_time"]=>
string(10) "1160322362"
["hidden"]=>
string(1) "0"
["sticky"]=>
string(1) "0"
["locked"]=>
string(1) "0"
}
[1]=>
&string(6) "thread"
[2]=>
&string(13) "views=views+1"
}
}
[2]=>
array(7) {
["file"]=>
string(63) "/boinc/projects/docking/html_v2/user/community/forum/thread.php"
["line"]=>
int(184)
["function"]=>
string(6) "update"
["class"]=>
string(11) "BoincThread"
["object"]=>
object(BoincThread)#3 (16) {
["id"]=>
string(2) "77"
["forum"]=>
string(1) "5"
["owner"]=>
string(2) "15"
["status"]=>
string(1) "0"
["title"]=>
string(27) "Bug reports for charmm 5.03"
["timestamp"]=>
string(10) "1163000212"
["views"]=>
string(4) "1977"
["replies"]=>
string(2) "25"
["activity"]=>
string(20) "1.6767435786541e-128"
["sufferers"]=>
string(1) "0"
["score"]=>
string(1) "0"
["votes"]=>
string(1) "0"
["create_time"]=>
string(10) "1160322362"
["hidden"]=>
string(1) "0"
["sticky"]=>
string(1) "0"
["locked"]=>
string(1) "0"
}
["type"]=>
string(2) "->"
["args"]=>
array(1) {
[0]=>
&string(13) "views=views+1"
}
}
}
query: update docking.thread set views=views+1 where id=77