From owner-freebsd-hackers Sun Nov 23 01:36:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA01239 for hackers-outgoing; Sun, 23 Nov 1997 01:36:59 -0800 (PST) (envelope-from owner-freebsd-hackers) Received: from atlantis.ping.at (a064.static.Vienna.AT.EU.net [193.154.186.64]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA01220 for ; Sun, 23 Nov 1997 01:36:53 -0800 (PST) (envelope-from hfwirth@eunet.at) Received: from atlantis (localhost.ping.at [127.0.0.1]) by atlantis.ping.at (8.8.8/8.6.12) with SMTP id KAA00684; Sun, 23 Nov 1997 10:36:55 +0100 (MET) Message-ID: <3477F937.41C67EA6@eunet.at> Date: Sun, 23 Nov 1997 10:36:55 +0100 From: "Helmut F. Wirth" X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: freebsd-hackers@freebsd.org Subject: Adaptec 2940 timeout problems, again Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I just sent a new bug report: The (at last for me old) problem with the ADAPTEC reporting "timed out while idle" bites again: sd0: SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR = 0x8 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa sd0: Queueing an Abort SCB sd0: Abort Message Sent sd0: SCB 1 - Abort Completed. sd0: no longer in timeout .... The behaviour is improved somewhat as the system seems to recover in many cases. But a hard reset does not help, if the system hangs: I have to power cycle the system to bring the disk to work again. The disk is in a very peculiar state, as it responds to the BIOS while booting, but it then hangs during the boot (boot block loads, then it hangs). Here is the relevant part of the kernel boot: Nov 23 09:42:58 atlantis /kernel: ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs Nov 23 09:42:58 atlantis /kernel: ahc0: waiting for scsi devices to settle Nov 23 09:42:58 atlantis /kernel: scbus0 at ahc0 bus 0 Nov 23 09:42:58 atlantis /kernel: sd0 at scbus0 target 0 lun 0 Nov 23 09:42:58 atlantis /kernel: sd0: type 0 fixed SCSI 2 Nov 23 09:42:58 atlantis /kernel: sd0: Direct-Access 2050MB (4199760 512 byte sectors) Nov 23 09:42:58 atlantis /kernel: sd1 at scbus0 target 1 lun 0 Nov 23 09:42:58 atlantis /kernel: sd1: type 0 fixed SCSI 2 Nov 23 09:42:58 atlantis /kernel: sd1: Direct-Access 1034MB (2118144 512 byte sectors) Nov 23 09:42:58 atlantis /kernel: sd2 at scbus0 target 2 lun 0 Nov 23 09:42:58 atlantis /kernel: sd2: type 0 fixed SCSI 2 Nov 23 09:42:58 atlantis /kernel: sd2: Direct-Access 2151MB (4406960 512 byte sectors) Nov 23 09:42:58 atlantis /kernel: sd3 at scbus0 target 3 lun 0 Nov 23 09:42:58 atlantis /kernel: sd3: type 0 removable SCSI 2 Nov 23 09:42:58 atlantis /kernel: sd3: Direct-Access Nov 23 09:42:58 atlantis /kernel: sd3: ILLEGAL REQUEST asc:24,0 Invalid field in CDB Nov 23 09:42:58 atlantis /kernel: sd3 could not mode sense (4). Using ficticious geometry Nov 23 09:42:58 atlantis /kernel: Nov 23 09:42:58 atlantis /kernel: sd3: NOT READY asc:3a,0 Medium not present Nov 23 09:42:58 atlantis /kernel: sd3: could not get size I have currently AHC_ALLOW_MEMIO, AHC_TAGENABLE and AHC_SCBPAGING_ENABLE *disabled*, i.e. they are not in my kernel configuration. The error occurs with heavy disk load (for example while building world for FreeBSD-current). It seems to be limited to sd0, a QUANTUM ATLAS disk. The second QUANTUM disk (sd2) has *upgraded* firmware, for the first disk there is no upgrade available (the disk is about one year older). For more detail please see my bug report (i386/5128). Any hints ? This is really annoying, any hint would help. Thank you. Helmut F. Wirth Email: hfwirth@eunet.at