June 2013 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem
by Jeff Hammond 13 Jun '13

13 Jun '13

Sorry, I misinterpreted/misread your question or otherwise acted stupidly. I think http://www.linfo.org/su.html and http://www.howtogeek.com/111479/htg-explains-whats-the-difference-between-s… answer everything in detail, but "sudo" and "su" give you the same environment. Jeff On Thu, Jun 13, 2013 at 9:36 AM, Lee, Eibhlin <eibhlin.lee10(a)imperial.ac.uk> wrote: > In that case there are definitely misleading guides out there. http://www.cyberciti.biz/faq/ubuntu-linux-root-password-default-password/ This implies that sudo bash does log you in as root user. > Either my second question confused you; it wasn't the right question to ask; or the guide I linked to is completely wrong. > Eibhlin > ________________________________________ > From: discuss-bounces(a)mpich.org [discuss-bounces(a)mpich.org] on behalf of Jeff Hammond [jhammond(a)alcf.anl.gov] > Sent: 13 June 2013 15:27 > To: discuss(a)mpich.org > Subject: Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem > > No, of course the root environment is not the same as your user > environment. There are plenty of "intro to Linux" resources online if > you need this kind of information. > > If you want your user environment as root, which I don't think is > particularly safe or a good idea, you can set it with "source > ~${yourusername}/.${yourshell}rc" where yourusername is $USERNAME when > you are not root and yourshell is $SHELL when you are not root. > > The better option is to figure out what environment variables you need > to set in the mpiexec environment that are currently defined in your > user environment and set those manually. > > Jeff > > On Thu, Jun 13, 2013 at 9:15 AM, Lee, Eibhlin > <eibhlin.lee10(a)imperial.ac.uk> wrote: >> Jeff, >> Does that put you into the same environment as sudo bash? Because I have already tried that with no success. >> Eibhlin >> ________________________________________ >> From: discuss-bounces(a)mpich.org [discuss-bounces(a)mpich.org] on behalf of Jeff Hammond [jhammond(a)alcf.anl.gov] >> Sent: 13 June 2013 13:58 >> To: discuss(a)mpich.org >> Subject: Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem >> >> Just su to root instead of using sudo. >> >> Jeff >> >> On Thu, Jun 13, 2013 at 6:56 AM, Lee, Eibhlin >> <eibhlin.lee10(a)imperial.ac.uk> wrote: >>> Hello all, >>> >>> I am trying to use two raspberry-pi to sample and then process some data. >>> The first process samples while the second processes and vice versa. To do >>> this I use gpio and also mpich-3.0.4 with the process manager smpd. I have >>> successfully run cpi on both machines (from the master machine). I have also >>> managed to run a similar program but without the MPI, this involved >>> compiling with gcc and when running putting sudo in front of the binary >>> file. >>> >>> When I combine these two processes I get various error messages. >>> For input: >>> mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >>> the error is: >>> Can't open /dev/mem >>> Did you forget to use 'sudo .. ?' >>> >>> For input: >>> sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >>> the error is: >>> sudo: mpiexec: Command not found >>> >>> I therefore put mpiexec into /usr/bin >>> >>> now for input: >>> sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >>> the error is: >>> Can't open /dev/mem >>> Did you forget to use 'sudo .. ?' >>> >>> Does anyone know how I can work around this? >>> Thanks, >>> Eibhlin >>> >>> >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >> >> >> >> -- >> Jeff Hammond >> Argonne Leadership Computing Facility >> University of Chicago Computation Institute >> jhammond(a)alcf.anl.gov / (630) 252-5381 >> http://www.linkedin.com/in/jeffhammond >> https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond >> ALCF docs: http://www.alcf.anl.gov/user-guides >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > > > -- > Jeff Hammond > Argonne Leadership Computing Facility > University of Chicago Computation Institute > jhammond(a)alcf.anl.gov / (630) 252-5381 > http://www.linkedin.com/in/jeffhammond > https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond > ALCF docs: http://www.alcf.anl.gov/user-guides > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute jhammond(a)alcf.anl.gov / (630) 252-5381 http://www.linkedin.com/in/jeffhammond https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond ALCF docs: http://www.alcf.anl.gov/user-guides

1 0

Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem
by Gus Correa 13 Jun '13

13 Jun '13

Hi Lee How about replacing "~/main" in the mpiexec command line by one-liner script? Say, "sudo_main.sh", something like this: #! /bin/bash sudo ~/main After all, it is "main" that accesses /dev/mem, and needs "sudo" permissions, not mpiexec, right? [Or do the mpiexec-launched processes inherit the "sudo" stuff from mpiexec?] Not related, but, instead of putting mpiexec in /usr/bin, can't you just use the full path to it? I hope this helps, Gus Correa On 06/13/2013 10:09 AM, Lee, Eibhlin wrote: > Pavan, > I had a lot of trouble getting hydra to work without having to enter a password/passphrase. I saw the option to pass a phrase in the mpich installers guide. I eventually found that for that command you needed to use the smpd process manager. That's the only reason I chose smpd over hydra. > As to your other suggestion. I ran ./main and the same error (Can't open /dev/mem...) appeared. sudo ./main works but of course without multiple processes. > Eibhlin > ________________________________________ > From: discuss-bounces(a)mpich.org [discuss-bounces(a)mpich.org] on behalf of Pavan Balaji [balaji(a)mcs.anl.gov] > Sent: 13 June 2013 14:34 > To: discuss(a)mpich.org > Subject: Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem > > I just saw your older email. Why are you using smpd instead of the > default process manager (hydra)? > > -- Pavan > > On 06/13/2013 08:05 AM, Pavan Balaji wrote: >> >> What's "-phrase"? That's not a recognized option. I'm not sure where >> the /dev/mem check is coming from. Try running ~/main without mpiexec >> first. >> >> -- Pavan >> >> On 06/13/2013 06:56 AM, Lee, Eibhlin wrote: >>> Hello all, >>> >>> I am trying to use two raspberry-pi to sample and then process some >>> data. The first process samples while the second processes and vice >>> versa. To do this I use gpio and also mpich-3.0.4 with the process >>> manager smpd. I have successfully run cpi on both machines (from the >>> master machine). I have also managed to run a similar program but >>> without the MPI, this involved compiling with gcc and when running >>> putting sudo in front of the binary file. >>> >>> When I combine these two processes I get various error messages. >>> For input: >>> mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >>> the error is: >>> Can't open /dev/mem >>> Did you forget to use 'sudo .. ?' >>> >>> For input: >>> sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >>> the error is: >>> sudo: mpiexec: Command not found >>> >>> I therefore put mpiexec into /usr/bin >>> >>> now for input: >>> sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >>> the error is: >>> Can't open /dev/mem >>> Did you forget to use 'sudo .. ?' >>> >>> Does anyone know how I can work around this? >>> Thanks, >>> Eibhlin >>> >>> >>> >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >>> >> > > -- > Pavan Balaji > http://www.mcs.anl.gov/~balaji > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem
by Lee, Eibhlin 13 Jun '13

13 Jun '13

In that case there are definitely misleading guides out there. http://www.cyberciti.biz/faq/ubuntu-linux-root-password-default-password/ This implies that sudo bash does log you in as root user. Either my second question confused you; it wasn't the right question to ask; or the guide I linked to is completely wrong. Eibhlin ________________________________________ From: discuss-bounces(a)mpich.org [discuss-bounces(a)mpich.org] on behalf of Jeff Hammond [jhammond(a)alcf.anl.gov] Sent: 13 June 2013 15:27 To: discuss(a)mpich.org Subject: Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem No, of course the root environment is not the same as your user environment. There are plenty of "intro to Linux" resources online if you need this kind of information. If you want your user environment as root, which I don't think is particularly safe or a good idea, you can set it with "source ~${yourusername}/.${yourshell}rc" where yourusername is $USERNAME when you are not root and yourshell is $SHELL when you are not root. The better option is to figure out what environment variables you need to set in the mpiexec environment that are currently defined in your user environment and set those manually. Jeff On Thu, Jun 13, 2013 at 9:15 AM, Lee, Eibhlin <eibhlin.lee10(a)imperial.ac.uk> wrote: > Jeff, > Does that put you into the same environment as sudo bash? Because I have already tried that with no success. > Eibhlin > ________________________________________ > From: discuss-bounces(a)mpich.org [discuss-bounces(a)mpich.org] on behalf of Jeff Hammond [jhammond(a)alcf.anl.gov] > Sent: 13 June 2013 13:58 > To: discuss(a)mpich.org > Subject: Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem > > Just su to root instead of using sudo. > > Jeff > > On Thu, Jun 13, 2013 at 6:56 AM, Lee, Eibhlin > <eibhlin.lee10(a)imperial.ac.uk> wrote: >> Hello all, >> >> I am trying to use two raspberry-pi to sample and then process some data. >> The first process samples while the second processes and vice versa. To do >> this I use gpio and also mpich-3.0.4 with the process manager smpd. I have >> successfully run cpi on both machines (from the master machine). I have also >> managed to run a similar program but without the MPI, this involved >> compiling with gcc and when running putting sudo in front of the binary >> file. >> >> When I combine these two processes I get various error messages. >> For input: >> mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >> the error is: >> Can't open /dev/mem >> Did you forget to use 'sudo .. ?' >> >> For input: >> sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >> the error is: >> sudo: mpiexec: Command not found >> >> I therefore put mpiexec into /usr/bin >> >> now for input: >> sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >> the error is: >> Can't open /dev/mem >> Did you forget to use 'sudo .. ?' >> >> Does anyone know how I can work around this? >> Thanks, >> Eibhlin >> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > > > -- > Jeff Hammond > Argonne Leadership Computing Facility > University of Chicago Computation Institute > jhammond(a)alcf.anl.gov / (630) 252-5381 > http://www.linkedin.com/in/jeffhammond > https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond > ALCF docs: http://www.alcf.anl.gov/user-guides > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute jhammond(a)alcf.anl.gov / (630) 252-5381 http://www.linkedin.com/in/jeffhammond https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond ALCF docs: http://www.alcf.anl.gov/user-guides _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] How to keep the VS console window open on exceptions during debug of a parallel code
by Feng Xiao 13 Jun '13

13 Jun '13

Thinking most of people here don't use visual studio very often (me either), I tried several ways and found a solution. It might be useful for someone, so I am writing to you all again to close my own question. I added the following line to the Command Line of Post-Build Event of Build Events on the property pages, "D:\Program Files\MPICH2\bin\mpiexec.exe" -n 2 "$(TargetDir)\$(TargetName).exe" --result_code=no --report_level=no The code executes after the build and all messages are written in the VS output window. On Thu, Jun 13, 2013 at 7:38 AM, Feng Xiao <fxiao(a)mymail.mines.edu> wrote: > Hello all, > > I am writing about how to keep the console window open on exceptions > during debug of a parallel code (either F5 or Ctrl+F5). > I am running MPICH2 FORTRAN program in Visual Studio 2010, everything > works fine, expect that I could not see the exception/error messages on the > console window, it closes right after the program exits on exceptions. > I do know how to keep the console window open when program meets the end, > or put a read statement to pause the program during the execution. > I did some google search, the only relevant solution I could find is > > http://www.boost.org/doc/libs/1_36_0/libs/test/doc/html/utf/usage-recommend…, > which is about making debugger break at the point the failure by adding > extra command line argument and seeing the runtime error in the output > window. However, it looks like something for a serial code without > mpiexec.exe in the command line, and I am not a advanced VS user, so I > don't know how to do it for a parallel code, or if there is any other way > out. > > Thanks in advance! > > -- > Feng Xiao > > Doctoral Student > Petroleum Engineering > Colorado School of Mines > > Cell 918-814-2644 > > -- Feng Xiao Doctoral Student Petroleum Engineering Colorado School of Mines Cell 918-814-2644

1 0

Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem
by Jeff Hammond 13 Jun '13

13 Jun '13

No, of course the root environment is not the same as your user environment. There are plenty of "intro to Linux" resources online if you need this kind of information. If you want your user environment as root, which I don't think is particularly safe or a good idea, you can set it with "source ~${yourusername}/.${yourshell}rc" where yourusername is $USERNAME when you are not root and yourshell is $SHELL when you are not root. The better option is to figure out what environment variables you need to set in the mpiexec environment that are currently defined in your user environment and set those manually. Jeff On Thu, Jun 13, 2013 at 9:15 AM, Lee, Eibhlin <eibhlin.lee10(a)imperial.ac.uk> wrote: > Jeff, > Does that put you into the same environment as sudo bash? Because I have already tried that with no success. > Eibhlin > ________________________________________ > From: discuss-bounces(a)mpich.org [discuss-bounces(a)mpich.org] on behalf of Jeff Hammond [jhammond(a)alcf.anl.gov] > Sent: 13 June 2013 13:58 > To: discuss(a)mpich.org > Subject: Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem > > Just su to root instead of using sudo. > > Jeff > > On Thu, Jun 13, 2013 at 6:56 AM, Lee, Eibhlin > <eibhlin.lee10(a)imperial.ac.uk> wrote: >> Hello all, >> >> I am trying to use two raspberry-pi to sample and then process some data. >> The first process samples while the second processes and vice versa. To do >> this I use gpio and also mpich-3.0.4 with the process manager smpd. I have >> successfully run cpi on both machines (from the master machine). I have also >> managed to run a similar program but without the MPI, this involved >> compiling with gcc and when running putting sudo in front of the binary >> file. >> >> When I combine these two processes I get various error messages. >> For input: >> mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >> the error is: >> Can't open /dev/mem >> Did you forget to use 'sudo .. ?' >> >> For input: >> sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >> the error is: >> sudo: mpiexec: Command not found >> >> I therefore put mpiexec into /usr/bin >> >> now for input: >> sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >> the error is: >> Can't open /dev/mem >> Did you forget to use 'sudo .. ?' >> >> Does anyone know how I can work around this? >> Thanks, >> Eibhlin >> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > > > -- > Jeff Hammond > Argonne Leadership Computing Facility > University of Chicago Computation Institute > jhammond(a)alcf.anl.gov / (630) 252-5381 > http://www.linkedin.com/in/jeffhammond > https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond > ALCF docs: http://www.alcf.anl.gov/user-guides > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute jhammond(a)alcf.anl.gov / (630) 252-5381 http://www.linkedin.com/in/jeffhammond https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond ALCF docs: http://www.alcf.anl.gov/user-guides

1 0

Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem
by Pavan Balaji 13 Jun '13

13 Jun '13

smpd was mainly meant for windows support. It is now deprecated, so we don't officially support that. Someone on the mailing list might help, but no promises. With respect to hydra, problems with that is what you should have reported on this mailing list and we would have tried to help. :-) If ./main itself is not working, there's no hope of getting it to work with mpiexec. You'll need to debug that first. -- Pavan On 06/13/2013 09:09 AM, Lee, Eibhlin wrote: > Pavan, > I had a lot of trouble getting hydra to work without having to enter a password/passphrase. I saw the option to pass a phrase in the mpich installers guide. I eventually found that for that command you needed to use the smpd process manager. That's the only reason I chose smpd over hydra. > As to your other suggestion. I ran ./main and the same error (Can't open /dev/mem...) appeared. sudo ./main works but of course without multiple processes. > Eibhlin > ________________________________________ > From: discuss-bounces(a)mpich.org [discuss-bounces(a)mpich.org] on behalf of Pavan Balaji [balaji(a)mcs.anl.gov] > Sent: 13 June 2013 14:34 > To: discuss(a)mpich.org > Subject: Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem > > I just saw your older email. Why are you using smpd instead of the > default process manager (hydra)? > > -- Pavan > > On 06/13/2013 08:05 AM, Pavan Balaji wrote: >> >> What's "-phrase"? That's not a recognized option. I'm not sure where >> the /dev/mem check is coming from. Try running ~/main without mpiexec >> first. >> >> -- Pavan >> >> On 06/13/2013 06:56 AM, Lee, Eibhlin wrote: >>> Hello all, >>> >>> I am trying to use two raspberry-pi to sample and then process some >>> data. The first process samples while the second processes and vice >>> versa. To do this I use gpio and also mpich-3.0.4 with the process >>> manager smpd. I have successfully run cpi on both machines (from the >>> master machine). I have also managed to run a similar program but >>> without the MPI, this involved compiling with gcc and when running >>> putting sudo in front of the binary file. >>> >>> When I combine these two processes I get various error messages. >>> For input: >>> mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >>> the error is: >>> Can't open /dev/mem >>> Did you forget to use 'sudo .. ?' >>> >>> For input: >>> sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >>> the error is: >>> sudo: mpiexec: Command not found >>> >>> I therefore put mpiexec into /usr/bin >>> >>> now for input: >>> sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >>> the error is: >>> Can't open /dev/mem >>> Did you forget to use 'sudo .. ?' >>> >>> Does anyone know how I can work around this? >>> Thanks, >>> Eibhlin >>> >>> >>> >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >>> >> > > -- > Pavan Balaji > http://www.mcs.anl.gov/~balaji > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem
by Lee, Eibhlin 13 Jun '13

13 Jun '13

Jeff, Does that put you into the same environment as sudo bash? Because I have already tried that with no success. Eibhlin ________________________________________ From: discuss-bounces(a)mpich.org [discuss-bounces(a)mpich.org] on behalf of Jeff Hammond [jhammond(a)alcf.anl.gov] Sent: 13 June 2013 13:58 To: discuss(a)mpich.org Subject: Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem Just su to root instead of using sudo. Jeff On Thu, Jun 13, 2013 at 6:56 AM, Lee, Eibhlin <eibhlin.lee10(a)imperial.ac.uk> wrote: > Hello all, > > I am trying to use two raspberry-pi to sample and then process some data. > The first process samples while the second processes and vice versa. To do > this I use gpio and also mpich-3.0.4 with the process manager smpd. I have > successfully run cpi on both machines (from the master machine). I have also > managed to run a similar program but without the MPI, this involved > compiling with gcc and when running putting sudo in front of the binary > file. > > When I combine these two processes I get various error messages. > For input: > mpiexec -phrase cat -machinefile machinefile -n 2 ~/main > the error is: > Can't open /dev/mem > Did you forget to use 'sudo .. ?' > > For input: > sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main > the error is: > sudo: mpiexec: Command not found > > I therefore put mpiexec into /usr/bin > > now for input: > sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main > the error is: > Can't open /dev/mem > Did you forget to use 'sudo .. ?' > > Does anyone know how I can work around this? > Thanks, > Eibhlin > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute jhammond(a)alcf.anl.gov / (630) 252-5381 http://www.linkedin.com/in/jeffhammond https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond ALCF docs: http://www.alcf.anl.gov/user-guides _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem
by Lee, Eibhlin 13 Jun '13

13 Jun '13

Pavan, I had a lot of trouble getting hydra to work without having to enter a password/passphrase. I saw the option to pass a phrase in the mpich installers guide. I eventually found that for that command you needed to use the smpd process manager. That's the only reason I chose smpd over hydra. As to your other suggestion. I ran ./main and the same error (Can't open /dev/mem...) appeared. sudo ./main works but of course without multiple processes. Eibhlin ________________________________________ From: discuss-bounces(a)mpich.org [discuss-bounces(a)mpich.org] on behalf of Pavan Balaji [balaji(a)mcs.anl.gov] Sent: 13 June 2013 14:34 To: discuss(a)mpich.org Subject: Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem I just saw your older email. Why are you using smpd instead of the default process manager (hydra)? -- Pavan On 06/13/2013 08:05 AM, Pavan Balaji wrote: > > What's "-phrase"? That's not a recognized option. I'm not sure where > the /dev/mem check is coming from. Try running ~/main without mpiexec > first. > > -- Pavan > > On 06/13/2013 06:56 AM, Lee, Eibhlin wrote: >> Hello all, >> >> I am trying to use two raspberry-pi to sample and then process some >> data. The first process samples while the second processes and vice >> versa. To do this I use gpio and also mpich-3.0.4 with the process >> manager smpd. I have successfully run cpi on both machines (from the >> master machine). I have also managed to run a similar program but >> without the MPI, this involved compiling with gcc and when running >> putting sudo in front of the binary file. >> >> When I combine these two processes I get various error messages. >> For input: >> mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >> the error is: >> Can't open /dev/mem >> Did you forget to use 'sudo .. ?' >> >> For input: >> sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >> the error is: >> sudo: mpiexec: Command not found >> >> I therefore put mpiexec into /usr/bin >> >> now for input: >> sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main >> the error is: >> Can't open /dev/mem >> Did you forget to use 'sudo .. ?' >> >> Does anyone know how I can work around this? >> Thanks, >> Eibhlin >> >> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> > -- Pavan Balaji http://www.mcs.anl.gov/~balaji _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] How to keep the VS console window open on exceptions during debug of a parallel code
by Wesley Bland 13 Jun '13

13 Jun '13

Sorry, you probably won't find any VS developers here either. MPICH stopped supporting Windows a few versions back and none of us are likely to know much about the specifics of Visual Studio. You might try somewhere like StackExchange or a similar forum where you're more likely to get a wide variety of people. Wesley On Jun 13, 2013, at 8:38 AM, Feng Xiao <fxiao(a)mymail.mines.edu> wrote: > Hello all, > > I am writing about how to keep the console window open on exceptions during debug of a parallel code (either F5 or Ctrl+F5). > I am running MPICH2 FORTRAN program in Visual Studio 2010, everything works fine, expect that I could not see the exception/error messages on the console window, it closes right after the program exits on exceptions. > I do know how to keep the console window open when program meets the end, or put a read statement to pause the program during the execution. > I did some google search, the only relevant solution I could find is > http://www.boost.org/doc/libs/1_36_0/libs/test/doc/html/utf/usage-recommend…, which is about making debugger break at the point the failure by adding extra command line argument and seeing the runtime error in the output window. However, it looks like something for a serial code without mpiexec.exe in the command line, and I am not a advanced VS user, so I don't know how to do it for a parallel code, or if there is any other way out. > > Thanks in advance! > > -- > Feng Xiao > > Doctoral Student > Petroleum Engineering > Colorado School of Mines > > Cell 918-814-2644 > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

How to keep the VS console window open on exceptions during debug of a parallel code
by Feng Xiao 13 Jun '13

13 Jun '13

Hello all, I am writing about how to keep the console window open on exceptions during debug of a parallel code (either F5 or Ctrl+F5). I am running MPICH2 FORTRAN program in Visual Studio 2010, everything works fine, expect that I could not see the exception/error messages on the console window, it closes right after the program exits on exceptions. I do know how to keep the console window open when program meets the end, or put a read statement to pause the program during the execution. I did some google search, the only relevant solution I could find is http://www.boost.org/doc/libs/1_36_0/libs/test/doc/html/utf/usage-recommend…, which is about making debugger break at the point the failure by adding extra command line argument and seeing the runtime error in the output window. However, it looks like something for a serial code without mpiexec.exe in the command line, and I am not a advanced VS user, so I don't know how to do it for a parallel code, or if there is any other way out. Thanks in advance! -- Feng Xiao Doctoral Student Petroleum Engineering Colorado School of Mines Cell 918-814-2644

1 0