Troubleshooting guide

or (for RedHat Linux):

chkconfig –add mx

Alternatively, you may start and stop the driver manually using

su root

/etc/init.d/mx start

/etc/init.d/mx stop

su root

/etc/init.d/mx restart

The mx “stop” script performs the following operations:

• Shuts down the mx_mapper daemon

• ifconfig’s down the myri* ethernet devices

• Unloads the MX modules (using rmmod)

The mx "restart" script performs an mx stop followed by an mx start.

Note:

1. Legacy PCI64-based and PCI32-based Myrinet NICs are not supported.

2. MX must be compiled with the system compiler (gcc for Linux, Mac OS X, and

FreeBSD). We do not support third-party compilers.

3. If you are installing MX on Linux, you must configure/compile/load MX on a Linux

box whose running kernel is configured to match the source kernel tree. Note that

some Linux distributions ship a mismatched source kernel tree.

4. For optimal performance of MX on i386 and x86_64 hosts, write-combining must be

enabled on the PCI chipset. Refer to the MX README for details.

5. For application or middleware developers who need to develop code using the MX

API, refer to the MX API manual (

http://www.myri.com/scs/MX/doc/mx.pdf).

6. If a host is rebooted, you must reload the MX drivers.

The most common /etc/init.d/mx start failures are:

• APIC IRQ conflicts (encountered on several Tyan and AMD motherboards)

• Running kernel / source kernel mismatch

• Defective or inadequate riser cards

The solutions for these problems are summarized in the Myrinet FAQ

(

http://www.myri.com/scs/FAQ/).

Undoubtedly, if you encounter an issue on a specific motherboard or version of Linux,

someone else has too, and it will be documented on the Myricom web site. If not, contact

us at help@myri.com.