Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.netspace.net.au!serval.net.wsu.edu!netnews.nwnet.net!oracle.pnl.gov!osi-east2.es.net!lll-winken.llnl.gov!uwm.edu!news.moneng.mei.com!hookup!olivea!uunet!zib-berlin.de!rs1-hrz.uni-duisburg.de!rrz.uni-koeln.de!RRZ.Uni-Koeln.DE!RRZ.Uni-Koeln.DE!news
From: a0045@roxi.rrz.Uni-Koeln.DE (Jochen Roderburg)
Newsgroups: comp.os.386bsd.questions
Subject: FreeBSD 2.0: SCSI problems
Date: 12 Jan 1995 10:17:14 GMT
Organization: Regional Computing Center, University of Cologne
Lines: 49
Distribution: world
Message-ID: <A0045.95Jan12111714@roxi.rrz.Uni-Koeln.DE>
NNTP-Posting-Host: roxi.rrz.uni-koeln.de
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).
One system has an old ESDI boot disk and an Adaptec 1542B adapter with an
internal tape and external 2 disks and CD-ROM (The disks are a CONNER
CFP1060S and a SEAGATE ST31200N).
After the system is running a while it always seems to loose the contact
with the disks. Everything stops and I get a never-ending flood of messages
on the console like:
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
Luckily enough I never had a corrupted filesystem, but the only way to get
out of the situation has always been a reboot.
Before FreeBSD I had Linux on the same hardware where I never saw something
similar, but through several FreeBSD versions (1.1, 1.1.5, 2.0) the problem
has not changed.
The other system is an SCSI-only system with an Adaptec 1542CF adapter and
only internal devices (disk, tape and CD-ROM again). On this system it is
even worse. I have not even been able to install FreeBSD successfully there,
I have already corrupted files and file-systems during the early stage of
the installation. Again, DOS/Windows/Linux run without disk problems here.
Jochen Roderburg
Regional Computing Center
University of Cologne
Robert-Koch-Str. 10 Tel.: +49-221/470-4564
D-50931 Koeln E-Mail: Roderburg@rrz.Uni-Koeln.DE
Germany