Error log information and TTY log identifiers

Edit online

The following commands and logging files relate to TTYs.

Command: errclear

This command deletes entries from the error log. The entire log can be erased with errclear 0 or entries with specified 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 encountered by system. The errlog file tends to become quite lengthy. If not cleared on a regular basis, it can occupy quite a bit of space on your hard disk. Use the errclear command mentioned previously to clean out this file.

File: /usr/include/sys/errids.h

The errids.h header file correlates error IDs with error labels.

The following common error report messages relate to TTY:

Table 1. TTY error messages
Message Description Comments
Core Dump Software program abnormally terminated This error is logged when a software program abnormally ends and causes a core dump. Users might not be exiting applications correctly, the system might have been shut down while users were working in application, or the user's terminal might have locked up and the application stopped.
Errlog On Errdaemon turned on This error is logged by the error daemon when the error logging is started. The system automatically turns off error logging during shutdown.
Lion Box Died Lost communication with 64-port concentrator 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 and time stamp to see if user might have caused this message to occur. A series of these errors can indicate a problem with the 64-port adapter or its associated hardware.
Lion Buffero Buffer overrun: 64-port concentrator This error occurs when the hardware buffer in a 64-port concentrator is overrun. If device and cabling allow, try adding request to send (RTS) handshaking to the port and device. Also try lowering the baud rate.
Lion Chunknumc Bad chunk count: 64-port controller 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.
Lion Hrdwre Cannot access memory on 64-port controller This error is logged by the 64-port concentrator driver if it is unable to access memory on the 64-port controller.
Lion Mem ADAP Cannot allocate memory: ADAP structure This error is logged by the 64-port concentrator driver if the malloc routine for the adap structure fails.
Lion Mem List Cannot allocate memory: TTYP_T List This error is logged by the 64-port concentrator driver if the malloc routine for the ttyp_t list structure fails
Lion Pin ADAP Cannot pin memory: ADAP structure This error is logged by the 64-port concentrator driver if the pin routine for the adap structure fails.
SRC Software program error This error is logged by the System Resource Controller (SRC) daemon in the event of some abnormal condition. Abnormal conditions are divided in three areas: failing subsystems, communication failures, and other failures.
Lion Unkchunk Unknown error code from the 64-port concentrator Error Code: Number of characters in the chunk received.
TTY Badinput Bad cable or connection The port is generating input faster than the system can consume it, and some of that input is being discarded. Usually, the bad input is caused by one or more RS-232 signals changing their status rapidly and repeatedly in a short period of time, causing your system to spend a lot of time in the interrupt handler. The signal errors are usually caused by a loose or broken connector; a bad, ungrounded, or unshielded cable; or by a "noisy" communications link.
TTY Overrun Receiver overrun on input Most TTY ports have a 16-character input FIFO, and the default setting specifies that an interrupt is posted after 14 characters have been received. This error is reported when the driver interrupt handler cleared the input FIFO and data has been lost. Potential solutions depend on the hardware you are using:
  • 8-port and 128-port adapters

    Verify that flow control is configured correctly. If it is, run diagnostics, and replace the hardware as appropriate.

  • Native ports

    If the problem happens on an idle system, move the workload to a different port. If that corrects the problem, upgrade the system firmware.

  • General solutions
    • Reduce the "RECEIVE trigger level" parameter for this port from 3 to either 2 or 1.
    • Reduce the line speed on this port.
    • Examine other devices and processes to try to reduce the time that the system is spending with interrupts disabled.
TTY TTYHOG TTYHOG overrun This error is usually caused by a mismatch in the flow control method being used between the transmitter and receiver. The TTY driver has made several attempts to ask the transmitter to pause, but the input has not stopped, causing the data to be discarded. Check the flow control methods configured on each end to make sure that the same method is being used on each.
TTY Parerr Parity/Framing error on input This error indicates parity errors on incoming data to asynchronous ports on a character-by-character basis. This is usually caused by a mismatch in line control parameters (parity, line speed, character size, or number of stop bits) between the transmitter and receiver. Line control parameters have to be set the same on both sides in order to communicate.
TTY Prog PTR Driver internal error This error is logged by the tty driver if t_hptr pointer is null.