Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Apr 1995 21:40:04 -0700
From:      Stephen Hocking <sysseh@devetir.qld.gov.au>
To:        freebsd-bugs
Subject:   i386/337: Seagate code hangs on bootup.
Message-ID:  <199504120440.VAA26981@freefall.cdrom.com>
In-Reply-To: Your message of Wed, 12 Apr 1995 14:29:44 %2B1000 <199504120429.EAA12627@netfl15a.devetir.qld.gov.au>

next in thread | previous in thread | raw e-mail | index | archive | help

>Number:         337
>Category:       i386
>Synopsis:       seagate controller code hangs on boot.
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    freebsd-bugs (FreeBSD bugs mailing list)
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Apr 11 21:40:02 1995
>Originator:     Stephen Hocking
>Organization:
DEVETIR
>Release:        FreeBSD 2.1.0-Development i386
>Environment:

	FreeBSD-2.1-current src-cur.0500

	Hardware - 25MHz 386sx/386sx, 8Mb, S3911, TMC 885 SCSI controller,
        	WREN 6 harddrive "CDC 94191-15 0136"

>Description:

	On boot up, the machine hangs after identifying the controller, while
attempting to attach devices.

>How-To-Repeat:

	Get hold of appropriate hardware and boot.

>Fix:
	
	I had some success by making a bunch of variables volatile. However
this was still unstable and would usually start printing out timeouts
shortly after boot, if not during. This often had sad consequences for the
integrity of the filesystems. The final fix was to drag the source off the
2.0 CDROM and undefine SEA_BLINDTRANSFER and SEA_ASSEMBLER (at line 107 and
108 of /sys/i386/isa/seagate.c). It is slow, but at the moment it is partway
through a "make world" without complaining. This controller is at the moment
eating upto 50% of the CPU on interrupts, the rest mostly going on system
CPU. Why am I running this pile of canine ordure? My beloved Buslogic 542B
finally died after many years of service and I was desperate & cashless. The
Buslogic card would get by on 3-5% interrupt CPU, some system time (mostly
fs code) leaving plenty of idle CPU for other things. It could drive the
disk at platter speed, the seagate only manages about 30% (if that).


        I do not speak for the Worker's Compensation Board of Queensland -
                     They don't pay me enough for that!

>Audit-Trail:
>Unformatted:





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199504120440.VAA26981>