Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 4 Jan 1996 07:52:57 -0500 (EST)
From:      Peter Dufault <dufault@hda.com>
To:        obrien@cs.ucdavis.edu (David E. O'Brien)
Cc:        freebsd-questions@freebsd.org
Subject:   Re: SCSI bus/device timeouts on AHA-1542b
Message-ID:  <199601041252.HAA07040@hda.com>
In-Reply-To: <9601041020.AA14216@toadflax.cs.ucdavis.edu> from "David E. O'Brien" at Jan 4, 96 02:20:32 am

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
These kinds of errors are typical of something wedging the
SCSI bus and hanging the controller.

As always, "SCSI bus integrity".  Be sure that only the first
and last devices are terminated, that you have the appropriate
cables, and that someone is supplying terminator power.

> After hard useage (heavy cp'ing/tar'ing), I get:
> 
> Jan  3 02:56:35 foobar /kernel: sd0(aha0:0:0): timed out

A disk transfer timed out.  The 1542B light is probably on solid,
and the firmware is hung.

> Jan  3 02:56:35 foobar /kernel: adapter not taking commands.. frozen?!

The 1542 won't talk.

> Jan  3 02:56:35 foobar /kernel: Debugger("aha1542") called.

If "ddb" were configured you'd be in ddb now.

> Jan  3 02:56:35 foobar /kernel:  AGAIN

The host adapter transaction timed out again...

> Jan  3 02:56:35 foobar /kernel: aha0: MBO 02 and not 00 (free)

And the command mailbox is not free.   It is still the 02 put there
to try to abort the transaction.

> Jan  3 02:56:45 foobar /kernel: sd0(aha0:0:0): timed out
> Jan  3 02:56:45 foobar /kernel: adapter not taking commands.. frozen?!
> Jan  3 02:56:45 foobar /kernel: Debugger("aha1542") called.

If this isn't the cables, then maybe there is a new firmware rev for something?

--

Peter Dufault               Real Time Machine Control and Simulation
HD Associates, Inc.         Voice: 508 433 6936
dufault@hda.com             Fax:   508 433 5267



Want to link to this message? Use this URL: <http://docs.FreeBSD.org/cgi/mid.cgi?199601041252.HAA07040>