From owner-freebsd-bugs  Tue Oct 14 11:10:03 1997
Return-Path: <owner-freebsd-bugs>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA07018
          for bugs-outgoing; Tue, 14 Oct 1997 11:10:03 -0700 (PDT)
          (envelope-from owner-freebsd-bugs)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA07012;
          Tue, 14 Oct 1997 11:10:01 -0700 (PDT)
          (envelope-from gnats)
Resent-Date: Tue, 14 Oct 1997 11:10:01 -0700 (PDT)
Resent-Message-Id: <199710141810.LAA07012@hub.freebsd.org>
Resent-From: gnats (GNATS Management)
Resent-To: freebsd-bugs
Resent-Reply-To: FreeBSD-gnats@FreeBSD.ORG, jayrich@sysc.com
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id LAA06423;
          Tue, 14 Oct 1997 11:02:49 -0700 (PDT)
          (envelope-from nobody)
Message-Id: <199710141802.LAA06423@hub.freebsd.org>
Date: Tue, 14 Oct 1997 11:02:49 -0700 (PDT)
From: jayrich@sysc.com
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: kern/4764: adaptec driver in 2.2-stable causes timeout errors that freeze system
Sender: owner-freebsd-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk


>Number:         4764
>Category:       kern
>Synopsis:       adaptec driver in 2.2-stable causes timeout errors that freeze system
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Oct 14 11:10:01 PDT 1997
>Last-Modified:
>Originator:     Jay Richmond
>Organization:
Eagle Micro
>Release:        latest 2.2-stable
>Environment:
FreeBSD room101.sysc.com 2.2-STABLE FreeBSD 2.2-STABLE #0: Tue Oct 14 11:40:22 EST 1997     jayrich@room101.sysc.com:/usr/src/sys/compile/ROOM101  i386
>Description:
Noticed when running the dump utility overnight, came back to system in the morning
and it was "looping" with scb timeout errors:

sd0(ahc 0:6:0):SCB0x3 - timed out while idle, LASTPHASE == 0x1,SCSISIGI == 0x0
       SEQ ADDR == 0x5
       sd0(ahc 0:6:0): Queueing an Abort SCB
       sd0(ahc 0:6:0): SCB0x3 - timed out while idle, LAST PHASE == 0x1, SCSISIGI == 0x0
       SEQ ADDR == 0x5
       sd0(ahc 0:6:0): no longer in timeout
       ahc0: Issued Channel A Bus Reset. 2 SCBs aborted

PR bin/4333 reported a similar problem and the suggestion was made
to upgrade to the latest 2.2-stable kernel, which I did and am
still having problems.

I tried this with any combination of the AHC options enabled in the
kernel, including none, and it occurs under every one.

The system required a hard reboot to come back on-line.

Here's my kernel probe:Oct 12 01:24:56 room101 /kernel: ahc0 <Adaptec 2940 Ultra SCSI host adapter> rev 0 int a irq 10 on pci0:10

Oct 12 01:24:56 room101 /kernel: ahc0: aic7880 Wide Channel, SCSI Id=0, 16/255 SCBs
Oct 12 01:24:56 room101 /kernel: ahc0 waiting for scsi devices to settle
Oct 12 01:24:56 room101 /kernel: (ahc0:6:0): "QUANTUM XP32275W LXY4" type 0 fixed SCSI 2
Oct 12 01:24:56 room101 /kernel: sd0(ahc0:6:0): Direct-Access 2170MB (4445380 512 byte sectors)
Oct 12 01:24:56 room101 /kernel: (ahc0:7:0): "iomega jaz 1GB H.71" type 0 removable SCSI 2
Oct 12 01:24:56 room101 /kernel: sd1(ahc0:7:0): Direct-Access
Oct 12 01:24:56 room101 /kernel: sd1(ahc0:7:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB
Oct 12 01:24:56 room101 /kernel: sd1 could not mode sense (4). Using ficticious geometry


>How-To-Repeat:
This error occurs under heavy load.  Happens every so often with the 'dump'
utility.
>Fix:

>Audit-Trail:
>Unformatted: