On Wed, 6 Jun 2001, Karsten W. Rohrbach wrote:
> Thomas Seck([EMAIL PROTECTED])@2001.06.05 12:56:35 +0000:
> > On Jun 05 2001, Jan Conrad wrote:
> > > Hi,
> > >
> > > I just got the following error message (running 4.3R)
> > >
> >
> (snipped)
>
> i guess you both ran into the quite well known bad termination problem.
> there were some questions a while ago concerning the freebsd vs linux
> scenario where a freebsd fails with SCB timeouts while a linux runs
> along with apparently no problems at all. the quick answer for this
> particular behaviour in freebsd is, that the io subsystem is designed to
> put more load onto the scsi devices than the implementation of other
> os'es io subsystems. so, basically, what happens is, that you only see
> the timeouts under freebsd, of course, since it arbits the scsi bus more
> often, and with more data in the same period of time compared to other
> implementations.
>
> terminate correctly, symmetric terminators, active, for u160. use good
> cables, no vobis crap ;-) i use amphenol cables for external links and
> gr-kabel (german distributor) for internal wiring. this solved most of
> my scsi problems with u160.
Well - let's go a bit more to the details here.
As for my part, the problem occured on the secondary single ended segment
of an Adaptec 29160. The (only) attached drive is an IBM DGHS09U 0350
running at 40MB/s. It is three years old, attached to the same cable since
three years (68pin internal cable). The drive is operating with on drive
termination. The 29160 checks for the proper termination of the drives and
gives no error message.
The SCSI 160 part of the system is running without any problems.
We will have to install a new fan anyway, so I will have the oportunity to
play around with the cableing a bit. Let's see...
>
> >
> > Regards from Bornheim :-)
> > Thomas Seck
> cheers from darmstadt,
> /k
thanks for all your responses
>
>
-Jan
--
Physikalisches Institut der Universitaet Bonn
Nussallee 12
D-53115 Bonn
GERMANY
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-stable" in the body of the message
