BIP bugs |
BIP 0.99a did not compile with uniprocessor kernels |
BIP 0.98 is broken, use version 0.98a instead |
All these bugs are solved in BIP 0.98a.
biproute seems to work but reports failure |
While running biproute, files are normally created in $HOME/.bip on the first machine in the list (with bipmapper launched via rsh). Close to the end, biproute might report the error than $HOME/.bip/map/mapper.routes does not exists because of NFS propagation delays (the rsh completion should imply that the files have been written, but the machine running biproute may still be unable to see them).
The older erratas below are obsolete and will generally provide no clue when using BIP versions >= 0.97 |
BIP driver does not load on LANAI4.3 based cards |
It was because of a conservative check in the code about the different LANAI versions that were known to work.
fatal error detected on lanai |
fatal error detected on lanai: error on LANAI ****************************** DEBUGGING INFO for NODE 1: ...In most cases, these messages were probably due to the failure of BIP and MPI, to meet some real-time constraints with the Myrinet network. This problems are compltely resolved in the recent versions of MPI (please tell us if you have still any problems).
bip_tprobe does not behave as documented |
The documentation was saying that bip_probe return the message size in bytes or words(4 bytes), this is wrong. If there is no message available, it returns 0. If there is some messages, it returns 1.
Message with size not multiple of 4 bytes |
Be aware that plain BIP (as opposed to MPI-BIP) requires sizes multiple of 4 bytes and proper alignement.
Error: "dio_mlock: out of memory" |
Error: "bipcc not in standard arborescence" |
Error: "bipcc not in standard arborescence"Check your PATH variable, the .../bip/bin component should not end with a slash, this is the cause of the error.
BIP does not work with glibc2 (Redhat 5.0, Debian 2.0) |
undefined reference to __init_brk in hook.o
bip_mpi-0.xx-bin.tar.gzand one for the GLIBC2 systems, the distribution is named like.
bip_mpi_glibc2-0.xx-bin.tar.gz
incompatibilities with Portland Group compilers |
BIP 0.93a does not work correctly |
So only very trivial programs were working with this 0.93a release, most programs failed at the first communications.
Note that this only affect the publically available release limited to 4 processors. The unlimited version was correctly generated.
Please upgrade to the BIP0.93b. "0.93a" will definitely not work.
BIP does not work with SMP kernel |
A workaround (not guaranteed) to use plain BIP and MPI-BIP with an SMP kernel is to add the compilation flags -D__SMP__ to the bip/kernel/Makefile and to recompile the dio module. Not that still only one processs on each computer may be used as part of a BIP application.
Note that the bipip network driver will NOT work on a SMP kernel. Mail us if you want to give a try with such configuration.
ipset put suffix after domain name |
A temporary workaround is to put IP adresses with the name ipset looks for into /etc/hosts, for instance, with suffix -t:
192.168.0.2 lhpcd.univ-lyon1.fr-t
Or alternatively to use short name when configuring each machine hostname.
biproute is failing for users with a csh/tcsh shell |
unexpected output:00:ff:...
Linux module for 2.0.30 was the same as 2.0.29 |
The 2.0.30 modules were in fact incorrectly generated and will refuse to be loaded.
Bip IP driver not working on no switch links |
No myrinet route for ...
And all packets will be dropped.
Thanks to Valentin Puente for reporting the problem.
Host names longer than 10 caracters |
The problem will only occur at execution with messages such as:
maragota.atc.unican.es: I am not in the config file
Thanks to Valentin Puente for reporting the problem.
CRC errors ignored |
In BIP-0.9, any CRC error on the network will stop the application with an error message. In BIPIP-0.9, such error packets will be silently drop, the number of such errors can be looked at with ifconfig in the field rx errors.
Thanks to Olivier Dalle for reporting the problem.
Creation of /dev/dio is incorrectly documented |
3) as root, install the kernel module on each computer of the configuration, first create a new device with: 3.1) mknod /dev/dio b 61 0The application will abort on message send greater than 148 bytes with the following message:
opening /dev/dio: No such device
In fact the c should have been b so you must do instead:
3.1) mknod /dev/dio c 61 0 ^^^/dev/dio should look like:
crw-r--r-- 1 root root 61, 0 Feb 24 21:35 /dev/dio
Thanks to Olivier Dalle pointing out the problem.
![]() |
Last modified: Wed Nov 10 00:03:03 MET 1999 © BIP team |