MESSAGES(M) UNIX System V
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
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.
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.
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
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.
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.
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.
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
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?
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.
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
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.
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
(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
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
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
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
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 UNIX. 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
IRWIN:ERROR:Tape bad block table was not successfully read.
When the tape device is open the bad block table is
read into memory. This messages indicates that the read
did not work correctly.
IRWIN:ERROR:Tape is not formatted.
The tape must be formatted before use.
IRWIN:ERROR:Tape is write protected.
The write protect tab must be removed for use.
IRWIN:ERROR:Cannot write to DC1000 cartridge.
Only Irwin model 110 or 125 drives can write to DC1000
cartridges.
IRWIN:ERROR:Not enough memory for mini-cartridge;
retrying...
The Irwin is waiting for enough user memory to become
available to use the device.
IRWIN:ERROR:Not enough memory for mini-cartridge; open
failed.
The Irwin did not get enough memory to be able to use
the device after several retries.
IRWIN:ERROR:Tape write error.
A write attempt was unsuccessful for an unknown reason.
IRWIN:ERROR:Tape verify error.
A verify attempt was unsuccessful for an unknown
reason.
IRWIN:ERROR:Tape read error.
A read attempt was unsuccessful for an unknown reason.
IRWIN:ERROR:Tape uncorrectable ECC error.
An uncorrectable ECC memory error has occurred, check
your hardware for defective chips.
IRWIN:ERROR:Cannot format DC1000 cartridge.
Only Irwin model 110 or 125 drives can write to DC1000
cartridges.
IRWIN:ERROR:Bad state:num
Unknown state in the interrupt routine.
IRWIN:ERROR:DMA boundary error - start address:num ending
address:num
Device tried to transfer data from a buffer that
crosses a 64k boundary.
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.
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.
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
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,
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.
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
Not all messages appear on all machines. Some messages are
processor dependent.
(printed 8/23/89) MESSAGES(M)