From owner-freebsd-scsi Sun Jul 23 22:59:33 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mta5.snfc21.pbi.net (mta5.snfc21.pbi.net [206.13.28.241]) by hub.freebsd.org (Postfix) with ESMTP id 6C70537BA2E for ; Sun, 23 Jul 2000 22:59:29 -0700 (PDT) (envelope-from gdinolt@pacbell.net) Received: from pacbell.net ([63.201.59.169]) by mta5.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with ESMTP id <0FY600MV1T0DGT@mta5.snfc21.pbi.net> for scsi@freebsd.org; Sun, 23 Jul 2000 22:38:38 -0700 (PDT) Date: Sun, 23 Jul 2000 22:39:20 -0700 From: "George W. Dinolt" Subject: (noperiph:ahc0:0:-1:-1) & forwarded message ... To: scsi@freebsd.org Cc: rmtodd@servalan.servalan.com, mjacob@feral.com, Gemorga2@vt.edu, mwm@mired.org Message-id: <397BD688.983DCD97@pacbell.net> MIME-version: 1.0 X-Mailer: Mozilla 4.73 [en] (X11; I; Linux 2.2.12 i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Last week I reported on a pair of errors I have had trying to boot my 5.0-current system using the new (July 18 and later) ahc code. Specifically (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. panic: Bogus resid sgptr value 0xbd68609 I have done a little more investigation. My scsi chain normally contains the following (taken from a dmesg from a kernel.GENERIC from July 16) ----------------- Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 5.0-20000716-CURRENT #0: Sun Jul 16 12:24:18 GMT 2000 root@usw2.freebsd.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6(tm) 3D processor (451.02-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x58c Stepping = 12 Features=0x8021bf AMD Features=0x80000800 ... ahc0: port 0xe000-0xe0ff mem 0xe0200000-0xe0200fff irq 9 at device 14.0 on pci0 ... pass3 at ahc0 bus 0 target 5 lun 0 pass3: Fixed Scanner SCSI-2 device pass3: 3.300MB/s transfers Mounting root from ufs:/dev/ad0s2a cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed da2 at ahc0 bus 0 target 6 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) da2: 2048MB (4194304 512 byte sectors: 255H 63S/T 261C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) da4 at ahc0 bus 0 target 9 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da4: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) da3 at ahc0 bus 0 target 8 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 8683MB (17783112 512 byte sectors: 255H 63S/T 1106C) da1 at ahc0 bus 0 target 4 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) ... ---------------- Note the pass3 device, the UMAX astra 1220s V1.3 scanner I have one disk and the cdrw on the "internel" end of the SCSI chain off my 2940 UW. The other four disks are in a separate box (with cooling) on a 68 pin bus. The scanner is attached via a 68pin to 25pin "cable/adapter" from the other external 68 pin connector on the external box. If I have the scanner attached, then the two errors from above appear and the system refuses to boot. This happens whether I put the terminator on the scanner or not. If I remove the scanner from the chain, then the new kernel (after July 18) yields the error message (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. still appears, but the system continues to boot and works fine afterwords as far as I can tell. I still would like to check all my disks for correct termination conditions. But, since the system worked before, I am hopeful that it will work again in its current state, with scanner attached. If someone can give me further pointers, I would appreciate it. Many thanks. George Dinolt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message