01/12/96, 4FAX# 2609 Error Log Information and TTY Log Identifiers SPECIAL NOTICES Information in this document is correct to the best of our knowledge at the time of this writing. Please send feedback by fax to "AIXServ Information" at (512) 823-4009. Please use this information with care. IBM will not be responsible for damages of any kind resulting from its use. The use of this information is the sole responsibility of the customer and depends on the customer's ability to eval- uate and integrate this information into the customer's operational environment. +----------------------------------------------------------+ | | | NOTE: The information in this document is NOT appli- | | cable for AIX 4.1. | | | +----------------------------------------------------------+ ABOUT THIS DOCUMENT This document applies to AIX versions 3.2.3 and later. IMPORTANT ERROR LOGGING FILES AND COMMANDS Command: "errclear" This command deletes entries from the error log. The entire log can be erased with "errclear 0" or entries with speci- fied error ID numbers, classes, or types can be removed. Command: "errpt" This command generates an error report from entries in the system error log. The most used format for this command is "errpt -a | pg" which generates a detailed report starting with the most current errors. File: "/var/adm/ras/errlog" This file stores instances of errors and failures encount- ered by system. The errlog file tends to become quite lengthy and, if not cleared on a regular basis, can occupy quite a bit of space on your hard disk. Use the "errclear" command mentioned above to clean out this file. Error Log Information and TTY Log Identifiers 1 01/12/96, 4FAX# 2609 File: "/usr/include/sys/errids.h" The "errids.h" header file correlates error IDs with error labels. MOST COMMON ERROR REPORT MESSAGES RELATING TO TTYS NOTE: The resource name "cxmadd" shown below for the 128-port adapter may be changed or removed in later versions of AIX. If so, a more specific name will be used in its place which will point out the individual adapter card having problems. Message: "Com_cfg_resid" DESCRIPTION: Configuration failed: resid not correct RESOURCE NAME: cxmadd EXPLANATION: The DDS structure passed from the cfgcxma con- figuration method to the driver configuration entry point is not the correct size. Reinstall the driver software. If the problem persists, contact your service representative. Message: "Com_cfg_uio" DESCRIPTION: Configuration failed: resid not correct RESOURCE NAME: cxmadd EXPLANATION: The DDS structure passed from the cfgcxma con- figuration method to the driver configuration entry point is unreadable. Reinstall the driver software. If the problem persists, contact your service representative. Message: "Com_cfg_deva" DESCRIPTION: Configuration failed: devswadd failed RESOURCE NAME: cxmadd EXPLANATION: The driver configuration entry point encount- ered an error adding entries to the device switch table. Reinstall the driver software. If the problem persists, contact your service representative. Message: "Com_cfg_pin" DESCRIPTION: CONFIGURATION FAILED: PINCODE FAILED RESOURCE NAME: cxmadd EXPLANATION: The driver configuration entry point encount- ered an error pinning driver resources in memory. Reinstall the driver software. If the problem persists, contact your service representative. Error Log Information and TTY Log Identifiers 2 01/12/96, 4FAX# 2609 Message: "Com_cfg_mnr" DESCRIPTION: Configuration failed: bad minor number RESOURCE NAME: cxmadd EXPLANATION: The driver configuration entry point is called with an illegal minor device number. Make sure parameters passed to the configuration method are correct. Reinstall the driver software. If the problem persists, contact your service representative. Message: "Com_cfg_unk" DESCRIPTION: Configuration failed: bad adapter type RESOURCE NAME: cxmadd INSTALL CAUSES: Configuration database improperly set up. FAILURE CAUSES: Adapter type specified not known to this level of driver EXPLANATION: An unknown adapter type is passed to the driver configuration point. Reinstall the driver software. If the problem persists, contact your service represen- tative. Message: "Com_cfg_nadp" DESCRIPTION: Configuration failed: adapter missing RESOURCE NAME: cxmadd INSTALL CAUSES: Configuration database improperly set up. FAILURE CAUSES: Bus configurator error EXPLANATION: An unknown adapter is detected in the slot where the 128-port controller is being configured. Verify that parameters passed to the configuration method are correct. Message: "Com_cfg_devd" DESCRIPTION: Configuration failed: devswdel failed RESOURCE NAME: cxmadd INSTALL CAUSES: Configuration database improperly set up. EXPLANATION: The driver configuration entry point encount- ered an error removing entries to the device switch table. A previous attempt to configure a 128-port controller has failed and left the configuration database in an incomplete state. Verify the adapter is no longer configured. If problem persists, contact your service representative. Error Log Information and TTY Log Identifiers 3 01/12/96, 4FAX# 2609 Message: "Core Dump" DESCRIPTION: Software program abnormally terminated EXPLANATION: This error is logged when a software program abnormally terminates and causes a core dump. Users may not be exiting applications correctly or system may have been shutdown while users were working in application or user's terminal may have locked up and knocked user out of applica- tion. Message: "dasync_cfg_bios" DESCRIPTION: Adapter BIOS initialization failed RESOURCE NAME: cxmadd FAILURE CAUSES: Device driver error or adapter is going bad. EXPLANATION: An error occurred executing the on-board BIOS. Contact service representative. Message: "dasync_cfg_fepos" DESCRIPTION: Adapter FEPOS execution failed RESOURCE NAME: cxmadd FAILURE CAUSES: Device driver error or adapter is going bad. EXPLANATION: An error occurred executing the on-board FEPOS. Contact your service representative. Message: "dasync_cfg_mtst" DESCRIPTION: Adapter memory test failed RESOURCE NAME: cxmadd FAILURE CAUSES: Adapter is going bad EXPLANATION: An error occurred during the reading of the 128-port's dual ported memory. Make sure the controller is fully seated in slot. Contact your service representative. Message: "dasync_cfg_rst" DESCRIPTION: Adapter reset failed RESOURCE NAME: cxmadd FAILURE CAUSES: Adapter is going bad EXPLANATION: The 128-port controller did not respond to reset. Make sure the controller is fully seated in the slot. Error Log Information and TTY Log Identifiers 4 01/12/96, 4FAX# 2609 Message: "dasync_cfg_talloc" DESCRIPTION: talloc failed RESOURCE NAME: cxmadd FAILURE CAUSES: Out of virtual memory space EXPLANATION: An error occurred during an attempt to allo- cate a "trb" timer structure. Contact your service repre- sentative. Message: "dasync_err_evnt" DESCRIPTION: Event handler failure RESOURCE NAME: cxmadd FAILURE CAUSES: Device driver error or adapter is going bad EXPLANATION: An illegal event was received from the 128-port controller. Message: "dasync_io_att" DESCRIPTION: I/O segment attach failed RESOURCE NAME: cxmadd FAILURE CAUSES: Device driver error, or adapter is going bad. EXPLANATION: An error occurred during an attempt the attach to I/O memory and indicates a device driver error. Contact service representative. Message: "dasync_mem_att" DESCRIPTION: Memory segment attach failed RESOURCE NAME: cxmadd FAILURE CAUSES: Device driver error, or adapter is going bad. EXPLANATION: An error occurred during an attempt to attach to bus memory and caused a device driver error. Contact your service representative. Message: "dasync_mem_ch" DESCRIPTION: Can't allocate ch_t structures RESOURCE NAME: cxmadd FAILURE CAUSES: Out of virtual memory space. Error Log Information and TTY Log Identifiers 5 01/12/96, 4FAX# 2609 EXPLANATION: An error occurred during an attempt to "malloc" channel structure memory. Try to isolate those processes which are hoarding memory. If problem reoccurs, obtain a dump and contact a service representative. Message: "dasync_mem_bd" DESCRIPTION: Can't allocate bd_t structures RESOURCE NAME: cxmadd FAILURE CAUSES: Out of virtual memory space. EXPLANATION: An error occurred during an attempt to "malloc" board structure memory. Attempt to identify process which is using up the most memory. Message: "dasync_mem_tty" DESCRIPTION: Can't allocate tty_t structures RESOURCE NAME: cxmadd FAILURE CAUSES: Out of virtual memory space EXPLANATION: An error occurred during an attempt to "malloc" tty structure memory. Try to isolate those proc- esses which are hoarding memory. If problem reoccurs, obtain a dump and contact a service representative. Message: "Errorlog Off" DESCRIPTION: Errdaemon turned off EXPLANATION: This error is logged by the error daemon when the error login is stopped. The system automatically turns off error logging during initialization. Message: "Errlog On" DESCRIPTION: Errdaemon turned on EXPLANATION: This error is logged by the error daemon when the error logging is started. The system automatically turns off error logging during shutdown. Message: "Lion Box Died" DESCRIPTION: Lost communication with 64-port concentrator. EXPLANATION: This error is logged by the 64-port concentrator driver if communications with the concentrator are lost. If you receive this error, check the "Date/Time:" stamp to see if user may have caused this message to occur. A series of these errors can indicate a problem with the 64-port adapter or its associated hardware. Error Log Information and TTY Log Identifiers 6 01/12/96, 4FAX# 2609 Message: "Lion Buffero" DESCRIPTION: Buffer overrun: 64-port concentrator EXPLANATION: This error occurs when the hardware buffer in a 64-port concentrator is overrun. If device and cabling allow, try adding "rts" handshaking to the port and device. Also try lowering baud rate. Message: "Lion Chunknumc" DESCRIPTION: Bad chunk count: 64-port controller. EXPLANATION: This error occurs when the value for the number of characters in a chunk does not match the actual values in the buffer. This error may indicate a problem with the hardware; try running diagnostics on devices. Message: "Lion Hrdwre" DESCRIPTION: Cannot access memory on 64-port controller EXPLANATION: This error is logged by the 64-port concentrator driver if it is unable to access memory on the 64-port controller. Message: "Lion Mem ADAP" DESCRIPTION: Cannot allocate memory: ADAP structure EXPLANATION: This error is logged by the 64-port concentrator driver if malloc() for the adap structure fails. Message: "Lion Mem List" DESCRIPTION: Cannot allocate memory: TTYP_T List EXPLANATION: This error is logged by the 64-port concentrator driver if malloc() for the ttyp_t list struc- ture fails. Message: "Lion Pin ADAP" DESCRIPTION: Cannot pin memory: ADAP structure EXPLANATION: This error is logged by the 64-port voncentrator driver if pin() for the adap structure fails. Message: "SRC" | DESCRIPTION: Software program error EXPLANATION: This error is logged by the system resource controller daemon in the event of some abnormal condition. Abnormal conditions are divided in three areas: failing subsystems, communication failures, and other failures. Error Log Information and TTY Log Identifiers 7 01/12/96, 4FAX# 2609 Message: "Lion Unkchunk" DESCRIPTION: Unknown error code from the 64-port concentrator ERROR CODE: Number of characters in the chunk received. Message: "TTY BADINPUT" DESCRIPTION: Bad tty input return RESOURCE NAME: cxmadd, rsdd, liondd EXPLANATION: If the error code is -1 or ENOMEM, then the problem is that the system is out of cblocks. The error can also be caused by noise on port or cable. This message is logged in a number of places in the driver for various reasons. This means there is a problem between the device driver and the tty subsystem. Message: "TTY Overrun" DESCRIPTION: Receiver overrun on input EXPLANATION: The sending device is ignoring flow control and overloading the hardware buffer on the adapter. This occurs prior to the driver accessing the hardware FIFO. Try adding rts to the port and to device (if possible). Message: "TTY TTYHOG" DESCRIPTION: TTYHOG Overrun EXPLANATION: The sending device is ignoring flow control. This error occurs after the hardware FIFO has been accessed and has written to the software buffer. In other words the tty hog error is logged because the buffer where incoming characters are placed is overflowing. When the buffer is about 3/4's full, the device driver notifies the hardware (in this case tty) to send the XOFF char to the sender to stop sending data. If the sender continues to send data AND the buffer is not emptied, the device driver flushes the buffer and logs the error message in the error log. Message: "TTY Parerr" DESCRIPTION: Parity/framing error on input EXPLANATION: Parity errors on incoming data to asynchronous ports on a character-by-character basis. Message: "TTY Prog PTR" DESCRIPTION: Software error: T_HPTR field invalid EXPLANATION: This error is logged by the TTY driver if "t_hptr" pointer is null. Error Log Information and TTY Log Identifiers 8 01/12/96, 4FAX# 2609 READER'S COMMENTS Please fax this form to (512) 823-4009, attention "AIXServ Informa- tion". You may also e-mail comments to: elizabet@austin.ibm.com. These comments should include the same customer information requested below. Use this form to tell us what you think about this document. If you have found errors in it, or if you want to express your opinion about it (such as organization, subject matter, appearance) or make sug- gestions for improvement, this is the form to use. If you need technical assistance, contact your local branch office, point of sale, or 1-800-CALL-AIX (for information about support offer- ings). These services may be billable. Faxes on a variety of sub- jects may be ordered free of charge from 1-800-IBM-4FAX. Outside the U.S. call 415-855-4329 using a fax machine phone. When you send comments to IBM, you grant IBM a nonexclusive right to use or distribute your comments in any way it believes appropriate without incurring any obligation to you. NOTE: If you have a problem report or item number, supplying that number may help us determine why a procedure did or did not work in your specific situation. Problem Report or Item #: Branch Office or Customer #: Be sure to print your name and fax number below if you would like a reply: ______________________________________________________________________ END OF DOCUMENT (errpt.zap, 4FAX# 2609) Error Log Information and TTY Log Identifiers 9