Date: Fri, 8 Dec 1995 17:22:27 -0800 (PST) From: Julian Elischer <julian@ref.tfs.com> To: se@zpr.uni-koeln.de (Stefan Esser) Cc: rmallory@wiley.csusb.edu, scsi@freebsd.org Subject: Re: Check back Re: Problem with IBM 2 gig Message-ID: <199512090122.RAA07036@ref.tfs.com> In-Reply-To: <199512081523.AA26892@Sysiphos> from "Stefan Esser" at Dec 8, 95 04:23:21 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> } > Dec 3 22:56:03 kickme /kernel: ncr0:6: ERROR (80:140) (8-2a-0) (88/13) @ (bd4:900b0000).
> } > Dec 3 22:56:03 kickme /kernel: ncr0:6: ERROR (80:140) (8-2a-0) (88/13) @ (bd4:900b0000).
>
> It is quite funny to see this (and the other messages)
> appear twice ... Never observed that before ...
that's just syslog entering it twice I would guess.
>
> } > Dec 3 22:56:04 kickme /kernel: sd0(ncr0:0:0): UNIT ATTENTION asc:29,0
>
> The hard disk complains about the bus reset. Why was there
> no message from the NCR driver, that it was about to send
> a SCSI bus reset ??? Hmmm.
I tcould have been a power glitch to the drives too.
I've seen that.. (loose power connector..)
gives the same error message....
>
> } > Dec 3 22:56:05 kickme /kernel: sd0(ncr0:0:0): Power on, reset, or bus device reset occurred
> } > Dec 3 22:56:05 kickme /kernel: sd0(ncr0:0:0): Power on, reset, or bus device reset occurred
>
> The same in text form ...
>
> I'm a little confused about the two identical error messages.
> The commands in question are one and the same (as the @f0aa8a00
> command control block address proves).
as I said, that's just syslog
If you looked in dmesg, there would only actually be one..
>
> If this remains a single case, thaen I'd say it most likely was
> a glitch. The driver was in an consistent state, and the NCR
> seems to have missed the fact, that the bus was ready for the
> requested command transfer, according to the SCSI control lines
> printed in the error message.
>
> The timeout lead to a SCSI bus reset, but the generic SCSI code
> should have resent the command to the hard disk, and if the
> CDROM did not lock up internally, then it should have been able
> to continue normal operation as well.
>
> Or did the system crash as a result ???
>
>
> Regards, STefan
>
That was my thought on the matter too...
julian
+----------------------------------+ ______ _ __
| __--_|\ Julian Elischer | \ U \/ / On assignment
| / \ julian@ref.tfs.com +------>x USA \ in a very strange
| ( OZ ) 300 lakeside Dr. oakland CA. \___ ___ | country !
+- X_.---._/ USA+(510) 645-3137(wk) \_/ \\
v
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199512090122.RAA07036>