Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Mar 1997 00:42:41 -0800 (PST)
From:      Matt Dillon <dillon@best.net>
To:        FreeBSD-gnats-submit@freebsd.org
Subject:   i386/2985: Getting "Target did not send an IDENTIFY" panic
Message-ID:  <199703140842.AAA06253@flea.best.net>
Resent-Message-ID: <199703140850.AAA07793@freefall.freebsd.org>

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

>Number:         2985
>Category:       i386
>Synopsis:       stable machine crashes every 8 or so hours with SCSI panic
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Mar 14 00:50:01 PST 1997
>Last-Modified:
>Originator:     Matt Dillon
>Organization:
BEST Internet Communications, Inc.
>Release:        2.1.? CTM 0291
>Environment:

	PPro 200, 128MB ram, five 4GB disks (one quantum, four barracudas...
  	the quantum has been upgraded).  Adaptec PCI SCSI card as shown
	below.

    Probing for devices on PCI bus 0:^M
    chip0  Intel 82440FX (Natoma) PCI and memory controller  rev 2 on pci0:0^M
    chip1  Intel 82371SB PCI-ISA bridge  rev 1 on pci0:1:0^M
    chip2  Intel 82371SB IDE interface  rev 0 on pci0:1:1^M
    ahc0  Adaptec 2940 Ultra SCSI host adapter  rev 0 int a irq 12 on pci0:9^M
    ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs^M
    ahc0 waiting for scsi devices to settle^M
	...


	

>Description:

    We get a consistant panic every 8 or so hours.  It goes something like:

    ahc0:A:0: no active SCB for reconnecting target - issuing ABORT^M
    SAVED_TCL == 0x20^M
    panic: ahc0:A:0: Target did not send an IDENTIFY message. LASTPHASE = 0x0, SAVED
    _TCL == 0x10

    The only real custom config that might apply is that four of the disks
    are striped with ccd.  The machine is a very heavily used nntp reader
    machine, with lots of disk I/O.

>How-To-Repeat:

    The machine panics every so often.  I cannot force the panic to occur with
    any particular sequence of commands.

    We are currently running an older kernel (Feb 25 kernel, CTMs through 286)
    to determine if the Feb 26 ctm patch (src-2.1.0287) is the cause of
    the panic.  We will not know the answer for another day or two.

>Fix:
	
	

>Audit-Trail:
>Unformatted:



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