Ian>>>>> I replaced a failed SCSI tape drive on an OSR507 system and
Ian>>>>> subsequently get this message at start-up:
Ian>>>>>
Ian>>>>> NOTICE: cha: SCSI bus has been reset ha=1
Ian>>>>> Attached SCSI peripherals will return to power up state \
Ian>>>>> (cha N04)
Ian>>>>> NOTICE: cha: Unexpected SCSI phase change \
Ian>>>>> ha=1 id=6 lun=0 cmd=12 blk=0 len=36
Ian>>>>> A SCSI peripheral behaved unexpectedly
Ian>>>>> Use Compaq diagnostics to confirm a hardware failure \
Ian>>>>> (chaN02)

Tony>>>> http://aplawrence.com/SCOFAQ/FAQ_scotec6cha.html ?

Bela>> The advice it gives:
Bela>>
Bela>> "int cha_print_warnings=0;"
Bela>>
Bela>> seems a little questionable to me. You don't know what other warnings
Bela>> it might turn off (media error messages? "The controller hardware
Bela>> reports it's about to die"?) I recommend leaving the warning on and
Bela>> simply ignoring it.

Ian> Ideally you'd be able to suppress notices and still receive warnings.
Ian>
Ian> I looked in /etc/conf/pack.d/cha/space.c and found this:
Ian>
Ian> /* Should NOTICE messages from the driver be printed?
Ian> Each possible NOTICE message is associated with one
Ian> bit in cha_print_notices. The value -1 turns on all the bits.
Ian> The value 0 suppresses all NOTICE messages.
Ian> To turn off message CHAN03, turn off bit 03.
Ian> */
Ian> int cha_print_notices = -1; /* 0 to supress all notices */
Ian>
Ian> Tony - you might like to update the SCOFAQ? If I get time, I'll try
Ian> setting cha_print_notices to 0 and report back here.
Ian>
Ian> The documentation (man HW cha) says "Although they may be recoverable,
Ian> you should attempt to determine their root cause and correct it." I
Ian> don't think I want to play around with the hardware too much.
Ian>
Ian> I'll just ignore the messages for now.

Well, it seems odd that the FAQ says to set `cha_print_warnings' to 0
when the messages you're trying to silence are labeled "NOTICE".

But, all that aside, I would recommend against suppressing the message
even if you were able to pinpoint a single bit in `cha_print_notices'
which controlled it. The fact that the controller burps up that notice
at boot time is well enough known to appear in the FAQ. The drive
works. So just ignore the notice.

If you get the _same_ notices later, during actual drive operation,
you'll want to see them -- otherwise the drive will seem to have just
mysteriously failed.

>Bela<