messages man page on Xenix

Man page or keyword search:  
man Server   1130 pages
apropos Keyword Search (all sections)
Output format
Xenix logo
[printable version]



     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

     Name
	  messages - Description of system console messages.

     Description
	  This section describes the various system messages which may
	  appear on the system console.	 All messages are displayed in
	  the following format:

	       label:severity:comment

	  The segments break down as follows:

	  label
	       Name of the driver or routine where the error occurred.

	  severity
	       The level of error severity, consisting of four levels:

	  PANIC	    These fatal messages indicate
		    hardware problems or kernel
		    inconsistencies that are too
		    severe for continued
		    operation.	After displaying a
		    PANIC message, the system
		    stops.  Rebooting is required.

	  ERROR	    Resource use has been
		    affected.  Some corrective
		    action is needed.

	  WARNING   An error indication that
		    should be monitored (example,
		    free file space is low) but
		    requires no immediate action.

	  INFO	    Some information about the
		    system is provided.

	  comment
	       A field containing information about the problem at
	       hand.

	  action
	       The course of action to remedy the situation.

	  The system services error messages are generated by the
	  shell and do not follow the above convention.

	System Message Meanings
	  The following classifications are meant to be a key for you
	  to use to determine the actions to take to correct an error
	  situation. Each kernel message will have one of the

     Page 1					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  following three classifications listed with it. The
	  classifications are:

	  System inconsistency
	       A contradictory situation exists in the kernel.

	  Abnormal
	       A probably legitimate but extreme situation exists.

	  Hardware
	       Indicates a hardware problem.

	  System inconsistency messages indicate problems usually
	  traceable to hardware malfunction, such as memory failure.
	  These messages rarely occur since associated hardware
	  problems are generally detected before such an inconsistency
	  can occur.

	  Abnormal messages represent kernel operation problems, such
	  as the overflow of critical tables.  It takes extreme
	  situations to bring these problems about, so they should
	  never occur in normal system use.  However, in some cases
	  you can modify the kernel parameters that are causing the
	  error message.  Use the configure(ADM) utility to make the
	  necessary changes.

	  Hardware messages normally specify the device, dev, that
	  caused the error.  Each message gives a device specification
	  of the form nn/mm where nn is the major number of the
	  device, and mm is its minor number.  The command pipeline

	       ls -l /dev | grep nn | grep mm

	  may be used to list the name of the device associated with
	  the given major and minor numbers.

     System Messages
	  **  Normal System Shutdown  **
	       This message appears when the system has been shutdown
	       properly.  It indicates that the machine may now be
	       rebooted or powered down.

	  kernel:PANIC:** ABNORMAL System Shutdown **
	       This message appears when errors occur during system
	       shutdown.  It is usually accompanied by other system
	       messages.  System inconsistency, fatal.

	  kernel:WARNING:bad block on dev nn/mm
	       A nonexistent disk block was found on, or is being
	       inserted in, the structure's free list.	System
	       inconsistency.

     Page 2					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  kernel:WARNING:bad count on dev nn/mm
	       A structural inconsistency in the superblock of a file
	       system. The system attempts a repair, but this message
	       will probably be followed by more complaints about this
	       file system.  System inconsistency.

	  kernel:WARNING:Bad free count on dev nn/mm
	       A structural inconsistency in the superblock of a file
	       system. The system attempts a repair, but this message
	       will probably be followed by more complaints about this
	       file system.  System inconsistency.

	  kernel:ERROR:error on dev name (nn/mm)
	       This is the way that most device driver diagnostic
	       messages start.	The message will indicate the specific
	       driver and complaint.  The name is a word identifying
	       the device.

	  kernel:ERROR:iaddress > 2^24
	       This indicates an attempted reference to an illegal
	       block number, one so large that it could only occur on
	       a file system larger than 8 billion bytes.  Abnormal.

	  kernel:WARNING:Inode table overflow
	       Each open file requires an inode entry to be kept in
	       memory.	When this table overflows, the specific
	       request (usually open(S) or creat(S)) is refused.
	       Although not fatal to the system, this event may damage
	       the operation of various spoolers, daemons, the mailer,
	       and other important utilities.  Abnormal results and
	       missing data files are a common result.	Use
	       configure(ADM) to raise the number of inodes.
	       Abnormal.

	  kernel:WARNING:interrupt from unknown device, vec=num
	       The CPU received an interrupt via a supposedly unused
	       vector.	This message is followed by ``panic:unknown
	       interrupt.''  Typically, this event comes about when a
	       hardware failure miscomputes the vector of a valid
	       interrupt.  Hardware.

	  kernel:WARNING:stray interrupt on vector num
	       The CPU received an interrupt via a supposedly unused
	       vector.	Hardware.

     Page 3					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  kernel:WARNING:no file
	       There are too many open files. The system has run out
	       of entries in its ``open file'' table.  The warnings
	       given for the message ``inode table overflow'' apply
	       here.  Use configure(ADM) to raise the total number of
	       available files or the number of files available per
	       process.	 Abnormal.

	  kernel:WARNING:no space on dev nn/mm
	       This message means that the specified file system has
	       run out of free blocks.	Although not normally as
	       serious, the warnings discussed for ``inode table
	       overflow'' apply:often user programs are written
	       casually and ignore the error code returned when they
	       tried to write to the disk; this results in missing
	       data and ``holes'' in data files. The system
	       administrator should keep close watch on the amount of
	       free disk space and take steps to avoid this situation.
	       Abnormal.

	  kernel:WARNING:Out of inodes on dev nn/mm
	       The indicated file system has run out of free inodes.
	       The number of inodes available on a file system is
	       determined when the file system is created (using
	       mkfs(ADM)).  The default number is quite generous; this
	       message should be very rare.  The only recourse is to
	       remove some worthless files from that file system, or
	       dump the entire system to a backup device, run
	       mkfs(ADM) with more inodes specified, and restore the
	       files from backup.  Abnormal.

	  kernel:PANIC:blkdev
	       An internal disk I/O request, already verified as
	       valid, is discovered to be referring to a nonexistent
	       disk.  System inconsistency, fatal.

	  kernel:PANIC:devtab
	       An internal disk I/O request, already verified as
	       valid, is discovered to be refering to a nonexistent
	       disk.  System inconsistency, fatal.

	  kernel:PANIC:iinit
	       The super-block of the root file system could not be
	       read.  This message occurs only at boot time.
	       Hardware, fatal.

	  kernel:PANIC:swap IO error
	       A fatal I/O error occurred while reading or writing the
	       swap area.  System inconsistency, fatal.

	  kernel:PANIC:memory failure - parity error
	       A hardware memory failure trap has been taken.  System

     Page 4					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	       inconsistency, fatal.

	  kernel:PANIC:no fs
	       A mounted file system's entry has disappeared from the
	       system mount table.  System inconsistency, fatal.

	  kernel:PANIC:no imt
	       A mounted file system has disappeared from the mount
	       table.  System inconsistency, fatal.

	  kernel:PANIC:no procs
	       Each user is limited in the amount of simultaneous
	       processes he can have; an attempt to create a new
	       process when none is available or when the user's limit
	       is exceeded and refused. That is an occasional event
	       and produces no console messages; this panic occurs
	       when the kernel has certified that a free process table
	       entry is available and can't find one when it goes to
	       get it.	System inconsistency, fatal.

	  kernel:WARNING:Out of swap
	       There is insufficient space on the swap disk to hold a
	       task.  The system refuses to create tasks when it feels
	       there is insufficient disk space, but it is possible to
	       create situations to circumvent this mechanism.
	       Abnormal.

	  kernel:PANIC:general protection trap
	       General protection trap taken in kernel.	 System
	       inconsistency, fatal.

	  kernel:PANIC:segment not present
	       An attempt has been made to access an invalid segment.
	       It may also indicate the segment-not-present trap has
	       been taken in the kernel.  System inconsistency, fatal.

	  kernel:PANIC:Timeout table overflow
	       The timeout table is full.  Timeout requests are
	       generated by device drivers, there should usually be
	       room for one entry per system serial line plus ten more
	       for other usages.  Use configure(ADM) to raise the
	       number of timeout table entries.

	  kernel:PANIC:Trap in system
	       The CPU has generated an illegal instruction trap while
	       executing kernel or device driver code.	This message
	       is preceded with an information dump describing the
	       trap.  System inconsistency, fatal.

	  kernel:PANIC:Invalid TSS
	       Internal tables have become corrupted.  System
	       inconsistency, fatal.

     Page 5					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  kernel:WARNING:bootstring invalid, ignored
	       A bad bootstring was entered at the Boot prompt.

	  kernel:ERROR:bad syntax - string
	       A bad bootstring was entered at the Boot prompt.

	  kernel:PANIC:bad mapping in copyio
	       Copyio was called with a strange request. Usually a bad
	       driver.

	  kernel:WARNING:HARDWARE FAILURE:386 incorrectly multiplies
	       32-bit numbers
	       The cpu is displaying the 32-bit multiply bug.

	  kernel:PANIC:*** POWER CYCLE TO REBOOT ***
	       This message follows the above HARDWARE FAILURE 32 bit
	       error message.

	  kernel:INFO:10 bits of I/O address decoding
	       The hardware is only decoding 10 bits of i/o addresses.
	       This amount is sufficient in most cases. This condition
	       is only an issue if you are strapping i/o devices with
	       a base address above 400 (hex).

	  kernel:WARNING:A31 CPU bug workaround not possible for this
	       machine
	       A31 was specified on the boot line, but cannot be
	       applied to the current system.

	  kernel:INFO:A31 CPU bug workaround in effect
	       A31 was specified on the boot line and the software
	       workaround is currently in effect.

	  kernel:PANIC:bad boot string An invalid boot string was
	       entered at the Boot prompt.

	  kernel:PANIC:** WYSE/SCO UNIX only operates on WYSE PC
	       systems **
	       A kernel was serialized for WYSE hardware only and is
	       being booted on a non-WYSE machine.

	  kernel:PANIC:out of both memory & swap
	       No more memory pages or swap pages are free.

	  kernel:PANIC:not enough contiguous memory
	       The kernel memory allocation routines require more
	       physically contiguous memory.  Either decrease the size
	       of some kernel parameters (like disk buffers) or add
	       more physical memory.

	  kernel:WARNING:filesystem page read failed
	       An error occurred trying to read a page from the disk.

     Page 6					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	       This is not fatal, but usually indicates hardware
	       problems.

	  kernel:PANIC:free inode isn't
	       There is internal inode table corruption within the
	       kernel.

	  kernel:ERROR:Map overflow (num), shutdown and reboot, mp-
	       >mpent
	       There are internal kernel map inconsistencies. Reboot
	       your system.

	  kernel:PANIC:write_sb():cannot cvts3superb() yet
	       This message is found in the 386 kernel only. A write
	       of a non SYS III or SYS V filesystem superblock is
	       being attempted.	 This action should be impossible due
	       to earlier checks.

	  kernel:WARNING:Can't allocate message buffer
	       This message indicates a lack of memory.	 Processes
	       should be killed to make more room.  Another option is
	       to add more physical memory.

	  kernel:PANIC:Large model 386 ssig
	       Internal kernel error in processing large model 386
	       signals.

	  Trap type
	       This message precedes a ``kernel:PANIC:'' message.  The
	       type is the trap number given by the processor. The
	       message is followed by a dump of registers.  System
	       inconsistency, fatal.

	  fpsave:PANIC:no fp_task
	       No floating point context to save, internal kernel
	       error.

	  mdep.386/fp.c:WARNING:No floating point emulator found in
	       string,
	       No /etc/emulator was present in the root filesystem.
	       The System Administrator should install one and reboot.

	  fp_OVERRUN:PANIC:coprocessor overrun - with no 287/387
	       Internal coprocessor error.  fatal.

	  fp_COPROC:PANIC:, coprocessor error - with no 287/387
	       Inconsistent kernel internal state.

	  fp_COPROC:PANIC:coprocessor error - switched away from
	       fp_task
	       Internal kernel mismanagement of floating point
	       processes.

     Page 7					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  fp_DNA:PANIC:
	       A device trap happened while emulating floating point
	       instructions.

	  iinit:PANIC:cannot copy in superblock
	       An error happened during the root filesystem superblock
	       loading.

	  srmount:PANIC:cannot cvtv7superb() yet
	       A root filesystem superblock was not recognized as a
	       SYS III or SYS V superblock.  V7 superblocks cannot
	       currently be converted on the 386 kernel.

	  mapphys:PANIC:sptmap overflow
	       No system page table pages are available. This is an
	       internal error in the kernel, usually caused by a
	       faulty device driver.

	  physio:PANIC:bad state
	       A device driver made an invalid request to physio.

	  badint:PANIC:bad interrupt handler
	       Invalid interrupt request, usually fault hardware.

	  setup:PANIC:sptmap overflow
	       This message indicates possible kernel image corruption
	       or lack of physical memory.

	  setup:PANIC:u-area not page aligned
	       This indicates possible kernel image corruption.

	  setup:PANIC:u-area address does not match SPTADDR
	       Indicates possible kernel image corruption.

	  cmn_err:PANIC:DOUBLE PANIC The kernel panicked while trying
	       to panic.  You must power cycle at this point to reboot
	       the machine.

	  cmn_err:PANIC:unknown level in cmn_err (level=num,
	       msg=string),
	       The kernel's cmn_err() routine was called with an
	       invalid argument.

	Kernel Paging Messages
	  The following messages indicate system inconsistencies in
	  the kernel paging code. These inconsistencies can be caused
	  by hardware or software problems. Reboot your system and
	  note the circumstances if you see one of these messages:

	  mfalloc:PANIC:page not free

	  mfalloc:PANIC:page not free at exit

     Page 8					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  mffree:PANIC:page already free

	  mffree:PANIC:page is locked

	  dfalloc:PANIC:frame not free at exit

	  xlcheck:PANIC:xlink serial mismatch

	  impcode:PANIC:called to load impure 386

	  impcode:PANIC:more than 1 data segment?

	  preload:PANIC:, invalid page (num, num)

	  kernel:PANIC:bad page type for protection fault

	  kernel:PANIC:protection fault on read access

	  kernel:PANIC:not present fault on shared data

	  kernel:PANIC:added strange page table - num, index

	  pgfind:PANIC:not in cache

	  pghash:PANIC:not in cache

	  pginval:PANIC:list broken

	  pginval:PANIC:not in cache

	  mftomp:PANIC:bad frameno num

	  mptomf:PANIC:bad mp num

	  swapadd:PANIC:no space for dpfi

	  dftodp:PANIC:bad frameno num

	  dptodf:PANIC:bad dp num

	  dptodf:PANIC:bad dp num

	  pgread:PANIC:no xlink

	  pgfree:PANIC:invalid page marked present

	  pgfree:PANIC:freeing intransit page

	  pgpid:WARNING:setting disk pid

	  kernel:PANIC:page table under page table?

     Page 9					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  kernel:PANIC:swapping intransit page

	  dftomf:PANIC:non-swap page table entry changed

	  dftomf:PANIC:swap disk frame rcnt(num) != 1, dp=num, dp-
	       >dp_rcnt,dp

	  dftomf:PANIC:page type mismatch - mptype num dptype num mp
	       num dp num, mp->mp_type, dp->dp_type, mp, dp

	  dftomf2:PANIC:, swap memory frame rcnt(num) != 1, mp=num,

	  dftomf3:PANIC:swap mem frame rcnt(num) != 1, mp=num, mp-
	       >mp_rcnt, mp

	  mftodf1:PANIC:swap mem frame rcnt(num) != 1, mp=num, mp-
	       >mp_rcnt, mp

	  mftodf:PANIC:memory frame marked in transit

	  mftodf:PANIC:page type mismatch - dptype num mptype num dp
	       num mp num

	  mftodf2:PANIC:swap disk frame rcnt(num) != 1, dp=num

	  mftodf3:PANIC:swap disk frame rcnt(num) != 1, dp=num, dp-
	       >dp_rcnt, dp

	  fftomf:PANIC:page type(num) not TE_FILSYS, mp = num,mp-
	       >mp_type, mp

	  mfcvt:PANIC:zero ref count

	  ptdup:PANIC:TE_SWAP page rcnt(num) > 1,

	  ptdup:PANIC:xlinked page has reference

	  ptdup2:PANIC:TE_SWAP page rcnt > 1

	  ptdup:PANIC:xlinked page has reference

	  ptdup:PANIC:locked page not present

	  ptdup:PANIC:intransit page

	  pgcheck:PANIC:page type mismatch:ptp num type num xtype
	       num,ptp,type,xtype

	  The above listed messages indicate system inconsistencies in
	  the kernel paging code. These inconsistencies can be caused
	  both by hardware or software problems. Reboot your system.

     Page 10					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  cputok:PANIC:

	  cpktou:PANIC:

	  sdfrcm:PANIC:sdp->sd_inode not found

	  The above 3 errors indicate internal shared data errors
	  within the kernel.

	  v86sighdlint:WARNING:lost signal

	  v86setint:PANIC:xtss pte not present

	  The above 2 errors indicate internal VPIX processing errors
	  within the kernel.

	  namei:PANIC:null cache ino

	  namei:PANIC:duplicating cache

	  The above 2 messages indicate internal file management
	  errors in the kernel.

     System Services Messages
	  The following messages are displayed by the shell when a
	  system call fails.

	  Not owner:
	       Typically, this error indicates an attempt to modify a
	       file in some way forbidden except to its owner or
	       super-user.  It is also returned for attempts by
	       ordinary users to do things allowed only to the super-
	       user.

	  No such file or directory:
	       This error occurs when a filename is specified and the
	       file should exist but doesn't, or when one of the
	       directories in a pathname does not exist.

	  No such process:
	       No process can be found corresponding to that specified
	       by pid in kill or ptrace.

	  Interrupted system call:
	       An asynchronous signal (such as interrupt or quit),
	       which the user has elected to catch, occurred during a
	       system call.  If execution is resumed after processing
	       the signal, it will appear as if the interrupted system
	       call returned this error condition.

	  I/O error:
	       Some physical I/O error.	 This error may in some cases

     Page 11					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	       occur on a call following the one to which it actually
	       applies.

	  No such device or address:
	       I/O on a special file refers to a subdevice which does
	       not exist, or beyond the limits of the device.  It may
	       also occur when, for example, a tape drive is not on-
	       line or no disk pack is loaded on a drive.

	  Arg list too long:
	       An argument list longer than 5,120 bytes is presented
	       to a member of the exec family.

	  Exec format error:
	       A request is made to execute a file which, although it
	       has the appropriate permissions, does not start with a
	       valid magic number (see a.out(F)).

	  Bad file number:
	       Either a file descriptor refers to no open file, or a
	       read (respectively write) request is made to a file
	       which is open only for writing (respectively reading).

	  No child processes:
	       A wait was executed by a process that had no existing
	       or unwaited-for child processes.

	  No more processes:
	       A fork failed because the system's process table is
	       full or the user is not allowed to create any more
	       processes.

	  Not enough space:
	       During an exec, or sbrk, a program asks for more space
	       than the system is able to supply.  This is not a
	       temporary condition; the maximum space size is a system
	       parameter.  The error may also occur if the arrangement
	       of text, data, and stack segments requires too many
	       segmentation registers, or if there is not enough swap
	       space during a fork.

	  Permission denied:
	       An attempt was made to access a file in a way forbidden
	       by the protection system.

	  Bad address:
	       The system encountered a hardware fault in attempting
	       to use an argument of a system call.

	  Block device required:
	       A nonblock file was mentioned where a block device was
	       required, e.g., in mount.

     Page 12					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  Device busy:
	       An attempt to mount a device that was already mounted
	       or an attempt was made to dismount a device on which
	       there is an active file (open file, current directory,
	       mounted-on file, active text segment).  It will also
	       occur if an attempt is made to enable accounting when
	       it is already enabled.

	  File exists:
	       An existing file was mentioned in an inappropriate
	       context, e.g., link.

	  Cross-device link:
	       A link to a file on another device was attempted.

	  No such device:
	       An attempt was made to apply an inappropriate system
	       call to a device; e.g., read a write-only device.

	  Not a directory:
	       A nondirectory was specified where a directory is
	       required, for example, in a path prefix or as an
	       argument to chdir(S).

	  Is a directory:
	       An attempt to write on a directory.

	  Invalid argument:
	       An invalid argument (e.g., dismounting a nonmounted
	       device; mentioning an undefined signal in signal or
	       kill; reading or writing a file for which lseek has
	       generated a negative pointer).  Also set by the math
	       functions described in the (S) entries of this manual.

	  File table overflow:
	       The system's table of open files is full and
	       temporarily no more opens can be accepted.

	  Too many open files:
	       No process may have more than 60 file descriptors open
	       at a time.

	  Not a character device

	  Text file busy:
	       An attempt to execute a pure-procedure program which is
	       currently open for writing (or reading).	 Also an
	       attempt to open for writing a pure-procedure program
	       that is being executed.

	  File too large:
	       The size of a file exceeded the maximum file size

     Page 13					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	       (1,082,201,088 bytes) or ULIMIT; see ulimit(S).

	  No space left on device:
	       During a write to an ordinary file, there is no free
	       space left on the device.

	  Illegal seek:
	       An lseek was issued to a pipe.

	  Read-only file system:
	       An attempt to modify a file or directory was made on a
	       device mounted read-only.

	  Too many links:
	       An attempt to make more than the maximum number of
	       links (1000) to a file.

	  Broken pipe:
	       A write on a pipe for which there is no process to read
	       the data.  This condition normally generates a signal;
	       the error is returned if the signal is ignored.

	  Arg out of domain of func:
	       The argument of a function in the math package is out
	       of the domain of the function.

	  Result too large:
	       The value of a function in the math package is not
	       representable within machine precision.

	  File system needs cleaning:
	       An attempt was made to mount(S) a file system whose
	       super-block is not flagged clean.

	  Would deadlock:
	       A process' attempt to lock a file region would cause a
	       deadlock between processes vying for control of that
	       region.

	  Not a name file:
	       A creatsem(S), opensem(S), waitsem(S), or sigsem(S) was
	       issued using an invalid semaphore identifier.

	  Not available:
	       An opensem(S), waitsem(S) or sigsem(S) was issued to a
	       semaphore that has not been initialized by a call to
	       creatsem(S).  A sigsem was issued to a semaphore out of
	       sequence; i.e., before the process has issued the
	       corresponding waitsem to the semaphore.	An nbwaitsem
	       was issued to a semaphore guarding a resource that is
	       currently in use by another process.  The semaphore on
	       which a process was waiting has been left in an

     Page 14					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	       inconsistent state when the process controlling the
	       semaphore exits without relinquishing control properly;
	       i.e., without issuing a waitsem on the semaphore.

	  A name file:
	       A name file (semaphore, shared data, etc.) was
	       specified when not expected.

	  No message of desired type:  An attempt was made to receive
	       a message of a type that does not exist on the
	       specified message queue [see msgop(S)].
	       An attempt was made to receive a message of a type that
	       does not exist on the specified message queue;  see
	       msgop(S).

	  Identifier removed:
	       This error is returned to a process that resumes
	       execution due to the removal of an identifier from the
	       file system's
	       name space; see msgctl(S), semctl(S), and shmctl(S).

	  No record locks available:
	       In fcntl(S) the setting or removing of record locks on
	       a file cannot be accomplished because there are no more
	       record entries left on the system.

	  Channel number out of range

	  Level 2 not synchronized

	  Level 3 halted

	  Level 3 reset

	  Link number out of range

	  Protocol driver not attached

	  No CSI structure available

	  Level 2 halted

	  Deadlock situation detected/avoided
	       A deadlock situation was detected and avoided.  This
	       error pertains to file and record locking.

	  No record locks available

	  Bad exchange descriptor

	  Bad request descriptor

     Page 15					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  Message tables full

	  Inode table overflow

	  Bad request code

	  Invalid slot

	  File locking deadlock

	  Bad font file format

	  Not a stream device
	       A putmsg(S) or getmsg(S) system call was attempted on a
	       file descriptor that is not a STREAMS device.

	  No data available

	  Timer expired
	       The timer set for a STREAMS ioctl(S) call has expired.
	       The cause of this error is device specific and could
	       indicate either a hardware or software failure, or
	       perhaps a timeout value that is too short for the
	       specific operation.  The status of the ioctl(S)
	       operation is indeterminate.

	  Out of stream resources
	       During a STREAMS open(S), either no STREAMS queues or
	       no STREAMS head data structures were available.

	  Machine is not on the network
	       This error is Remote File Sharing (RFS) specific.  It
	       occurs when users try to advertise, unadvertise, mount,
	       or unmount remote resources while the machine has not
	       done the proper startup to connect to the network.

	  Package not installed
	       This error occurs when users attempt to use a system
	       call from a package which has not been installed.

	  Object is remote
	       This error is RFS specific. It occurs when users try to
	       advertise a resource which is not on the local machine,
	       or try to mount/unmount a device (or pathname) that is
	       on a remote machine.

	  Link has been severed
	       This error is RFS specific.  It occurs when the link
	       (virtual circuit) connecting to a remote machine is
	       gone.

	  Advertise error

     Page 16					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	       This error is RFS specific. It occurs when users try to
	       advertise a resource which has been advertised already,
	       or try to stop the RFS while there are resources still
	       advertised, or try to force unmount a resource when it
	       is still advertised.

	  Srmount error
	       This error is RFS specific. It occurs when users try to
	       stop RFS while there are resources still mounted by
	       remote machines.

	  Communication error on send
	       This error is RFS specific. It occurs when trying to
	       send messages to remote machines but no virtual circuit
	       can be found.

	  Protocol error
	       Some protocol error occurred.  This error is device
	       specific, but is generally not related to a hardware
	       failure.

	  Multihop attempted
	       This error is RFS specific. It occurs when users try to
	       access remote resources which are not directly
	       accessible.

	  Not a data message
	       During a read(S), getmsg(S), or ioctl(S) I_RECVFD
	       system call to a STREAMS device, something has come to
	       the head of the queue that can't be processed.  That
	       something depends on the system call:
		 read(S) - control information or a passed file
	       descriptor.
		 getmsg(S) - passed file descriptor.
		 ioctl(S) - control or data information.

	  Name not unique on network

	  File descriptor in bad state

	  Remote address changed

	  Cannot access a needed shared library
	       Trying to exec(S) an a.out that requires a shared
	       library (to be linked in) and the shared library
	       doesn't exist or the user doesn't have permission to
	       use it.

	  Accessing a corrupted shared library
	       Trying to exec(S) an a.out that requires a shared
	       library (to be linked in) and exec(S) could not load
	       the shared library. The shared library is probably

     Page 17					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	       corrupted.

	  Trying to exec(S) an a.out that requires a shared library
	       (to be linked in) and there was erroneous data in the
	       .lib section of the a.out. The .lib section tells
	       exec(S) what shared libraries are needed. The a.out is
	       probably corrupted.

	  Attempting to link in more shared libraries than system
	       limit
	       Trying to exec(S) an a.out that requires more shared
	       libraries (to be linked in) than is allowed on the
	       current configuration of the system. See the System
	       Administrator's Guide.

	  Cannot exec a shared library directly
	       Trying to exec(S) a shared library directly. This is
	       not allowed.

     Driver Messages
	  The following messages are different from kernel messages in
	  that they are generated by the device drivers for the
	  various hardware supported under . The source of the message
	  can be determined by checking the label field of the
	  message.

	Console Driver Messages
	  console:WARNING:Kernel messages lost on non-text screen
		       (also check /usr/adm/messages)
	       Kernel messages were lost while the console was in
	       graphics mode and did not appear. Check the last lines
	       of /usr/adm/messages to find the messages.

	  console:WARNING:Too many keyboard groups
	       There are more video devices attached to your system
	       than your kernel is designed to support.

	Irwin Driver Messages
	  mc:ERROR:Block not found
	       A block not found error occurs when the driver cannot
	       locate a physical tape block during a read or write
	       operation. Ensure the tape head is clean (see the tape
	       drive hardware manual for cleaning instructions).  When
	       this message is displayed during a data restore
	       operation, try retensioning the tape, then repeat the
	       restore operation.  If this fails, try restoring the
	       data using a different tape drive.  When this message
	       is displayed during data backup operation, try another
	       tape.  If your backup is successful on another tape,
	       discard or bulk erase and reformat the original tape.

	  mc:ERROR:Data CRC error

     Page 18					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  mc:ERROR:ID CRC error
	       These messages are displayed during a tape read
	       operation when a tape block cannot be recovered by ECC.
	       If this message appears, retension the tape and try
	       again. If this fails, the data might be recovered by
	       using a different tape drive. Causes of persistent CRC
	       errors are: poor quality tapes, worn tape head, a
	       defect in the drive's record circuitry, or an
	       incompatible or otherwise defective data separator
	       circuit on the controller. CRC errors might be stopped
	       by using new tapes, or installing a data compensator
	       circuit on the drive.

	  mc:ERROR:Record not found
	       This error occurs when some sector within a tape block
	       cannot be located.  This error typically occurs on or
	       during a tape read operation when there are too many
	       erroneous sectors to recover data using ECC.  (See Data
	       CRC error.)

	  mc:ERROR:Drive not found
	       When /etc/mcdaemon is run for the first time after
	       system boot, a drive searching algorithm is executed by
	       the driver.  If this algorithm fails to detect the
	       presence of a tape drive, the message ``mc:ERROR:Drive
	       not found'' is displayed. Subsequently, the same
	       message is displayed on any read or write access to an
	       opened mc device file for which no drive is present.
	       When this message appears, hardware should be checked.

	  Shut down the system and then cycle the power switch.	 With
	  no cartridge present, the tape drive should flash its LED on
	  power up. If it doesn't, power down and check (when
	  applicable) for a disconnected or defective tape drive power
	  cable.  On PC/AT class machines (and some Micro Channel
	  compatibles) the power cable resembles the four wire cable
	  which powers the floppy diskette drive.  For internally
	  mounted drives, the power cable is connected directly to the
	  drive (whether the drive connected to the system floppy
	  controller, a 4251 extender, or a 4100 PC bus controller).
	  For external drives, make sure the four wire cable is
	  connected to the 4251 floppy extender or 4100 PC bus
	  controller adapters.	Also check that the 35-pin connector
	  at the end of the tape drive's cable is correctly seated in
	  the adapter socket on the back of the computer.  If a 4251
	  board is present, check the tubular glass fuses.  When
	  cables and fuses appear to be in order and the LED still
	  doesn't flash, either the cables, 4251 or 4100 (when
	  applicable), or drive may be defective.

	  The drive select jumper (on the tape drive) should also be
	  checked. In most installations, the jumper should connect

     Page 19					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  the DRIVE SELECT 2 pin pair.	For 5-1/4 form factor drives,
	  DRIVE SELECT 2 is labeled with a "[2]" on the drive's
	  circuit board.  For 3-1/2 inch form factor drives with
	  connector adapter which have jumpers mounted on the adapter,
	  consult the hardware installation instructions.  For other
	  3-1/2 inch form factor drives, the DRIVE SELECT 2 is the
	  forth pin pair from the corner of the drive's circuit board:

	       ----------------------
	       |	   o o o o o
	       |	   o o o o o
	       |	     4 3 2 1

	  If the drive is connected to an Irwin 4251 floppy extender
	  which is, in turn, cabled to an Adaptec suffix 'B' (e.g.,
	  ACB-2xxxB, or 1542B scsi) controller and the "Drive not
	  found" message is seen, check the 4251 jumpers.  In the "as
	  shipped from the factory" state, the A0, A2, and A3 pin
	  pairs are jumpered, and the A7 pin pair has a spare jumper
	  (stored on one pin of the pair).  If the jumpers are in this
	  "as shipped" state, reinstall the A7 jumper to connect the
	  pin pair.  Typically this change will allow the drive to be
	  found.

	  mc:ERROR:Servo failure
	       This is a tape formatting error message.	 The servo
	       writing function is a part of the tape drive's
	       firmware.  The driver issues a command to the drive to
	       servo write and awaits tape drive completion status.
	       Usually the drive's LED will be flashing on servo
	       writing failure.	 Try bulk erasing the cartridge and
	       restarting the format.  If this fails, try another
	       cartridge.

	  mc:ERROR:Insufficient memory
	       This message is displayed when the driver fails to
	       allocate at least three tape block buffers.  Sufficient
	       memory may be available when single user mode is
	       entered immediately after system boot.  Usually adding
	       memory to the system will stop this message.

	  mc:ERROR:Block 0 missing servo header

	  mc:ERROR:Too many sequential missing servo headers

	  mc:ERROR:Too many missing servo headers on track

	  mc:ERROR:Too many missing servo headers

	  mc:ERROR:Too many sequential bad blocks

	  mc:ERROR:Too many bad blocks on a track

     Page 20					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  mc:ERROR:Too many bad blocks
	       These messages occur during formatting.	When
	       formatting fails for one of these reasons, try bulk
	       erasing the cartridge and reformatting.	If this fails,
	       try another cartridge.

	  mc:ERROR:Block 0 medium error
	       This error results when, during tape state
	       determination, the first tape block has a medium error
	       which is not recoverable by either redundant correction
	       or ECC.	Normally the cartridge should be reformatted
	       or discarded.  If the cartridge has a backup on it, try
	       using a different drive to read the tape.

	  If this message persists for multiple cartridges, the tape
	  drive's read circuitry may be out of adjustment, or there
	  may be an incompatibility between the floppy controller's
	  data separator circuit and the tape drive.  When running on
	  a Micro Channel machine, the problem can be overcome by
	  adding the following line to the /etc/default/mcconfig file:

	       iropt=I

	  This enables an algorithm known as "wait-for-index."

	  mc:ERROR:Defect list has unrecoverable error
	       This message is displayed when both copies of the
	       relocation table (kept in the second and third good
	       tape blocks) have unrecoverable medium errors or are
	       otherwise corrupt.

	  mc:ERROR:Defect list corrupt
	       This message is displayed if an error is found in the
	       primary defect list kept in block 0. Reformat the tape.

	  mc:ERROR:Daemon not started
	       The tape driver uses a single daemon process to encode
	       ECC during tape write operations and recover data with
	       ECC during tape reads. When this message occurs,
	       execute /etc/mcdaemon and retry the tape operation.

	  mc:ERROR:Timeout reading controller result
	       mc:ERROR:Timeout writing controller command
	       The driver accesses the tape drive by sending commands
	       to and reading results from a floppy controller chip.
	       These messages are displayed when the controller will
	       not accept a command or return results in the manner
	       expected by the driver.	Floppy controller access
	       timeouts may indicate a driver conflict.	 For instance,
	       a diskette driver may be accessing the floppy
	       controller chip at the same time as the tape driver.

     Page 21					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  mc:ERROR:Unrecognized controller error
	       This message indicates the floppy controller has
	       returned an error code which is not in a list kept by
	       the tape driver.	 Causes might be defective hardware,
	       or a new floppy controller chip.	 This error message
	       has yet to be seen.

	  mc:ERROR:State machine hung
	       The driver will enter the hung state when an unexpected
	       event occurs.  The hung state is cleared when the
	       device file is first closed, then reopened.  Causes for
	       this condition are:

		o   A hardware defect, or

		o   another device driver is accessing the floppy
		    controller, or

		o   some system function or driver has kept interrupts
		    disabled for an excessive period of time.

	  mc:ERROR:DMA attempt past end of cylinder
	       This error occurs the floppy controller receives a DMA
	       data transfer request after data for a given tape block
	       has been transferred.

	  The message may indicate a hardware problem or an error in
	  driver programming.  The message can appear when another
	  device driver attempts use the tape drive's DMA channel
	  while in use by the tape driver.  This message has been seen
	  on XT class machines which are fitted with certain early
	  Advanced Micro Devices (AMD) DMA controllers.	 These
	  controllers have a defect which doesn't allow concurrent DMA
	  accesses (on different channels) by the tape and hard disk.

	  mc:ERROR:Write protected
	       The "Write protected" message appears when an attempt
	       is made to write a write protected cartridge.  Writing
	       includes both formatting and back-up operations.	 Check
	       the cartridge write protect silder.  It must be in the
	       RECORD position before the tape can be written.	When a
	       cartridge is inserted with the slider in the RECORD
	       position, the slider presses against the lever of a
	       microswitch.  The switch is one of two visible in the
	       mouth of the drive and is the closest to the circuit
	       board.  The slider's pressure closes the (normally
	       open) micro switch which, in turn, enables write
	       circuitry in the drive.	If the "Write protected"
	       message persists, the switch lever may be bent, the
	       switch may be electrically noisy, or the switch or
	       associated write circuitry may be defective.

     Page 22					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  mc:ERROR:No ID address mark
	       A "No ID address mark" is used internally by the driver
	       and does not normally appear.  "IDMARK" may be seen
	       when debugging of data transfers is enabled.  The error
	       normally appears when tape block's servo header is weak
	       or missing.  This error will also occur when the "read
	       data" signal path is broken or defective.  When
	       applicable, check the cable which connects the tape
	       drive to the floppy controller (try a substitute).

	  mc:ERROR:Request timed out
	       This message occurs when the drive's BUSY (i.e., TRACK
	       0) line remains active for more than a certain period.
	       Typically two minutes for data transfers.  (Yet to be
	       implemented.)

	  mc:ERROR:DMA boundary error
	       A "DMA boundary error" messages indicate an an attempt
	       to program the DMA controller to transfer data which
	       crosses a 64K physical memory boundary in an AT class
	       machine.	 This may be due to an error in programming.

	  mc:ERROR:Cylinder not found
	       This code is returned by the floppy controller chip and
	       used internally by the driver.  It is not returned to a
	       program by the driver interface.

	  mc:ERROR:No data address mark
	       Each sector is comprised of an ID field and a data
	       field.  The data address mark is used by the controller
	       to identify the start of a data field.  The "No data
	       address mark" message is displayed as the result of a
	       read error.  However, the cause of the error is related
	       to writing the tape.  When this message persists for
	       different tapes after writing then reading, there may
	       be defect somewhere in the write circuitry.  The write
	       circuitry includes the floppy controller, the WRITE
	       DATA signal line at the floppy controller/tape drive
	       interface and the write circuitry internal to the tape
	       drive.  If data needs to be recovered from a tape, try
	       a different drive.

	  mc:ERROR:DMA overrun
	       Tape data transfers between the floppy controller and
	       memory are accomplished using the services of a special
	       chip called the Direct Memory Access (DMA) controller.
	       When the floppy controller needs to transfer a data
	       byte to or from its register, it activates a hardware
	       signal called the DMA Request line (DRQ).  This tells
	       the DMA that its time to move a data byte.  When the
	       memory bus is available the DMA controller responds by
	       activating the appropriate bus signals to transfer the

     Page 23					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	       data byte.  Upon completion of the transfer, the DMA
	       controller activates a DMA Acknowledge (DACK) line to
	       inform the floppy controller.

	  DMA Overrun errors result when the DMA controller is too
	  slow in responding to a floppy controller data transfer
	  request.

	  Most floppy controllers are sensitive to slow DMA response.
	  At a 500 KHz data transfer rate (i.e., the transfer rate
	  used by 125, 145, 165, 285 drives) the DMA controller must
	  respond with in 13 microseconds.

	  In some cases DMA Overruns can be cured by not printing to
	  the screen during tape operations.  Try "silent" modes.

	  In most cases DMA Overruns are stopped by attaching the tape
	  drive to a floppy adapter which has a first-in-first-out
	  (FIFO) buffer. The FIFO is part of the floppy controller
	  chip.	 Intel 82072 and 82077 controller chips have FIFOs.
	  Certain Adaptec AT class controllers have the 82072 (those
	  with a 'B' suffix).  Both the Irwin 4100 (for AT class
	  machines) and 4100MC (Micro Channel) tape adapters employ
	  the 82077.

	  mc:ERROR:Memory address conversion error
	       The "Memory address conversion error" message occurs,
	       when the driver encounters an error converting a
	       logical (or virtual) memory address to a physical
	       memory address.	In 80286 systems this message might
	       mean the system is out of selectors.

	  mc:ERROR:Controller not found
	       When the driver's tape drive search debug option is
	       enabled, the "Controller not found" message is given
	       for each controller which has been tested for presence
	       but not found.

	  mc:ERROR:Equipment fault
	       An "Equipment fault" error is generated when a selected
	       drive sets the equipment fault signal line.  As this
	       line is wired to an inactive state at the floppy
	       controller chip, this error might indicate a controller
	       hardware error.	This error has not yet been seen.

	  mc:ERROR:Drive not ready

	  mc:ERROR:Medium changed
	       The driver polls the tape drive for cartridge presence
	       and change status.  The tape drive senses cartridge
	       presence and removal using a "cartridge present"
	       microswitch.  The switch is one of two visible in the

     Page 24					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	       mouth of the drive and is the furthest from the circuit
	       board.  When a cartridge is present, it presses the
	       micro switch lever causing the switch to close.	When a
	       new cartridge is inserted, the tape is brought to
	       load-point.  For some drives, the load-point operation
	       is automatically performed on cartridge insertion.  For
	       others, the driver issues the load-point command to the
	       drive.  When either the "Drive not ready" or "Medium
	       changed" messages is seen and the cartridge is known to
	       be present or not changed, there may be a defect in the
	       cartridge present microswitch.  The switch might have a
	       bent lever, or may be electrically disconnected or
	       noisy. to be found.

	  mc:ERROR:Erase failure
	       Some 145 Irwin tape drives support an erase feature.
	       It is recommended that this feature not be used.
	       Erasing is done by applying a DC bias to the tape head,
	       repeatedly spooling the tape from end-to-end and
	       stepping the head 1/4 of a track at the end of each
	       repetition.  The "Erase failure" message appears when
	       the drive does not support the erase feature.

	  mc:ERROR:Seek track error
	       This code is used internally by the driver.  If
	       displayed, there may be an error in programming.

	  mc:ERROR:Track following error
	       A track following error results when no index signals
	       are received from the controller.  The following are
	       possible causes:

		o   The cartridge is erased (no servo tracks and not
		    formatted).

		o   The cartridge was formatted on a higher density
		    tape drive and is not recognized in a lower
		    density drive.  For example an 80 MB cartridge
		    (formatted on a 285 drive) in early 145 drive.

		o   The tape is despooled (examine the cartridge)

		o   The INDEX signal line may be broken or the cable
		    which connects the tape drive to the controller.

		o   The main tape driving motor in the drive is not
		    spinning. Check that the tape driving capstan (the
		    rubber wheel visible in the mouth of the tape
		    drive) spins freely.  If the capstan cannot be
		    rotated with a finger, check for an obstruction in
		    the area of the main flywheel/rotor on the side of
		    the drive opposite to the printed circuit board.

     Page 25					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

		    If the motor spins freely, the motor fuse may be
		    blown.  The fuse is soldered in. Send the drive in
		    to Irwin for repair.

	  mc:ERROR:Too many outstanding interrupts
	       When the driver receives an interrupt, it enters a loop
	       in which the initial interrupt and additional hidden
	       interrupts are serviced.	 To prevent infinite looping
	       in the interrupt handler, four iterations are allowed.
	       On the fifth iteration, the driver stops processing and
	       enters a hung state.  If a request is in service, the
	       "Too many outstanding interrupts" message is displayed.
	       This condition has yet to be seen.

	  mc:ERROR:Error on sense interrupt status

	  mc:ERROR:Sense drive status failure
	       When the tape driver receives an interrupt, it
	       retrieves the content of both the floppy controller
	       interrupt status and the drive status registers.
	       Interrupt status is used to determine the interrupt
	       type.  Drive status tells the state of signal lines at
	       the floppy interface cable.  If retrieval of either of
	       these status registers fails, the appropriate message
	       is displayed if a tape transfer request is active.
	       These messages may caused by faulty floppy arbitration
	       programming.  That is, both the tape and diskette
	       drivers are communicating with the floppy controller
	       concurrently.

	  mc:ERROR:Floppy controller reset failure
	       When the tape driver gains owner ship of the floppy
	       controller, it starts a floppy controller reset
	       procedure.  When the procedure cannot be completed
	       successfully, this message will be displayed if a tape
	       data transfer request being processed.

	  mc:ERROR:Error sending command to drive
	       The driver uses two floppy controller signal lines to
	       both communicate with the tape drive and control tape
	       motion.	"Pulse" commands are sent by the driver to the
	       tape drive on the STEP signal line.  In turn, the tape
	       drive responds by either activating or deactivating the
	       TRACK 0 line.  When the "Error sending command to
	       drive" message appears, the controller did not accept
	       the command to send STEP pulses.	 Typically this
	       message is generated when two drivers are using the
	       floppy controller concurrently.	That is, there is a
	       failure in floppy ownership arbitration.

	  mc:ERROR:Error starting data transfer
	       "Error starting data transfer" is displayed when the

     Page 26					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	       driver fails to setup the floppy controller chip at the
	       start of a read/write/format operation.	This error may
	       indicate a tape driver/diskette driver conflict.	 That
	       is, both drivers may be using the floppy controller
	       concurrently.

	  mc:ERROR:Vector installation failure
	       This message indicates the driver could not install its
	       interrupt vector.  It may indicate an error in
	       programming.

	  mc:ERROR:Unexpected interrupt
	       An "Unexpected interrupt" occurs when the tape driver
	       is in a state in which it is not expecting an interrupt
	       from the floppy controller.  If this message is seen,
	       there may be a tape driver/diskette driver conflict or
	       a noisy interrupt line.

	  mc:ERROR:Internal error
	       "Internal error" may be an indication of an error in
	       driver programming.

	  mc:ERROR:Request aborted
	       "Request aborted" is a message used internally by the
	       driver.	When seen, there may be a an error in driver
	       programming.

	  mc:ERROR:Bad operation code

	  mc:ERROR:Bad device number

	  mc:ERROR:Bad block address

	  mc:ERROR:Bad count
	       These messages, in general, indicate an error in driver
	       programming.  When tape drive search debugging is
	       enabled (irdbg=s), it is normal for the "BADDEV"
	       message to be displayed for the alternate floppy
	       controller (ALTFDC).  By default, the BADDEV error code
	       is set in low level controller searching algorithms to
	       prevent testing for drive presence on this controller.
	       Testing for drives on an alternate controller (other
	       than a 4100) is explicitly enabled by user
	       configuration (altfdc=config).

	  mc:ERROR:No servo
	       The "No servo" message is synonymous with the message
	       "Track following error."

	  mc:ERROR:Servo but no sector format
	       Normally "Servo but no sector format" means that a
	       cartridge has servo written but no sector ID's have

     Page 27					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	       been written.  The message is displayed at the
	       completion of tape state determination.	Tape state
	       determination is the first operation performed for a
	       freshly inserted cartridge.  Tape state determination
	       includes up to 5 tries at reading block zero -- the
	       first block on the tape.	 When a cartridge is known to
	       have been correctly formatted, this message may
	       indicate a defect somewhere in the read data signal
	       path. Included in the read data signal path are the
	       tape drive's head and read circuitry, the cable which
	       connects the drive to the controller, and the floppy
	       controller's data receiving and separator circuit.

	  mc:ERROR:Block 0 corrupt
	       A "Block 0 corrupt" message is displayed when the
	       driver does not recognize the data in the first sector
	       on the tape (i.e., the physical tape header).  This may
	       be the result of incomplete formatting or a tape which
	       was written by another tape driver.

	  mc:ERROR:Defect list has unrecoverable error
	       This message is displayed when both copies of the
	       relocation table (kept in the second and third good
	       tape blocks) have unrecoverable medium errors or are
	       otherwise corrupt.

	  When this message is displayed on the first backup after
	  drive installation in a Micro Channel machine, the wait-
	  for-index algorithm may be need to be enabled.

	  mc:ERROR:Block merge failure
	       The tape driver writes only full tape blocks.  Since
	       system blocks are smaller (usually 512 through 10 KB)
	       are smaller than than tape blocks (8, 16, or 29 KB) a
	       block merging operation is occasionally performed.  A
	       merging operation typically takes place at the end of a
	       tar backup or the start of a tar append.	 This
	       operation involves reading the medium copy of the tape
	       block, partially overlaying the tape block data with
	       user data, appending ECC sectors and finally writing
	       the block back to tape.	A "Block merge failure"
	       message is displayed when some part of the operation
	       fails.

	  mc:ERROR:Block allocation failure
	       This message is displayed, when during a write
	       relocation operation, no spare block can be allocated.
	       The driver keeps a count of free spare blocks and will
	       not attempt block relocation when the count is zero.
	       Therefore, this message indicates the defect lists
	       associated with block relocation are most probably
	       corrupt.

     Page 28					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  mc:ERROR:Block relocation failure

	  mc:ERROR:Maximum block relocation tries reached
	       The "Maximum block relocation tries reached" message
	       may be displayed when three sequential attempts to
	       relocate a given tape block fail.  This message might
	       indicate a tape is of low quality. It may also be the
	       result of sector 1 errors in certain Micro Channel
	       machines.  If this is the case, enabling the wait-for-
	       index algorithm may alleviate this condition (see
	       "Block 0 medium error").

	  mc:ERROR:Incompatible cartridge
	       During reading, this message appears when the cartridge
	       was formatted by a higher density drive.	 Newer 145
	       drives recognize cartridges servo written by by 165 (64
	       MB), 285 and 287 (80/120 MB) drives.  Tapes are not
	       read as the tracks are too narrow.

	  During writing the "Incompatible cartridge" message appears
	  for cartridges which have formatted tracks which are other
	  than the width of the tape head.

	  During formatting, this message normally occurs, when a
	  cartridge already has servo tracks written by a drive of a
	  different type. The message also appears when formatting of
	  a blank DC-1000 (0.150 inch wide tape) cartridge is
	  attempted in 165, 285, or 287 drives. These drives will only
	  servo write quarter inch DC-2000 and DC-2120 cartridges.

	  The "Incompatible cartridge" message also occurs when the
	  tape drive's read circuitry is disturbed by magnetic fields
	  generated by CRT monitors.  Strong magnetic disturbance
	  prevents the drive from correctly reading the "servo-type-
	  finger-print" recorded at the beginning of tape, during the
	  load-point operation.	 Lower levels of disturbance prevent
	  tape data from being read.  It is important that external
	  drives be separated by a good distance from display
	  monitors.  Internal drives may also be affected when the
	  display monitor sits on the case.  If the computer has a
	  plastic enclosure, try moving the monitor off the case.
	  Otherwise, if the computer has a metal case, try sliding the
	  monitor toward the back of the computer (away from the bezel
	  of the tape drive).

	  mc:ERROR:Timer initialization failure
	       This message is displayed, when during initialization,
	       no timer interrupts were received from the system.

	  mc:ERROR:Operating system call failed
	       This message may indicate an error in driver
	       programming.

     Page 29					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  mc:ERROR:Invalid parameter
	       The "Invalid parameter" message is associated with
	       incorrect parameters passed by ioctl calls.  If this
	       message is seen, there is either an error in the
	       application making the call or the driver.

	  mc:ERROR:Device busy

	  mc:ERROR:Device busy formatting

	  mc:ERROR:Device performing diagnostic
	       If these messages appear the device is in use by
	       another task.  Try again later.

	  mc:ERROR:Read after write miscompare
	       At the end of the first backup, the driver will
	       checksum the last block written, read the block, re-
	       checksum the block and compare the checksums.   If the
	       checksums don't match, the "Read after write
	       miscompare" message is displayed.

	  When this message occurs the following should be checked:
	  If the tape drive is connected to an Irwin 4251 floppy
	  extender board which is, in turn, connected to a DTC (Data
	  Technology Corporation) hard disk/floppy disk controller,
	  check the jumper pins on the 4251 board.  In the "as shipped
	  from the factory" state, the A0, A2, and A3 pin pairs are
	  jumpered, and the A7 pin pair has a spare jumper (stored on
	  one pin of the pair).	 If the jumpers are in this "as
	  shipped" state, reinstall the A7 jumper to connect the pin
	  pair.	 Typically this change will allow tapes to be
	  correctly written.

	  The "Read after write miscompare" message will also be
	  displayed if either the "write data" or "write gate" signal
	  lines in the (when applicable) cable which connects the tape
	  drive to floppy controller are broken.  Check the cable
	  connection.

	Cartridge Driver Messages
	  ct:ERROR:Tape controller (type=name) not found
	       The controller specified in in the file
	       /usr/sys/io/ctconf.asm was not found.

	  ct:ERROR:Cartridge tape is write protected
	       You must remove the write protect tab from the
	       cartridge before use.

	  ct:ERROR:system too busy for efficient tape use
	       There is not enough user memory available to allow the
	       device to work.

     Page 30					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  ct:WARNING:attempted to free invalid buffer
	       The driver attempted free a buffer that was not active.
	       The buffer must be activated before use.

	SCSI Driver Messages
	  scsi:ERROR:No controller response :num
	       Requested controller is not present on SCSI bus num.
	       Check your system setup and connections.

	  scsi:ERROR:CTLR num LUN num not attached
	       Requested unit not present on controller. Check your
	       system setup.

	  scsi:ERROR:CTLR num LUN num:invalid type <num>,
	       Requested unit is not a disk or tape. Disk and tape and
	       printer are currently the only supported SCSI devices.

	  scsi:ERROR:CTLR num LUN num:device not ready, ctlr, x);
	       Requested device is busy.

	  scsi:ERROR:adstrategy:device/type error 0xtype/0xtype
	       Internal error - open device is not disk, tape or
	       printer.

	  scsi:ERROR:adioctl:ADMODESENSE rc num host num unit num
	       ioctl sense command did not complete as expected.

	  scsi:WARNING:adioctl:ADEXECUTE rc num host num unit num
	       ioctl execute command did not complete as expected.

	  scsi:INFO:adioctl:num reassigned
	       ioctl bad block mapping completed (done in pairs)

	  scsi:WARNING:adsetparam:ADMODESENSE rc num host num unit num
	       Mode sense command did not complete as expected.

	  scsi:ERROR:adgetcdb:unsupported command num
	       Internal error - unexpected command.

	  scsi:WARNING:adintr:adapter num SR_DETECTED status=num,
	       intr=num
	       SCSI reset detected.

	  scsi:WARNING:Unexpected MBI status num
	       Unexpected condition after interrupt.

	  scsi:WARNING:ad_sndcmd:unexpected port status = num
	       Unable to send command to adapter.

	  scsi:ERROR:adpresent:Adapter num internal failure:num
	       Adapter returned bad status on initialization.

     Page 31					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  scsi:ERROR:on disk dev=num/num ha=num id=num lun=num
	       block=num sector=num, cylinder/head = num/num
	       Disk I/O failure.

	  scsi:ERROR:on tape ha=num id=num lun=num hst num ust num
		       AHA-1540	 cmd  :num [num ...]
		       AHA-1540 sense :num [num ...]
	       Tape I/O failure; followed by one of these messages:

	  end of tape
	  tape is write protected
	  wrong record length

	Disk Driver Messages
	  disk:ERROR:Diskinfo table overflow
	       Too many disk drives in use - reconfigure kernel to
	       increase the available number of disks.

	  disk:ERROR:Invalid partition sector on hard disk
	       Master boot block on disk is unrecognizable. Run
	       fsck(ADM).

	Floppy Driver Messages
	  floppy:WARNING:CMOS indicates no diskette drives installed
	       Configuration memory invalid - run your DOS SETUP disk.

	  floppy:WARNING:CMOS indicates diskette drive num not present
	       Configuration memory invalid - run your DOS SETUP disk.

	  floppy:ERROR:fdnum being formatted
	       The floppy drive is in use.

	  floppy:ERROR:disk is write protected
	       The disk cannot be written because it is protected.

	  floppy:ERROR:on dev (num/num), block=num cmd=num status=num
	       Floppy I/O failure.  possibly followed by the message:
	       insert disk or close floppy door
	       if appropriate.

	  floppy:WARNING:cmd result error
	       I/O error on the floppy drive.

	VPIX Messages
	  VPIX:command completed unexpectedly
	       Process terminated prematurely.

	OMTI Driver Messages
	  omti:ERROR:cannot allocate a GDT descriptor
	       Internal error - kernel dscralloc routine failed.

	  omti:ERROR:unit=num controller not configured

     Page 32					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	       Internal error - driver open failed to identify disk
	       type.

	  omti:WARNING:already busy
	       Internal error - omtistart called for a busy drive.

	  omti:ERROR:unknown command(num), bp->b_cmd
	       Internal error - omtistart encountered an unrecognized
	       command.

	  omti:ERROR:command setup failed
	       Controller failed to accept command.

	  omti:WARNING:non-omti interrupt (num), omti_status
	       Controller did not signal an interrupt when an
	       interrupt was received.

	  omti:WARNING:unexpected omti interrupt (num), omti_status
	       Internal error - no pending command when interrupt
	       received.

	  omti:WARNING:still busy
	       Controller still busy after generating an interrupt.

	  omti:ERROR:during omti_sense
	       Interrupt received during an OMTI sense command.

	  omti:ERROR:initialization failure
	       Error indicated during an initialization.

	  omti:ERROR:sense command setup failed
	       Controller failed to accept setup command.

	  omti:ERROR:minor=num, block=num, errtype=num, code=num,
	       unit=num [sector=num, cylinder/head=num/num, ]
	       <message>
	       Disk I/O failure. <message> is one of:

	  No error or no sense information,
	  No Index,
	  No Seek/Command Complete,
	  Write/Drive Fault,
	  Drive Not Selected/Not Ready,
	  No Track zero or Cylinder zero found,
	  Multiple Drives Selected,
	  Seek/Command in progress,
	  Cartridge Changed
	  ID CRC,
	  Uncorrectable Data ECC,
	  ID Address Mark Not Found,
	  Data Address Mark Not Found,
	  Sector Not Found,

     Page 33					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	  Seek Error,
	  Sequence/DMA,
	  Write Protected,
	  Correctable ECC,
	  Bad Track Encountered,
	  Illegal Interleave Factor,
	  Unknown Error,
	  Ilegal Access To An Alternated Track/Unable to Read the
	  Alternate Track Address,
	  Alternate of Bad Track Already Assigned,
	  No Alternate Track Found,
	  Illegal Alternate Track Address
	  Invalid Command,
	  Illegal Disk Address,
	  Illegal Function for Drive Type,
	  Volume Overflow
	  RAM error,
	  EPROM Checksum/Internal Diagnostic error
	  Error with unknown type or code

	  omti:ERROR:controller already in select state
	       Internal error - controller busy when sending command.

	  omti:ERROR:cannot enter command phase
	       Controller failed to accept select command.

	  omti:ERROR:C_D bit stuck off
	       Controller failed to indicate readiness for command.

	  omti:ERROR:OMTI_BUSY bit still stuck on
	       Controller failed to obey reset command.

	  omti:INFO:unloading all requests
	       Preparing for manual reset because programmed reset did
	       not work.

	  omti:WARNING:colliding polling routines ...
	       Internal error - multiple instances of omtipoll.

	  omti:ERROR:timed out
	       Expected interrupt did not arrive.

	  omti:ERROR:please use sfmt to modify disk parameters
	       Attempt to write disk characteristics directly with
	       DIOWDISK ioctl.

	Serial Driver Messages
	  serial:ERROR:Garbage or loose cable on dev num, port shut
	       down
	       Too many interrupts were received together. Check your
	       connections.

     Page 34					      (printed 2/7/91)

     MESSAGES(M)	      XENIX System V		   MESSAGES(M)

	Winchester Driver Messages
	  wd:ERROR:on fixed disk dev=num/num block=num cmd=num
	       status=num sector=num, cylinder/head = num/num
	       Disk I/O failure.

	Event Driver Messages
	  event:ERROR:event channel full
	       There are no more devices available in the event queue.

	  event:ERROR:event table full
	       All of the system's event queues are opened.

	Keyboard Driver Messages
	  kb:ERROR:keyboard is in an unknown mode
	       The keyboard has been set in an invalid mode through an
	       ioctl(). The only valid keyboard modes are XT (0) and
	       AT(1).

     Notes
	  Some messages are processor dependent.

     Page 35					      (printed 2/7/91)

[top]
                             _         _         _ 
                            | |       | |       | |     
                            | |       | |       | |     
                         __ | | __ __ | | __ __ | | __  
                         \ \| |/ / \ \| |/ / \ \| |/ /  
                          \ \ / /   \ \ / /   \ \ / /   
                           \   /     \   /     \   /    
                            \_/       \_/       \_/ 
More information is available in HTML format for server Xenix

List of man pages available for Xenix

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net