*BSD News Article 71368


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.rmit.EDU.AU!news.unimelb.EDU.AU!munnari.OZ.AU!news.mel.connect.com.au!news.mira.net.au!inquo!news.uoregon.edu!vixen.cso.uiuc.edu!newsfeed.internetmci.com!in2.uu.net!csnews!boulder!coopnews.coop.net!news.verinet.com!news
From: mike@bamboo.verinet.com (Mike Loseke)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: 2940 Ultra problems
Date: 18 Jun 1996 09:27:53 -0000
Organization: Verinet Communications
Lines: 76
Message-ID: <4q5sqp$giv@bamboo.verinet.com>
NNTP-Posting-Host: bamboo.verinet.com
Keywords: Adaptec 2940 Time-out

 I've encountered some strangeness, as of late, on my 2.1R system which
is using an Adptec 2940 Ultra. Here's what `dmesg` reports:

ahc0 <Adaptec 2940 Ultra SCSI host adapter> rev 0 int a irq 9 on pci0:20

Here are the devices, as well:

(ahc0:0:0): "QUANTUM FIREBALL1080S 1Q08" type 0 fixed SCSI 2
sd0(ahc0:0:0): Direct-Access 1042MB (2134305 512 byte sectors)
(ahc0:1:0): "Quantum XP34300 81HB" type 0 fixed SCSI 2
sd1(ahc0:1:0): Direct-Access 4101MB (8399520 512 byte sectors)
(ahc0:4:0): "ARCHIVE Python 28388-XXX 5.72" type 1 removable SCSI 2
st0(ahc0:4:0): Sequential-Access density code 0x13, 512-byte blocks, write-enabled

The problem is that I've been getting device timeouts and some (automatic)
reboots in the middle of the night due to who knows what. As of last night,
I've gotten time outs on all three devices. sd0 did not get a time out,
possibly due to it's not being mounted. Here is the series of entries from
last night's adventure from /var/log/messages:

Jun 18 04:38:19 tango /kernel: ahc0: target 4, lun 0 (st0) timed out
Jun 18 04:38:19 tango /kernel: st0(ahc0:4:0): BUS DEVICE RESET message queued.
Jun 18 04:38:21 tango /kernel: ahc0: target 4, lun 0 (st0) timed out
Jun 18 04:38:21 tango /kernel: ahc0: Issued Channel A Bus Reset #1. 1 SCBs aborted
Jun 18 04:40:01 tango /kernel: ahc0: target 4, lun 0 (st0) timed out
Jun 18 04:40:01 tango /kernel: ahc0: Issued Channel A Bus Reset #2. 0 SCBs aborted
Jun 18 04:41:41 tango /kernel: ahc0: target 4, lun 0 (st0) timed out
Jun 18 04:41:41 tango /kernel: ahc0: Issued Channel A Bus Reset #2. 0 SCBs aborted
Jun 18 04:42:09 tango /kernel: ahc0: target 1, lun 0 (sd1) timed out
Jun 18 04:42:09 tango /kernel: ahc0: Issued Channel A Bus Reset #2. 0 SCBs aborted
Jun 18 04:42:19 tango /kernel: ahc0: target 1, lun 0 (sd1) timed out
Jun 18 04:42:19 tango /kernel: sd1(ahc0:1:0): BUS DEVICE RESET message queued.
Jun 18 04:42:19 tango /kernel: ahc0: target 1, lun 0 (sd1) timed out
Jun 18 04:42:19 tango /kernel: sd1(ahc0:1:0): BUS DEVICE RESET message queued.
Jun 18 04:42:21 tango /kernel: ahc0: target 1, lun 0 (sd1) timed out
Jun 18 04:42:21 tango /kernel: ahc0: Issued Channel A Bus Reset #1. 5 SCBs aborted
Jun 18 04:42:21 tango /kernel: sd1(ahc0:1:0): UNIT ATTENTION asc:29,2
Jun 18 04:42:21 tango /kernel: , FAILURE
Jun 18 04:42:31 tango /kernel: ahc0: target 1, lun 0 (sd1) timed out
Jun 18 04:42:31 tango /kernel: ahc0: Issued Channel A Bus Reset #2. 0 SCBs aborted
Jun 18 04:42:41 tango /kernel: ahc0: target 1, lun 0 (sd1) timed out
Jun 18 04:42:41 tango /kernel: sd1(ahc0:1:0): BUS DEVICE RESET message queued.
Jun 18 04:42:41 tango /kernel: ahc0: target 1, lun 0 (sd1) timed out
Jun 18 04:42:41 tango /kernel: ahc0: Issued Channel A Bus Reset #1. 6 SCBs aborted
Jun 18 04:42:41 tango /kernel: ahc0:A:1: ahcintr - referenced scb not valid during seqint 0x71 scb(0)
Jun 18 04:42:41 tango /kernel: ahc0: WARNING no command for scb 0 (cmdcmplt)
Jun 18 04:42:41 tango /kernel: QOUTCNT == 0
Jun 18 04:42:41 tango /kernel: ahc0:A:1: no active SCB for reconnecting target -issuing ABORT
Jun 18 04:42:41 tango /kernel: SAVED_TCL == 0x10
Jun 18 04:42:51 tango /kernel: ahc0: target 1, lun 0 (sd1) timed out
Jun 18 04:42:51 tango /kernel: st0(ahc0:4:0): error code 0
Jun 18 04:42:51 tango /kernel: biodone: buffer already done
Jun 18 04:42:51 tango /kernel: ahc0: Issued Channel A Bus Reset #3. 0 SCBs aborted
Jun 18 04:42:51 tango /kernel: sd1(ahc0:1:0): UNIT ATTENTION asc:29,2
Jun 18 04:42:51 tango /kernel: , retries:2
Jun 18 04:43:01 tango /kernel: ahc0: target 4, lun 0 (st0) timed out
Jun 18 04:43:01 tango /kernel: ahc0: Issued Channel A Bus Reset #2. 0 SCBs aborted
Jun 18 04:43:11 tango /kernel: ahc0: target 1, lun 0 (sd1) timed out
Jun 18 04:43:11 tango /kernel: sd1(ahc0:1:0): BUS DEVICE RESET message queued.
Jun 18 04:43:13 tango /kernel: ahc0: target 1, lun 0 (sd1) timed out
Jun 18 04:43:13 tango /kernel: ahc0: Issued Channel A Bus Reset #1. 3 SCBs aborted
Jun 18 04:43:13 tango /kernel: sd1(ahc0:1:0): UNIT ATTENTION asc:29,2
Jun 18 04:43:13 tango /kernel: , retries:2
Jun 18 04:44:41 tango /kernel: ahc0: target 4, lun 0 (st0) timed out
Jun 18 04:44:41 tango /kernel: ahc0: Issued Channel A Bus Reset #2. 0 SCBs aborted
Jun 18 04:44:51 tango /kernel: ahc0: target 1, lun 0 (sd1) timed out
Jun 18 04:44:51 tango /kernel: sd1(ahc0:1:0): BUS DEVICE RESET message queued.

At this point the machine rebooted itself. Do I need to junk the controller
and get a new one, or is there something I'm missing? I've only been working
with FreeBSD for a few months so I'm no expert.
-- 
        Mike Loseke         |  If nobody else was violent, I could conquer
    System Administrator    |  the whole stupid planet with just a butter
   Verinet Communications   |  knife.                       -- Dogbert
      mike@verinet.com      |            ( DNRC Member )