[mvapich-discuss] MVAPICH2 1.7 + LiMIC2 0.5.5
Jonathan Perkins
perkinjo at cse.ohio-state.edu
Fri Feb 24 10:53:04 EST 2012
On Fri, Feb 24, 2012 at 04:47:20PM +0100, Tibor Pausz wrote:
> Hello Karl,
>
> thanks for the adwise.
>
> Am 24.02.2012 16:24, schrieb Karl Schulz:
> > One other possible thing to check is to see if the limic device is created correctly when the kernel module is loaded. If you don't have a /dev/limic after loading the module, that can be a problem (which you can resolve with mknod)
> The output from
>
> srun ls -l /dev/limic
> crw-rw---- 1 root root 246, 0 24. Feb 10:19 /dev/limic
> crw-rw---- 1 root root 246, 0 24. Feb 10:19 /dev/limic
It looks like this is the problem. On a working installation I get the
following...
[perkinjo at head ~]$ srun -n 2 ls -l /dev/limic
crw-r--r-- 1 root root 249, 0 Feb 22 01:32 /dev/limic
crw-r--r-- 1 root root 249, 0 Feb 22 01:32 /dev/limic
It seems that the mask of device file didn't take effect and non-root
users cannot read the device.
Do you know with which options LiMIC2 was configured? I suggest
`--enable-module --prefix=/usr --sysconfdir=/etc'.
--
Jonathan Perkins
http://www.cse.ohio-state.edu/~perkinjo
More information about the mvapich-discuss
mailing list