Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!msunews!uwm.edu!math.ohio-state.edu!howland.reston.ans.net!swrinde!news.uh.edu!uuneo.neosoft.com!pluto.ops.NeoSoft.com!not-for-mail
From: smace@pluto.ops.NeoSoft.com (Scott Mace)
Newsgroups: comp.os.386bsd.questions
Subject: Re: FreeBSD 2.0: SCSI problems
Date: 17 Jan 1995 14:36:28 -0600
Organization: NeoSoft Internet Services +1 713 968 5800
Lines: 39
Message-ID: <3fh9oc$ldt@pluto.ops.NeoSoft.com>
References: <A0045.95Jan12111714@roxi.rrz.Uni-Koeln.DE> <3f4g60$jp1@ivory.lm.com>
NNTP-Posting-Host: pluto.ops.neosoft.com
In article <3f4g60$jp1@ivory.lm.com>,
Peter Berger <peterb@telerama.lm.com> wrote:
>In article <A0045.95Jan12111714@roxi.rrz.Uni-Koeln.DE>,
>Jochen Roderburg <a0045@roxi.rrz.Uni-Koeln.DE> wrote:
>>nate@FreeBSD.org wrote here (I lost the original reference):
>>
>>>> Saying it works under DOS doesn't necessarily mean anything, and it's
>>>> possible that the Linux drivers doesn't use the devices as 'hard' as the
>>>> FreeBSD driver. Basically, termination problems might not show up until
>>>> the system is used heavily enough to cause 'reflections' to wipe out
>>>> good date on the wire.
>>
>>Is it possible to understand in which way FreeBSD uses SCSI devices *harder*
>>than Linux? I ask because I have various similar SCSI problems on two
>>systems under FreeBSD which do not show up at all under Linux
>>(and of course not under DOS/Windows).
>>
>
>SCSI problems are very pernicious. They don't always show up
>deterministically, especially under different operating systems.
>
>> aha0: MBO not free
>> sd0(aha0:0:0): timed out
>> adapter not taking commands.. frozen?!
>> Debugger("aha1542") called.
>> sd0(aha0:0:0): timed out
>> adapter not taking commands.. frozen?!
>> Debugger("aha1542") called. AGAIN
>
>I ran into the exact same problem. To fix it, I needed to turn off
>synchronous access on -both- the host adapter and the drive.
>
>
I had some weird scsi problems a while back and it turned out that it was
a termination problem. I had to set the drive(which was a seagate st32550n
to either terminator power from the bus. After that it seemed to work great...
Scott