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!vixen.cso.uiuc.edu!howland.reston.ans.net!news.sprintlink.net!sun.cais.com!news.cais.com!interlog.com!morphos.com!daves
From: daves@interlog.com (David Shadoff)
Newsgroups: comp.os.386bsd.questions
Subject: Re: FreeBSD 2.0: SCSI problems
Date: Fri, 20 Jan 1995 01:30:37
Organization: Morphos Systens Inc.
Lines: 49
Distribution: world
Message-ID: <daves.10.000182BB@interlog.com>
References: <A0045.95Jan12111714@roxi.rrz.Uni-Koeln.DE>
NNTP-Posting-Host: morphos.interlog.com
X-Newsreader: Trumpet for Windows [Version 1.0 Rev A]
In article <A0045.95Jan12111714@roxi.rrz.Uni-Koeln.DE> a0045@roxi.rrz.Uni-Koeln.DE (Jochen Roderburg) writes:
>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.
I went through some of the same problems as you - 1542B controller with those
same errors, and nobody believed me. I got a new motherboard, and things
worked fine again.
Parameters for my problem: the montherboard was a 'PC CHIP' chipset, TI
486DLC, with AHA-1542B. Tried several drives, ALL permutations of
termination, and several cables. New motherboard (Intel 486DX2-66/SIS
chipset) solved all problems.
Software which worked: DOS, Linux up to at least Jan 1994 (I gave up on Linux
at that time in favour of FreeBSD), FreeBSD 1.0, etc.
Software which failed: FreeBSD 1.1, FreeBSD 2.0, Linux Slackware Fall 1994.
I can only conclude that the drivers changed in the spring/summer last year,
and were duplicated into both OS's - while my chipset was untested, it seemed
as though many people thought such a bug was impossible - that it must be a
hardware problem.