From owner-freebsd-scsi Mon Jul 3 12:12:28 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from goliath.siemens.de (goliath.siemens.de [194.138.37.131]) by hub.freebsd.org (Postfix) with ESMTP id 745E437B902 for ; Mon, 3 Jul 2000 12:12:24 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer goliath.siemens.de) Received: from mail2.siemens.de (mail2.siemens.de [139.25.208.11]) by goliath.siemens.de (8.10.1/8.10.1) with ESMTP id e63JBwB03846 for ; Mon, 3 Jul 2000 21:11:58 +0200 (MET DST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail2.siemens.de (8.10.1/8.10.1) with ESMTP id e63JBwN08086 for ; Mon, 3 Jul 2000 21:11:58 +0200 (MET DST) Received: (from localhost) by curry.mchp.siemens.de (8.10.2/8.10.2) id e63JBwv28404 for freebsd-scsi@freebsd.org; Mon, 3 Jul 2000 21:11:58 +0200 (CEST) Date: Mon, 3 Jul 2000 21:11:57 +0200 From: Andre Albsmeier To: freebsd-scsi@freebsd.org Subject: slightly OT: Differences between SE and LVD Terminators Message-ID: <20000703211157.A67801@curry.mchp.siemens.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can s.o. please tell me if there is a difference between SE and LVD terminators? I have an internal terminator here (which can be attached to the end of an internal 68p cable) with "LVD/SE" printed on it so I assume it can be used for both types. Thanks, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 3 18:43:46 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (mg136-135.ricochet.net [204.179.136.135]) by hub.freebsd.org (Postfix) with ESMTP id 25EA037C1B6; Mon, 3 Jul 2000 18:42:21 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id SAA00380; Mon, 3 Jul 2000 18:46:35 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007040146.SAA00380@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Nat Lanza Cc: scsi@freebsd.org, hackers@freebsd.org Subject: Re: SCSI HBA device detection? In-reply-to: Your message of "23 Jun 2000 13:10:26 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 03 Jul 2000 18:46:30 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm writing a SCSI HBA driver that simulates a bus with some > ramdisk-backed disks attached to it. I've read through the HBA > tutorial in Daemon News, but I'm still unsure how to tell the system > about my pretend disk devices. I suspect part of the problem is that > I don't actually have real devices or a real IO bus. If this is meant to be an exercise in writing a CAM HBA driver, then you need to teach your disk-emulation code about the basic SCSI commands (INQUIRY, TEST UNIT READY, etc). The SCSI infrastructure will use these commands to automatically detect your drives. If you're writing a generic ramdisk, this is a really masochistic way to go about doing it. 8) -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 3 19:10:18 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hurlame.pdl.cs.cmu.edu (HURLAME.PDL.CS.CMU.EDU [128.2.189.78]) by hub.freebsd.org (Postfix) with SMTP id B4F9637BAAF; Mon, 3 Jul 2000 19:10:11 -0700 (PDT) (envelope-from magus+@hurlame.pdl.cs.cmu.edu) To: Mike Smith Cc: scsi@freebsd.org, hackers@freebsd.org Subject: Re: SCSI HBA device detection? References: <200007040146.SAA00380@mass.osd.bsdi.com> From: Nat Lanza Date: 03 Jul 2000 22:09:36 -0400 In-Reply-To: Mike Smith's message of "Mon, 03 Jul 2000 18:46:30 -0700" Message-ID: Lines: 26 User-Agent: Gnus/5.0802 (Gnus v5.8.2) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith writes: > If this is meant to be an exercise in writing a CAM HBA driver, then you > need to teach your disk-emulation code about the basic SCSI commands > (INQUIRY, TEST UNIT READY, etc). The SCSI infrastructure will use these > commands to automatically detect your drives. I already have code for handling the basic SCSI commands (I'm really porting a scsi-ramdisk driver from Linux rather than writing from scratch). The bit I'm curious about are which XPT actions I'll need to support other than XPT_PATH_INQ and XPT_SCSI_IO. > If you're writing a generic ramdisk, this is a really masochistic way to > go about doing it. 8) It's really a mix of an exercise in writing a CAM HBA driver and a first step towards a SCSI-over-IP driver. Also, a SCSI ramdisk can be handy for some of the benchmarking and tracing we do. --nat -- nat lanza --------------------- research programmer, parallel data lab, cmu scs magus@cs.cmu.edu -------------------------------- http://www.cs.cmu.edu/~magus/ there are no whole truths; all truths are half-truths -- alfred north whitehead To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 4 11:56:41 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from thelab.hub.org (nat196.249.mpoweredpc.net [142.177.196.249]) by hub.freebsd.org (Postfix) with ESMTP id EA72137BACB for ; Tue, 4 Jul 2000 11:56:32 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id PAA29212 for ; Tue, 4 Jul 2000 15:55:02 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 4 Jul 2000 15:55:02 -0300 (ADT) From: The Hermit Hacker To: freebsd-scsi@freebsd.org Subject: chio inserted tape, but gives error? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org thor# chio status picker 0: slot 0: slot 1: slot 2: slot 3: drive 0: thor# chio move slot 0 drive 0 chio: /dev/ch0: CHIOMOVE: Input/output error thor# chio status picker 0: slot 0: slot 1: slot 2: slot 3: drive 0: thor# mt -f /dev/rsa0 status Mode Density Blocksize bpi Compression Current: 0x24:DDS-2 variable 61000 DCLZ ---------available modes--------- 0: 0x24:DDS-2 variable 61000 DCLZ 1: 0x24:DDS-2 variable 61000 DCLZ 2: 0x24:DDS-2 variable 61000 DCLZ 3: 0x24:DDS-2 variable 61000 DCLZ --------------------------------- Current Driver State: at rest. --------------------------------- File Number: 0 Record Number: 0 The drive/changer come up as: sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) ch0 at ahc0 bus 0 target 4 lun 1 ch0: Removable Changer SCSI-2 device ch0: 5.000MB/s transfers (5.000MHz, offset 15) ch0: 4 slots, 1 drive, 1 picker, 0 portals And /var/log/messages show: (ch0:ahc0:0:4:1): SCB 0xd - timed out while idle, SEQADDR == 0xa (ch0:ahc0:0:4:1): Queuing a BDR SCB (ch0:ahc0:0:4:1): Bus Device Reset Message Sent (ch0:ahc0:0:4:1): no longer in timeout, status = 34b ahc0: Bus Device Reset on A:4. 1 SCBs aborted I'm trying to get things to work with Amanda2.4.2 right now, and have the 'tapetype' command running so that I can get some stats off the tape, which, so far, ignoring those errors above, appears to be working *cross fingers* I'm running 4.0-CURRENT as of about 20minutes ago (July 4th, 2000) ... Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 4 12: 0:33 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5A06E37B6E0 for ; Tue, 4 Jul 2000 12:00:27 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA04816; Tue, 4 Jul 2000 12:00:21 -0700 Date: Tue, 4 Jul 2000 12:00:22 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: The Hermit Hacker Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: chio inserted tape, but gives error? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You have to find out what command timed out. Build a CAMDEBUG kernel and use camcontrol to turn on command tracing for that device. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 4 14:49:44 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id B1D1737BB37; Tue, 4 Jul 2000 14:49:23 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-117-132.nnj.dialup.bellatlantic.net [151.198.117.132]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id RAA07445; Tue, 4 Jul 2000 17:49:17 -0400 (EDT) Message-ID: <39625C24.5D49AF08@bellatlantic.net> Date: Tue, 04 Jul 2000 17:50:28 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: Nat Lanza Cc: Mike Smith , scsi@freebsd.org, hackers@freebsd.org Subject: Re: SCSI HBA device detection? References: <200007040146.SAA00380@mass.osd.bsdi.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nat Lanza wrote: > > Mike Smith writes: > > > If this is meant to be an exercise in writing a CAM HBA driver, then you > > need to teach your disk-emulation code about the basic SCSI commands > > (INQUIRY, TEST UNIT READY, etc). The SCSI infrastructure will use these > > commands to automatically detect your drives. > > I already have code for handling the basic SCSI commands (I'm really > porting a scsi-ramdisk driver from Linux rather than writing from > scratch). The bit I'm curious about are which XPT actions I'll need to > support other than XPT_PATH_INQ and XPT_SCSI_IO. The tutorial in DaemonNews has this information, as well as information on minimal implementations of the reqired actions. Obviously the actions for SCSI negotiations don't need to be supported because these negotiations make no sense for an emulator or over IP. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 4 15:11:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E1E3437B938; Tue, 4 Jul 2000 15:11:20 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id PAA05459; Tue, 4 Jul 2000 15:11:07 -0700 Date: Tue, 4 Jul 2000 15:11:07 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Sergey Babkin Cc: Nat Lanza , Mike Smith , scsi@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: SCSI HBA device detection? In-Reply-To: <39625C24.5D49AF08@bellatlantic.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > The tutorial in DaemonNews has this information, as well as information > on minimal implementations of the reqired actions. Obviously the actions > for SCSI negotiations don't need to be supported because these > negotiations make no sense for an emulator or over IP. > Or over Fibre Channel (which the DaemonNews article completely missed) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 4 16:20: 2 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp02.teb1.iconnet.net (smtp02.teb1.iconnet.net [209.3.218.43]) by hub.freebsd.org (Postfix) with ESMTP id 0327437B7EF; Tue, 4 Jul 2000 16:19:40 -0700 (PDT) (envelope-from babkin@bellatlantic.net) Received: from bellatlantic.net (client-151-198-117-132.nnj.dialup.bellatlantic.net [151.198.117.132]) by smtp02.teb1.iconnet.net (8.9.1/8.9.1) with ESMTP id TAA09479; Tue, 4 Jul 2000 19:19:27 -0400 (EDT) Message-ID: <39627146.6110151A@bellatlantic.net> Date: Tue, 04 Jul 2000 19:20:38 -0400 From: Sergey Babkin X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.0-19990626-CURRENT i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: mjacob@feral.com Cc: Nat Lanza , Mike Smith , scsi@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: SCSI HBA device detection? References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote: > > > > > The tutorial in DaemonNews has this information, as well as information > > on minimal implementations of the reqired actions. Obviously the actions > > for SCSI negotiations don't need to be supported because these > > negotiations make no sense for an emulator or over IP. > > > > Or over Fibre Channel (which the DaemonNews article completely missed) Well, I concentrated on the CAM side of interface. The underlying hardware is one of device-dependent parts. BTW, I looked up the list of of absolutely neccessary calls for simulated SCSI: XPT_SCSI_IO XPT_RESET_BUS (at least silently return success) XPT_ABORT (at least return CAM_UA_ABORT) XPT_CALC_GEOMETRY XPT_PATH_INQ -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 5 7:20:10 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from thelab.hub.org (nat196.249.mpoweredpc.net [142.177.196.249]) by hub.freebsd.org (Postfix) with ESMTP id EE23637BE5E for ; Wed, 5 Jul 2000 07:20:04 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id LAA52229; Wed, 5 Jul 2000 11:18:27 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 5 Jul 2000 11:18:27 -0300 (ADT) From: The Hermit Hacker To: Matthew Jacob Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: chio inserted tape, but gives error? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 4 Jul 2000, Matthew Jacob wrote: > > You have to find out what command timed out. Build a CAMDEBUG kernel and use > camcontrol to turn on command tracing for that device. Okay, built the new kernel and just ran the following: thor# chio move drive 0 slot 0 thor# chio move slot 0 drive 0 chio: /dev/ch0: CHIOMOVE: Input/output error Trying to do a subsequent 'unload' fails: thor# chio status picker 0: slot 0: slot 1: slot 2: slot 3: drive 0: thor# chio move drive 0 slot 0 chio: /dev/ch0: CHIOMOVE: Input/output error thor# chio status picker 0: slot 0: slot 1: slot 2: slot 3: drive 0: thor# part of my /var/log/messages follows (camcontrol debug -T 0:4:1) ... this machine is semi-production, so I can reboot as required (its doing secondary DNS and anon-ftp ... no shell, no web) ... Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): entering cdgetccb Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): xpt_schedule Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): xpt_setup_ccb Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): xpt_action Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): ahc_action Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): ahc_done - scb 4 Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): xpt_done Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): camisr(ch0:ahc0:0:4:1): xpt_action Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): ahc_action Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): ahc_done - scb 4 Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): xpt_done Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): camisr(ch0:ahc0:0:4:1): entering chioctl Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): trying to do ioctl 0x800a6301 Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): entering cdgetccb Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): xpt_schedule Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): xpt_setup_ccb Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): xpt_action Jul 5 10:10:37 thor /kernel: (ch0:ahc0:0:4:1): ahc_action Jul 5 10:12:17 thor /kernel: (ch0:ahc0:0:4:1): SCB 0x5 - timed out while idle, SEQADDR == 0xa Jul 5 10:12:17 thor /kernel: (ch0:ahc0:0:4:1): Queuing a BDR SCB Jul 5 10:12:17 thor /kernel: (ch0:ahc0:0:4:1): Bus Device Reset Message Sent Jul 5 10:12:17 thor /kernel: (noperiph:ahc0:0:4:1): xpt_compile_path Jul 5 10:12:17 thor /kernel: (ch0:ahc0:0:4:1): ahc_done - scb 5 Jul 5 10:12:17 thor /kernel: (ch0:ahc0:0:4:1): no longer in timeout, status = 34b Jul 5 10:12:17 thor /kernel: (ch0:ahc0:0:4:1): xpt_done Jul 5 10:12:17 thor /kernel: (noperiph:ahc0:0:4:1): xpt_setup_ccb Jul 5 10:12:17 thor /kernel: (noperiph:ahc0:0:4:1): xpt_async Jul 5 10:12:17 thor /kernel: (noperiph:ahc0:0:4:1): xpt_async Jul 5 10:12:17 thor /kernel: (noperiph:ahc0:0:4:1): xpt_compile_path Jul 5 10:12:17 thor /kernel: (noperiph:ahc0:0:4:1): xpt_release_path Jul 5 10:12:17 thor /kernel: (noperiph:ahc0:0:4:1): xpt_free_path Jul 5 10:12:17 thor /kernel: (noperiph:ahc0:0:4:1): xpt_release_path Jul 5 10:12:17 thor /kernel: ahc0: Bus Device Reset on A:4. 1 SCBs aborted Jul 5 10:12:17 thor /kernel: (ch0:ahc0:0:4:1): camisr(ch0:ahc0:0:4:1): xpt_action Jul 5 10:12:17 thor /kernel: (ch0:ahc0:0:4:1): xpt_setup_ccb Jul 5 10:12:17 thor /kernel: (ch0:ahc0:0:4:1): xpt_action Jul 5 10:12:17 thor /kernel: (ch0:ahc0:0:4:1): ahc_action Jul 5 10:12:17 thor /kernel: (noperiph:ahc0:0:4:1): xpt_compile_path Jul 5 10:12:17 thor /kernel: (noperiph:ahc0:0:4:1): xpt_setup_ccb Jul 5 10:12:17 thor /kernel: (noperiph:ahc0:0:4:1): xpt_async Jul 5 10:12:17 thor /kernel: (noperiph:ahc0:0:4:1): xpt_free_path Jul 5 10:12:17 thor /kernel: (noperiph:ahc0:0:4:1): xpt_release_path Jul 5 10:12:17 thor /kernel: (ch0:ahc0:0:4:1): ahc_done - scb 5 Jul 5 10:12:17 thor /kernel: (ch0:ahc0:0:4:1): xpt_done Jul 5 10:12:18 thor /kernel: (ch0:ahc0:0:4:1): camisr(ch0:ahc0:0:4:1): xpt_setup_ccb Jul 5 10:12:18 thor /kernel: (ch0:ahc0:0:4:1): xpt_action Jul 5 10:12:18 thor /kernel: (ch0:ahc0:0:4:1): xpt_action Jul 5 10:12:18 thor /kernel: (ch0:ahc0:0:4:1): xpt_setup_ccb Jul 5 10:12:18 thor /kernel: (ch0:ahc0:0:4:1): xpt_action Jul 5 10:12:18 thor /kernel: (ch0:ahc0:0:4:1): ahc_action Jul 5 10:12:18 thor /kernel: (ch0:ahc0:0:4:1): ahc_done - scb 10 Jul 5 10:12:18 thor /kernel: (ch0:ahc0:0:4:1): xpt_done Jul 5 10:12:18 thor /kernel: (ch0:ahc0:0:4:1): camisr(ch0:ahc0:0:4:1): xpt_setup_ccb Jul 5 10:12:18 thor /kernel: (ch0:ahc0:0:4:1): xpt_action To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 5 10: 0:47 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id B362937B65E for ; Wed, 5 Jul 2000 10:00:45 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA08247; Wed, 5 Jul 2000 10:00:40 -0700 Date: Wed, 5 Jul 2000 09:59:07 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: The Hermit Hacker Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: chio inserted tape, but gives error? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Uh- try camcontrol debug -c 0:4:1 (to get what command is blowing up) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 5 10:12:23 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from thelab.hub.org (nat196.249.mpoweredpc.net [142.177.196.249]) by hub.freebsd.org (Postfix) with ESMTP id DBDAA37B621 for ; Wed, 5 Jul 2000 10:12:19 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id OAA59780; Wed, 5 Jul 2000 14:10:43 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 5 Jul 2000 14:10:43 -0300 (ADT) From: The Hermit Hacker To: Matthew Jacob Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: chio inserted tape, but gives error? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 5 Jul 2000, Matthew Jacob wrote: > > Uh- try camcontrol debug -c 0:4:1 > > (to get what command is blowing up) this help? Jul 5 13:05:27 thor /kernel: (ch0:ahc0:0:4:1): MODE SENSE(06). CDB: 1a 28 1d 0 20 0 Jul 5 13:05:27 thor /kernel: (ch0:ahc0:0:4:1): MODE SENSE(06). CDB: 1a 28 1f 0 20 0 Jul 5 13:05:27 thor /kernel: (ch0:ahc0:0:4:1): MOVE MEDIUM. CDB: a5 20 0 0 0 2 0 1 0 0 0 0 Jul 5 13:07:07 thor /kernel: (ch0:ahc0:0:4:1): SCB 0x0 - timed out while idle, SEQADDR == 0xb Jul 5 13:07:07 thor /kernel: (ch0:ahc0:0:4:1): Queuing a BDR SCB Jul 5 13:07:07 thor /kernel: (ch0:ahc0:0:4:1): Bus Device Reset Message Sent Jul 5 13:07:07 thor /kernel: (ch0:ahc0:0:4:1): no longer in timeout, status = 34b Jul 5 13:07:07 thor /kernel: ahc0: Bus Device Reset on A:4. 1 SCBs aborted Jul 5 13:07:07 thor /kernel: (ch0:ahc0:0:4:1): MOVE MEDIUM. CDB: a5 20 0 0 0 2 0 1 0 0 0 0 Jul 5 13:07:07 thor /kernel: (ch0:ahc0:0:4:1): MOVE MEDIUM. CDB: a5 20 0 0 0 2 0 1 0 0 0 0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 5 10:17:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E3F3037B79E for ; Wed, 5 Jul 2000 10:17:32 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA08321; Wed, 5 Jul 2000 10:17:30 -0700 Date: Wed, 5 Jul 2000 10:15:57 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: The Hermit Hacker Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: chio inserted tape, but gives error? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It smells like broken h/w to me then- A MOVE MEDIUM to load the drive was issued at 13:05:27 and then times out 100 seconds later. I have trouble believing that the changer forgot to get back to you for that long. Was the front panel flashing? Anything- these are Python drives, right? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 5 10:23:41 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from thelab.hub.org (nat196.249.mpoweredpc.net [142.177.196.249]) by hub.freebsd.org (Postfix) with ESMTP id A593D37C03F for ; Wed, 5 Jul 2000 10:23:38 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.3/8.9.3) with ESMTP id OAA60106; Wed, 5 Jul 2000 14:22:04 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 5 Jul 2000 14:22:04 -0300 (ADT) From: The Hermit Hacker To: Matthew Jacob Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: chio inserted tape, but gives error? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't have physical access to these machines, as they are half-a-country away ... dmesg shows it as: sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 15) if that means anything? I have no probs telling the client its h/w related and letting them deal with it ... would you suggest it was the tape drive or the changer itself? I don't even know if one can be replaced without replaing the other, but figured I'd ask before I go to the client ... thanks for your time on this ... On Wed, 5 Jul 2000, Matthew Jacob wrote: > > It smells like broken h/w to me then- > > A MOVE MEDIUM to load the drive was issued at 13:05:27 and then times out 100 > seconds later. > > I have trouble believing that the changer forgot to get back to you for that > long. > > Was the front panel flashing? Anything- these are Python drives, right? > > > Marc G. Fournier ICQ#7615664 IRC Nick: Scrappy Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 5 10:43: 3 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 370D837BB66 for ; Wed, 5 Jul 2000 10:42:51 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA08415; Wed, 5 Jul 2000 10:42:48 -0700 Date: Wed, 5 Jul 2000 10:41:15 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: The Hermit Hacker Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: chio inserted tape, but gives error? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I don't have physical access to these machines, as they are half-a-country > away ... dmesg shows it as: > > sa0 at ahc0 bus 0 target 4 lun 0 > sa0: Removable Sequential Access SCSI-2 device Yeah- a python.... > sa0: 5.000MB/s transfers (5.000MHz, offset 15) > > if that means anything? > > I have no probs telling the client its h/w related and letting them deal > with it ... would you suggest it was the tape drive or the changer > itself? I don't even know if one can be replaced without replaing the > other, but figured I'd ask before I go to the client ... Well, these drives *do* bung up substantially on occasion. It varies a lot. Some folks have had a perfect time with them. I had, up until the last year or so at NASA Ames, where the two of them I had started to get *stuck* on tapes- so much so that you had to powercycle the drive. There are a few things to note here: 1. As you probably know, the DAT standards pooched it and various levels of media are *not* interchangeable. So, if you put a DDS2 tape into a DDS capable drive, it can't read it. If you put a DDS3 tape into a DDS2 drive, etc... What *may* be happening here is that the drive is totally hung up trying to find BOT on media it can't read. I don't know for sure about this. A test for this is to have your client pop the magazine out and feed in a single tape by hand (this *can* be done, albeit it does require a bit of manual dexterity). 2. Usually, when the drive has fouled up for whatever reason, it'll flash a code on the front panel. Since you can't see the drive, ask your clients, etc... 3. Has this changer been known to work before? It may be bad. They do go bad, and while they're certainly cheap enough, well, they're cheap....:-;.... So to answer your questions above- it might be the changer- it might be the tape side of it- it might be pilot error with the wrong tapes. Hard to say. They *are* a single unit- 5.25" form factor with a four slot magazine. That's my best guess. I don't believe a 100 second timeout on a command is too short for loading a tape into a changer (at least in *this* case- maybe for one of the big Metrum changers that used a VHS tape that then would have to rewind first.......but that's a horse of a different choler indeed....) -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 5 20:44:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from elbas.partitur.se (elbas.partitur.se [193.219.246.222]) by hub.freebsd.org (Postfix) with ESMTP id 6529437B6D9 for ; Wed, 5 Jul 2000 20:44:24 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from partitur.se (localhost.partitur.se [127.0.0.1]) by elbas.partitur.se (8.9.3/8.9.3) with ESMTP id FAA38159; Thu, 6 Jul 2000 05:44:25 +0200 (CEST) (envelope-from girgen@partitur.se) Message-ID: <39640099.8230F10F@partitur.se> Date: Thu, 06 Jul 2000 05:44:25 +0200 From: Palle Girgensohn Reply-To: kudo@partitur.se, girgen@partitur.se Organization: Partitur X-Mailer: Mozilla 4.73 [en] (X11; I; FreeBSD 4.0-STABLE i386) X-Accept-Language: sv, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Cc: kudo@partitur.se Subject: ahc0 times out? system panics... Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! I have problems getting a dual motherboard with built in adaptec aic780 The board is a SuperMicro PIIIDM3, built in SCSI (aic7892) and ethernet. It failed with panics when trying to restore a dump to it. I boot from an IDE drive for the moment, to try to find the source of this problem. It seems that the scsi somehow times out. I've tried both the Ultra2 wide and the LVD connector - seems to be about the reactions. I tried with one or two disks, same result. Here's something I jotted down while it was failing at one time: (probe0:ahc0:0:1:2): SCB 0xe - timed out while idle SEQ ADDR =3D 0x9 (probe0:ahc0:0:1:2): No longer in timetout, status =3D 34b ahc0: Issued Channel A bus reset. 1 SBCs aborted ahc0:A:0: ahc_intr - referenced scb not valid during seqint 0x71 sbc(14) ahc WARNING no command for scb 14 (cmdsplit) OUTPOS =3D 0 =2E.. The above was repeating at a rather slow pace. After a reboot, I got a panic. After next reboot, the system gets up. Stressing the scsi gets the system back to instability very soon. :( =46rom one of the after-reboot panics, I registrered these few lines from a screenful panic message: Fatal trap 12: page fault =2E.. interrupt mask: ... cam =2E.. Huh? I can't make anything out of this, but there probably someone out there who can, right? Is it the motherboard giving me problems? SMP? Don=E4t think so, since I've tried without SMP with exactly the same result. = It DOES work fine with BIOS settings set to the template "failsafe" and with on ly ONE SCSI drive. With two it still still fails. They have numbers 0 and one, and the onboard scsi bios has no problem seeing both as the correct numbers... The system is from Fresh 4.0-STABLE sources (from yesterday). I'm attaching the kernel config. Here's some dmesg: real memory =3D 536739840 (524160K bytes) avail memory =3D 518340608 (506192K bytes) Programming 24 pins in IOAPIC #0 IOAPIC #0 intpin 2 -> irq 0 Programming 24 pins in IOAPIC #1 IOAPIC #1 intpin 8 -> irq 2 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170020, at 0xfec00000 io1 (APIC): apic id: 3, version: 0x00178020, at 0xf68fe000 Preloaded elf kernel "kernel" at 0xc0301000. Pentium Pro MTRR support enabled npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci4: on pcib1 pci4: at 0.0 pcib2: at device 2.0 on pci0 pci2: on pcib2 pcib3: at device 31.0 on pci2 pci3: on pcib3 pci3: (vendor=3D0x8086, dev=3D0x1161) at 0.0 ahc0: port 0xb800-0xb8ff mem 0xf68ff000-0xf68fffff irq 2 at device 4.0 on pci3 ahc0: aic7892 Wide Channel A, SCSI Id=3D7, 16/255 SCBs pcib4: at device 30.0 on pci0 pci1: on pcib4 fxp0: port 0xaf00-0xaf3f mem 0xf6600000-0xf66fffff,0xf67ff000-0xf67fffff irq 16 at device 8.0 on pci1 fxp0: Ethernet address 00:30:48:00:3b:65 isab0: at device 31.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 31.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 pci0: at 31.2 irq 19 pci0: (vendor=3D0x8086, dev=3D0x2413) at 31.3 irq 17 chip1: port 0xef00-0xef3f,0xe800-0xe8ff irq 17 at device 31.5 on pci0 fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: on isa0 sc0: VGA <16 virtual consoles, flags=3D0x200> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/8 bytes threshold lpt0: on ppbus0 lpt0: Interrupt-driven port APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via IOAPIC #0 intpin 2 SMP: AP CPU #1 Launched! ad0: 8063MB [16383/16/63] at ata0-master using UDMA33 Mounting root from ufs:/dev/ad0s2a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device = da0: 40.000MB/s transfers (20.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 8750MB (17921835 512 byte sectors: 255H 63S/T 1115C) If anyone can help me with this, I'll be very happy. Thanks! Palle Girgensohn Partitur PS. I'll be on vacation, but feel free mail any responses to my colleauge, kudo@partitur.se (I've set reply-to). DS. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 5 23:23:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144]) by hub.freebsd.org (Postfix) with ESMTP id 3F82237B62D for ; Wed, 5 Jul 2000 23:23:11 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay01.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000706062412.EIMP28214.relay01@chello.nl> for ; Thu, 6 Jul 2000 08:24:12 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id IAA02522 for freebsd-scsi@freebsd.org; Thu, 6 Jul 2000 08:23:08 +0200 (CEST) (envelope-from wkb) Date: Thu, 6 Jul 2000 08:23:08 +0200 From: Wilko Bulte To: FreeBSD SCSI hackers Subject: adaptec 2940uw error message on -stable Message-ID: <20000706082308.A2499@freebie.wbnet> Reply-To: wilko@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi I just saw: (da1:ahc0:0:1:0): SCB 0x2c - timed out in Data-in phase, SEQADDR == 0x114 (da1:ahc0:0:1:0): BDR message in message buffer (da1:ahc0:0:1:0): SCB 0x2c - timed out in Data-in phase, SEQADDR == 0x115 (da1:ahc0:0:1:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 42 SCBs aborted (da1:ahc0:0:1:0): SCB 0x1b - timed out in Data-in phase, SEQADDR == 0x114 (da1:ahc0:0:1:0): BDR message in message buffer (da1:ahc0:0:1:0): SCB 0x1b - timed out in Data-in phase, SEQADDR == 0x114 (da1:ahc0:0:1:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 44 SCBs aborted in my log files. This was while copying a couple of Gb from my IBM Ultrastar 18Gb to my newly acquired Cheetah 18LP 9Gb disk. I suspect the SCA-HD68 converter*), but I like comments on the error message. *) I know, SCA converters are not the best things to use. But I could get the Cheetah brand-new for only $60 + some surplus stuff I no longer used ;-) -- Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try" wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 6 9:59:45 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id B350637B9F2; Thu, 6 Jul 2000 09:59:37 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA23901; Thu, 6 Jul 2000 10:59:33 -0600 (MDT) (envelope-from ken) Date: Thu, 6 Jul 2000 10:59:33 -0600 From: "Kenneth D. Merry" To: wilko@FreeBSD.ORG Cc: FreeBSD SCSI hackers Subject: Re: adaptec 2940uw error message on -stable Message-ID: <20000706105933.A23871@panzer.kdm.org> References: <20000706082308.A2499@freebie.wbnet> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000706082308.A2499@freebie.wbnet>; from wkb@chello.nl on Thu, Jul 06, 2000 at 08:23:08AM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 06, 2000 at 08:23:08 +0200, Wilko Bulte wrote: > Hi > > I just saw: > > (da1:ahc0:0:1:0): SCB 0x2c - timed out in Data-in phase, SEQADDR == 0x114 > (da1:ahc0:0:1:0): BDR message in message buffer > (da1:ahc0:0:1:0): SCB 0x2c - timed out in Data-in phase, SEQADDR == 0x115 > (da1:ahc0:0:1:0): no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 42 SCBs aborted > (da1:ahc0:0:1:0): SCB 0x1b - timed out in Data-in phase, SEQADDR == 0x114 > (da1:ahc0:0:1:0): BDR message in message buffer > (da1:ahc0:0:1:0): SCB 0x1b - timed out in Data-in phase, SEQADDR == 0x114 > (da1:ahc0:0:1:0): no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 44 SCBs aborted > > in my log files. This was while copying a couple of Gb from my IBM Ultrastar > 18Gb to my newly acquired Cheetah 18LP 9Gb disk. I suspect the SCA-HD68 > converter*), but I like comments on the error message. > > *) I know, SCA converters are not the best things to use. But I could get > the Cheetah brand-new for only $60 + some surplus stuff I no longer used ;-) That's usually indicative of a cabling or termination problem. Essentially it means that the bus was stuck in data-in phase. The timeout for reads and writes for the da(4) driver is 60 seconds, so it may have been stuck in data-in phase for a while. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 7 2:47:52 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from freenix.no (atreides.freenix.no [213.188.21.6]) by hub.freebsd.org (Postfix) with ESMTP id AA80537B7AC for ; Fri, 7 Jul 2000 02:47:48 -0700 (PDT) (envelope-from shamz@freenix.no) Received: (from shamz@localhost) by freenix.no (8.9.3/8.9.3) id LAA25683 for freebsd-scsi@FreeBSD.ORG; Fri, 7 Jul 2000 11:47:43 +0200 (CEST) (envelope-from shamz) Date: Fri, 7 Jul 2000 11:47:43 +0200 From: Shaun Jurrens To: freebsd-scsi@FreeBSD.ORG Subject: Re: adaptec 2940uw error message on -stable Message-ID: <20000707114743.A25559@atreides.freenix.no> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Operating-System: FreeBSD 4.0-STABLE X-Philosophy: If you can read this, you're too close. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, Guess it's time I get back to you on how I got to the root of a very similar problem. I too was plagued by the same problem for months. Changed every imaginable thing. In the end it was a bios setting for ram that I had changed from the default setting in an interrupted bios tuning/testing session. It seems to cause very small data corruption problems: copying large .tar files succeeded only rarely, daily checks caused errors too, but not always. A very tough bug to track down. Even building world didn't seem to be affected, but cvsup was a nightmare... Suggestion: set any bios changes for your ram back to default and change only those you know work under load (cvsup or cpio/tar | cp). I don't know if it's because the ram is marginal or not. Since I reset the setting (it was just one and I had forgotten that I changed it at all) I haven't had a single error, and I even have a lvd disk with adapter. I hope I have been of some help. -- Yours truly, Shaun D. Jurrens shaun@shamz.net shamz@freenix.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 8 1: 1:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id DE03037B7F4 for ; Sat, 8 Jul 2000 01:01:13 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e6881Dp09947 for scsi@freebsd.org; Sat, 8 Jul 2000 01:01:13 -0700 (PDT) Date: Sat, 8 Jul 2000 01:01:13 -0700 From: Alfred Perlstein To: scsi@freebsd.org Subject: Invalidating pack weirdness Message-ID: <20000708010113.A25571@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Someone just tossed me an email saying they're getting the dreaded "Invalidating pack" kernel messages followed by: "Device not configured" errors from 'cp' Doing a search of the lists turns up a bunch of people having these problems, but no solution/fix posted. Does anyone know if this is most likely coming from: 1) driver problem 2) hardware misconfig 3) hardware problem thanks, -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 8 1: 3:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id A603037BC97 for ; Sat, 8 Jul 2000 01:03:12 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id BAA20601; Sat, 8 Jul 2000 01:03:10 -0700 Date: Sat, 8 Jul 2000 01:03:11 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Alfred Perlstein Cc: scsi@FreeBSD.ORG Subject: Re: Invalidating pack weirdness In-Reply-To: <20000708010113.A25571@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 1) driver problem > 2) hardware misconfig > 3) hardware problem #3 is most likely . You have to get details about the actual device for us to guess about #2's likelihood. The driver should work harder at avoiding this situation. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 8 2:44:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from dastor.albury.net.au (dastor.albury.NET.AU [203.15.244.203]) by hub.freebsd.org (Postfix) with ESMTP id 1790A37B8DA for ; Sat, 8 Jul 2000 02:44:28 -0700 (PDT) (envelope-from nicks@dastor.albury.net.au) Received: (from nicks@localhost) by dastor.albury.net.au (8.10.2/8.10.2) id e689iLm80662; Sat, 8 Jul 2000 19:44:21 +1000 (EST) Date: Sat, 8 Jul 2000 19:44:21 +1000 From: Nick Slager To: Alfred Perlstein Cc: scsi@FreeBSD.ORG Subject: Re: Invalidating pack weirdness Message-ID: <20000708194421.A80601@albury.net.au> References: <20000708010113.A25571@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000708010113.A25571@fw.wintelcom.net>; from bright@wintelcom.net on Sat, Jul 08, 2000 at 01:01:13AM -0700 X-Homer: Whoohooooooo! Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thus spake Alfred Perlstein (bright@wintelcom.net): > Does anyone know if this is most likely coming from: > > 1) driver problem > 2) hardware misconfig > 3) hardware problem > #3. For me, this appeared to be caused by weird interactions between my Adaptec controller and Seagate disks. Disabling write caching in the BIOS appeared to fix it. Obviously, this is specific to my hardware; YMMV. Nick. -- From a Sun Microsystems bug report (#4102680): "Workaround: don't pound on the mouse like a wild monkey." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 8 5:24:14 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from rose.niw.com.au (app3022-2.gw.connect.com.au [203.63.119.4]) by hub.freebsd.org (Postfix) with ESMTP id 9383037BDCF for ; Sat, 8 Jul 2000 05:24:11 -0700 (PDT) (envelope-from ian@niw.com.au) Received: by rose.niw.com.au (Postfix, from userid 1000) id B645762F35; Sat, 8 Jul 2000 21:53:57 +0930 (CST) Date: Sat, 8 Jul 2000 21:53:57 +0930 From: Ian West To: Alfred Perlstein Cc: scsi@freebsd.org Subject: Re: Invalidating pack weirdness Message-ID: <20000708215357.Z24142@rose.niw.com.au> References: <20000708010113.A25571@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000708010113.A25571@fw.wintelcom.net>; from bright@wintelcom.net on Sat, Jul 08, 2000 at 01:01:13AM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jul 08, 2000 at 01:01:13AM -0700, Alfred Perlstein wrote: > Someone just tossed me an email saying they're getting the dreaded > "Invalidating pack" kernel messages followed by: > > "Device not configured" > > errors from 'cp' > > Doing a search of the lists turns up a bunch of people having these > problems, but no solution/fix posted. > > Does anyone know if this is most likely coming from: > > 1) driver problem > 2) hardware misconfig > 3) hardware problem > > thanks, > -Alfred > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message I spoke to Seagate, and they recommend disabling write caching on their drives for FreeBSD and Novell systems as this is a known 'feature'. I have done this to my system, (which was seeing these messages) and since then it has performed perfectly (ran make -j12 world in a loop for a full week, previously it lasted less than one full make world) Hardware is an aha29260 with 2 * da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 8 10:15: 2 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from relay01.chello.nl (smtp.chello.nl [212.83.68.144]) by hub.freebsd.org (Postfix) with ESMTP id 1EE4637B513; Sat, 8 Jul 2000 10:14:58 -0700 (PDT) (envelope-from wkb@chello.nl) Received: from chello.nl ([213.46.78.184]) by relay01.chello.nl (InterMail vK.4.02.00.00 201-232-116 license 2ee4e7c625482f2f2a1950a80f6c8d58) with ESMTP id <20000708171557.KEXZ8575.relay01@chello.nl>; Sat, 8 Jul 2000 19:15:57 +0200 Received: (from wkb@localhost) by chello.nl (8.9.3/8.9.3) id TAA02213; Sat, 8 Jul 2000 19:14:51 +0200 (CEST) (envelope-from wkb) Date: Sat, 8 Jul 2000 19:14:51 +0200 From: Wilko Bulte To: "Kenneth D. Merry" Cc: wilko@FreeBSD.ORG, FreeBSD SCSI hackers Subject: Re: adaptec 2940uw error message on -stable Message-ID: <20000708191451.A2191@freebie.wbnet> Reply-To: wilko@FreeBSD.ORG References: <20000706082308.A2499@freebie.wbnet> <20000706105933.A23871@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000706105933.A23871@panzer.kdm.org>; from ken@kdm.org on Thu, Jul 06, 2000 at 10:59:33AM -0600 X-OS: FreeBSD 4.0-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Jul 06, 2000 at 10:59:33AM -0600, Kenneth D. Merry wrote: > On Thu, Jul 06, 2000 at 08:23:08 +0200, Wilko Bulte wrote: > > Hi > > > > I just saw: > > > > (da1:ahc0:0:1:0): SCB 0x2c - timed out in Data-in phase, SEQADDR == 0x114 > > (da1:ahc0:0:1:0): BDR message in message buffer > > (da1:ahc0:0:1:0): SCB 0x2c - timed out in Data-in phase, SEQADDR == 0x115 > > (da1:ahc0:0:1:0): no longer in timeout, status = 34b > > ahc0: Issued Channel A Bus Reset. 42 SCBs aborted > > (da1:ahc0:0:1:0): SCB 0x1b - timed out in Data-in phase, SEQADDR == 0x114 > > (da1:ahc0:0:1:0): BDR message in message buffer > > (da1:ahc0:0:1:0): SCB 0x1b - timed out in Data-in phase, SEQADDR == 0x114 > > (da1:ahc0:0:1:0): no longer in timeout, status = 34b > > ahc0: Issued Channel A Bus Reset. 44 SCBs aborted > > > > in my log files. This was while copying a couple of Gb from my IBM Ultrastar > > 18Gb to my newly acquired Cheetah 18LP 9Gb disk. I suspect the SCA-HD68 > > converter*), but I like comments on the error message. > > > > *) I know, SCA converters are not the best things to use. But I could get > > the Cheetah brand-new for only $60 + some surplus stuff I no longer used ;-) > > That's usually indicative of a cabling or termination problem. > > Essentially it means that the bus was stuck in data-in phase. The timeout > for reads and writes for the da(4) driver is 60 seconds, so it may have > been stuck in data-in phase for a while. It appears fixed now. This bleedin' SCA thing contributed a lot to the problem. What I did to make it usable: - Cut all unused etch traces (to the unused 50 pin header connector) - Using tweezers pull (and therefore remove) these traces from the PCB. This eliminates the very undesirable stubs on the signal lines. - *important* use heavy gauge litze (braided?) copper to make a *real* low impedance path for the signal ground. This PCB had ground routing from hell, a truly lousy job if I ever saw one.. - Saw the part off the PCB that had the 50pin connector. Use a sharp metal cutting saw. Now it works ;-) -- Wilko Bulte http://www.freebsd.org "Do, or do not. There is no try" wilko@freebsd.org http://www.nlfug.nl Yoda - The Empire Strikes Back To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 8 15:18:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-193-112-57.dsl.snfc21.pacbell.net [63.193.112.57]) by hub.freebsd.org (Postfix) with ESMTP id B911237B51A for ; Sat, 8 Jul 2000 15:18:22 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id PAA01296; Sat, 8 Jul 2000 15:26:11 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200007082226.PAA01296@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alfred Perlstein Cc: scsi@freebsd.org Subject: Re: Invalidating pack weirdness In-reply-to: Your message of "Sat, 08 Jul 2000 01:01:13 PDT." <20000708010113.A25571@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 Jul 2000 15:26:11 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If this is a new SCSI disk and an Adaptec controller - yes, it's a known problem. At this point in time, I don't think you can buy a U160 disk from anyone that will work with an Adaptec controller and our driver. Justin is at work on the problem at the moment. > Someone just tossed me an email saying they're getting the dreaded > "Invalidating pack" kernel messages followed by: > > "Device not configured" > > errors from 'cp' > > Doing a search of the lists turns up a bunch of people having these > problems, but no solution/fix posted. > > Does anyone know if this is most likely coming from: > > 1) driver problem > 2) hardware misconfig > 3) hardware problem > > thanks, > -Alfred > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 8 17:40: 6 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9A82E37BC1D for ; Sat, 8 Jul 2000 17:40:03 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA22777 for ; Sat, 8 Jul 2000 17:40:03 -0700 Date: Sat, 8 Jul 2000 17:38:16 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: scsi@freebsd.org Subject: -stable branch: timed out while idle haha again.... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is with a 3940 with nothing connected to it (albeit, on an alpha...) while booting: Timedout SCB handled by another timeout (probe310:ahc1:0:2:0): SCB 0x3a - timed out while idle, SEQADDR == 0x18e (probe310:ahc1:0:2:0): Queuing a BDR SCB (probe310:ahc1:0:2:0): no longer in timeout, status = 35b Timedout SCB handled by another timeout (probe320:ahc1:0:13:0): SCB 0x2d - timed out while idle, SEQADDR == 0x4a (probe320:ahc1:0:13:0): SCB 45: Immediate reset. Flags = 0x4040 (probe320:ahc1:0:13:0): no longer in timeout, status = 34b ahc1: Issued Channel A Bus Reset. 13 SCBs aborted Anyone know if this has been fixed lately? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message