BAD TRAP
Cause
A bad trap can indicate faulty hardware or a mismatch between hardware and its
configuration information. Data loss is possible if the problem occurs other than at
boot time.
Action
If you recently installed new hardware, verify that the software was correctly
configured. Check the kernel traceback displayed on the console to see which device
generated the trap. If the configuration files are correct, you probably have to replace
the device.
In some cases, the bad trap message indicates a bad or down-rev CPU.
Technical Notes
A hardware processor trap occurred, and the kernel trap handler was unable to
restore the system state. This message is a fatal error that usually precedes a panic,
after which the system performs a sync, dump, and reboot. The following conditions
can cause a bad trap: a system text or data access fault, a system data alignment
error, or certain kinds of user software traps.
#####################################################################
/bin/sh: file: too big
Cause
This Bourne shell message indicates a classic "no memory" error. While trying to load
the program specified after the first colon, the shell noticed that the system ran out
of virtual memory (swap space).
Action
Add virtual swap space
######################################################################
Block device required
Cause
A raw (character special) device was specified where a block device was required,
such as during a call to the mount(1M) command.
Action
To see which block devices are available, use ls -l to look in /devices. Then
specify a block device instead of a character device. Block device modes start with a
b, whereas raw character device modes start with a c.
Technical Notes
The symbolic name of this error is ENOTBLK, errno=15.
################################################################
Boot device: /iommu/sbus/directory/directory/
sd@3,0
Cause
This message always appears at the beginning of rebooting. If there is a problem, the
system hangs, and no other messages appear. This condition is caused by conflicting
SCSI targets for the boot device, which is almost always target 3.
Action
The boot device is usually the machine’s internal disk drive, target 3. Make sure that
external and secondary disk drives are targeted to 1, 2, or 0, and do not conflict with
each other. Also make sure that the tape drives are targeted to 4 or 5, and CD drives
to 6, avoiding any conflict with each other or with the disk drives. You can set a
device’s target number using push-button switches or a dial on the back near the
SCSI cables. If the targeting of the internal disk drive is in question, check it by
powering off the machine, removing all external drives, turning the power on, and
running the probe-scsi-all or probe-scsi command from the PROM monitor.
Cause
A bad trap can indicate faulty hardware or a mismatch between hardware and its
configuration information. Data loss is possible if the problem occurs other than at
boot time.
Action
If you recently installed new hardware, verify that the software was correctly
configured. Check the kernel traceback displayed on the console to see which device
generated the trap. If the configuration files are correct, you probably have to replace
the device.
In some cases, the bad trap message indicates a bad or down-rev CPU.
Technical Notes
A hardware processor trap occurred, and the kernel trap handler was unable to
restore the system state. This message is a fatal error that usually precedes a panic,
after which the system performs a sync, dump, and reboot. The following conditions
can cause a bad trap: a system text or data access fault, a system data alignment
error, or certain kinds of user software traps.
#####################################################################
/bin/sh: file: too big
Cause
This Bourne shell message indicates a classic "no memory" error. While trying to load
the program specified after the first colon, the shell noticed that the system ran out
of virtual memory (swap space).
Action
Add virtual swap space
######################################################################
Block device required
Cause
A raw (character special) device was specified where a block device was required,
such as during a call to the mount(1M) command.
Action
To see which block devices are available, use ls -l to look in /devices. Then
specify a block device instead of a character device. Block device modes start with a
b, whereas raw character device modes start with a c.
Technical Notes
The symbolic name of this error is ENOTBLK, errno=15.
################################################################
Boot device: /iommu/sbus/directory/directory/
sd@3,0
Cause
This message always appears at the beginning of rebooting. If there is a problem, the
system hangs, and no other messages appear. This condition is caused by conflicting
SCSI targets for the boot device, which is almost always target 3.
Action
The boot device is usually the machine’s internal disk drive, target 3. Make sure that
external and secondary disk drives are targeted to 1, 2, or 0, and do not conflict with
each other. Also make sure that the tape drives are targeted to 4 or 5, and CD drives
to 6, avoiding any conflict with each other or with the disk drives. You can set a
device’s target number using push-button switches or a dial on the back near the
SCSI cables. If the targeting of the internal disk drive is in question, check it by
powering off the machine, removing all external drives, turning the power on, and
running the probe-scsi-all or probe-scsi command from the PROM monitor.
No comments:
Post a Comment