one of my folders jsut picked up a tinker as well, despite running the 1.54 core and the -advmethods flag....
Printable View
one of my folders jsut picked up a tinker as well, despite running the 1.54 core and the -advmethods flag....
Well, one thing I have noticed is that the -forceasm on the 3.25 beta, nor the forceSSE on the 4.01 beta work on a tinker, heck as for as I can see I don`t even get a 3D now boost either.Quote:
Originally posted by thebove
one of my folders jsut picked up a tinker as well, despite running the 1.54 core and the -advmethods flag....
the one system i have here that picked up a tinker is my 1.6GHz xp1800, which runs 3.25 -advmethods -forceasm, and i DO have an "Extra SSE Boost OK" in my log file for it. frame times are still over 15 minutes though, and i'm not sure how much difference the tinkers have over the gromacs without SSE, so i don't really have anything to compare it to...Quote:
Originally posted by lonewolfroger
Well, one thing I have noticed is that the -forceasm on the 3.25 beta, nor the forceSSE on the 4.01 beta work on a tinker, heck as for as I can see I don`t even get a 3D now boost either.
I am running the 3.25 beta on my 1600+ running at 1.8ghz also and I am using -advmethods and -forceasm, but I don`t have sse boost showing in my log file, but I am running on the fah_65 core right now, maybe that has something to do with it. I`m on a 681 and it is running at 10 minutes per 1%. Update, I just sent in the results for the tinker, then it downloaded another 1.54 core and I`m back on a gromacs WU, so I guess all that happened was it reasigned me to a new server.Quote:
Originally posted by thebove
the one system i have here that picked up a tinker is my 1.6GHz xp1800, which runs 3.25 -advmethods -forceasm, and i DO have an "Extra SSE Boost OK" in my log file for it. frame times are still over 15 minutes though, and i'm not sure how much difference the tinkers have over the gromacs without SSE, so i don't really have anything to compare it to...
Is it common to have a completed file result kept in the queue for sometime? I resatrted my machine to see if that would help connect to the server. We shall see:confused:
Recently seems a lot more common. We must be overloading their servers. :DQuote:
Originally posted by gkline
Is it common to have a completed file result kept in the queue for sometime? I resatrted my machine to see if that would help connect to the server. We shall see:confused:
Don't worry about those saved WUs, it is kind nice when you finally get 4 or 5 WUs sent up in an hour.
I have not had one of those finished units lost, even when I had a BSOD that wiped the current in progress unit.
Thanks RealBeast. It finally uploaded!:D
Tried 3.25 but no help. This is getting insane. Rig#1 gives me errors even at stock settings. Rig#2 Is okay at stock but if I go so much as 5mhz up on the fsb, I get the same errors. Granted both will eventually start processing a work unit but it takes 10-15 tries (per the log file) on average. As I stated before no errors during the actual folding ONLY when opening up new WU for the first time. Both of these machines have been very stable till now. I tried going up to 1.9vcore on rig#2, didn't help. All my PSU rails are stable and temps are in the low 30C range. None of this is making sense and I never had these problems with SETI. I have a hard time believing this is due to system "stability". I am a freak for stability testing and won't consider a rig good to go unless it'll prime95 + toast for 24-48 hrs straight. I game, produce music, and process DV all the time with no problems. This may be a bios/hardware setting issue in relation to FAH, but I'm not buying the general stability hypothesis. Not sure what to do though.:mad: :mad: :mad: :mad:
Hypo_Luxa, the only thing I can think of is you might have something running in the background, corrupting the download of the WU or interferring with it. Although it happing on both rigs it would seem to be something in common with both of them. Edit to add: you might check here http://forum.folding-community.org for a solution to your problem.
Yeah, that is a good possibility. I'll try shutting down various background stuff and see what happens. It's just frustrating as hell to keep seeing these errors in the log file. I'm not actually dropping units or anything so I guess in the long run I could just live with the errors, but I want to know why it's happening. Also because on rig#2 it seems somehow related to oc'ing, although as I explained before, I'm not sure how. We'll see I guess.
EDIT...
Well, I just checked out that forum link and it appears I am not the only one with this problem. Seems it's happening on both OC and non OC machines with no common denominator yet found. Sad to say, but I feel better that I'm not the only one.
this is weird. not exactly a problem, but today i overclocked my computer too high, and folding crashed with some weird errors. no big deal, i just lowered my settings and everything was fine.
but i just checked the stanford stats page, and my WUs almost doubled from around 130 to 256! anyone know exactly what that means, or where it reads that number from? i seem to remember a couple of other members had relatively high WU numbers a while back.
NM
[20:19:29] Folding@home Gromacs Core
[20:19:29] Version 1.54 (November 26, 2003)
[20:19:29]
[20:19:29] Preparing to commence simulation
[20:19:29] - Assembly optimizations manually forced on.
[20:19:29] - Not checking prior termination.
[20:19:29] Couldn't v3Decompress
[20:19:29] - Fatal: Could not decompress work unit data.
[20:19:29] Error: Could not open work file
[20:19:29]
[20:19:29] Folding@home Core Shutdown: FILE_IO_ERROR
[20:19:33] CoreStatus = 75 (117)
[20:19:33] Error opening or reading from a file.
[20:19:33] Deleting current work unit & continuing...
This is the error as it appears in the log file. I am curious how many others are having this problem but are unaware of it happening. You wouldn't know unless you check your log file regularly, as it will eventually succeed in decompressing a work unit and begin folding. My systems were chugging along completing and uploading WUs for a couple weeks before I checked the log and saw the dozens of decompress errors scattered throughout. Others on the FAH forums are having this problem as well. I only saw one poster who was able to fix his problem. He is running a dual Xeon server and only fixed the problem by replacing BOTH Xeons. This was on the recommendation of another who said it helped him. Although it's always possible, I have a hard time believing both of my cpus are flaky and I'm not about to replace 2 processors because they might (and a big might at that) be causing an FAH error. Common sense would seem to dictate that a flaky processor would error DURING the actual folding as well, as this is technically the most CPU intensive part of the process. Most who are having this problem get no errors at all once a unit is begun. This is a very interesting problem indeed. I am hoping that others on the team will check their logs for this error and post if they have it. Might help figure out a common problem. Thanks to all that have posted advice so far.
Every 24-36 hours my laptop, which is folding 24/7 goes down from a heat issue. It's in a cool room, screen open but off, and sitting up on some books for airflow. Any other ideas? It's a 2.4GHz Sony Vaio.
got any big room fans? other then that, i'm not really sure. those laptops sure can get hot sometimes, can't they.Quote:
Originally posted by RealBeast
Every 24-36 hours my laptop, which is folding 24/7 goes down from a heat issue. It's in a cool room, screen open but off, and sitting up on some books for airflow. Any other ideas? It's a 2.4GHz Sony Vaio.