Subject: kernel.debug messages and /dev/rst0
To: None <current-users@netbsd.org>
From: Bill Squier <groo@guinness.cs.stevens-tech.edu>
List: current-users
Date: 01/21/1999 23:54:35
I've been carting files from home to school on DDS1 90M tapes for a while
now, using an Archive Python on my NetBSD/i386:
st0 at scsibus0 targ 4 lun 0: <ARCHIVE, Python 28454-XXX, 4.BL> SCSI2 1/sequential removable
and an Archive Python on a Sun 670MP (Solaris 2.5.1):
st11: <Archive Python 4mm Helical Scan>
with no problems. Today I began writing some tapes on my O2, using:
Device: ARCHIVE: Python 25501-XXX6320
and although my NetBSD box can read these tapes, I get zillions of the
following kernel.debug messages:
Jan 21 23:13:38 cthulhu /netbsd: st0(aic0:4:0): Check Condition on opcode 0x8
Jan 21 23:13:38 cthulhu /netbsd: SENSE KEY: No Additional Sense
Jan 21 23:13:38 cthulhu /netbsd: Incorrect Length Indicator Set
Jan 21 23:13:38 cthulhu /netbsd: INFO FIELD: 9728
Jan 21 23:13:38 cthulhu /netbsd: ASC/ASCQ: No Additional Sense Information
Jan 21 23:13:38 cthulhu /netbsd:
I'm sure this must be yet-another-IRIXism. Can someone enlighten me on the
meaning of that message so I can beat on the appropriate part of IRIX?
I've "solved" the problem temporarily by dropping kernel.debug from
syslog.conf but syslogd still consumes 75% of the CPU dropping those messages
during an extract. ;-(
-wps