This chapter contains kernel error messages specific to ptx/SPDRIVERS V3.2.2. You can place this chapter in your DYNIX/ptx Error Messages binder so that all DYNIX/ptx error message documentation will be located in the same place.
The kernel error messages are grouped by type: PANIC, WARNING, and TO USER. When you need to look up an error message, go to the section of this document that corresponds to the message type.
Variables in the error messages are specified by the following conversion strings:
When such a variable appears in an error message, you will see an actual value in that position when the message is displayed on your screen or console.
For more information about conversion strings, refer to the printf(3S) man page.
The kernel "panics" whenever it detects an irreparable problem in one of its data structures or encounters a hardware error that causes the entire system to fail catastrophically. A panic usually proceeds as follows:
The CPU that panicked sends NMI (nonmaskable interrupt) signals to the other CPUs to shut them down.
The kernel prints the word PANIC: on the console, along with a message describing the reason for the panic.
The kernel prints a hexadecimal stack dump and a stack trace from the process that the CPU was executing at the time of the panic. This is usually, but not always, the process that caused the panic.
The kernel attempts to synch the disks (that is, to copy all cached disk blocks from memory to disk). Occasionally, it will be impossible to complete the synch operation. For example, a data structure needed for the operation might have been locked by one of the other (now paused) CPUs. In this case, the message sync timeout will appear.
The kernel terminates, returning to the power-up monitor. If you have set the monitor's secondary reboot string (the dump string) and have enabled auto-reboot (by using the AUTO button), the monitor automatically invokes the stand-alone dump utility to save a copy of system memory. If auto-reboot is not set, you will see the power-up monitor prompt. At this point, you should manually obtain a dump of system memory. Refer to the DYNIX/ptx V4.5 System Recovery and Troubleshooting Guide for information about the dump command.
Panics can be caused by an incorrect system configuration. If you have just installed a new kernel, check its configuration. If the system had been running properly and you are sure it is configured correctly, contact customer support.
Tried to deconfigure a device that is not in devsw or it has active references other than this caller. Indicates a software error.
Unexpected command is passed to scsimc_send(). Internal software error. Call service.
It's a logic error to not have a valid dev structure, and not installed in the devsw table.
Failure from devsw_add() is not expected at this point. This indicates some logic error.
Warning messages are generated when the kernel encounters an error condition that does not affect the entire system. Typically, warning messages are caused by situations such as a request for space in an operating-system data structure that is filled to capacity, or a hardware error that causes an operation to fail.
Some of the following error messages suggest a corrective action. Typically, if a data structure is filled, you can reconfigure the kernel to increase the size of the data structure. If a filesystem is full, you can delete unneeded files from the filesystem or add additional disks. If you have a hardware problem that you cannot correct, contact customer support.
The ml, ms, mw, or mxdriver was unable to add the drive to the devsw data structure. This condition indicates that some other driver is using the same major number or memory corruption. The device is unavailable until it is reconfigured.
Check if all the tape drives are connected to the same SCSI bus as the medium changer. Or may be some of the tape drives of this changer are deconfigured before the first open of the medium changer.
The specified tape device provides status that indicates the device needs cleaning. The device should be cleaned before further use. Consult device documentation for instructions on cleaning.
Burst size parameter is not programmed correctly. Check the Space file if the parameter value is acceptable to the DLT tape drives.
The tape drive was programmed to a specific set of parameters, but did not acknowledge correct parameters when queried in verification.
The tape drive was programmed to a specific set of parameters, but did not acknowledge correct parameters when queried in verification.
Write delay time parameter is not programmed correctly. Check the Space file if the parameter value is acceptable to the DLT tape drives.
The requested tape drive was programmed to a specific set of parameters, but did not acknowledge correct parameters when queried in verification. Check if all the tunable parameters are set properly.
Compression page is not programmed correctly. Check if the drive supports compression for the given density.
INQUIRY command has failed. This is a serious error. The underlying adapter will be the culprit.
This failure can be because of a UNIT ATTENTION or a diagnostic failure.
INQUIRY command has failed. This is a serious error. The underlying adapter will be the culprit.
This failure can be because of a UNIT ATTENTION or a diagnostic failure.
This failure can be because of a UNIT ATTENTION or a diagnostic failure.
This failure can be because of a UNIT ATTENTION or a diagnostic failure.
This failure can be because of a UNIT ATTENTION or a diagnostic failure.
This command fails for EXB-10i if there is a cartridge in the CMH.
The SCSI adapter providing service to this media changer can not support large enough SCSI commands and sense data buffers.
Adapter could not send the command to the device. Adapter/device failure.
Internal error or inappropriate unit options. May be something wrong with the Space File.
This SCSI Termination status is unknown to the driver. Not expected from SCSI devices.
Unexpected SCSI Sense Key value from device.
Unexpected Error Code from the device.
At first open of a device, the tdstack stacker driver needs to request information from the device for use during normal operation. The driver was unable to get this information from the device.
INQUIRY command has failed. This is a serious error. The underlying adapter will be the culprit.
SCSI INIT ELEMENT STATUS command has failed. Stacker requires service.
To-user messages occur when a user operation fails. They appear only on the user's terminal.
The scsitape driver has a verbose mode; this message provides status information to the user.
This failure can be because of a UNIT ATTENTION or a diagnostic failure.
The td or tl driver was waiting on open for the device to become ready, and was interrupted out of the wait. The open will return with an error.
The scsitape driver has a verbose mode; this message provides status information to the user.
A td device which was not initially ready for use when opened became ready within the configured wait time.
The scsitape driver has a verbose mode; this message provides status information to the user.
The specified tape device provides status that indicates the device needs cleaning. The device should be cleaned before further use. Consult device documentation for instructions on cleaning.
The scsitape driver has a verbose mode; this message provides status information to the user.
The scsitape driver has a verbose mode; this message provides status information to the user.
The scsitape driver has a verbose mode; this message provides status information to the user.
The scsitape driver has a verbose mode; this message provides status information to the user.
User requested compression, but the drive doesn't support compression.
The td or tl device was not ready when opened and was either not configured to wait or timed out waiting for the device to become ready. This typically happens when there is no cartridge in the drive, or the open occurs immediately after the cartridge was inserted and the driver is not configured for a long enough wait time, since the tl device takes some time to become ready after a cartridge is inserted.
A DLT drive that was not initially ready for use when opened, became ready within the configured wait time.
The specified DAT drive does not support compression as requested by the user.
The requested tape drive detected that the write-protect mechanism is enabled. Corrective action:enable write operations on the drive and/or on the tape or cartridge itself.
The scsitape driver has a verbose mode; this message provides status information to the user.
The requested tape drive detects that logical write protection is enabled. This could consist of any combination of: Associated, Persistent, or WORM Write Protection. Corrective action: Reset Associated or Persistent; WORM unchangeable.
The requested tape drive detects that the write protect mechanism is enabled. Corrective action: enable write operations on the drive and/or on the tape or cartridge itself.
The scsitape driver has a verbose mode; this message provides status information to the user.
The scsitape driver has a verbose mode; this message provides status information to the user.
The scsitape driver has a verbose mode; this message provides status information to the user.
A tape density value was requested that is not supported on the current tape cartridge type. Either use a different typed cartridge or request a different density.
The scsitape driver has a verbose mode; this message provides status information to the user.
The user requested a diagnostic ID through TCIOC_RCV_DIAG IOCTL that does not have a result.
The user passed in an invalid diagnostic ID to the TCIOC_SND_DIAG IOCTL
This is an informational message from the td or tl driver indicating that on open, the indicated device was not ready, and that the driver will wait up to the configured number of seconds for it to become ready. A drive is not ready if there is no cartridge inserted, and for several seconds immediately after a new cartridge is inserted.
The scsitape driver has a verbose mode; this message provides status information to the user.
The scsitape driver has a verbose mode; this message provides status information to the user.
The scsitape driver has a verbose mode; this message provides status information to the user.
Tape is already loaded in the drive.
The scsitape driver has a verbose mode; this message provides status information to the user.
The scsitape driver has a verbose mode; this message provides status information to the user.
The scsitape driver has a verbose mode; this message provides status information to the user.
The scsitape driver has a verbose mode; this message provides status information to the user.
The scsitape driver has a verbose mode; this message provides status information to the user.