Fahmon problem

Associate
Joined
17 May 2006
Posts
1,189
Location
Manchester, UK
I have had a few 'Double Gromacs B' WUs and Fahmon tells me that they will take much less time than they do and therefore that my PPD will be more than 3x what it should be.

fahmon.jpg


This screenshot shows that my WU will finish in 8 mins even though it's only 48% done.

When i try to submit a FahMon bug report I just get this page:

http://trac.fahmon.net/wiki/ReportingBugs

Which is titled 'How to Submit a Bug Report'. Unfortunately it only tells me what to do before submitting a Bug Report rather than How to Submit a Bug Report. I must be missing something really obvious. Can someone tell me if this is a known bug and if not point me in the direction of submitting the bug?

Thanks muchly
 
Thanks rich, it's always worthwhile posting in this forum. Probably the best thing about being in this team :)
 
Nice one, it works fine. Thanks again. Guess no-one else here has come accross this problem (specifically p3097) as you're all SMP fiends.. ;)
 
Assuming that rich's info in the html page is correct then this 3907 WU is easily the best ppd of any WU I have crunched on this PC. I'm getting 618ppd (based on the last three frames). My next highest (and this PC has done _a lot_ of WUs) is 479ppd from project 2611. A lot of WUs I just get around 120ppd.
 
Heh, now things are really f'd up. My last successfull WU went from 0-100 and sent fine, then the core crashed as soon as it got new work 3 times in a row causing 3 EUEs without any frames being completed. Now it's started a 3907 WU from frame 50 even though I can't see how I had any WUs that got to frame 50 and stopped. It's also not a newly downloaded WU that is doing frames 50 to 100.

This is causing FahMon to read this new WU as 100% complete right from when it started. Guess I will edit rich's html file it's looking at.
 
Last edited:
hmm, unitinfo.txt is showing it as 100% complete too. and Fahlog.txt doesn't show anything beyond the client closing the previous time i closed it. So the new work starting from 50 is not showing in Fahlog. I'll play around and see what I can do.
 
rich: yeah they were all Gen 1. This new one that started from 50 though is a Gen 0 which previously i've not had problems with. Perhaps the core crashes borked this one and when the WU completes I'll have to delete the work.

Snapshot: FahMon was originally showing twice what it showed once I started using rich's html for the proper WU info for a 3907. So yeah, these are the best ppd WUs I have ever had. I get slightly more ppd from my A64 4000 than you get from each core of your stock 6300.

Here's my current situation.

fahscreens.jpg


As you can see the WU is progressing and using CPU time but it doesn't show up in the Fahlog.txt. I have restarted the console and my PC but the result is the same. I'll see what happens when it gets to 100
 
Now i've got a Gen 1 p3907 that hasn't crashed but Fahlog still isn't updating. The last WU sent ok. oddly.
 
Back
Top Bottom