Subject: Re: Boot messages into /var/log/messages ...
To: None <current-users@NetBSD.ORG>
From: Dave Sainty <Dave.Sainty@MCS.VUW.AC.NZ>
List: current-users
Date: 09/27/1997 13:19:03
Luwenth the Lewd writes:

> 	I am working on trying to figure out why a recently acquired SCSI
> tape changer isn't behaving, and I noticed a large change in the
> information that's being put into /var/log/messages on a reboot.
> 	It used to be that all the messages to console started with cpu0.
> Now, I seem to be only getting snippets of all the messages.
> 	Is this something I likely flubbed in my config file, or is there
> something else that I'm missing?
> 	I'm including the messages old and new, and my conf file, if anyone
> wants to take the time to look them over.
> 	-- Ricky
> ---- old listing
> Sep 26 12:24:07 meta /netbsd: ch4 at scsibus0 targ 4 lun 1: <@RBHHVD, Pxthnn 28848,XXX, 4.B> SCSI2 8/changer removable
> Sep 26 12:24:07 meta /netbsd: ch4(aic0:4:1): error code 0
> Sep 26 12:24:07 meta /netbsd: ch4: could not sense element address page
> Sep 26 12:24:07 meta /netbsd: ch4: offline

Looks like hardware to me, bit 0 of your SCSI bus is always low.  You
can see this from what the message should be, as posted by someone

Sep 26 14:25:38 frobzit /netbsd: ch0 at scsibus0 targ 3 lun 1:
<ARCHIVE, Python 28849-XXX, 4.CM> SCSI2 8/changer removable

Might just be your cable.