Vista x64 and SMP
Snarkasm
Madison, WI Icrontian
You guys know my setup - GA-P35-DS4, Q6600, 4 gigs OCZ, etc.
For the life of me, no matter what I try lately, I cannot get the SMP client to retain my position when I reboot. It comes back every time with a "Work_unit_missing" or various things of that nature. When I ctrl-c it, I make sure all the processes have exited, I make a backup folder of the files, and when I reboot, nothin'. The files are on a separate hard drive from the system OS, everything's as ideal as I think I can make it.
Any ideas what the nuts is screwing with it? Maybe I'm not getting every process? Maybe I'm not supposed to force quit the extra processes?
Thanks, guys.
For the life of me, no matter what I try lately, I cannot get the SMP client to retain my position when I reboot. It comes back every time with a "Work_unit_missing" or various things of that nature. When I ctrl-c it, I make sure all the processes have exited, I make a backup folder of the files, and when I reboot, nothin'. The files are on a separate hard drive from the system OS, everything's as ideal as I think I can make it.
Any ideas what the nuts is screwing with it? Maybe I'm not getting every process? Maybe I'm not supposed to force quit the extra processes?
Thanks, guys.
0
Comments
Also a couple of faq's
http://fahwiki.net/index.php/How_do_I_install_the_SMP_Console_client_in_Windows_Vista%3F
http://fahwiki.net/index.php/How_do_I_install_the_CPU_Console_client_in_Windows_Vista%3F
Interestingly, in my recent testing, I found that just a cold reboot works just fine. If I don't even touch the console window and just reboot, it shuts down and comes back exactly where it left off. Apparently handling it with kid gloves is worse than just letting it do its thing.
Yessir! This is my fahlog-prev, it clearly shows the problems. Like I said, currently, if I just cold shut it down, no problem, picks it up perfectly. Towards the end, you'll see exactly that happen. The only difference is the missing_wu errors happen after I ctrl-c and force mpiexec to quit, and then reboot. Until a cold reboot fails me, I guess I'll just keep doing that.
(Hopefully this isn't incredibly miserably long, I put the code tags in, but I've never used them before)
log-prev:
And from there on it pretty much just picks up correctly because I haven't forced a quit since. That's as far back as the log appears to go, sadly. Hope it helps if you have an idea.