This chapter lists the error messages that the IRIS HIPPI utilities can display.
This section is a reference section containing an alphabetical list of all the error messages that can be displayed by IRIS HIPPI software.
With each error message is a discussion of the problems the message may indicate. The list contains only messages that indicate an error or problem; it does not contain informational messages that occur during normal operation.
Messages are alphabetized according to the following rules:
Each message is alphabetized by the numerals (0–9) and letters (a–z) of the message's text. Numerals precede letters. (Figure 4-1 illustrates the text of an error message.)
Nonletters (for example, - or %) and blank spaces are shown in the text of the message, but are ignored in alphabetization. For example, the message hip_open appears between hipnet and hippi.
When an error message includes an item that the software specifies differently (fills in) for each instance of the message, this item is displayed in italic font and labeled with a generic name (for example, filename). The generic names are skipped for alphabetization purposes. For example, the error message goofy not responding is located under hostname not responding among the “n” listings. Common generic names used in this listing include hostname, interfacename, packet#, version#, userentry, reason, digit, filename, and hexnumeral.
Note: If you cannot find an error message in the listing, identify potential fill-in words, then look up the message without those words. Capitalization is not considered in alphabetization.
The creator of each message is listed, in angled brackets, below the text of the message: (<creator>).
IRIS HIPPI error messages are written into the file /usr/var/adm/SYSLOG or displayed at the terminal; some messages appear in both places. Within the SYSLOG file, each message is preceded by the date, time, host name, name of the process that created the message, and process ID number, as illustrated in Figure 4-1. Only the text of the error message (as illustrated in Figure 4-1) is included in the alphabetic list that follows.
| Note: The list of error messages in this chapter covers only those unique to IRIS HIPPI. Standard system error messages, even when caused by the IRIS HIPPI code, are not covered. |
This section lists the error messages displayed on the console by the IRIS HIPPI utilities and driver. Many of these messages are also written to the SYSLOG file.
#: bad HIPPI unit number
The entry used on the command line with hipcntl to identify the IRIS HIPPI board (hippi#) contains an invalid unit number. Valid command line entries are: hippi0, hippi1, hippi2, and so on, for as many of the installed boards as were located during the last restart.
harpioctl: unknown cmd: command
While attempting to resolve an address, the driver encountered the indicated unknown ioctl command. This indicates that an upper layer application (for example, the ifconfig utility) is passing the unknown ARP command to the driver. Valid ARP commands include SIOCSHARP, SIOCGHARP, SIOCDHARP, and SIOCGHARPTBL.
hip#: ifhip_output: Unsupported addr. family:0xhexnumeral
While processing a packet for transmission, the driver found that the specified destination address does not belong to a supported address family. The packet's address family is indicated by hexnumeral. The packet was not sent.
hipcntl: couldn't get HIPPI statistics: reason
The ioctl call for the command HIPIOC_GET_STATS failed. The reason is any of those described by the intro(2) man page.
hipcntl: couldn't open HIPPI device /dev/hippi#
The open system call for the indicated IRIS HIPPI file device failed. This may indicate that the IRIS HIPPI software has not been installed properly or that it has been partially removed. Use inst to reinstall the IRIS HIPPI software from the CD-ROM or distribution directory.
hipcntl: couldn't set HIPPI accept flag: reason
The ioctl call for the command HIPIOC_ACCEPT_FLAG failed to changed the destination channel's accept/reject setting. The reason is any of those described by the intro(2) man page.
hipcntl: couldn't set src timeout: reason
The ioctl call for the command HIPIOC_STIMEO failed to set a new timeout for the source channel. The reason is any of those described by the intro(2) man page.
hipcntl: Double Warning: may be firmware driver mismatch if you force download.
As hipcntl prepared to download firmware (startup) and discovered that the driver is a debug version, it also discovered that the driver and the firmware that is about to be loaded do not match. This probably indicates a mismatch between the hipcntl utility and the driver. Erase this hipcntl utility and install a copy that matches the driver.
hipcntl: Error: board is already up.
When hipcntl attempted to start the board, it found the board already started.
hipcntl: Error: couldn't get version numbers.
Possible hipcntl/kernel-driver mismatch.
Please autoconfig your system and reboot.
As hipcntl prepared to download firmware (startup), it discovered that it either could not retrieve a version number for the current driver or for the firmware currently loaded into the PROM on the IRIS HIPPI board. This indicates that the IRIS HIPPI driver has not been built into the operating system.
hipcntl: Error: mismatch between kernel driver and hipcntl.
Cannot startup adapter.
You probably need to autoconfig and reboot your system
and/or remove any old copies of hipcntl(1m) on your system.
As hipcntl prepared to download firmware (startup), it discovered that the driver and the firmware that is about to be loaded do not match. This probably indicates a mismatch between the hipcntl utility and the driver. Erase this hipcntl utility, reinstall the IRIS HIPPI software, and build a new operating system.
hipcntl: HIPPI Board is down
The ioctl call for the command HIPIOC_GET_STATS failed because the IRIS HIPPI board is not available (that is,it is shutdown or not responding). To remedy this problem,use command hipcntl startup. If it does not solve the problem, you may need to have the IRIS HIPPI board checked.
hipcntl: problem programming flash: reason
The ioctl call for the command HIPPI_PGM_FLASH failed to download new firmware into the IRIS HIPPI board's PROM. The reason is any of those described by the intro(2) man page. The new firmware has not been loaded into the IRIS HIPPI board's PROM. This message should be preceeded by other error messages indicating problems with the board's FLASH EEPROM. Contact the Silicon Graphics Technical Assistance Center.
hipcntl: trouble bringing up HIPPI: reason
The ioctl call for the command HIPPI_SETONOFF failed to start the IRIS HIPPI board. The reason is any of those described by the intro(2) man page. This message probably indicates that the board is dysfunctional. Invoke hipcntl to shut down the board; then, try to start the board. If this does not succeed, contact the Silicon Graphics Technical Assistance Center.
hipcntl: trouble shutting down HIPPI: reason
The ioctl call for the command HIPPI_SETONOFF failed to shutdown the IRIS HIPPI board. The reason is any of those described by the intro(2) man page.
hipmap: couldn't bind socket: reason
The utility was unable to bind to the raw socket. This indicates a problem with the operating system, not with the IRIS HIPPI software or hardware. The reason is any of those described by the intro(2) man page.
hipmap: couldn't get raw socket: reason
The utility was unable to obtain a raw socket. This indicates a problem with the operating system, not with the IRIS HIPPI software or hardware. The reason is any of those described by the intro(2) man page.
hipmap: couldn't open input file: reason
The file supplied on the command line (for example, /usr/etc/hippi.imap) could not be opened. This can indicate that the file does not exist, or that the permissions are not set correctly. The reason is any of those described by the intro(2) man page.
hipmap: couldn't SIOCDHARP: reason
The SIOCDHARP command within an ioctl system call failed. The reason is any of those described by the intro(2) man page.
hipmap: couldn't SIOCSHARP: reason
The SIOCSHARP command within an ioctl system call failed. The reason is any of those described by the intro(2) man page.
hipmap: malformed address name: IPaddress or hostname
The hostname or IPaddress indicated is not valid. The hostname or IPaddress is a user entry from a file (for example, the /usr/etc/hippi.imap file) or a command line entry.
hipmap: malformed I-field in line: line#
The second entry on the indicated line does not conform to a valid I-field. To be valid, the I-field entry must be a 32-bit value in hexadecimal format (for example, 0x00100003).
hipmap: malformed line: line#
The indicated line in the file being read (for example, /usr/etc/hippi.imap) is not correctly formatted.
hipmap: malformed switch address.
The I-field entered on the command line is not valid. To be valid, the I-field entry must be a 32-bit value in hexadecimal format (for example, 0x0100000C or 0100000C).
hipmap: malformed ULA in line: line#
On the indicated line, there is an optional third entry that does not conform to a valid IEEE universal LAN MAC address (ULA) address. To be valid, the ULA entry must be a 48-bit value in hexadecimal format (for example, 0x7A385CF9028D).
hipmap: trouble flushing harp entry: reason
The SIOCDHARP command failed within an ioctl system call.The reason is any of those described by the intro(2) man page.
hipmap: trouble reading harptable: reason
The SIOCGHARPTBL command failed within an ioctl system call. The reason is any of those described by the intro(2) man page.
hipmap: warning: couldn't resolve name: hostname
The system call, gethostbyname, failed for the indicated IPaddress or hostname. This probably means that the indicated entry does not exist in the host name database (the /etc/hosts file on the local filesystem or on the NIS server).
hippi#: board asleep at iofile:line# with cmd_addr not cmd_addr after cmd_addr at line#
The indicated IRIS HIPPI board (hippi#) controled by the indicated iofile is not responding to commands from the driver. The line# and cmd_addr variables indicate the expected and actual locations in the command queues. Use hipcntl to shut down then startup the IRIS HIPPI board. If this does not resolve the problem, the board is probably dysfunctional. Contact the Silicon Graphics Technical Assistance Center.
hippi#: EEPROM erase FAILED!
While attempting to erase the FLASH EEPROM on the IRIS HIPPI board, the driver encountered an error. Contact the Silicon Graphics Technical Assistance Center.
hippi#: erase FAILED while zeroing flash
While attempting to zero out the FLASH EEPROM on the IRIS HIPPI board, the driver encountered an error. Contact the Silicon Graphics Technical Assistance Center.
hippi#: flash write failed!
While attempting to download new firmware into the FLASH EEPROM on the IRIS HIPPI board, the driver encountered an error. Contact the Silicon Graphics Technical Assistance Center.
hippi#: no board signature!
While the startup software was attempting to initialize the host-to-board interface, the board's initialization firmware did not respond. Contact the Silicon Graphics Technical Assistance Center.
hippi_b2h: unknown op: command
The driver received an unknown command from the IRIS HIPPI board. This may indicate a mismatch between the driver and firmware versions. Contact the Silicon Graphics Technical Assistance Center.
hiptest(DST): couldn't bind fd_i to ULP: reason hiptest(SRC): couldn't bind fd_o to ULP: reason |
The test's HIPIOC_BIND_ULP ioctl() call failed. For the source (SRC), the output (writing) call failed; for the destination (DST), the input (reading) call failed. The reason is any of those described by the intro(2) man page.
This indicates either a problem with the software or too many applications trying to use the ULP-id. Perhaps the driver has not been built into the operating system or the IRIS HIPPI software has not been installed properly. This error message also appears if more than four applications (for example, instances of hiptest) try to use ULP-id 0x89.
hiptest(DST): couldn't open hippi device: reason
hiptest(SRC): couldn't open hippi device: reason
The IRIS HIPPI board (for example, /dev/hippi#) was not found. The reason is any of those described by the intro(2) man page.
For example, this message can indicate that the device file was not found (perhaps the software was not installed properly) or that the board was not located at startup time. To verify the latter, use the /sbin/hinv command.
hiptest(DST): couldn't open hippi device: Permission denied
hiptest(SRC): couldn't open hippi device: Permission denied
You must be superuser to use hiptest.
hiptest(SRC): couldn't set D1_SIZE hdr: reason
The test's HIPIOC_D1_SIZE ioctl() call failed. The reason is any of those described by the intro(2) man page.
This indicates a problem with the software. Perhaps the driver has not been built into the operating system or the IRIS HIPPI software has not been installed properly.
hiptest(SRC): couldn't set I-field: reason
The test's HIPIOC_I ioctl() call failed. The reason is any of those described by the intro(2) man page.
This indicates a problem with the software. Perhaps the driver has not been built into the operating system or the IRIS HIPPI software has not been installed properly.
hiptest(DST): data integrity error at offset byte_offset
hiptest(DST): packet#: expecting tx_data got rcv_data
hiptest(DST): virtual address = ptr_rcv_data
The D2 data in the received packet does not match the D2 data that hiptest sent. The byte_offset variable indicates the word within the packet where the error was detected. The tx_data variable indicates what was sent as compared to rcv_data, which was received. The problematic word of received data is located at ptr_rcv_data.
hiptest(DST): packet#: length error: retv=rcv_bytecount len2=tx_bytecount
The D2 data set from the received packet is not the same size as that sent. The two bytecounts are displayed: rcv_bytecount is for the received packet and tx_bytecount is for the packet that was sent.
hiptest(DST): packet#: trouble reading header: reason
The read() call for the header of the packet specified by packet# failed. The reason is any of those described by the intro(2) man page.
hiptest(DST): packet#: header is bytecount long!? |
The header (that is, FP header and D1 data) for the packet specified by packet# was longer than the header that hiptest sent. The length of the received header is indicated by bytecount. The test always sends 32 bytes.
hiptest(DST): packet#: trouble reading body: reason
The read() call for the body of a packet failed. The reason is any of those described by the intro(2) man page.
hiptest(SRC): packet#: write return value: returnvalue
hiptest(SRC): trouble writing: reason
The write() call for the packet failed, or the connection request that was triggered by this write() failed to open a connection. For example, if there is a switch between the source and destination endpoints, the I-field may be invalid.
The packet# indicates which packet in the series failed, where 0 is the first packet. The returnvalue indicates the number of bytes that were successfully sent; when returnvalue is -1, the write() call failed to send any data. The reason is any of those described by the intro(2) man page.
if_hip#: can't output checksum proto headertype
While processing a packet for transmission, the driver found that the header was not TCP nor UDP, and because of this could not calculate a checksum for the packet. The packet was not sent.
Usage: hipcntl stimeo <value>
The hipcntl command line for setting the source's connection timeout did not contain a valid setting. Valid settings for the timeout value are milliseconds entered in decimal format (for example, hipcntl stimeo 1000 sets the timeout to 1000 milliseconds or 1 second).