From owner-freebsd-scsi Mon Feb 28 3:40:56 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from procsys.com (PPP-190-108.bng.vsnl.net.in [203.197.190.108]) by hub.freebsd.org (Postfix) with SMTP id 4453E37B753 for ; Mon, 28 Feb 2000 03:38:51 -0800 (PST) (envelope-from nanda@procsys.com) Received: from nanda ([192.168.1.70]) by procsys.com with SMTP; Mon, 28 Feb 2000 17:10:01 +0800 Message-ID: <38BA5F43.69C0@procsys.com> Date: Mon, 28 Feb 2000 17:13:00 +0530 From: Nanda Kumar Reply-To: nanda@procsys.com X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: IOCTL support in SCSI block driver References: <38B22C09.2B7A@procsys.com> <20000221235253.A16855@panzer.kdm.org> <38B2653A.41C5@procsys.com> <20000222102314.A20290@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I had obtained some clarifications from you regarding writing a SCSI block driver. I have a few more questions ? 1). I want the SCSI block driver to support IOCTL's passed to that. Basically this is used to communicate with the firmware and get some statistics and also use some facilities like upgrading of firmware etc. 2). Is there anyway to write the SCSI block driver bypassing the CAM layer ? We are planning to write the device driver in 3.4 FreeBSD which is the stable version now. Regards, Nandan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 28 7:58:46 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (castles529.castles.com [208.214.165.93]) by hub.freebsd.org (Postfix) with ESMTP id 36D4D37B8AA for ; Mon, 28 Feb 2000 07:58:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id HAA07891; Mon, 28 Feb 2000 07:58:23 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002281558.HAA07891@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nanda@procsys.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IOCTL support in SCSI block driver In-reply-to: Your message of "Mon, 28 Feb 2000 17:13:00 +0530." <38BA5F43.69C0@procsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 28 Feb 2000 07:58:23 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > > I had obtained some clarifications from you regarding writing a SCSI > block driver. I have a few more questions ? > > 1). I want the SCSI block driver to support IOCTL's passed to that. > Basically this is used to communicate with the firmware and get some > statistics and also use some facilities like upgrading of firmware etc. > > 2). Is there anyway to write the SCSI block driver bypassing the CAM > layer ? We are planning to write the device driver in 3.4 FreeBSD which > is the stable version now. From these two questions, it's quite clear that your device should not be using CAM for I/O. Please take a few moments to look at how the Compaq Smart Array, AMI MegaRAID and Mylex DAC960 drivers work; you'll discover that you can achieve your goal with a lot less code and effort that way. To answer 1), look at the Mylex driver (sys/dev/mlx), which has a control device (/dev/mlx) which handles per-controller ioctls as well as handling per-device ioctls on the /dev/mlxd nodes. For 2), you should _definitely_ write for 4.x and backport. Writing for 3.x leaves you with a driver with no future, wheras developing for 4.x means that you're already up to date with the current (soon to be stable) release, and you won't have to bring your driver forwards at a later date. -- \\ 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 Feb 28 21:44:13 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from procsys.com (PPP-190-85.bng.vsnl.net.in [203.197.190.85]) by hub.freebsd.org (Postfix) with SMTP id 8AAC137C314; Mon, 28 Feb 2000 21:42:34 -0800 (PST) (envelope-from nanda@procsys.com) Received: from nanda ([192.168.1.70]) by procsys.com with SMTP; Tue, 29 Feb 2000 11:09:34 +0800 Message-ID: <38BB5C4F.7A9D@procsys.com> Date: Tue, 29 Feb 2000 11:12:39 +0530 From: Nanda Kumar Reply-To: nanda@procsys.com X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: Mike Smith Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IOCTL support in SCSI block driver References: <200002281558.HAA07891@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, >Mike Smith wrote: > > > Hi, > > > > I had obtained some clarifications from you regarding writing a SCSI > > block driver. I have a few more questions ? > > > > 1). I want the SCSI block driver to support IOCTL's passed to that. > > Basically this is used to communicate with the firmware and get some > > statistics and also use some facilities like upgrading of firmware etc. > > > > 2). Is there anyway to write the SCSI block driver bypassing the CAM > > layer ? We are planning to write the device driver in 3.4 FreeBSD which > > is the stable version now. > > >From these two questions, it's quite clear that your device should not be > using CAM for I/O. Please take a few moments to look at how the Compaq > Smart Array, AMI MegaRAID and Mylex DAC960 drivers work; you'll discover > that you can achieve your goal with a lot less code and effort that way. Actaully we were planning to write the SCSI block driver for FreeBSD version 3.4 (Now we are looking into 4.x after your suggestion) and i was going through the source code of the SCSI block device drivers of DPT,Qlogic and Adaptec. And i found that all of them are interfacing with the CAM layer. So i thaught all the SCSI block device drivers should interface with the CAM layer. Is this assumption true in FreeBSD 3.4 ? If we can bypass CAM and write a SCSI block driver which results with a lot of less code, then why someone has to write a driver which uses CAM interface ? > To answer 1), look at the Mylex driver (sys/dev/mlx), which has a control > device (/dev/mlx) which handles per-controller ioctls as well as handling > per-device ioctls on the /dev/mlxd nodes. > I couldn't find these in FreeBSD 3.4 source code. > For 2), you should _definitely_ write for 4.x and backport. Writing for > 3.x leaves you with a driver with no future, wheras developing for 4.x > means that you're already up to date with the current (soon to be stable) > release, and you won't have to bring your driver forwards at a later date. > Will the drivers changes significantly from 3.4 to 4.x ? So far i was seeing only the FreeBSD 3.4 drivers. Regards, Nandan > -- > \\ 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 Feb 28 23:34:39 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from procsys.com (PPP-190-181.bng.vsnl.net.in [203.197.190.181]) by hub.freebsd.org (Postfix) with SMTP id 4DE2F37BA6C for ; Mon, 28 Feb 2000 23:34:13 -0800 (PST) (envelope-from nanda@procsys.com) Received: from nanda ([192.168.1.70]) by procsys.com with SMTP; Tue, 29 Feb 2000 13:05:32 +0800 Message-ID: <38BB731F.7E33@procsys.com> Date: Tue, 29 Feb 2000 13:08:37 +0530 From: Nanda Kumar Reply-To: nanda@procsys.com X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Some more clarifications Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I went through some more details regarding SCSI block driver and CAM interface and i have some more questions 1). Our firmware expects the SCSI CDB,path id,target id,lun number etc. from the host. But for the purpose of communicating with the firmware regarding statistics,firmware upgrade etc. the driver should support IOCTL interface. Hence i think i have to write the driver as HBA driver under CAM SCSI layer. But how do i interface with the IOCTL ? Regards, Nandan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 28 23:51:10 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 0E4DF37BA6C for ; Mon, 28 Feb 2000 23:51:06 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA20064; Tue, 29 Feb 2000 00:42:08 -0700 (MST) (envelope-from ken) Date: Tue, 29 Feb 2000 00:42:07 -0700 From: "Kenneth D. Merry" To: Nanda Kumar Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Some more clarifications Message-ID: <20000229004207.A20006@panzer.kdm.org> References: <38BB731F.7E33@procsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38BB731F.7E33@procsys.com>; from nanda@procsys.com on Tue, Feb 29, 2000 at 01:08:37PM +0530 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Feb 29, 2000 at 13:08:37 +0530, Nanda Kumar wrote: > Hi, > > I went through some more details regarding SCSI block driver and CAM > interface and i have some more questions > > 1). Our firmware expects the SCSI CDB,path id,target id,lun number etc. > from the host. But for the purpose of communicating with the firmware > regarding statistics,firmware upgrade etc. the driver should support > IOCTL interface. Hence i think i have to write the driver as HBA driver > under CAM SCSI layer. But how do i interface with the IOCTL ? Well, the DPT driver does something like that. It is a CAM HBA driver that also has its own separate ioctl routine. So you can have a separate character device interface for the HBA driver's firmware routines, statistics and so forth. The primary interface to the driver would be via the CAM XPT<->SIM interface, but you would also be able to do maintenance from the character device driver associated with your HBA driver. Anything that utilizes SCSI commands can be accomplished via the standard CAM peripheral drivers (da, cd, sa, pass, etc.). Anything that needs hardware-specific commands can use the ioctl interface in your driver. 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 Tue Feb 29 2:37:49 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from router.difi.de (router.difi.de [212.6.96.2]) by hub.freebsd.org (Postfix) with ESMTP id 3568C37BA9D for ; Tue, 29 Feb 2000 02:37:47 -0800 (PST) (envelope-from uwe.laverenz@difi.de) Received: from max.difi.de (max.difi.de [192.168.1.2]) by router.difi.de (8.9.3/8.9.3) with ESMTP id LAA42401 for ; Tue, 29 Feb 2000 11:37:45 +0100 (CET) (envelope-from uwe.laverenz@difi.de) Received: from difi.de (edv1.difi.de [192.168.1.54]) by max.difi.de (8.9.3/8.9.3) with ESMTP id LAA87649 for ; Tue, 29 Feb 2000 11:37:45 +0100 (CET) (envelope-from uwe.laverenz@difi.de) Message-ID: <38BBA179.6DE313AA@difi.de> Date: Tue, 29 Feb 2000 11:37:45 +0100 From: Uwe Laverenz Organization: DIFI Dierk Filmer GmbH X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Tandberg SLR-50 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, one of our HP DDS3 streamers died recently and I'd like to replace both our HP-drives with 2 Tandberg SLR-50 streamers. I think the Tandbergs (drives and media) are far more robust and reliable. My questions: is this the right way to go under FreeBSD? Are there any known problems with these drives? What are your experiences? thanks in advance, uwe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 29 15:55:59 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from aero.org (aero.org [130.221.16.2]) by hub.freebsd.org (Postfix) with ESMTP id 57D2C37B8F1 for ; Tue, 29 Feb 2000 15:55:57 -0800 (PST) (envelope-from scottm@aero.org) Received: by aero.org id <18320-3>; Tue, 29 Feb 2000 15:55:51 -0800 Received: from rushe.aero.org(130.221.201.83) via SMTP by aero.org, id smtpdAAAa16327; Tue Feb 29 15:49:57 2000 Received: from aero.org (rdwarrior.aero.org [130.221.202.71]) by rushe.aero.org (8.9.3/8.9.3) with ESMTP id PAA00141 for ; Tue, 29 Feb 2000 15:49:56 -0800 (PST) Message-ID: <38BC5B4B.108DEB35@aero.org> From: Scott Michel Reply-To: scottm@cs.ucla.edu Organization: UCLA Computer Chaos X-Mailer: Mozilla 4.7 [en]C-CCK-MCD {Sony} (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Sony SDT-5000 tape drive (again) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 29 Feb 2000 15:49:58 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Perhaps it's just the way I ask questions or possibly I'm not supplying the correct information. I recently purchased a SDT-5000 and attempted to use it with FreeBSD 3.4. For some reason or another, when using flexbackup, the SCSI tape driver appears to lose its concept of sesssion, and the messages about the tape being frozen appear. What would be useful information to help diagnose this problem, in addition to my kernel config, the output from 'boot -v' when using the tape? How should I go about diagnosing the problem, given I'm not a SCSI guru? Suggestions gratefully accepted, even if they include "Go jump off a tall building." -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 29 17:16:43 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ns1.networkiowa.com (ns1.networkiowa.com [209.234.64.192]) by hub.freebsd.org (Postfix) with ESMTP id 5420037BC58 for ; Tue, 29 Feb 2000 17:16:39 -0800 (PST) (envelope-from johnl@raccoon.com) Received: from raccoon.com (dsl.72.145.networkiowa.com [209.234.72.145]) by ns1.networkiowa.com (8.9.3/8.9.3) with ESMTP id TAA14458 for ; Tue, 29 Feb 2000 19:19:16 -0600 Message-ID: <38BC6F9A.CF26BAD1@raccoon.com> Date: Tue, 29 Feb 2000 19:17:14 -0600 From: John Lengeling X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: scsi@freebsd.org Subject: Cheap AMI MegaRAID 428 boards Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I found a source for cheap (versus Adaptec) AMI MegaRAID 428 boards. Are these boards any good and does the freebsd driver work well with this board? They are used at $109.00 at www.teamexcess.com. It sounds like a good deal to me... johnl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 29 17:36:10 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 5500737BD06 for ; Tue, 29 Feb 2000 17:36:07 -0800 (PST) (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 RAA21640; Tue, 29 Feb 2000 17:36:03 -0800 Date: Tue, 29 Feb 2000 17:36:03 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: scottm@cs.ucla.edu Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Sony SDT-5000 tape drive (again) In-Reply-To: <38BC5B4B.108DEB35@aero.org> 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, 29 Feb 2000, Scott Michel wrote: > Perhaps it's just the way I ask questions or possibly I'm not > supplying the correct information. > > I recently purchased a SDT-5000 and attempted to use it with > FreeBSD 3.4. For some reason or another, when using flexbackup, > the SCSI tape driver appears to lose its concept of sesssion, > and the messages about the tape being frozen appear. This means that the tape driver has lost a notion of where it is. > > What would be useful information to help diagnose this problem, > in addition to my kernel config, the output from 'boot -v' when > using the tape? How should I go about diagnosing the problem, > given I'm not a SCSI guru? How about sending me the /var/log/messages from the freeze session? > > Suggestions gratefully accepted, even if they include "Go jump > off a tall building." Hmm. Not without a parasail.... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 29 19: 6: 9 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 875E437BD44 for ; Tue, 29 Feb 2000 19:06:07 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA01721; Tue, 29 Feb 2000 19:04:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003010304.TAA01721@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Lengeling Cc: scsi@freebsd.org Subject: Re: Cheap AMI MegaRAID 428 boards In-reply-to: Your message of "Tue, 29 Feb 2000 19:17:14 CST." <38BC6F9A.CF26BAD1@raccoon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Feb 2000 19:04:04 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I found a source for cheap (versus Adaptec) AMI MegaRAID 428 boards. > Are these boards any good and does the freebsd driver work well with > this board? They are used at $109.00 at www.teamexcess.com. It sounds > like a good deal to me... I've been quite happy with the 428, actually. It's a bit short on CPU power, so don't expect miracles, but the UF80 firmware seems quite reliable, and if you load it up with memory it tools along quite nicely. Note that it only does 20MHz ("ultra") 16-bit SCSI; if you're more interested in reliability than speed it should do you OK. Also note that as yet we don't have a management interface for this controller family, so you'll be flying a _little_ blind in eg. degraded/rebuild cases. -- \\ 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 Tue Feb 29 19: 8:37 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id DF8D637BCE4 for ; Tue, 29 Feb 2000 19:08:34 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id EAA32002 for freebsd-scsi@FreeBSD.ORG; Wed, 1 Mar 2000 04:02:47 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id CAA02644 for freebsd-scsi@FreeBSD.ORG; Wed, 1 Mar 2000 02:01:08 +0100 (CET) From: Juergen Lock Date: Wed, 1 Mar 2000 02:01:08 +0100 To: freebsd-scsi@FreeBSD.ORG Subject: running a cleaning tape with chio (not!) Message-ID: <20000301020107.A1387@saturn.kn-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! Is this supposed to work? it didn't for me today, it did load it and also print on the console its a cleaning tape, but when the drive ejected it after doing its thing (normal behaviour with cleaning tapes at least on dds drives), it tried to load it again. :( This is a 6-slot hp dds2 autoloader, and 3.4-stable... Thanx + Regards, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 29 19:14:34 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 034FB37B847; Tue, 29 Feb 2000 19:14:31 -0800 (PST) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id VAA14154; Tue, 29 Feb 2000 21:14:27 -0600 (CST) Date: Tue, 29 Feb 2000 21:14:27 -0600 From: Tim Tsai To: Mike Smith Cc: John Lengeling , scsi@FreeBSD.ORG Subject: Re: Cheap AMI MegaRAID 428 boards Message-ID: <20000229211427.A14103@futuresouth.com> References: <38BC6F9A.CF26BAD1@raccoon.com> <200003010304.TAA01721@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i In-Reply-To: <200003010304.TAA01721@mass.cdrom.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Are the problems with the 466 boards resolved? Thanks, Tim On Tue, Feb 29, 2000 at 07:04:04PM -0800, Mike Smith wrote: > > I found a source for cheap (versus Adaptec) AMI MegaRAID 428 boards. > > Are these boards any good and does the freebsd driver work well with > > this board? They are used at $109.00 at www.teamexcess.com. It sounds > > like a good deal to me... > > I've been quite happy with the 428, actually. It's a bit short on CPU > power, so don't expect miracles, but the UF80 firmware seems quite > reliable, and if you load it up with memory it tools along quite nicely. > > Note that it only does 20MHz ("ultra") 16-bit SCSI; if you're more > interested in reliability than speed it should do you OK. Also note that > as yet we don't have a management interface for this controller family, > so you'll be flying a _little_ blind in eg. degraded/rebuild cases. > > -- > \\ 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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 29 19:22:52 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 366C737BD4A; Tue, 29 Feb 2000 19:22:50 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA01880; Tue, 29 Feb 2000 19:21:54 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003010321.TAA01880@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tim Tsai Cc: Mike Smith , John Lengeling , scsi@FreeBSD.ORG Subject: Re: Cheap AMI MegaRAID 428 boards In-reply-to: Your message of "Tue, 29 Feb 2000 21:14:27 CST." <20000229211427.A14103@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Feb 2000 19:21:54 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Are the problems with the 466 boards resolved? Thanks, No. I've been too busy with other stuff to even get close to working on them. 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 Tue Feb 29 19:22:54 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ns1.networkiowa.com (ns1.networkiowa.com [209.234.64.192]) by hub.freebsd.org (Postfix) with ESMTP id ABEDC37BCA9; Tue, 29 Feb 2000 19:22:49 -0800 (PST) (envelope-from johnl@raccoon.com) Received: from raccoon.com (dsl.72.145.networkiowa.com [209.234.72.145]) by ns1.networkiowa.com (8.9.3/8.9.3) with ESMTP id VAA16454; Tue, 29 Feb 2000 21:25:29 -0600 Message-ID: <38BC8D30.22971D80@raccoon.com> Date: Tue, 29 Feb 2000 21:23:28 -0600 From: John Lengeling X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: Cheap AMI MegaRAID 428 boards References: <200003010304.TAA01721@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote: > > > I found a source for cheap (versus Adaptec) AMI MegaRAID 428 boards. > > Are these boards any good and does the freebsd driver work well with > > this board? They are used at $109.00 at www.teamexcess.com. It sounds > > like a good deal to me... > > I've been quite happy with the 428, actually. It's a bit short on CPU > power, so don't expect miracles, but the UF80 firmware seems quite > reliable, and if you load it up with memory it tools along quite nicely. > > Note that it only does 20MHz ("ultra") 16-bit SCSI; if you're more > interested in reliability than speed it should do you OK. Also note that > as yet we don't have a management interface for this controller family, > so you'll be flying a _little_ blind in eg. degraded/rebuild cases. What do you mean by blind? I won't know when I'm in a degraded state, or I will have to use some DOS/Win tools to do the rebuild? johnl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 29 19:50: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id B876C37BD1F; Tue, 29 Feb 2000 19:50:03 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA02184; Tue, 29 Feb 2000 19:50:26 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003010350.TAA02184@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: John Lengeling Cc: Mike Smith , scsi@FreeBSD.ORG Subject: Re: Cheap AMI MegaRAID 428 boards In-reply-to: Your message of "Tue, 29 Feb 2000 21:23:28 CST." <38BC8D30.22971D80@raccoon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Feb 2000 19:50:26 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > Note that it only does 20MHz ("ultra") 16-bit SCSI; if you're more > > interested in reliability than speed it should do you OK. Also note that > > as yet we don't have a management interface for this controller family, > > so you'll be flying a _little_ blind in eg. degraded/rebuild cases. > > What do you mean by blind? I won't know when I'm in a degraded state, > or I will have to use some DOS/Win tools to do the rebuild? You won't know if you're in a degraded mode (unless you look at what your drives are doing, or have a SAF-TE enclosure), and if you don't have a hot spare, you'll have to use the BIOS tools to instigate a rebuild. -- \\ 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 Tue Feb 29 20:31:34 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 B7FCE37BD93 for ; Tue, 29 Feb 2000 20:31:31 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id VAA27069; Tue, 29 Feb 2000 21:31:26 -0700 (MST) (envelope-from ken) Date: Tue, 29 Feb 2000 21:31:26 -0700 From: "Kenneth D. Merry" To: Juergen Lock Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: running a cleaning tape with chio (not!) Message-ID: <20000229213126.A27011@panzer.kdm.org> References: <20000301020107.A1387@saturn.kn-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000301020107.A1387@saturn.kn-bremen.de>; from nox@jelal.kn-bremen.de on Wed, Mar 01, 2000 at 02:01:08AM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 01, 2000 at 02:01:08 +0100, Juergen Lock wrote: > Hi! > > Is this supposed to work? it didn't for me today, it did load it > and also print on the console its a cleaning tape, but when the > drive ejected it after doing its thing (normal behaviour with > cleaning tapes at least on dds drives), it tried to load it again. :( > > This is a 6-slot hp dds2 autoloader, and 3.4-stable... Did you try to do I/O to the drive while the cleaning tape was in? The only reason you would have gotten an error message that a cleaning tape was installed would be in response to a command to the tape drive. My guess is that your problem is that your autoloader is configured in autoloader mode instead of changer mode or something. The fact that your cleaning tape got inserted again is likely the autoloader's problem, not FreeBSD's problem. FreeBSD just does what you tell it to do. :) 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 Tue Feb 29 21: 2:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 59A5437BCF8 for ; Tue, 29 Feb 2000 21:02:24 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA02846 for ; Tue, 29 Feb 2000 21:02:51 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003010502.VAA02846@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: scsi@freebsd.org Subject: chio trap with not-ready changer Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Feb 2000 21:02:51 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ok, after some interesting side trips I'm happily up and talking to our new (well, new-old) SpectraLogic STL-8000. There's only one catch so far - if the unit is still initialising itself when the 'ch' driver tries to talk to it, the latter fails in a messy fashion. It's easy enough to work around this by increasing the SCSI delay, but if you have 40 tapes in the unit and it's busy reading the barcodes off them all, this can be a loooong wait. 8) Is there any interest in debugging this at the moment, or should I hang back until someone familiar with the 'ch' driver has some time to tinker? -- \\ 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 Tue Feb 29 21:12:31 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 709DA37BD27; Tue, 29 Feb 2000 21:12:28 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA27460; Tue, 29 Feb 2000 22:12:27 -0700 (MST) (envelope-from ken) Date: Tue, 29 Feb 2000 22:12:27 -0700 From: "Kenneth D. Merry" To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer Message-ID: <20000229221227.A27407@panzer.kdm.org> References: <200003010502.VAA02846@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003010502.VAA02846@mass.cdrom.com>; from msmith@FreeBSD.ORG on Tue, Feb 29, 2000 at 09:02:51PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Feb 29, 2000 at 21:02:51 -0800, Mike Smith wrote: > > Ok, after some interesting side trips I'm happily up and talking to our > new (well, new-old) SpectraLogic STL-8000. There's only one catch so far > - if the unit is still initialising itself when the 'ch' driver tries to > talk to it, the latter fails in a messy fashion. It's easy enough to > work around this by increasing the SCSI delay, but if you have 40 tapes > in the unit and it's busy reading the barcodes off them all, this can be > a loooong wait. 8) > > Is there any interest in debugging this at the moment, or should I hang > back until someone familiar with the 'ch' driver has some time to tinker? Well, I don't infinite time to debug it, but I can certainly help you look into it. My guess is that the problem is that the mode sense that gets fired off on probe is failing since the drive isn't initialized. So the question is, how does it fail? Does the command time out (you might get a "timed out ..." message from the Adaptec driver), or does it just return an error message and fail to attach? Once we figure out how it is failing, we can try to figure out a way around it. IIRC, I've heard bad things about SpectraLogic changers, so I'm not sure this is a surprise. 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 Tue Feb 29 21:37:38 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 58A4337BF7E for ; Tue, 29 Feb 2000 21:37:35 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA03162; Tue, 29 Feb 2000 21:37:29 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003010537.VAA03162@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Kenneth D. Merry" Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-reply-to: Your message of "Tue, 29 Feb 2000 22:12:27 MST." <20000229221227.A27407@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Feb 2000 21:37:29 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Is there any interest in debugging this at the moment, or should I hang > > back until someone familiar with the 'ch' driver has some time to tinker? > > Well, I don't infinite time to debug it, but I can certainly help you look > into it. Ok, thanks. Matt Jacob sounds like he's also interested, so I'm going to answer his request here as well. Here are some relevant snips from a verbose boot: Waiting 3 seconds for SCSI devices to settle (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ahc0: target 5 synchronous at 5.0MHz, offset = 0xb ahc0: target 6 synchronous at 5.0MHz, offset = 0xb sa0 at ahc0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: Serial Number 02110501 sa0: 5.000MB/s transfers (5.000MHz, offset 11) sa1 at ahc0 bus 0 target 6 lun 0 sa1: Removable Sequential Access SCSI-2 device sa1: Serial Number 02088201 sa1: 5.000MB/s transfers (5.000MHz, offset 11) pass0 at ahc0 bus 0 target 4 lun 0 pass0: Removable Changer SCSI-2 device pass0: Serial Number 3 pass0: 3.300MB/s transfers ... (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): fatal error, failed to attach to device (ch0:ahc0:0:4:0): lost device (ch0:ahc0:0:4:0): removing device entry ... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x64 fault code = supervisor write, page not present instruction pointer = 0x8:0xc011f124 stack pointer = 0x10:0xc02635dc frame pointer = 0x10:0xc02635ec code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = cam kernel: type 12 trap, code=0 Stopped at xpt_release_ccb+0x20: decl 0x20(%eax) db> tr xpt_release_ccb(c0a22800,c0a22800,c09d1400,40080400,c0738700) at xpt_release_ccb+0x20 chdone(c0a2dc80,c0a22800,c0738a40,40000400,ffffffff) at chdone+0x26e camisr(c0280e10,c02636ac,c021d4a0,40000400,c022d3d2) at camisr+0x1eb swi_cambio(40000400,c022d3d2,c022cefb,40000400,c09be600) at swi_cambio+0xd splz_swi(c0738a80,0,c00f0010,1cd0010,c7d00010) at splz_swi+0x14 Xresume10() at Xresume10+0x2b --- interrupt, eip = 0xc0226552, esp = 0xc02636f4, ebp = 0 --- default_halt() at default_halt+0x2 > My guess is that the problem is that the mode sense that gets fired off on > probe is failing since the drive isn't initialized. > > So the question is, how does it fail? Does the command time out (you might > get a "timed out ..." message from the Adaptec driver), or does it just > return an error message and fail to attach? Looks like chdone() is releasing a CCB that someone else has already thrown away. I'm not familiar enough with who-does-what in the CAM stack to be any more certain about this - the error handling there is a bit convoluted. 8) > IIRC, I've heard bad things about SpectraLogic changers, so I'm not sure > this is a surprise. I've certainly heard mixed reports; I've been reasonably happy with this unit so far in terms of it actually working once I worked out how to get it going. It loads and unloads fine, the mechanicals seem to be quite robust, and basically "it just works" with the one exception above. I'm sure that I'll have more to say about it later, but for $450.oo I'm not going to complain _too_ loudly. 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 Tue Feb 29 21:44:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id E955837BD34 for ; Tue, 29 Feb 2000 21:44:27 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id VAA03274; Tue, 29 Feb 2000 21:44:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003010544.VAA03274@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nanda@procsys.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IOCTL support in SCSI block driver In-reply-to: Your message of "Tue, 29 Feb 2000 11:12:39 +0530." <38BB5C4F.7A9D@procsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Feb 2000 21:44:25 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > > > >Mike Smith wrote: > > > > > Hi, > > > > > > I had obtained some clarifications from you regarding writing a SCSI > > > block driver. I have a few more questions ? > > > > > > 1). I want the SCSI block driver to support IOCTL's passed to that. > > > Basically this is used to communicate with the firmware and get some > > > statistics and also use some facilities like upgrading of firmware etc. > > > > > > 2). Is there anyway to write the SCSI block driver bypassing the CAM > > > layer ? We are planning to write the device driver in 3.4 FreeBSD which > > > is the stable version now. > > > > >From these two questions, it's quite clear that your device should not be > > using CAM for I/O. Please take a few moments to look at how the Compaq > > Smart Array, AMI MegaRAID and Mylex DAC960 drivers work; you'll discover > > that you can achieve your goal with a lot less code and effort that way. > > Actaully we were planning to write the SCSI block driver for FreeBSD > version 3.4 (Now we are looking into 4.x after your suggestion) and i > was going through the source code of the SCSI block device drivers of > DPT,Qlogic and Adaptec. And i found that all of them are interfacing > with the CAM layer. So i thaught all the SCSI block device drivers > should interface with the CAM layer. Is this assumption true in FreeBSD > 3.4 ? No. The key issue here, and one that you still haven't answered is: Does your RAID device take SCSI commands, or does it have a different interface? > If we can bypass CAM and write a SCSI block driver which results with a > lot of less code, then why someone has to write a driver which uses CAM > interface ? You use CAM if your device is or looks exactly like a SCSI device. You do not use CAM if your device is not a SCSI device. > > To answer 1), look at the Mylex driver (sys/dev/mlx), which has a control > > device (/dev/mlx) which handles per-controller ioctls as well as handling > > per-device ioctls on the /dev/mlxd nodes. > > > > I couldn't find these in FreeBSD 3.4 source code. It's not in 3.4; try 4.0 or the CVS web interface at http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/dev/mlx/ > > For 2), you should _definitely_ write for 4.x and backport. Writing for > > 3.x leaves you with a driver with no future, wheras developing for 4.x > > means that you're already up to date with the current (soon to be stable) > > release, and you won't have to bring your driver forwards at a later date. > > > > Will the drivers changes significantly from 3.4 to 4.x ? So far i was > seeing only the FreeBSD 3.4 drivers. Yes, your driver will have to be fairly significantly modified for 4.x. If you write for 4.x to begin with, the process of backporting to 3.x is much easier. The 4.x driver model also encourages better driver authoring technique, which is important if you intend to maintain your driver. Regards, -- \\ 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 Tue Feb 29 21:50:42 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 4487337BD27; Tue, 29 Feb 2000 21:50:37 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA27865; Tue, 29 Feb 2000 22:50:36 -0700 (MST) (envelope-from ken) Date: Tue, 29 Feb 2000 22:50:36 -0700 From: "Kenneth D. Merry" To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer Message-ID: <20000229225036.B27747@panzer.kdm.org> References: <20000229221227.A27407@panzer.kdm.org> <200003010537.VAA03162@mass.cdrom.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="r5Pyd7+fXNt84Ff3" X-Mailer: Mutt 1.0i In-Reply-To: <200003010537.VAA03162@mass.cdrom.com>; from msmith@FreeBSD.ORG on Tue, Feb 29, 2000 at 09:37:29PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii On Tue, Feb 29, 2000 at 21:37:29 -0800, Mike Smith wrote: > > > Is there any interest in debugging this at the moment, or should I hang > > > back until someone familiar with the 'ch' driver has some time to tinker? > > > > Well, I don't infinite time to debug it, but I can certainly help you look > > into it. > > Ok, thanks. Matt Jacob sounds like he's also interested, so I'm going to > answer his request here as well. Here are some relevant snips from a > verbose boot: > > Waiting 3 seconds for SCSI devices to settle > (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. > ahc0: target 5 synchronous at 5.0MHz, offset = 0xb > ahc0: target 6 synchronous at 5.0MHz, offset = 0xb > sa0 at ahc0 bus 0 target 5 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: Serial Number 02110501 > sa0: 5.000MB/s transfers (5.000MHz, offset 11) > sa1 at ahc0 bus 0 target 6 lun 0 > sa1: Removable Sequential Access SCSI-2 device > sa1: Serial Number 02088201 > sa1: 5.000MB/s transfers (5.000MHz, offset 11) > pass0 at ahc0 bus 0 target 4 lun 0 > pass0: Removable Changer SCSI-2 device > pass0: Serial Number 3 > pass0: 3.300MB/s transfers > ... > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > (ch0:ahc0:0:4:0): fatal error, failed to attach to device > (ch0:ahc0:0:4:0): lost device > (ch0:ahc0:0:4:0): removing device entry > ... > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0x64 > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc011f124 > stack pointer = 0x10:0xc02635dc > frame pointer = 0x10:0xc02635ec > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = Idle > interrupt mask = cam > kernel: type 12 trap, code=0 > Stopped at xpt_release_ccb+0x20: decl 0x20(%eax) > db> tr > xpt_release_ccb(c0a22800,c0a22800,c09d1400,40080400,c0738700) at xpt_release_ccb+0x20 > chdone(c0a2dc80,c0a22800,c0738a40,40000400,ffffffff) at chdone+0x26e > camisr(c0280e10,c02636ac,c021d4a0,40000400,c022d3d2) at camisr+0x1eb > swi_cambio(40000400,c022d3d2,c022cefb,40000400,c09be600) at swi_cambio+0xd > splz_swi(c0738a80,0,c00f0010,1cd0010,c7d00010) at splz_swi+0x14 > Xresume10() at Xresume10+0x2b > --- interrupt, eip = 0xc0226552, esp = 0xc02636f4, ebp = 0 --- > default_halt() at default_halt+0x2 Okay, I think I know why the panic is happening at least. I don't understand why you're getting the unit attention error, though, since we generally retry unit attention errors unconditionally. Try the attached patch and see if it fixes things up. Once you've got the panic fixed, we can attempt to solve the unit attention problem. The comment in the patch should explain what is wrong. This looks like an oversight -- I didn't quite fix this driver completely when I went around fixing the way we handle probe failures with drivers that require an extra command to complete on probe. (e.g. da, cd, ch) > > My guess is that the problem is that the mode sense that gets fired off on > > probe is failing since the drive isn't initialized. > > > > So the question is, how does it fail? Does the command time out (you might > > get a "timed out ..." message from the Adaptec driver), or does it just > > return an error message and fail to attach? > > Looks like chdone() is releasing a CCB that someone else has already > thrown away. I'm not familiar enough with who-does-what in the CAM stack > to be any more certain about this - the error handling there is a bit > convoluted. 8) Yeah, it is somewhat tricky. Justin has a rewrite in the works, though. > > IIRC, I've heard bad things about SpectraLogic changers, so I'm not sure > > this is a surprise. > > I've certainly heard mixed reports; I've been reasonably happy with this > unit so far in terms of it actually working once I worked out how to get > it going. It loads and unloads fine, the mechanicals seem to be quite > robust, and basically "it just works" with the one exception above. I'm > sure that I'll have more to say about it later, but for $450.oo I'm not > going to complain _too_ loudly. 8) Well, hopefully we can get it at least functional. :) Ken -- Kenneth Merry ken@kdm.org --r5Pyd7+fXNt84Ff3 Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="scsi_ch.c.patch.20000229" ==== //depot/FreeBSD-ken/src/sys/cam/scsi/scsi_ch.c#3 - /a/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_ch.c ==== *** /tmp/tmp.27814.0 Tue Feb 29 22:44:32 2000 --- /a/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_ch.c Tue Feb 29 22:44:15 2000 *************** *** 688,695 **** xpt_announce_periph(periph, announce_buf); softc->state = CH_STATE_NORMAL; free(mode_header, M_TEMP); cam_periph_unlock(periph); ! break; } case CH_CCB_WAITING: { --- 688,704 ---- xpt_announce_periph(periph, announce_buf); softc->state = CH_STATE_NORMAL; free(mode_header, M_TEMP); + /* + * Since our peripheral may be invalidated by an error + * above or an external event, we must release our CCB + * before releasing the probe lock on the peripheral. + * The peripheral will only go away once the last lock + * is removed, and we need it around for the CCB release + * operation. + */ + xpt_release_ccb(done_ccb); cam_periph_unlock(periph); ! return; } case CH_CCB_WAITING: { *************** *** 697,702 **** --- 706,713 ---- wakeup(&done_ccb->ccb_h.cbfcnp); return; } + default: + break; } xpt_release_ccb(done_ccb); } --r5Pyd7+fXNt84Ff3-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 29 22: 6:34 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id AF51737BC54; Tue, 29 Feb 2000 22:06:30 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id BAA60715; Wed, 1 Mar 2000 01:06:29 -0500 (EST) Date: Wed, 1 Mar 2000 01:06:29 -0500 (EST) From: "Matthew N. Dodd" To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-Reply-To: <200003010502.VAA02846@mass.cdrom.com> 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, 29 Feb 2000, Mike Smith wrote: > Ok, after some interesting side trips I'm happily up and talking to > our new (well, new-old) SpectraLogic STL-8000. There's only one catch > so far - if the unit is still initialising itself when the 'ch' driver > tries to talk to it, the latter fails in a messy fashion. It's easy > enough to work around this by increasing the SCSI delay, but if you > have 40 tapes in the unit and it's busy reading the barcodes off them > all, this can be a loooong wait. 8) I think this is an artifact of the changer hardware being really stupid. I've got 2 different HP robots and a StorageWorks datawheel 8mm that I have to let settle before I bring up the box they are attached to. While the robot is doing self-test, calibration and inventory its -not- doing the right thing WRT being a SCSI device. Of course the degree of brokenness varies b/t the 3 different devices... I think your observed behavior is about par. :) See if you can frob your changer into not doing a media inventory on bus reset. That helps a bit here IIRC. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 29 22:20:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id B3B0937BE01; Tue, 29 Feb 2000 22:20:27 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA03645; Tue, 29 Feb 2000 22:20:21 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003010620.WAA03645@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Matthew N. Dodd" Cc: Mike Smith , scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-reply-to: Your message of "Wed, 01 Mar 2000 01:06:29 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Feb 2000 22:20:21 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > While the robot is doing self-test, calibration and inventory its -not- > doing the right thing WRT being a SCSI device. Of course the degree of > brokenness varies b/t the 3 different devices... Well, this one _seems_ to be doing about the right thing. I'm more inclined to make faces at 'ch' myself. > See if you can frob your changer into not doing a media inventory on bus > reset. That helps a bit here IIRC. Not an option with this unit, unfortunately. It might fare better with updated firmware, but since SpectraLogic don't want to say _anything_ about non-current products... -- \\ 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 Tue Feb 29 22:21:48 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 9AC4237BE01; Tue, 29 Feb 2000 22:21:45 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA03657; Tue, 29 Feb 2000 22:21:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003010621.WAA03657@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Kenneth D. Merry" Cc: Mike Smith , scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-reply-to: Your message of "Tue, 29 Feb 2000 22:50:36 MST." <20000229225036.B27747@panzer.kdm.org> Date: Tue, 29 Feb 2000 22:21:39 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Okay, I think I know why the panic is happening at least. I don't > understand why you're getting the unit attention error, though, since we > generally retry unit attention errors unconditionally. > > Try the attached patch and see if it fixes things up. Once you've got the > panic fixed, we can attempt to solve the unit attention problem. Ok, it's not panicking anymore: pass0 at ahc0 bus 0 target 4 lun 0 pass0: Removable Changer SCSI-2 device pass0: Serial Number 3 pass0: 3.300MB/s transfers ... (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): fatal error, failed to attach to device (ch0:ahc0:0:4:0): lost device (ch0:ahc0:0:4:0): removing device entry Now what? 8) (Sorry for the lag, rebooting this box is a bit slow due to the Mylex controller's interminable firmware diagnostics.) -- \\ 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 Tue Feb 29 22:21:49 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id EDD1337BC50; Tue, 29 Feb 2000 22:21:44 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id BAA60874; Wed, 1 Mar 2000 01:21:43 -0500 (EST) Date: Wed, 1 Mar 2000 01:21:42 -0500 (EST) From: "Matthew N. Dodd" To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-Reply-To: <200003010620.WAA03645@mass.cdrom.com> 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, 29 Feb 2000, Mike Smith wrote: > Not an option with this unit, unfortunately. It might fare better with > updated firmware, but since SpectraLogic don't want to say _anything_ > about non-current products... I bitched for -2- years to get the SCSI level specs out of HP for my robot/drive. Hunker down and prepare for the long seige. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 29 22:36:21 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 D81C937BE01; Tue, 29 Feb 2000 22:36:16 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA28394; Tue, 29 Feb 2000 23:36:15 -0700 (MST) (envelope-from ken) Date: Tue, 29 Feb 2000 23:36:15 -0700 From: "Kenneth D. Merry" To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer Message-ID: <20000229233615.A28297@panzer.kdm.org> References: <20000229225036.B27747@panzer.kdm.org> <200003010621.WAA03657@mass.cdrom.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="BXVAT5kNtrzKuDFl" X-Mailer: Mutt 1.0i In-Reply-To: <200003010621.WAA03657@mass.cdrom.com>; from msmith@FreeBSD.ORG on Tue, Feb 29, 2000 at 10:21:39PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii On Tue, Feb 29, 2000 at 22:21:39 -0800, Mike Smith wrote: > > Okay, I think I know why the panic is happening at least. I don't > > understand why you're getting the unit attention error, though, since we > > generally retry unit attention errors unconditionally. > > > > Try the attached patch and see if it fixes things up. Once you've got the > > panic fixed, we can attempt to solve the unit attention problem. > > Ok, it's not panicking anymore: > > pass0 at ahc0 bus 0 target 4 lun 0 > pass0: Removable Changer SCSI-2 device > pass0: Serial Number 3 > pass0: 3.300MB/s transfers > ... > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > (ch0:ahc0:0:4:0): fatal error, failed to attach to device > (ch0:ahc0:0:4:0): lost device > (ch0:ahc0:0:4:0): removing device entry > > Now what? 8) Well, I still can't figure out how you're getting a failure from a unit attention error. I suppose the next thing to try is to bump the retry count. The attached patch is the same as before, but with the retry count set to 3 instead of 1. > (Sorry for the lag, rebooting this box is a bit slow due to the Mylex > controller's interminable firmware diagnostics.) That's okay. Ken -- Kenneth Merry ken@kdm.org --BXVAT5kNtrzKuDFl Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="scsi_ch.c.patch.20000229" ==== //depot/FreeBSD-ken/src/sys/cam/scsi/scsi_ch.c#3 - /a/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_ch.c ==== *** /tmp/tmp.28374.0 Tue Feb 29 23:34:33 2000 --- /a/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_ch.c Tue Feb 29 23:33:00 2000 *************** *** 551,557 **** * Get the element address assignment page. */ scsi_mode_sense(&start_ccb->csio, ! /* retries */ 1, /* cbfcnp */ chdone, /* tag_action */ MSG_SIMPLE_Q_TAG, /* dbd */ (softc->quirks & CH_Q_NO_DBD) ? --- 551,557 ---- * Get the element address assignment page. */ scsi_mode_sense(&start_ccb->csio, ! /* retries */ 3, /* cbfcnp */ chdone, /* tag_action */ MSG_SIMPLE_Q_TAG, /* dbd */ (softc->quirks & CH_Q_NO_DBD) ? *************** *** 688,695 **** xpt_announce_periph(periph, announce_buf); softc->state = CH_STATE_NORMAL; free(mode_header, M_TEMP); cam_periph_unlock(periph); ! break; } case CH_CCB_WAITING: { --- 688,704 ---- xpt_announce_periph(periph, announce_buf); softc->state = CH_STATE_NORMAL; free(mode_header, M_TEMP); + /* + * Since our peripheral may be invalidated by an error + * above or an external event, we must release our CCB + * before releasing the probe lock on the peripheral. + * The peripheral will only go away once the last lock + * is removed, and we need it around for the CCB release + * operation. + */ + xpt_release_ccb(done_ccb); cam_periph_unlock(periph); ! return; } case CH_CCB_WAITING: { *************** *** 697,702 **** --- 706,713 ---- wakeup(&done_ccb->ccb_h.cbfcnp); return; } + default: + break; } xpt_release_ccb(done_ccb); } --BXVAT5kNtrzKuDFl-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 29 22:40:47 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 024FD37BE78; Tue, 29 Feb 2000 22:40:45 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA03924; Tue, 29 Feb 2000 22:40:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003010640.WAA03924@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Kenneth D. Merry" Cc: Mike Smith , scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-reply-to: Your message of "Tue, 29 Feb 2000 23:36:15 MST." <20000229233615.A28297@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Feb 2000 22:40:39 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Tue, Feb 29, 2000 at 22:21:39 -0800, Mike Smith wrote: > > > Okay, I think I know why the panic is happening at least. I don't > > > understand why you're getting the unit attention error, though, since we > > > generally retry unit attention errors unconditionally. > > > > > > Try the attached patch and see if it fixes things up. Once you've got the > > > panic fixed, we can attempt to solve the unit attention problem. > > > > Ok, it's not panicking anymore: > > > > pass0 at ahc0 bus 0 target 4 lun 0 > > pass0: Removable Changer SCSI-2 device > > pass0: Serial Number 3 > > pass0: 3.300MB/s transfers > > ... > > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > > (ch0:ahc0:0:4:0): fatal error, failed to attach to device > > (ch0:ahc0:0:4:0): lost device > > (ch0:ahc0:0:4:0): removing device entry > > > > Now what? 8) > > Well, I still can't figure out how you're getting a failure from a unit > attention error. I suppose the next thing to try is to bump the retry > count. The attached patch is the same as before, but with the retry count > set to 3 instead of 1. Ah. I think I understand this. How long is the delay between retries? Is there anyway to get a "device becoming ready" status? I'd hazard a guess that you're going to get the above error repeated until the changer has finished resetting (may be several minutes). -- \\ 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 Tue Feb 29 22:48:32 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 26E5337C016; Tue, 29 Feb 2000 22:48:29 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA28549; Tue, 29 Feb 2000 23:48:28 -0700 (MST) (envelope-from ken) Date: Tue, 29 Feb 2000 23:48:28 -0700 From: "Kenneth D. Merry" To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer Message-ID: <20000229234828.A28504@panzer.kdm.org> References: <20000229233615.A28297@panzer.kdm.org> <200003010640.WAA03924@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003010640.WAA03924@mass.cdrom.com>; from msmith@FreeBSD.ORG on Tue, Feb 29, 2000 at 10:40:39PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Feb 29, 2000 at 22:40:39 -0800, Mike Smith wrote: > > On Tue, Feb 29, 2000 at 22:21:39 -0800, Mike Smith wrote: > > > > Okay, I think I know why the panic is happening at least. I don't > > > > understand why you're getting the unit attention error, though, since we > > > > generally retry unit attention errors unconditionally. > > > > > > > > Try the attached patch and see if it fixes things up. Once you've got the > > > > panic fixed, we can attempt to solve the unit attention problem. > > > > > > Ok, it's not panicking anymore: > > > > > > pass0 at ahc0 bus 0 target 4 lun 0 > > > pass0: Removable Changer SCSI-2 device > > > pass0: Serial Number 3 > > > pass0: 3.300MB/s transfers > > > ... > > > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > > > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > > > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > > > (ch0:ahc0:0:4:0): fatal error, failed to attach to device > > > (ch0:ahc0:0:4:0): lost device > > > (ch0:ahc0:0:4:0): removing device entry > > > > > > Now what? 8) > > > > Well, I still can't figure out how you're getting a failure from a unit > > attention error. I suppose the next thing to try is to bump the retry > > count. The attached patch is the same as before, but with the retry count > > set to 3 instead of 1. > > Ah. I think I understand this. How long is the delay between retries? > Is there anyway to get a "device becoming ready" status? I'd hazard a > guess that you're going to get the above error repeated until the changer > has finished resetting (may be several minutes). What's confusing me about the problem is that cherror() is called with the SF_RETRY_UA flag. That's supposed to return ERESTART on any errors with a unit attention sense key, regardless of the retry count. So it should keep retrying unit attention errors indefinitely. I say indefinitely, but unit attenion conditions should generally be cleared once they're returned once. But that's evidently not happening in your case, and I don't know why. Anyway, to answer your questions: - there is no delay between retries in this case - there are "device becoming ready" status return values, and we do check for that. 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 Tue Feb 29 22:55:51 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 9B61837C054; Tue, 29 Feb 2000 22:55:48 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id WAA04061; Tue, 29 Feb 2000 22:55:43 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003010655.WAA04061@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Kenneth D. Merry" Cc: Mike Smith , scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-reply-to: Your message of "Tue, 29 Feb 2000 23:36:15 MST." <20000229233615.A28297@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Feb 2000 22:55:43 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > > (ch0:ahc0:0:4:0): fatal error, failed to attach to device > > (ch0:ahc0:0:4:0): lost device > > (ch0:ahc0:0:4:0): removing device entry > > > > Now what? 8) > > Well, I still can't figure out how you're getting a failure from a unit > attention error. I suppose the next thing to try is to bump the retry > count. The attached patch is the same as before, but with the retry count > set to 3 instead of 1. Ok. Just for kicks I tried 100 rather than 3, based on the assumption in my previous reply. Now it takes a _lot_ longer to give up; well past the point where the library becomes ready. Unfortunately, it's still failing: (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): fatal error, failed to attach to device (ch0:ahc0:0:4:0): lost device (ch0:ahc0:0:4:0): removing device entry I don't know whether it's necessary to clear this condition somehow... -- \\ 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 Tue Feb 29 23: 8:14 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 D447837BC50; Tue, 29 Feb 2000 23:08:09 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA28775; Wed, 1 Mar 2000 00:08:08 -0700 (MST) (envelope-from ken) Date: Wed, 1 Mar 2000 00:08:08 -0700 From: "Kenneth D. Merry" To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer Message-ID: <20000301000808.A28657@panzer.kdm.org> References: <20000229233615.A28297@panzer.kdm.org> <200003010655.WAA04061@mass.cdrom.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="KsGdsel6WgEHnImy" X-Mailer: Mutt 1.0i In-Reply-To: <200003010655.WAA04061@mass.cdrom.com>; from msmith@FreeBSD.ORG on Tue, Feb 29, 2000 at 10:55:43PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii On Tue, Feb 29, 2000 at 22:55:43 -0800, Mike Smith wrote: > > > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > > > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > > > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > > > (ch0:ahc0:0:4:0): fatal error, failed to attach to device > > > (ch0:ahc0:0:4:0): lost device > > > (ch0:ahc0:0:4:0): removing device entry > > > > > > Now what? 8) > > > > Well, I still can't figure out how you're getting a failure from a unit > > attention error. I suppose the next thing to try is to bump the retry > > count. The attached patch is the same as before, but with the retry count > > set to 3 instead of 1. > > Ok. Just for kicks I tried 100 rather than 3, based on the assumption in > my previous reply. Now it takes a _lot_ longer to give up; well past the > point where the library becomes ready. > > Unfortunately, it's still failing: > > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > (ch0:ahc0:0:4:0): fatal error, failed to attach to device > (ch0:ahc0:0:4:0): lost device > (ch0:ahc0:0:4:0): removing device entry > > I don't know whether it's necessary to clear this condition somehow... Well, normally, issuing any command other than an inquiry will clear a unit attention condition. What happens if you do something like: camcontrol tur passN -v Where passN is the passthrough device that attached to it? If it returns errors, try it a few times in a row. Also, it might be interesting to see what CAM status is getting returned each time. The attached patch is the same as the previous patch, except that it will print out the CAM status, SCSI status and retry count for each failed command during the probe phase. Ken -- Kenneth Merry ken@kdm.org --KsGdsel6WgEHnImy Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="scsi_ch.c.patch.20000229" ==== //depot/FreeBSD-ken/src/sys/cam/scsi/scsi_ch.c#3 - /a/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_ch.c ==== *** /tmp/tmp.28764.0 Wed Mar 1 00:07:36 2000 --- /a/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_ch.c Wed Mar 1 00:07:22 2000 *************** *** 551,557 **** * Get the element address assignment page. */ scsi_mode_sense(&start_ccb->csio, ! /* retries */ 1, /* cbfcnp */ chdone, /* tag_action */ MSG_SIMPLE_Q_TAG, /* dbd */ (softc->quirks & CH_Q_NO_DBD) ? --- 551,557 ---- * Get the element address assignment page. */ scsi_mode_sense(&start_ccb->csio, ! /* retries */ 3, /* cbfcnp */ chdone, /* tag_action */ MSG_SIMPLE_Q_TAG, /* dbd */ (softc->quirks & CH_Q_NO_DBD) ? *************** *** 621,626 **** --- 621,635 ---- } else { int error; + xpt_print_path(periph->path); + printf("CAM status = %#x, retry count = %d\n", + done_ccb->ccb_h.status, + done_ccb->ccb_h.retry_count); + + if ((done_ccb->ccb_h.status & CAM_STATUS_MASK) == + CAM_SCSI_STATUS_ERROR) + scsi_sense_print(&done_ccb->csio); + error = cherror(done_ccb, 0, SF_RETRY_UA | SF_NO_PRINT | SF_RETRY_SELTO); /* *************** *** 688,695 **** xpt_announce_periph(periph, announce_buf); softc->state = CH_STATE_NORMAL; free(mode_header, M_TEMP); cam_periph_unlock(periph); ! break; } case CH_CCB_WAITING: { --- 697,713 ---- xpt_announce_periph(periph, announce_buf); softc->state = CH_STATE_NORMAL; free(mode_header, M_TEMP); + /* + * Since our peripheral may be invalidated by an error + * above or an external event, we must release our CCB + * before releasing the probe lock on the peripheral. + * The peripheral will only go away once the last lock + * is removed, and we need it around for the CCB release + * operation. + */ + xpt_release_ccb(done_ccb); cam_periph_unlock(periph); ! return; } case CH_CCB_WAITING: { *************** *** 697,702 **** --- 715,722 ---- wakeup(&done_ccb->ccb_h.cbfcnp); return; } + default: + break; } xpt_release_ccb(done_ccb); } --KsGdsel6WgEHnImy-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 29 23:21:48 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id B5D2837C119 for ; Tue, 29 Feb 2000 23:21:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA04319; Tue, 29 Feb 2000 23:21:33 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003010721.XAA04319@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Kenneth D. Merry" Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-reply-to: Your message of "Wed, 01 Mar 2000 00:08:08 MST." <20000301000808.A28657@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 29 Feb 2000 23:21:33 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Unfortunately, it's still failing: > > > > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > > (ch0:ahc0:0:4:0): fatal error, failed to attach to device > > (ch0:ahc0:0:4:0): lost device > > (ch0:ahc0:0:4:0): removing device entry > > > > I don't know whether it's necessary to clear this condition somehow... > > Well, normally, issuing any command other than an inquiry will clear a > unit attention condition. > > What happens if you do something like: > > camcontrol tur passN -v > > Where passN is the passthrough device that attached to it? If it returns > errors, try it a few times in a row. > > Also, it might be interesting to see what CAM status is getting returned > each time. The attached patch is the same as the previous patch, except > that it will print out the CAM status, SCSI status and retry count for > each failed command during the probe phase. (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 0 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 0 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): fatal error, failed to attach to device (ch0:ahc0:0:4:0): lost device (ch0:ahc0:0:4:0): removing device entry ... fnord# camcontrol tur pass0 -v Unit is not ready (pass0:ahc0:0:4:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (pass0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (pass0:ahc0:0:4:0): Power on, reset, or bus device reset occurred field replaceable unit: 4 fnord# camcontrol tur pass0 -v Unit is ready Looks like it might want a TEST UNIT READY to clear the condition? -- \\ 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 Tue Feb 29 23:32:29 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.kpnqwest.ch (mail.eunet.ch [146.228.10.7]) by hub.freebsd.org (Postfix) with ESMTP id 4E79F37BE2F for ; Tue, 29 Feb 2000 23:32:21 -0800 (PST) (envelope-from mw@kpnqwest.ch) Received: (from mw@localhost) by mail.kpnqwest.ch (8.9.3/1.34) id HAA08757; Wed, 1 Mar 2000 07:30:58 GMT env-from (mw@kpnqwest.ch) From: mw@kpnqwest.ch Message-Id: <200003010730.HAA08757@mail.kpnqwest.ch> Subject: Re: Cheap AMI MegaRAID 428 boards In-Reply-To: <20000229211427.A14103@futuresouth.com> from Tim Tsai at "Feb 29, 2000 9:14:27 pm" To: tim@futuresouth.com (Tim Tsai) Date: Wed, 1 Mar 2000 08:30:57 +0100 (CET) Cc: scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Are the problems with the 466 boards resolved? Thanks, They aren't... mine still corrupts data sent to disk, and occasionally reboots the machine :( Markus -- KPNQwest Switzerland Ltd P.O. Box 9470, Zweierstrasse 35, CH-8036 Zuerich Tel: +41-1-298-6030, Fax: +41-1-291-4642 Markus Wild, Manager Engineering, e-mail: markus.wild@kpnqwest.ch To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 29 23:38:34 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 926F037BE2D; Tue, 29 Feb 2000 23:38:29 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA29063; Wed, 1 Mar 2000 00:38:28 -0700 (MST) (envelope-from ken) Date: Wed, 1 Mar 2000 00:38:28 -0700 From: "Kenneth D. Merry" To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer Message-ID: <20000301003828.A28889@panzer.kdm.org> References: <20000301000808.A28657@panzer.kdm.org> <200003010721.XAA04319@mass.cdrom.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="Dxnq1zWXvFF0Q93v" X-Mailer: Mutt 1.0i In-Reply-To: <200003010721.XAA04319@mass.cdrom.com>; from msmith@FreeBSD.ORG on Tue, Feb 29, 2000 at 11:21:33PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii On Tue, Feb 29, 2000 at 23:21:33 -0800, Mike Smith wrote: > > > Unfortunately, it's still failing: > > > > > > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > > > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > > > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > > > (ch0:ahc0:0:4:0): fatal error, failed to attach to device > > > (ch0:ahc0:0:4:0): lost device > > > (ch0:ahc0:0:4:0): removing device entry > > > > > > I don't know whether it's necessary to clear this condition somehow... > > > > Well, normally, issuing any command other than an inquiry will clear a > > unit attention condition. > > > > What happens if you do something like: > > > > camcontrol tur passN -v > > > > Where passN is the passthrough device that attached to it? If it returns > > errors, try it a few times in a row. > > > > Also, it might be interesting to see what CAM status is getting returned > > each time. The attached patch is the same as the previous patch, except > > that it will print out the CAM status, SCSI status and retry count for > > each failed command during the probe phase. > > (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 0 > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 0 > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > (ch0:ahc0:0:4:0): fatal error, failed to attach to device > (ch0:ahc0:0:4:0): lost device > (ch0:ahc0:0:4:0): removing device entry > ... > fnord# camcontrol tur pass0 -v > Unit is not ready > (pass0:ahc0:0:4:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (pass0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > (pass0:ahc0:0:4:0): Power on, reset, or bus device reset occurred field replaceable unit: 4 > fnord# camcontrol tur pass0 -v > Unit is ready > > Looks like it might want a TEST UNIT READY to clear the condition? Not necessarily a test unit ready, but perhaps something other than mode sense or inquiry. *sigh* I still don't understand how the retry count is getting decremented. Anyway, try the attached patch to scsi_all.c. It should send one or two test unit ready commands to the drive in response to a unit attention. Hopefully that'll clear the condition, and the mode sense can then succeed. Just for kicks, try it with the default retry count for the mode sense (in chstart()) of 1. [ FWIW, this also includes a patch for Joerg Wunsch that I forgot to commit a long time ago. ] I haven't tried compiling the patch, hopefully the syntax is correct. Ken -- Kenneth Merry ken@kdm.org --Dxnq1zWXvFF0Q93v Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="scsi_all.c.spectra.20000301" ==== //depot/FreeBSD-ken/src/sys/cam/scsi/scsi_all.c#4 - /a/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_all.c ==== *** /tmp/tmp.29026.0 Wed Mar 1 00:35:16 2000 --- /a/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_all.c Wed Mar 1 00:33:35 2000 *************** *** 725,730 **** --- 725,748 ---- * WARNING: You must update the num_ascs field below for this quirk table * entry if you add more entries. */ + static struct asc_table_entry spectra_8000_entries[] = { + {SST(0x29, 0x00, SS_TUR|SSQ_DECREMENT_COUNT|ENXIO, + "Power on, reset, or bus device reset occurred")} + } + + /* + * WARNING: You must update the num_ascs field below for this quirk table + * entry if you add more entries. + */ + static struct asc_table_entry sony_mo_entries[] = { + {SST(0x04, 0x00, SS_START|SSQ_DECREMENT_COUNT|ENXIO, + "Logical unit not ready, cause not reportable")} + }; + + /* + * WARNING: You must update the num_ascs field below for this quirk table + * entry if you add more entries. + */ static struct asc_table_entry quantum_fireball_entries[] = { {SST(0x04, 0x0b, SS_START|SSQ_DECREMENT_COUNT|ENXIO, "Logical unit not ready, initializing cmd. required")} *************** *** 741,746 **** --- 759,786 ---- {T_DIRECT, SIP_MEDIA_FIXED, "QUANTUM", "FIREBALL S*", "*"}, 1, /* number of vendor-specific sense codes for this entry */ quantum_fireball_entries + }, + { + /* + * This Sony MO drive likes to return 0x04, 0x00 when it + * isn't spun up. + * Reported by: Joerg Wunsch + */ + {T_DIRECT, SIP_MEDIA_REMOVABLE, "SONY", "SMO-C501-09*", "*"}, + 1, /* number of vendor-specific sense codes for this entry */ + sony_mo_entries + }, + { + /* + * The apparantly doesn't clear + * unit attention conditions when a mode sense is issued. + * So we have to issue test unit readies until the unit + * attention condition has been cleared. + * Reported by: Mike Smith + */ + {T_CHANGER, SIP_MEDIA_REMOVABLE, "SPECTRA", "STL-8000", "*"}, + 1, /* number of vendor-specific sense codes for this entry */ + spectra_8000_entries } }; --Dxnq1zWXvFF0Q93v-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 29 23:51:52 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from procsys.com (PPP-190-110.bng.vsnl.net.in [203.197.190.110]) by hub.freebsd.org (Postfix) with SMTP id 8076A37BE2D; Tue, 29 Feb 2000 23:51:25 -0800 (PST) (envelope-from nanda@procsys.com) Received: from nanda ([192.168.1.70]) by procsys.com with SMTP; Wed, 01 Mar 2000 13:24:12 +0800 Message-ID: <38BCCD40.355A@procsys.com> Date: Wed, 01 Mar 2000 13:26:48 +0530 From: Nanda Kumar Reply-To: nanda@procsys.com X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: Mike Smith Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IOCTL support in SCSI block driver References: <200003010544.VAA03274@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, >Mike Smith wrote: > > > Hi, > > > > > > >Mike Smith wrote: > > > > > > > Hi, > > > > > > > > I had obtained some clarifications from you regarding writing a SCSI > > > > block driver. I have a few more questions ? > > > > > > > > 1). I want the SCSI block driver to support IOCTL's passed to that. > > > > Basically this is used to communicate with the firmware and get some > > > > statistics and also use some facilities like upgrading of firmware etc. > > > > > > > > 2). Is there anyway to write the SCSI block driver bypassing the CAM > > > > layer ? We are planning to write the device driver in 3.4 FreeBSD which > > > > is the stable version now. > > > > > > >From these two questions, it's quite clear that your device should not be > > > using CAM for I/O. Please take a few moments to look at how the Compaq > > > Smart Array, AMI MegaRAID and Mylex DAC960 drivers work; you'll discover > > > that you can achieve your goal with a lot less code and effort that way. > > > > Actaully we were planning to write the SCSI block driver for FreeBSD > > version 3.4 (Now we are looking into 4.x after your suggestion) and i > > was going through the source code of the SCSI block device drivers of > > DPT,Qlogic and Adaptec. And i found that all of them are interfacing > > with the CAM layer. So i thaught all the SCSI block device drivers > > should interface with the CAM layer. Is this assumption true in FreeBSD > > 3.4 ? > > No. The key issue here, and one that you still haven't answered is: Does > your RAID device take SCSI commands, or does it have a different > interface? > Our RAID device takes SCSI commands. Typically the parameters passed to the firmware includes SCSI CDB,path id,target id,LUN number,data direction flag,SCSI tag queing attribute,data buffer pointers etc. Status returned consists of SCSI status and sense information. But my driver should also handle the IOCTL support for proprietary communication which will be used by a JAVA based Array Manager program for the purpose of getting statistics and configuring the card. Can i pass IOCTLs directly to the HAB SCSI CAM driver ? I want to avoid writing another character driver just for the sake of IOCTL handling we could do this in Linux and Windows NT. > > If we can bypass CAM and write a SCSI block driver which results with a > > lot of less code, then why someone has to write a driver which uses CAM > > interface ? > > You use CAM if your device is or looks exactly like a SCSI device. You do > not use CAM if your device is not a SCSI device. > > > > To answer 1), look at the Mylex driver (sys/dev/mlx), which has a control > > > device (/dev/mlx) which handles per-controller ioctls as well as handling > > > per-device ioctls on the /dev/mlxd nodes. > > > > > > > I couldn't find these in FreeBSD 3.4 source code. > > It's not in 3.4; try 4.0 or the CVS web interface at > http://www.FreeBSD.org/cgi/cvsweb.cgi/src/sys/dev/mlx/ > > > > For 2), you should _definitely_ write for 4.x and backport. Writing for > > > 3.x leaves you with a driver with no future, wheras developing for 4.x > > > means that you're already up to date with the current (soon to be stable) > > > release, and you won't have to bring your driver forwards at a later date. > > > > > > > Will the drivers changes significantly from 3.4 to 4.x ? So far i was > > seeing only the FreeBSD 3.4 drivers. > > Yes, your driver will have to be fairly significantly modified for 4.x. > If you write for 4.x to begin with, the process of backporting to 3.x is > much easier. The 4.x driver model also encourages better driver > authoring technique, which is important if you intend to maintain your > driver. > Regards, Nandan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 0: 3:14 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 6CF9A37BE00; Wed, 1 Mar 2000 00:03:10 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA04730; Wed, 1 Mar 2000 00:03:04 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003010803.AAA04730@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Kenneth D. Merry" Cc: Mike Smith , scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-reply-to: Your message of "Wed, 01 Mar 2000 00:38:28 MST." <20000301003828.A28889@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Mar 2000 00:03:04 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Looks like it might want a TEST UNIT READY to clear the condition? > > Not necessarily a test unit ready, but perhaps something other than mode > sense or inquiry. > > *sigh* > > I still don't understand how the retry count is getting decremented. I think there's something basic wrong there, yes. Whatever it is also seems to be inhibiting the TEST UNIT READY that your quirk entry is trying to send. > Anyway, try the attached patch to scsi_all.c. It should send one or two > test unit ready commands to the drive in response to a unit attention. > > Hopefully that'll clear the condition, and the mode sense can then succeed. > > Just for kicks, try it with the default retry count for the mode sense (in > chstart()) of 1. I tried with both 1 and also 100. With the latter, I get a lot of repeats, ending in: (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 1 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 0 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 0 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): fatal error, failed to attach to device (ch0:ahc0:0:4:0): lost device (ch0:ahc0:0:4:0): removing device entry (Note two there with a retry count of 0. Weird.) With 1, there's obviously a lot less, but the same result. Anyway, while this was spewing out, I logged in and issued two 'camcontrol tur 0:4 -v'. Neither ran until the device was removed, wherupon we get the same results - the first one fails, the second one succeeds. > I haven't tried compiling the patch, hopefully the syntax is correct. You missed a semicolon. -- \\ 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 Wed Mar 1 0: 5:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 5B06137BE24 for ; Wed, 1 Mar 2000 00:05:23 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA04782; Wed, 1 Mar 2000 00:05:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003010805.AAA04782@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Kenneth D. Merry" Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-reply-to: Your message of "Wed, 01 Mar 2000 00:03:04 PST." <200003010803.AAA04730@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Mar 2000 00:05:18 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > Looks like it might want a TEST UNIT READY to clear the condition? > > > > Not necessarily a test unit ready, but perhaps something other than mode > > sense or inquiry. > > > > *sigh* > > > > I still don't understand how the retry count is getting decremented. > > I think there's something basic wrong there, yes. Whatever it is also > seems to be inhibiting the TEST UNIT READY that your quirk entry is > trying to send. ... the rationale here being that if it was being sent and failing, we'd see an error from it, right? -- \\ 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 Wed Mar 1 0: 8:21 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 2B41237BE24 for ; Wed, 1 Mar 2000 00:08:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA04798; Wed, 1 Mar 2000 00:07:40 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003010807.AAA04798@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nanda@procsys.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IOCTL support in SCSI block driver In-reply-to: Your message of "Wed, 01 Mar 2000 13:26:48 +0530." <38BCCD40.355A@procsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Mar 2000 00:07:40 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > No. The key issue here, and one that you still haven't answered is: Does > > your RAID device take SCSI commands, or does it have a different > > interface? > > Our RAID device takes SCSI commands. Typically the parameters passed to > the firmware includes SCSI CDB,path id,target id,LUN number,data > direction flag,SCSI tag queing attribute,data buffer pointers etc. > Status returned consists of SCSI status and sense information. Ok. In that case, you're right on the target for using CAM. > But my driver should also handle the IOCTL support for proprietary > communication which will be used by a JAVA based Array Manager program > for the purpose of getting statistics and configuring the card. Can i > pass IOCTLs directly to the HAB SCSI CAM driver ? No. You will want to create a per-adapter device instance that takes the bus/target/lun information and passes it along with the ioctl data to the firmware. You can see an instance of this in the Mylex driver I referenced previously. > I want to avoid writing another character driver just for the sake of > IOCTL handling we could do this in Linux and Windows NT. You don't need another entire driver; just a few extra lines to instantiate a control interface node for the adapter. -- \\ 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 Wed Mar 1 0:25:34 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 F2AC237BE3E; Wed, 1 Mar 2000 00:25:30 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id BAA29410; Wed, 1 Mar 2000 01:25:28 -0700 (MST) (envelope-from ken) Date: Wed, 1 Mar 2000 01:25:28 -0700 From: "Kenneth D. Merry" To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer Message-ID: <20000301012528.A29274@panzer.kdm.org> References: <20000301003828.A28889@panzer.kdm.org> <200003010803.AAA04730@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003010803.AAA04730@mass.cdrom.com>; from msmith@FreeBSD.ORG on Wed, Mar 01, 2000 at 12:03:04AM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 01, 2000 at 00:03:04 -0800, Mike Smith wrote: > > > Looks like it might want a TEST UNIT READY to clear the condition? > > > > Not necessarily a test unit ready, but perhaps something other than mode > > sense or inquiry. > > > > *sigh* > > > > I still don't understand how the retry count is getting decremented. > > I think there's something basic wrong there, yes. Whatever it is also > seems to be inhibiting the TEST UNIT READY that your quirk entry is > trying to send. Maybe, mabye not. It could be that the quirk entry isn't matching for some reason. > > Anyway, try the attached patch to scsi_all.c. It should send one or two > > test unit ready commands to the drive in response to a unit attention. > > > > Hopefully that'll clear the condition, and the mode sense can then succeed. > > > > Just for kicks, try it with the default retry count for the mode sense (in > > chstart()) of 1. > > I tried with both 1 and also 100. With the latter, I get a lot of > repeats, ending in: > > (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 1 > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 0 > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 0 > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > (ch0:ahc0:0:4:0): fatal error, failed to attach to device > (ch0:ahc0:0:4:0): lost device > (ch0:ahc0:0:4:0): removing device entry > > (Note two there with a retry count of 0. Weird.) Note that one has the SMS_DBD flag set in the second byte of the CDB, the other has it cleared. > With 1, there's obviously a lot less, but the same result. Can you include a little more of the retries? The disable block descriptors flag is getting cleared mighty late if the above is the tail end of the output from the 100 retries. > Anyway, while this was spewing out, I logged in and issued two > 'camcontrol tur 0:4 -v'. Neither ran until the device was removed, > wherupon we get the same results - the first one fails, the second one > succeeds. Hmm. Not surprising I suppose. > > I haven't tried compiling the patch, hopefully the syntax is correct. > > You missed a semicolon. Oops, sorry. In any case, try putting a printf inside the SS_TUR case in cam_periph_error() in cam_periph.c, to see whether the quirk entry is getting matched correctly and therefore whether the test unit ready is getting issued. I won't be able to debug this more until tomorrow -- time to sleep. :) 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 Wed Mar 1 0:28:38 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 8BCE637C168; Wed, 1 Mar 2000 00:28:34 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id BAA29432; Wed, 1 Mar 2000 01:28:30 -0700 (MST) (envelope-from ken) Date: Wed, 1 Mar 2000 01:28:30 -0700 From: "Kenneth D. Merry" To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer Message-ID: <20000301012830.B29274@panzer.kdm.org> References: <200003010803.AAA04730@mass.cdrom.com> <200003010805.AAA04782@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003010805.AAA04782@mass.cdrom.com>; from msmith@FreeBSD.ORG on Wed, Mar 01, 2000 at 12:05:18AM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 01, 2000 at 00:05:18 -0800, Mike Smith wrote: > > > > Looks like it might want a TEST UNIT READY to clear the condition? > > > > > > Not necessarily a test unit ready, but perhaps something other than mode > > > sense or inquiry. > > > > > > *sigh* > > > > > > I still don't understand how the retry count is getting decremented. > > > > I think there's something basic wrong there, yes. Whatever it is also > > seems to be inhibiting the TEST UNIT READY that your quirk entry is > > trying to send. > > ... the rationale here being that if it was being sent and failing, we'd > see an error from it, right? Not necessarily. I don't think we print out sense information or errors if commands issued by the error recovery code result in errors. (That's often the point.) It's the original command that'll get reported as having failed. (And it really is a failure of the original command -- once we complete the error recovery action, the original command is reissued to see if it will complete successfully.) 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 Wed Mar 1 0:41:40 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 42B0137BE2D for ; Wed, 1 Mar 2000 00:41:38 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id AAA05125; Wed, 1 Mar 2000 00:41:33 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003010841.AAA05125@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Kenneth D. Merry" Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-reply-to: Your message of "Wed, 01 Mar 2000 01:25:28 MST." <20000301012528.A29274@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Mar 2000 00:41:33 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I tried with both 1 and also 100. With the latter, I get a lot of > > repeats, ending in: > > > > (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 1 > > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 > > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > > (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 0 > > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 > > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > > (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 0 > > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > > (ch0:ahc0:0:4:0): fatal error, failed to attach to device > > (ch0:ahc0:0:4:0): lost device > > (ch0:ahc0:0:4:0): removing device entry > > > > (Note two there with a retry count of 0. Weird.) > > Note that one has the SMS_DBD flag set in the second byte of the CDB, > the other has it cleared. I'm not sure what the significance of that is, actually. > > With 1, there's obviously a lot less, but the same result. > > Can you include a little more of the retries? The disable block > descriptors flag is getting cleared mighty late if the above is the tail > end of the output from the 100 retries. (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 13 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 12 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 11 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 10 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 9 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 8 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 7 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 6 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 5 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 4 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 3 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 2 (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred As far as I can see, they all look the same as the count=1 case. > In any case, try putting a printf inside the SS_TUR case in > cam_periph_error() in cam_periph.c, to see whether the quirk entry is > getting matched correctly and therefore whether the test unit ready is > getting issued. Hmm. Trying: if (((err_action & SS_MASK) == SS_TUR) && save_ccb != NULL && ccb->ccb_h.retry_count > 0) { printf("cam_periph_error: sending TUR\n"); I never see the above message. > I won't be able to debug this more until tomorrow -- time to sleep. :) Sounds like a good idea. 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 Wed Mar 1 5: 2:30 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from pawn.primelocation.net (pawn.primelocation.net [205.161.238.235]) by hub.freebsd.org (Postfix) with ESMTP id B07F337BCE7; Wed, 1 Mar 2000 05:02:28 -0800 (PST) (envelope-from jedgar@fxp.org) Received: from earth.fxp (oca-p2-65.hitter.net [207.192.76.65]) by pawn.primelocation.net (Postfix) with ESMTP id 5DAE69B19; Wed, 1 Mar 2000 08:02:25 -0500 (EST) Date: Wed, 1 Mar 2000 08:02:24 -0500 (EST) From: "Chris D. Faulhaber" X-Sender: jedgar@earth.fxp To: Mike Smith Cc: scsi@freebsd.org Subject: Re: chio trap with not-ready changer In-Reply-To: <200003010502.VAA02846@mass.cdrom.com> 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, 29 Feb 2000, Mike Smith wrote: > > Ok, after some interesting side trips I'm happily up and talking to our > new (well, new-old) SpectraLogic STL-8000. There's only one catch so far > - if the unit is still initialising itself when the 'ch' driver tries to > talk to it, the latter fails in a messy fashion. It's easy enough to > work around this by increasing the SCSI delay, but if you have 40 tapes > in the unit and it's busy reading the barcodes off them all, this can be > a loooong wait. 8) > I used to service/support these beasts (as a VAR) and have found that they will cause various OS's (NT/Netware/SCO) to hang if you don't let them fully initialize before booting...very poor firmware design. Unfortunately, we never found a reasonable work-around other than to wait. ----- Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org -------------------------------------------------------- FreeBSD: The Power To Serve - http://www.FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 7: 2: 1 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from spiral.inspiral.net (spiral.inspiral.net [194.204.49.249]) by hub.freebsd.org (Postfix) with ESMTP id A745E37C29B; Wed, 1 Mar 2000 07:01:33 -0800 (PST) (envelope-from mauri@inspiral.net) Received: from omhi (omhi.inspiral.net [192.168.1.8]) by spiral.inspiral.net (8.9.3/8.9.3) with ESMTP id RAA92577; Wed, 1 Mar 2000 17:01:01 +0200 (EET) (envelope-from mauri@inspiral.net) From: "Lauri Laupmaa" Organization: Inspiral.Net To: scsi@freebsd.org, current@freebsd.org Date: Wed, 1 Mar 2000 17:01:13 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: plist/glist query & proposal Message-ID: <38BD4CD9.22420.5550BD1@localhost> X-mailer: Pegasus Mail for Win32 (v3.12c) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi How does one query glist (grown defect list) from scsi device ? Wouldn't it be nice if weekly/monthly scripts saved/compared glist with previous versions, so admins can be alerted when devices start dying. L. _____________ Lauri Laupmaa +3725013369 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 8:37:36 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [206.168.13.65]) by hub.freebsd.org (Postfix) with ESMTP id ACDD637B84A; Wed, 1 Mar 2000 08:37:29 -0800 (PST) (envelope-from fbsd@Ilsa.StevesCafe.com) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.9.3/8.9.3) with ESMTP id JAA10612; Wed, 1 Mar 2000 09:37:12 -0700 (MST) (envelope-from fbsd@Ilsa.StevesCafe.com) Message-Id: <200003011637.JAA10612@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0.2 2/24/98 From: Steve Passe To: "Chris D. Faulhaber" Cc: Mike Smith , "Kenneth D. Merry" , scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-reply-to: Your message of "Wed, 01 Mar 2000 08:02:24 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Mar 2000 09:37:12 -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Tue, 29 Feb 2000, Mike Smith wrote: > > > > > Ok, after some interesting side trips I'm happily up and talking to our > > new (well, new-old) SpectraLogic STL-8000. There's only one catch so far > ... > I used to service/support these beasts (as a VAR) and have found that they > will cause various OS's (NT/Netware/SCO) to hang if you don't let them > fully initialize before booting...very poor firmware > design. Unfortunately, we never found a reasonable work-around other than > to wait. > > ----- > Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org So our sony sdt9000 just died (after several years of hard service) and I figured I would pop for a sony tsl-s9000 changer, expecting it would "just work". With all this discussion of funky changers, I decided I should ask, does anyone successfully use the sony tsl changer with either chio or amanda? Any other DDS changers that someone recommends (lower end of budget)? -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 8:42:19 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 0DE4637C341; Wed, 1 Mar 2000 08:42:14 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id KAA91336; Wed, 1 Mar 2000 10:42:06 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Wed, 1 Mar 2000 10:42:05 -0600 (CST) From: Chris Dillon To: Mike Smith Cc: John Lengeling , scsi@FreeBSD.ORG Subject: Re: Cheap AMI MegaRAID 428 boards In-Reply-To: <200003010304.TAA01721@mass.cdrom.com> 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, 29 Feb 2000, Mike Smith wrote: > > I found a source for cheap (versus Adaptec) AMI MegaRAID 428 boards. > > Are these boards any good and does the freebsd driver work well with > > this board? They are used at $109.00 at www.teamexcess.com. It sounds > > like a good deal to me... > > I've been quite happy with the 428, actually. It's a bit short on CPU > power, so don't expect miracles, but the UF80 firmware seems quite > reliable, and if you load it up with memory it tools along quite nicely. I couldn't pass that up. I just bought one. Since you're familiar with this thing and the specs aren't very specific, does this thing require ECC memory? If not require it, would it at least take advantage of it? -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 11: 9:56 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id A89C637B9D8; Wed, 1 Mar 2000 11:09:44 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id UAA07479; Wed, 1 Mar 2000 20:06:25 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA01130; Wed, 1 Mar 2000 19:37:12 +0100 (CET) (envelope-from wilko) Date: Wed, 1 Mar 2000 19:37:12 +0100 From: Wilko Bulte To: "Matthew N. Dodd" Cc: Mike Smith , scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer Message-ID: <20000301193712.D787@yedi.iaf.nl> References: <200003010502.VAA02846@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from winter@jurai.net on Wed, Mar 01, 2000 at 01:06:29AM -0500 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 01, 2000 at 01:06:29AM -0500, Matthew N. Dodd wrote: > On Tue, 29 Feb 2000, Mike Smith wrote: > > Ok, after some interesting side trips I'm happily up and talking to > > our new (well, new-old) SpectraLogic STL-8000. There's only one catch > > so far - if the unit is still initialising itself when the 'ch' driver > > tries to talk to it, the latter fails in a messy fashion. It's easy > > enough to work around this by increasing the SCSI delay, but if you > > have 40 tapes in the unit and it's busy reading the barcodes off them > > all, this can be a loooong wait. 8) > > I think this is an artifact of the changer hardware being really stupid. > > I've got 2 different HP robots and a StorageWorks datawheel 8mm that I > have to let settle before I bring up the box they are attached to. StorageWorks datawheel? That would be ?? I'm not aware we ever supplied anything but DAT and DLT loaders from DEC/Compaq... -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 11:12:11 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id B2F2D37BCA4; Wed, 1 Mar 2000 11:11:56 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.9.3/8.8.7) with ESMTP id OAA86226; Wed, 1 Mar 2000 14:11:38 -0500 (EST) Date: Wed, 1 Mar 2000 14:11:37 -0500 (EST) From: "Matthew N. Dodd" To: Wilko Bulte Cc: Mike Smith , scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-Reply-To: <20000301193712.D787@yedi.iaf.nl> 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, 1 Mar 2000, Wilko Bulte wrote: > > I've got 2 different HP robots and a StorageWorks datawheel 8mm that I > > have to let settle before I bring up the box they are attached to. > > StorageWorks datawheel? That would be ?? I'm not aware we ever supplied > anything but DAT and DLT loaders from DEC/Compaq... StorageTek. It was late. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | winter@jurai.net | 2 x '84 Volvo 245DL | ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 11:16:58 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 6D9B437B920; Wed, 1 Mar 2000 11:16:55 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA00847; Wed, 1 Mar 2000 11:16:51 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003011916.LAA00847@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Chris Dillon Cc: Mike Smith , John Lengeling , scsi@FreeBSD.ORG Subject: Re: Cheap AMI MegaRAID 428 boards In-reply-to: Your message of "Wed, 01 Mar 2000 10:42:05 CST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 01 Mar 2000 11:16:51 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Tue, 29 Feb 2000, Mike Smith wrote: > > I've been quite happy with the 428, actually. It's a bit short on CPU > > power, so don't expect miracles, but the UF80 firmware seems quite > > reliable, and if you load it up with memory it tools along quite nicely. > > I couldn't pass that up. I just bought one. Since you're familiar > with this thing and the specs aren't very specific, does this thing > require ECC memory? If not require it, would it at least take > advantage of it? It requires parity memory; I don't believe it would know what to do with ECC memory (ie. would just use one bit for parity). -- \\ 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 Wed Mar 1 11:48:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 5A35337C344; Wed, 1 Mar 2000 11:47:07 -0800 (PST) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id NAA93373; Wed, 1 Mar 2000 13:47:04 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Wed, 1 Mar 2000 13:47:03 -0600 (CST) From: Chris Dillon To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: Cheap AMI MegaRAID 428 boards In-Reply-To: <200003011916.LAA00847@mass.cdrom.com> 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, 1 Mar 2000, Mike Smith wrote: > > On Tue, 29 Feb 2000, Mike Smith wrote: > > > I've been quite happy with the 428, actually. It's a bit short on CPU > > > power, so don't expect miracles, but the UF80 firmware seems quite > > > reliable, and if you load it up with memory it tools along quite nicely. > > > > I couldn't pass that up. I just bought one. Since you're familiar > > with this thing and the specs aren't very specific, does this thing > > require ECC memory? If not require it, would it at least take > > advantage of it? > > It requires parity memory; I don't believe it would know what to do with > ECC memory (ie. would just use one bit for parity). Thanks. That's actually what I had meant, anyway. I'm too used to seeing these peecee boxes doing ECC with parity memory. I think I've got several sticks of 36-bit 72-pin SIMMs around here somewhere. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures. ( http://www.freebsd.org ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 12: 5:34 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from naiad.eclipse.net.uk (naiad.eclipse.net.uk [195.188.32.29]) by hub.freebsd.org (Postfix) with ESMTP id A347637BA61 for ; Wed, 1 Mar 2000 12:05:16 -0800 (PST) (envelope-from sthen@naiad.eclipse.net.uk) Received: by naiad.eclipse.net.uk (Postfix, from userid 475) id 2E1D4148D8; Wed, 01 Mar 2000 20:05:11 +0000 (GMT) Date: Wed, 1 Mar 2000 20:05:11 +0000 From: Stuart Henderson To: John Lengeling Cc: scsi@freebsd.org Subject: Re: Cheap AMI MegaRAID 428 boards Message-ID: <20000301200511.A20412@naiad.eclipse.net.uk> References: <38BC6F9A.CF26BAD1@raccoon.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.1.2i In-Reply-To: <38BC6F9A.CF26BAD1@raccoon.com>; from johnl@raccoon.com on Tue, Feb 29, 2000 at 07:17:14PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Feb 29, 2000 at 07:17:14PM -0600, John Lengeling wrote: > I found a source for cheap (versus Adaptec) AMI MegaRAID 428 boards. > Are these boards any good and does the freebsd driver work well with > this board? They are used at $109.00 at www.teamexcess.com. It sounds > like a good deal to me... Ahh, why is all the cheap hardware North America only :( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 12:34:57 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id B7DE037B9D0 for ; Wed, 1 Mar 2000 12:34:51 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id VAA25360; Wed, 1 Mar 2000 21:28:47 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id VAA38321; Wed, 1 Mar 2000 21:28:13 +0100 (CET) From: Juergen Lock Date: Wed, 1 Mar 2000 21:28:12 +0100 To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: running a cleaning tape with chio (not!) Message-ID: <20000301212812.A30440@saturn.kn-bremen.de> References: <20000301020107.A1387@saturn.kn-bremen.de> <20000229213126.A27011@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <20000229213126.A27011@panzer.kdm.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Feb 29, 2000 at 09:31:26PM -0700, Kenneth D. Merry wrote: > On Wed, Mar 01, 2000 at 02:01:08 +0100, Juergen Lock wrote: > > Hi! > > > > Is this supposed to work? it didn't for me today, it did load it > > and also print on the console its a cleaning tape, but when the > > drive ejected it after doing its thing (normal behaviour with > > cleaning tapes at least on dds drives), it tried to load it again. :( > > > > This is a 6-slot hp dds2 autoloader, and 3.4-stable... > > Did you try to do I/O to the drive while the cleaning tape was in? The No, no process did anything on /dev/(n)rsa0, the only one that was talking to it was the chio. > only reason you would have gotten an error message that a cleaning tape was > installed would be in response to a command to the tape drive. > Well... i didn't have the time today to attempt to debug this properly but i did turn on cam debugging and tried to reproduce it, and surely enough the same thing happened again. here's what it said: # camcontrol debug -I -T -S -c 0:4 Mar 1 19:22:32 src /kernel: (xpt0:ahc0:0:4:-1): xpt_free_path Mar 1 19:22:32 src /kernel: (xpt0:ahc0:0:4:-1): xpt_release_path Mar 1 19:22:32 src /kernel: (xpt0:ahc0:0:4:-1): debugging flags now f Mar 1 19:22:32 src /kernel: (xpt0:ahc0:0:4:-1): xpt_free_path Mar 1 19:22:32 src /kernel: (xpt0:ahc0:0:4:-1): xpt_release_path # chio move slot 5 drive 0 Mar 1 19:23:17 src /kernel: (ch0:ahc0:0:4:1): entering cdgetccb Mar 1 19:23:19 src /kernel: (ch0:ahc0:0:4:1): xpt_schedule Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): added periph to queue Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): calling xpt_run_devq Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): xpt_setup_ccb Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): xpt_action Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): MODE SENSE(06). CDB: 1a 28 1d 0 20 0 Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): ahc_action Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): start scb(0xc083c1a0) Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): ahc_done - scb 13 Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): xpt_done Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): camisr(ch0:ahc0:0:4:1): xpt_setup_ccb Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): xpt_action Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): xpt_action Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): MODE SENSE(06). CDB: 1a 28 1d 0 20 0 Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): xpt_setup_ccb Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): xpt_action Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): ahc_action Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): start scb(0xc083c140) Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): ahc_done - scb 10 Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): xpt_done Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): camisr(ch0:ahc0:0:4:1): xpt_action Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): MODE SENSE(06). CDB: 1a 28 1f 0 20 0 Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): ahc_action Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): start scb(0xc083c1a0) Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): ahc_done - scb 13 Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): xpt_done Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): camisr(ch0:ahc0:0:4:1): entering chioctl Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): trying to do ioctl 0x800a6301 Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): entering cdgetccb Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): xpt_schedule Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): added periph to queue Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): calling xpt_run_devq Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): xpt_setup_ccb Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): xpt_action Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): MOVE MEDIUM. CDB: a5 20 0 0 0 7 0 1 0 0 0 0 Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): ahc_action Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): start scb(0xc083c140) [here it was done with the (first) cleaning it seems] Mar 1 19:24:04 src /kernel: (ch0:ahc0:0:4:1): ahc_done - scb 10 Mar 1 19:24:04 src /kernel: (ch0:ahc0:0:4:1): xpt_done Mar 1 19:24:04 src /kernel: (ch0:ahc0:0:4:1): camisr(ch0:ahc0:0:4:1): xpt_setup_ccb Mar 1 19:24:04 src /kernel: (ch0:ahc0:0:4:1): xpt_action Mar 1 19:24:04 src /kernel: (ch0:ahc0:0:4:1): xpt_action Mar 1 19:24:04 src /kernel: (ch0:ahc0:0:4:1): MOVE MEDIUM. CDB: a5 20 0 0 0 7 0 1 0 0 0 0 Mar 1 19:24:04 src /kernel: (ch0:ahc0:0:4:1): xpt_setup_ccb Mar 1 19:24:04 src /kernel: (ch0:ahc0:0:4:1): xpt_action Mar 1 19:24:04 src /kernel: (ch0:ahc0:0:4:1): ahc_action Mar 1 19:24:04 src /kernel: (ch0:ahc0:0:4:1): start scb(0xc083c140) [and this is where it wanted to load it again, and i had to do a forced magazine eject] Mar 1 19:24:54 src /kernel: (ch0:ahc0:0:4:1): ahc_done - scb 10 Mar 1 19:24:54 src /kernel: (ch0:ahc0:0:4:1): xpt_done Mar 1 19:24:54 src /kernel: (ch0:ahc0:0:4:1): camisr(ch0:ahc0:0:4:1): xpt_setup_ccb Mar 1 19:24:54 src /kernel: (ch0:ahc0:0:4:1): xpt_action Mar 1 19:24:54 src /kernel: (ch0:ahc0:0:4:1): xpt_setup_ccb Mar 1 19:24:54 src /kernel: (ch0:ahc0:0:4:1): xpt_action Mar 1 19:24:54 src /kernel: (ch0:ahc0:0:4:1): MOVE MEDIUM. CDB: a5 20 0 0 0 7 0 1 0 0 0 0 Mar 1 19:24:54 src /kernel: (ch0:ahc0:0:4:1): MEDIUM ERROR asc:30,3 Mar 1 19:24:54 src /kernel: (ch0:ahc0:0:4:1): Cleaning cartridge installed Mar 1 19:24:54 src /kernel: (ch0:ahc0:0:4:1): xpt_setup_ccb Mar 1 19:24:54 src /kernel: (ch0:ahc0:0:4:1): xpt_action so the `Cleaning cartridge installed' only appeared at the end, didn't notice that at the first try cause i was on another vty. and it reports itself as a `HP C1553A 9608', does someone have the same drive who could also try this? > My guess is that your problem is that your autoloader is configured in > autoloader mode instead of changer mode or something. > Hmm i didn't have the sucker's manual handy to check this, so at the moment i can only say that chio does work on it with regular tapes... > The fact that your cleaning tape got inserted again is likely the > autoloader's problem, not FreeBSD's problem. FreeBSD just does what you > tell it to do. :) Well, at least it does that _much_ more often than e.g. anything from M$, yes. :) Thanx + Regards, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 12:37:11 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CF9D337BBC3; Wed, 1 Mar 2000 12:37:05 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id NAA34196; Wed, 1 Mar 2000 13:37:00 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id NAA97384; Wed, 1 Mar 2000 13:36:51 -0700 (MST) Message-Id: <200003012036.NAA97384@harmony.village.org> To: "Lauri Laupmaa" Subject: Re: plist/glist query & proposal Cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Wed, 01 Mar 2000 17:01:13 +0200." <38BD4CD9.22420.5550BD1@localhost> References: <38BD4CD9.22420.5550BD1@localhost> Date: Wed, 01 Mar 2000 13:36:51 -0700 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <38BD4CD9.22420.5550BD1@localhost> "Lauri Laupmaa" writes: : How does one query glist (grown defect list) from scsi device ? I use camcontrol defects -P or -G to get them. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 12:48: 5 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 1F16337BAAD; Wed, 1 Mar 2000 12:47:59 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA33270; Wed, 1 Mar 2000 13:47:26 -0700 (MST) (envelope-from ken) Date: Wed, 1 Mar 2000 13:47:26 -0700 From: "Kenneth D. Merry" To: Lauri Laupmaa Cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: plist/glist query & proposal Message-ID: <20000301134726.A33028@panzer.kdm.org> References: <38BD4CD9.22420.5550BD1@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38BD4CD9.22420.5550BD1@localhost>; from mauri@inspiral.net on Wed, Mar 01, 2000 at 05:01:13PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 01, 2000 at 17:01:13 +0200, Lauri Laupmaa wrote: > Hi > > How does one query glist (grown defect list) from scsi device ? Like this: # camcontrol defects da0 -f phys -G Got 8 defects: 4818:4:54 1338:0:138 1250:1:46 2661:5:117 1696:5:5 1760:5:58 688:9:133 1130:9:166 > Wouldn't it be nice if weekly/monthly scripts saved/compared glist > with previous versions, so admins can be alerted when devices > start dying. It would be nice, although I'm not sure everyone would want it. Also, one problem you may run into is that none of the defect list formats is mandatory. So there's no one format you can use that is guaranteed to work with all drives. If the drive doesn't support the requested format, it is supposed to return a specific error (which camcontrol looks for) along with the defect list in a format that it does support. Unfortunately, many drives don't do this, or return a different error, or return an error but no data. So camcontrol can't always tell the difference between "here's a defect list in some other format" and "I can't do that". One other probelm -- the read defect data command isn't mandatory in SCSI-2 at least. (haven't checked the SCSI-3 specs) So you can't even guarantee that the drive will support the command. Anyway, it should be easy enough to write a script that will compare glists for the drives on your machines and watch for failures. The defect list output is intended to be reasonably easy to script -- the number of defects goes to stderr, and the actual list of defects goes to stdout. 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 Wed Mar 1 13:39:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from pan.ch.intel.com (pan.ch.intel.com [143.182.246.24]) by hub.freebsd.org (Postfix) with ESMTP id F2E4237BB62; Wed, 1 Mar 2000 13:39:18 -0800 (PST) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by pan.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id OAA08907; Wed, 1 Mar 2000 14:39:10 -0700 (MST) Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id OAA18911; Wed, 1 Mar 2000 14:39:10 -0700 (MST) X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id QAA18110; Wed, 1 Mar 2000 16:39:10 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14525.36350.446934.308565@hip186.ch.intel.com> Date: Wed, 1 Mar 2000 14:39:10 -0700 (MST) To: Lyndon Nerenberg Cc: multimedia@freebsd.org, scsi@freebsd.org, Dmitry Sivachenko Subject: xpt* vs pass* (was Re: cdrecord ) In-Reply-To: <200003012126.e21LQRx04404@orthanc.ab.ca> References: <200003012107.AAA46366@netserv1.chg.ru> <200003012126.e21LQRx04404@orthanc.ab.ca> X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ I'm cc'ing this to -scsi because the scsi folks (hi Ken ;-) can more easily answer this simple-to-them question ] [ On Wednesday, March 1, Lyndon Nerenberg wrote: ] > > > > [ question about cdrecord not working with "file not found" messages ] > > Make sure /dev/pass6 exists, and that you have write permissions on it. > > For the HP drive itself you will find a couple of quarks. It doesn't > recognize the usual SCSI commands to change audio tracks, and it > doesn't report back the info needed for time-related functions (e.g. > time remaining for the track/disk), so it's pretty useless with things > like xmcd. None of these affect cdrecord, though. (And cdda2wav works > great with it.) > Just for my own clarification, is it the /dev/pass* entries that cdrecord needs or is the /dev/xpt* entries? It was not apparent after doing "man pass" and "man xpt". -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 13:52:57 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130]) by hub.freebsd.org (Postfix) with ESMTP id 8987C37BB3F; Wed, 1 Mar 2000 13:52:28 -0800 (PST) (envelope-from lyndon@orthanc.ab.ca) Received: from orthanc.ab.ca (localhost [127.0.0.1]) by orthanc.ab.ca (8.10.0.Beta11/8.10.0.Beta6) with ESMTP id e21Lp4x04494; Wed, 1 Mar 2000 14:51:04 -0700 (MST) Message-Id: <200003012151.e21Lp4x04494@orthanc.ab.ca> To: John Reynolds~ Cc: multimedia@freebsd.org, scsi@freebsd.org, Dmitry Sivachenko Subject: Re: xpt* vs pass* (was Re: cdrecord ) In-reply-to: Your message of "Wed, 01 Mar 2000 14:39:10 MST." <14525.36350.446934.308565@hip186.ch.intel.com> Date: Wed, 01 Mar 2000 14:51:04 -0700 From: Lyndon Nerenberg Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> "John" == John Reynolds~ writes: John> Just for my own clarification, is it the /dev/pass* entries John> that cdrecord needs or is the /dev/xpt* entries? It was not John> apparent after doing "man pass" and "man xpt". Argh. Operator error. cdrecord wants /dev/xpt*. It's xscanimage that's using the /dev/pass* device. Sorry about the bad info :-P --lyndon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 13:53:31 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 4BBBE37C473; Wed, 1 Mar 2000 13:53:13 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA33833; Wed, 1 Mar 2000 14:51:43 -0700 (MST) (envelope-from ken) Date: Wed, 1 Mar 2000 14:51:43 -0700 From: "Kenneth D. Merry" To: John Reynolds~ Cc: Lyndon Nerenberg , multimedia@FreeBSD.ORG, scsi@FreeBSD.ORG, Dmitry Sivachenko Subject: Re: xpt* vs pass* (was Re: cdrecord ) Message-ID: <20000301145143.A33812@panzer.kdm.org> References: <200003012107.AAA46366@netserv1.chg.ru> <200003012126.e21LQRx04404@orthanc.ab.ca> <14525.36350.446934.308565@hip186.ch.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <14525.36350.446934.308565@hip186.ch.intel.com>; from jreynold@sedona.ch.intel.com on Wed, Mar 01, 2000 at 02:39:10PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 01, 2000 at 14:39:10 -0700, John Reynolds~ wrote: > > [ I'm cc'ing this to -scsi because the scsi folks (hi Ken ;-) can more > easily answer this simple-to-them question ] > > [ On Wednesday, March 1, Lyndon Nerenberg wrote: ] > > > > > > [ question about cdrecord not working with "file not found" messages ] > > > > Make sure /dev/pass6 exists, and that you have write permissions on it. > > > > For the HP drive itself you will find a couple of quarks. It doesn't > > recognize the usual SCSI commands to change audio tracks, and it > > doesn't report back the info needed for time-related functions (e.g. > > time remaining for the track/disk), so it's pretty useless with things > > like xmcd. None of these affect cdrecord, though. (And cdda2wav works > > great with it.) > > > > Just for my own clarification, is it the /dev/pass* entries that cdrecord > needs or is the /dev/xpt* entries? It was not apparent after doing "man pass" > and "man xpt". It needs both. It needs /dev/xpt0 to get a list of devices in the system, and it needs /dev/pass* to send commands to those devices. 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 Wed Mar 1 13:56:18 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from melete.ch.intel.com (melete.ch.intel.com [143.182.246.25]) by hub.freebsd.org (Postfix) with ESMTP id DA0C037BAFC; Wed, 1 Mar 2000 13:56:08 -0800 (PST) (envelope-from jreynold@sedona.ch.intel.com) Received: from sedona.intel.com (sedona.ch.intel.com [143.182.218.21]) by melete.ch.intel.com (8.9.1a+p1/8.9.1/d: relay.m4,v 1.19 2000/01/29 00:15:43 dmccart Exp $) with ESMTP id VAA24069; Wed, 1 Mar 2000 21:57:42 GMT Received: from hip186.ch.intel.com (hip186.ch.intel.com [143.182.225.68]) by sedona.intel.com (8.9.1a/8.9.1/d: sendmail.cf,v 1.10 2000/02/10 21:38:16 steved Exp $) with ESMTP id OAA22465; Wed, 1 Mar 2000 14:56:03 -0700 (MST) X-Envelope-From: jreynold@sedona.ch.intel.com Received: (from jreynold@localhost) by hip186.ch.intel.com (8.9.1a/8.9.1/d: client.m4,v 1.3 1998/09/29 16:36:11 sedayao Exp sedayao $) id QAA19110; Wed, 1 Mar 2000 16:56:03 -0500 (EST) X-Authentication-Warning: hip186.ch.intel.com: jreynold set sender to jreynold@sedona.ch.intel.com using -f From: John Reynolds~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14525.37362.588361.780967@hip186.ch.intel.com> Date: Wed, 1 Mar 2000 14:56:02 -0700 (MST) To: multimedia@freebsd.org, scsi@freebsd.org, Dmitry Sivachenko Subject: Re: xpt* vs pass* (was Re: cdrecord ) In-Reply-To: <20000301145143.A33812@panzer.kdm.org> References: <200003012107.AAA46366@netserv1.chg.ru> <200003012126.e21LQRx04404@orthanc.ab.ca> <14525.36350.446934.308565@hip186.ch.intel.com> <20000301145143.A33812@panzer.kdm.org> X-Mailer: VM 6.75 under Emacs 20.3.11 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ On Wednesday, March 1, Kenneth D. Merry wrote: ] > > It needs both. It needs /dev/xpt0 to get a list of devices in the system, > and it needs /dev/pass* to send commands to those devices. > > Ken OK, thanks! Dmitry should be a-ok if he just does a "sh MAKEDEV all" in /dev ... -Jr -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= | John Reynolds WCCG, CCE, Higher Levels of Abstraction | | Intel Corporation MS: CH6-210 Phone: 480-554-9092 pgr: 602-868-6512 | | jreynold@sedona.ch.intel.com http://www-aec.ch.intel.com/~jreynold/ | =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 14:10:19 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 23BA737BB90; Wed, 1 Mar 2000 14:09:49 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA16118; Wed, 1 Mar 2000 22:56:55 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA02112; Wed, 1 Mar 2000 20:34:35 +0100 (CET) (envelope-from wilko) Date: Wed, 1 Mar 2000 20:34:35 +0100 From: Wilko Bulte To: "Matthew N. Dodd" Cc: Mike Smith , scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer Message-ID: <20000301203435.A1892@yedi.iaf.nl> References: <20000301193712.D787@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from winter@jurai.net on Wed, Mar 01, 2000 at 02:11:37PM -0500 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 01, 2000 at 02:11:37PM -0500, Matthew N. Dodd wrote: > On Wed, 1 Mar 2000, Wilko Bulte wrote: > > > I've got 2 different HP robots and a StorageWorks datawheel 8mm that I > > > have to let settle before I bring up the box they are attached to. > > > > StorageWorks datawheel? That would be ?? I'm not aware we ever supplied > > anything but DAT and DLT loaders from DEC/Compaq... > > StorageTek. It was late. Ah, I see. I think I even know what one looks like. -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 17:40: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from news-ma.rhein-neckar.de (news-ma.rhein-neckar.de [193.197.90.3]) by hub.freebsd.org (Postfix) with ESMTP id 16F9137BDBD for ; Wed, 1 Mar 2000 17:40:03 -0800 (PST) (envelope-from daemon@bigeye.rhein-neckar.de) Received: from bigeye.rhein-neckar.de (uucp@localhost) by news-ma.rhein-neckar.de (8.8.8/8.8.8) with bsmtp id CAA24494 for freebsd-scsi@freebsd.org; Thu, 2 Mar 2000 02:40:01 +0100 (CET) (envelope-from daemon@bigeye.rhein-neckar.de) Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id BAA77281 for freebsd-scsi@freebsd.org; Thu, 2 Mar 2000 01:57:33 +0100 (CET) (envelope-from daemon) From: naddy@mips.rhein-neckar.de (Christian Weisgerber) Subject: OnStream ADR50? Date: 2 Mar 2000 01:57:33 +0100 Message-ID: <89ke9t$2beo$1@bigeye.rhein-neckar.de> To: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Anybody out there who successfully uses an OnStream ADR50 off a FreeBSD box? This is not one of the old line of drives (now called "Echo") that require a special driver. According to the OnStream representative I talked to at CeBIT, the ADRxx series implements the usual SCSI tape command set and should work with any platform that supports SCSI tapes, e.g. they claim it's handled by the normal Linux SCSI driver. PS: Any opinions on OnStream (ADR) vs Ecrix (VXA), which seem to be similarly priced for both drives and media? -- Christian "naddy" Weisgerber naddy@mips.rhein-neckar.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 18:31:33 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp.america.net (smtp.america.net [199.170.121.14]) by hub.freebsd.org (Postfix) with ESMTP id 6B65C37BF1E; Wed, 1 Mar 2000 18:31:26 -0800 (PST) (envelope-from andrew@networkcomputerz.com) Received: from networkcomputerz.com (tnt1-84.america.net [206.67.248.84]) by smtp.america.net (8.9.1/8.9.1) with ESMTP id VAA02121; Wed, 1 Mar 2000 21:31:22 -0500 (EST) Message-ID: <38BDD1BD.F7D816BC@networkcomputerz.com> Date: Wed, 01 Mar 2000 21:28:13 -0500 From: Andrew Otwell Organization: Network Computerz X-Mailer: Mozilla 4.7 [en] (X11; I; FreeBSD 3.4-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Mike Smith Cc: John Lengeling , scsi@FreeBSD.ORG Subject: Re: Cheap AMI MegaRAID 428 boards References: <200003010350.TAA02184@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Actually, the 428 has an alarm feature that'll buzzzzzzzz you to death in the event of a disk failure. Mike Smith wrote: > > > > > > Note that it only does 20MHz ("ultra") 16-bit SCSI; if you're more > > > interested in reliability than speed it should do you OK. Also note that > > > as yet we don't have a management interface for this controller family, > > > so you'll be flying a _little_ blind in eg. degraded/rebuild cases. > > > > What do you mean by blind? I won't know when I'm in a degraded state, > > or I will have to use some DOS/Win tools to do the rebuild? > > You won't know if you're in a degraded mode (unless you look at what your > drives are doing, or have a SAF-TE enclosure), and if you don't have a > hot spare, you'll have to use the BIOS tools to instigate a rebuild. > > -- > \\ 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 -- _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ Andrew T. Otwell, Network Administrator andrew@networkcomputerz.com, 678.363.8491 http://www.NetworkComputerz.com yank GnuPG DSS key from hkp://pgpkeys.mit.edu _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 22:44:40 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 E9CA137C189; Wed, 1 Mar 2000 22:44:35 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA36646; Wed, 1 Mar 2000 23:44:35 -0700 (MST) (envelope-from ken) Date: Wed, 1 Mar 2000 23:44:34 -0700 From: "Kenneth D. Merry" To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer Message-ID: <20000301234434.A36537@panzer.kdm.org> References: <20000301012528.A29274@panzer.kdm.org> <200003010841.AAA05125@mass.cdrom.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="xHFwDpU9dbj6ez1V" X-Mailer: Mutt 1.0i In-Reply-To: <200003010841.AAA05125@mass.cdrom.com>; from msmith@FreeBSD.ORG on Wed, Mar 01, 2000 at 12:41:33AM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii On Wed, Mar 01, 2000 at 00:41:33 -0800, Mike Smith wrote: > > > I tried with both 1 and also 100. With the latter, I get a lot of > > > repeats, ending in: > > > > > > (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 1 > > > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 > > > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > > > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > > > (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 0 > > > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 > > > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > > > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > > > (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 0 > > > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > > > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > > > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > > > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > > > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > > > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > > > (ch0:ahc0:0:4:0): fatal error, failed to attach to device > > > (ch0:ahc0:0:4:0): lost device > > > (ch0:ahc0:0:4:0): removing device entry > > > > > > (Note two there with a retry count of 0. Weird.) > > > > Note that one has the SMS_DBD flag set in the second byte of the CDB, > > the other has it cleared. > > I'm not sure what the significance of that is, actually. Well, the changer probe code will try doing a mode sense without block descriptors disabled. That's because some changers don't like it when you disable block descriptors. The comment on rev 1.2 of scsi_ch.c describes the problem. > > > With 1, there's obviously a lot less, but the same result. > > > > Can you include a little more of the retries? The disable block > > descriptors flag is getting cleared mighty late if the above is the tail > > end of the output from the 100 retries. [ ... ] > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 4 > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 3 > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > (ch0:ahc0:0:4:0): CAM status = 0x4c, retry count = 2 > (ch0:ahc0:0:4:0): MODE SENSE(06). CDB: 1a 8 1d 0 20 0 > (ch0:ahc0:0:4:0): UNIT ATTENTION asc:29,0 > (ch0:ahc0:0:4:0): Power on, reset, or bus device reset occurred > > As far as I can see, they all look the same as the count=1 case. Yep, thanks. > > In any case, try putting a printf inside the SS_TUR case in > > cam_periph_error() in cam_periph.c, to see whether the quirk entry is > > getting matched correctly and therefore whether the test unit ready is > > getting issued. > > Hmm. Trying: > > if (((err_action & SS_MASK) == SS_TUR) > && save_ccb != NULL > && ccb->ccb_h.retry_count > 0) { > > printf("cam_periph_error: sending TUR\n"); > > I never see the above message. Okay, my guess is that I flubbed the quirk entry somehow. Anyway, try the attached patch for scsi_all.c. It makes the quirk entry much more generic in the hopes that it'll match. Ken -- Kenneth Merry ken@kdm.org --xHFwDpU9dbj6ez1V Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="scsi_all.c.spectra.20000301" ==== //depot/FreeBSD-ken/src/sys/cam/scsi/scsi_all.c#4 - /a/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_all.c ==== *** /tmp/tmp.36576.0 Wed Mar 1 23:33:51 2000 --- /a/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_all.c Wed Mar 1 23:33:31 2000 *************** *** 725,730 **** --- 725,748 ---- * WARNING: You must update the num_ascs field below for this quirk table * entry if you add more entries. */ + static struct asc_table_entry spectra_8000_entries[] = { + {SST(0x29, 0x00, SS_TUR|SSQ_DECREMENT_COUNT|ENXIO, + "Power on, reset, or bus device reset occurred")} + }; + + /* + * WARNING: You must update the num_ascs field below for this quirk table + * entry if you add more entries. + */ + static struct asc_table_entry sony_mo_entries[] = { + {SST(0x04, 0x00, SS_START|SSQ_DECREMENT_COUNT|ENXIO, + "Logical unit not ready, cause not reportable")} + }; + + /* + * WARNING: You must update the num_ascs field below for this quirk table + * entry if you add more entries. + */ static struct asc_table_entry quantum_fireball_entries[] = { {SST(0x04, 0x0b, SS_START|SSQ_DECREMENT_COUNT|ENXIO, "Logical unit not ready, initializing cmd. required")} *************** *** 741,746 **** --- 759,786 ---- {T_DIRECT, SIP_MEDIA_FIXED, "QUANTUM", "FIREBALL S*", "*"}, 1, /* number of vendor-specific sense codes for this entry */ quantum_fireball_entries + }, + { + /* + * This Sony MO drive likes to return 0x04, 0x00 when it + * isn't spun up. + * Reported by: Joerg Wunsch + */ + {T_DIRECT, SIP_MEDIA_REMOVABLE, "SONY", "SMO-C501-09*", "*"}, + 1, /* number of vendor-specific sense codes for this entry */ + sony_mo_entries + }, + { + /* + * The apparantly doesn't clear + * unit attention conditions when a mode sense is issued. + * So we have to issue test unit readies until the unit + * attention condition has been cleared. + * Reported by: Mike Smith + */ + {T_CHANGER, SIP_MEDIA_REMOVABLE, "SPECT*", "*", "*"}, + 1, /* number of vendor-specific sense codes for this entry */ + spectra_8000_entries } }; --xHFwDpU9dbj6ez1V-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Mar 1 23: 4: 8 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 359B237BEFD for ; Wed, 1 Mar 2000 23:04:04 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id AAA36823; Thu, 2 Mar 2000 00:04:00 -0700 (MST) (envelope-from ken) Date: Thu, 2 Mar 2000 00:04:00 -0700 From: "Kenneth D. Merry" To: Juergen Lock Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: running a cleaning tape with chio (not!) Message-ID: <20000302000359.A36748@panzer.kdm.org> References: <20000301020107.A1387@saturn.kn-bremen.de> <20000229213126.A27011@panzer.kdm.org> <20000301212812.A30440@saturn.kn-bremen.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000301212812.A30440@saturn.kn-bremen.de>; from nox@jelal.kn-bremen.de on Wed, Mar 01, 2000 at 09:28:12PM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Mar 01, 2000 at 21:28:12 +0100, Juergen Lock wrote: > On Tue, Feb 29, 2000 at 09:31:26PM -0700, Kenneth D. Merry wrote: > > On Wed, Mar 01, 2000 at 02:01:08 +0100, Juergen Lock wrote: > > > Hi! > > > > > > Is this supposed to work? it didn't for me today, it did load it > > > and also print on the console its a cleaning tape, but when the > > > drive ejected it after doing its thing (normal behaviour with > > > cleaning tapes at least on dds drives), it tried to load it again. :( > > > > > > This is a 6-slot hp dds2 autoloader, and 3.4-stable... > > > > Did you try to do I/O to the drive while the cleaning tape was in? The > > No, no process did anything on /dev/(n)rsa0, the only one that was > talking to it was the chio. Hmm, I guess I'm used to changers where the tape mechanism and the changer mechanism are relatively separate. In most cases the changer has little idea about what type of tape it put in the drive. The only thing it might know is an id from a barcode label. Your changer is evidently different, as the error below suggests -- it indeed came from the changer LUN on the device. > > only reason you would have gotten an error message that a cleaning tape was > > installed would be in response to a command to the tape drive. > > > Well... i didn't have the time today to attempt to debug this > properly but i did turn on cam debugging and tried to reproduce it, > and surely enough the same thing happened again. here's what it said: > > # camcontrol debug -I -T -S -c 0:4 > Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): MODE SENSE(06). CDB: 1a 28 1d 0 20 0 > Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): MODE SENSE(06). CDB: 1a 28 1d 0 20 0 > Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): MODE SENSE(06). CDB: 1a 28 1f 0 20 0 > Mar 1 19:23:21 src /kernel: (ch0:ahc0:0:4:1): MOVE MEDIUM. CDB: a5 20 0 0 0 7 0 1 0 0 0 0 > [here it was done with the (first) cleaning it seems] > Mar 1 19:24:04 src /kernel: (ch0:ahc0:0:4:1): MOVE MEDIUM. CDB: a5 20 0 0 0 7 0 1 0 0 0 0 > [and this is where it wanted to load it again, and i had to do a forced magazine eject] > Mar 1 19:24:54 src /kernel: (ch0:ahc0:0:4:1): MOVE MEDIUM. CDB: a5 20 0 0 0 7 0 1 0 0 0 0 > Mar 1 19:24:54 src /kernel: (ch0:ahc0:0:4:1): MEDIUM ERROR asc:30,3 > Mar 1 19:24:54 src /kernel: (ch0:ahc0:0:4:1): Cleaning cartridge installed > so the `Cleaning cartridge installed' only appeared at the end, didn't > notice that at the first try cause i was on another vty. From the logs above, it looks like you tried to move the tape into the drive twice. Note that the first and second move medium commands are identical -- i.e. same source and destination. So is that what happened? Once a tape drive has ejected a tape, I'm not sure if you can push the tape back in the tape drive without first moving it back to a slot or something. If you wanted to put it back in the drive, you'd probably have to do something like: chio move drive 0 drive 0 But I kinda doubt that would work. I'm surprised it gave the error it did, though. I would expect something like "source element empty" or "destination element full". > and it reports itself as a `HP C1553A 9608', does someone have the > same drive who could also try this? > > > My guess is that your problem is that your autoloader is configured in > > autoloader mode instead of changer mode or something. > > > Hmm i didn't have the sucker's manual handy to check this, so > at the moment i can only say that chio does work on it with > regular tapes... Ahh. So you probably have it in changer mode. > > The fact that your cleaning tape got inserted again is likely the > > autoloader's problem, not FreeBSD's problem. FreeBSD just does what you > > tell it to do. :) > > Well, at least it does that _much_ more often than e.g. anything > from M$, yes. :) :) 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 Thu Mar 2 2:49:54 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from procsys.com (PPP-190-104.bng.vsnl.net.in [203.197.190.104]) by hub.freebsd.org (Postfix) with SMTP id E51A937C01A; Thu, 2 Mar 2000 02:49:41 -0800 (PST) (envelope-from nanda@procsys.com) Received: from nanda ([192.168.1.70]) by procsys.com with SMTP; Thu, 02 Mar 2000 16:22:21 +0800 Message-ID: <38BE4879.F41@procsys.com> Date: Thu, 02 Mar 2000 16:24:49 +0530 From: Nanda Kumar Reply-To: nanda@procsys.com X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: Mike Smith Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IOCTL support in SCSI block driver References: <200003010807.AAA04798@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I went through the mylex code to find how they implement the control interface. But i have some doubts regarding this. Mainly these doubts come since i am still quiete new to the FreeBSD world and don't have good text books regarding how to write device drivers etc. 1). In the user space how do i specify a controller to communicate with that ? For eg. if i want to open the device and a send an IOCTL how do i specify that ? In our case actual disks will be seen as part of target discovery done through the CAM SCSI interface. 2). I found that the while registering the character device the "softc" structure does not come to picture at all. But later while opening the device the "softc" structure is obtained using "devclass_get_softc". How is it obtained ? If there are some documents regarding these you can tell me and i will go through it. Regards, Nandan >Mike Smith wrote: > > > > No. The key issue here, and one that you still haven't answered is: Does > > > your RAID device take SCSI commands, or does it have a different > > > interface? > > > > Our RAID device takes SCSI commands. Typically the parameters passed to > > the firmware includes SCSI CDB,path id,target id,LUN number,data > > direction flag,SCSI tag queing attribute,data buffer pointers etc. > > Status returned consists of SCSI status and sense information. > > Ok. In that case, you're right on the target for using CAM. > > > But my driver should also handle the IOCTL support for proprietary > > communication which will be used by a JAVA based Array Manager program > > for the purpose of getting statistics and configuring the card. Can i > > pass IOCTLs directly to the HAB SCSI CAM driver ? > > No. You will want to create a per-adapter device instance that takes the > bus/target/lun information and passes it along with the ioctl data to the > firmware. You can see an instance of this in the Mylex driver I > referenced previously. > > > I want to avoid writing another character driver just for the sake of > > IOCTL handling we could do this in Linux and Windows NT. > > You don't need another entire driver; just a few extra lines to > instantiate a control interface node for the adapter. > > -- > \\ 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 Thu Mar 2 4:14:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from netserv1.chg.ru (netserv1.chg.ru [193.233.46.3]) by hub.freebsd.org (Postfix) with ESMTP id E94D637BFAA; Thu, 2 Mar 2000 04:14:18 -0800 (PST) (envelope-from dima@netserv1.chg.ru) Received: (from dima@localhost) by netserv1.chg.ru (8.9.3/8.9.3) id PAA64102; Thu, 2 Mar 2000 15:13:16 +0300 (MSK) Date: Thu, 2 Mar 2000 15:13:16 +0300 (MSK) Message-Id: <200003021213.PAA64102@netserv1.chg.ru> From: Dmitry Sivachenko To: jreynold@sedona.ch.intel.com Cc: multimedia@freebsd.org, scsi@freebsd.org In-reply-to: <14525.37362.588361.780967@hip186.ch.intel.com> (message from John Reynolds~ on Wed, 1 Mar 2000 14:56:02 -0700 (MST)) Subject: Re: xpt* vs pass* (was Re: cdrecord ) References: <200003012107.AAA46366@netserv1.chg.ru> <200003012126.e21LQRx04404@orthanc.ab.ca> <14525.36350.446934.308565@hip186.ch.intel.com> <20000301145143.A33812@panzer.kdm.org> <14525.37362.588361.780967@hip186.ch.intel.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ On Wednesday, March 1, Kenneth D. Merry wrote: ] > > It needs both. It needs /dev/xpt0 to get a list of devices in the system, > and it needs /dev/pass* to send commands to those devices. > > Ken Does it mean I should enable pass0 device in my kernel? PS: I do have xpt0 and pass0 devices in /dev/ Thank for your answers, Dima. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 7: 0: 8 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from procsys.com (PPP-190-182.bng.vsnl.net.in [203.197.190.182]) by hub.freebsd.org (Postfix) with SMTP id 0EBCB37C5A4; Thu, 2 Mar 2000 06:59:21 -0800 (PST) (envelope-from nanda@procsys.com) Received: from nanda ([192.168.1.70]) by procsys.com with SMTP; Thu, 02 Mar 2000 20:13:12 +0800 Message-ID: <38BE7E99.48A0@procsys.com> Date: Thu, 02 Mar 2000 20:15:45 +0530 From: Nanda Kumar Reply-To: nanda@procsys.com X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: Mike Smith Cc: freebsd-scsi@FreeBSD.ORG Subject: RAID controllers in FreeBSD 3.4 References: <200003010807.AAA04798@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Why there is no AMI driver,Mylex driver for FreeBSD version 3.4. Is there any specific reason for that ? Regards, Nandan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 7: 4: 2 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from shell.futuresouth.com (shell.futuresouth.com [198.78.58.28]) by hub.freebsd.org (Postfix) with ESMTP id 1296D37C45C for ; Thu, 2 Mar 2000 07:03:57 -0800 (PST) (envelope-from tim@futuresouth.com) Received: (from tim@localhost) by shell.futuresouth.com (8.9.3/8.9.3) id JAA13845 for scsi@FreeBSD.ORG; Thu, 2 Mar 2000 09:03:52 -0600 (CST) Date: Thu, 2 Mar 2000 09:03:52 -0600 From: Tim Tsai To: scsi@FreeBSD.ORG Subject: adaptec 29160? Message-ID: <20000302090352.A13672@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is the Adaptec 29160 supported? I didn't find anything on the mailing list archives. Thanks, Tim To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 7:59:54 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 3733637BB4E; Thu, 2 Mar 2000 07:59:48 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id IAA39322; Thu, 2 Mar 2000 08:58:47 -0700 (MST) (envelope-from ken) Date: Thu, 2 Mar 2000 08:58:47 -0700 From: "Kenneth D. Merry" To: Dmitry Sivachenko Cc: jreynold@sedona.ch.intel.com, multimedia@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: xpt* vs pass* (was Re: cdrecord ) Message-ID: <20000302085847.A39306@panzer.kdm.org> References: <200003012107.AAA46366@netserv1.chg.ru> <200003012126.e21LQRx04404@orthanc.ab.ca> <14525.36350.446934.308565@hip186.ch.intel.com> <20000301145143.A33812@panzer.kdm.org> <14525.37362.588361.780967@hip186.ch.intel.com> <200003021213.PAA64102@netserv1.chg.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003021213.PAA64102@netserv1.chg.ru>; from dima@Chg.RU on Thu, Mar 02, 2000 at 03:13:16PM +0300 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 02, 2000 at 15:13:16 +0300, Dmitry Sivachenko wrote: > [ On Wednesday, March 1, Kenneth D. Merry wrote: ] > > > > It needs both. It needs /dev/xpt0 to get a list of devices in the system, > > and it needs /dev/pass* to send commands to those devices. > > > > Ken > > Does it mean I should enable pass0 device in my kernel? Yes, you need that in order for the pass devices to work. > PS: I do have xpt0 and pass0 devices in /dev/ 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 Thu Mar 2 8: 2:54 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 7B4DD37C406 for ; Thu, 2 Mar 2000 08:02:49 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id JAA39339; Thu, 2 Mar 2000 09:00:12 -0700 (MST) (envelope-from ken) Date: Thu, 2 Mar 2000 09:00:12 -0700 From: "Kenneth D. Merry" To: Tim Tsai Cc: scsi@FreeBSD.ORG Subject: Re: adaptec 29160? Message-ID: <20000302090012.B39306@panzer.kdm.org> References: <20000302090352.A13672@futuresouth.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <20000302090352.A13672@futuresouth.com>; from tim@futuresouth.com on Thu, Mar 02, 2000 at 09:03:52AM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 02, 2000 at 09:03:52 -0600, Tim Tsai wrote: > Is the Adaptec 29160 supported? I didn't find anything on the mailing > list archives. Yes, but only in -current, and they'll currently only run at 80MB/sec. Justin is working on Ultra160 support for those controllers. 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 Thu Mar 2 8:56:48 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by hub.freebsd.org (Postfix) with SMTP id CCD4837B827 for ; Thu, 2 Mar 2000 08:56:45 -0800 (PST) (envelope-from up@3.am) Received: (qmail 2912 invoked by uid 1825); 2 Mar 2000 16:56:38 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 2 Mar 2000 16:56:38 -0000 Date: Thu, 2 Mar 2000 11:56:38 -0500 (EST) From: X-Sender: up@richard2.pil.net To: scsi@freebsd.org Subject: Can't see DLT4000 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 just upgraded our tape drive from a DDS-2 DAT to a Quantum DLT4000 and can't seem to get the system to see the DLT, no matter what. If I switch back to the DDS2 and reboot, mt sees it fine. A rundown: Both are External SCSI drives set to SCSI ID 4 used the same terminator and cable I've rebooted several times The SCSI host adapter is an on-board Adaptec AIC-7896 (Intel L440GX+) using the second (B) SCSI bus. When I have the DDS-2 drive hooked up, the server's drive light functions normally (blinks when accessed), when I hook up the DLT, it just stays on. The only difference I can see is that the DLT is "differential" SCSI, which, AFAIK, just allows it to work with a longer bus. Is there something that has to be done to the host adapter to accomodate differential devices? TIA, James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 9:14: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 3A74137BB4E for ; Thu, 2 Mar 2000 09:14:31 -0800 (PST) (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 JAA28381; Thu, 2 Mar 2000 09:14:08 -0800 Date: Thu, 2 Mar 2000 09:14:04 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: up@3.am Cc: scsi@FreeBSD.ORG Subject: Re: Can't see DLT4000 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 Don't mix differential with single ended. It's an electrical thing- it's very bad to mix the two- you run the risk of damaging the SE components. On Thu, 2 Mar 2000 up@3.am wrote: > > I just upgraded our tape drive from a DDS-2 DAT to a Quantum DLT4000 and > can't seem to get the system to see the DLT, no matter what. If I switch > back to the DDS2 and reboot, mt sees it fine. A rundown: > > Both are External SCSI drives set to SCSI ID 4 > > used the same terminator and cable > > I've rebooted several times > > The SCSI host adapter is an on-board Adaptec AIC-7896 (Intel L440GX+) > using the second (B) SCSI bus. When I have the DDS-2 drive hooked up, the > server's drive light functions normally (blinks when accessed), when I > hook up the DLT, it just stays on. > > The only difference I can see is that the DLT is "differential" SCSI, > which, AFAIK, just allows it to work with a longer bus. Is there > something that has to be done to the host adapter to accomodate > differential devices? > > TIA, > > James Smallacombe PlantageNet, Inc. CEO and Janitor > up@3.am http://3.am > ========================================================================= > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 9:19:51 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by hub.freebsd.org (Postfix) with SMTP id 648F437BD29 for ; Thu, 2 Mar 2000 09:19:48 -0800 (PST) (envelope-from up@3.am) Received: (qmail 5515 invoked by uid 1825); 2 Mar 2000 17:19:47 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 2 Mar 2000 17:19:47 -0000 Date: Thu, 2 Mar 2000 12:19:47 -0500 (EST) From: X-Sender: up@richard2.pil.net To: Matthew Jacob Cc: scsi@FreeBSD.ORG Subject: Re: Can't see DLT4000 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 Thu, 2 Mar 2000, Matthew Jacob wrote: > Don't mix differential with single ended. It's an electrical thing- it's very > bad to mix the two- you run the risk of damaging the SE components. ok...but what if they're on a separate SCSI bus? I have the hard drives on channel A (LVD ultra everything) and the tape drive *alone* on channel B. Does that make a difference? > On Thu, 2 Mar 2000 up@3.am wrote: > > > > > I just upgraded our tape drive from a DDS-2 DAT to a Quantum DLT4000 and > > can't seem to get the system to see the DLT, no matter what. If I switch > > back to the DDS2 and reboot, mt sees it fine. A rundown: > > > > Both are External SCSI drives set to SCSI ID 4 > > > > used the same terminator and cable > > > > I've rebooted several times > > > > The SCSI host adapter is an on-board Adaptec AIC-7896 (Intel L440GX+) > > using the second (B) SCSI bus. When I have the DDS-2 drive hooked up, the > > server's drive light functions normally (blinks when accessed), when I > > hook up the DLT, it just stays on. > > > > The only difference I can see is that the DLT is "differential" SCSI, > > which, AFAIK, just allows it to work with a longer bus. Is there > > something that has to be done to the host adapter to accomodate > > differential devices? > > > > TIA, > > > > James Smallacombe PlantageNet, Inc. CEO and Janitor > > up@3.am http://3.am > > ========================================================================= > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > > > James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 9:26:29 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 5FDE737BD8C for ; Thu, 2 Mar 2000 09:26:27 -0800 (PST) (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 JAA28433; Thu, 2 Mar 2000 09:26:24 -0800 Date: Thu, 2 Mar 2000 09:26:24 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: up@3.am Cc: scsi@FreeBSD.ORG Subject: Re: Can't see DLT4000 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 > > > Don't mix differential with single ended. It's an electrical thing- it's very > > bad to mix the two- you run the risk of damaging the SE components. > > ok...but what if they're on a separate SCSI bus? I have the hard drives > on channel A (LVD ultra everything) and the tape drive *alone* on channel > B. Does that make a difference? Yes- normally that'd be the case if the second bus was indeed high voltage differential. *I* was confused by this too when I first got an LVD controller- I don't know of any that support low-voltage differential, single-ended *AND* high voltage differential- as far as I know, and maybe Ken/Justin will correct me on this, the LVD controllers we know of support SE/LowVoltageDiff- this does not include your DLT4000. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 9:43: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (castles502.castles.com [208.214.165.66]) by hub.freebsd.org (Postfix) with ESMTP id 0021037C34A for ; Thu, 2 Mar 2000 09:42:52 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA02472; Thu, 2 Mar 2000 09:43:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003021743.JAA02472@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: up@3.am Cc: scsi@freebsd.org Subject: Re: Can't see DLT4000 In-reply-to: Your message of "Thu, 02 Mar 2000 11:56:38 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Mar 2000 09:43:18 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The only difference I can see is that the DLT is "differential" SCSI, > which, AFAIK, just allows it to work with a longer bus. Is there > something that has to be done to the host adapter to accomodate > differential devices? You can't use that DLT with anything other than a HVD differential controller. Don't confuse this with LVD, which is designed for backwards support of single-ended devices. You can get a quite respectable, low-cost HVD differential controller from Corpsys - www.corpsys.com. -- \\ 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 Thu Mar 2 9:49:38 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (castles502.castles.com [208.214.165.66]) by hub.freebsd.org (Postfix) with ESMTP id 337E537BD8C for ; Thu, 2 Mar 2000 09:49:28 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id JAA02499; Thu, 2 Mar 2000 09:46:28 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003021746.JAA02499@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nanda@procsys.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: RAID controllers in FreeBSD 3.4 In-reply-to: Your message of "Thu, 02 Mar 2000 20:15:45 +0530." <38BE7E99.48A0@procsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Mar 2000 09:46:27 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Why there is no AMI driver,Mylex driver for FreeBSD version 3.4. Is > there any specific reason for that ? The drivers have actually been backported to 3.4 (hence some of my experience with the process), however they're not at this point part of the system. I don't maintain them as actively as I do the versions in 4.x, for the reasons I've already given. You can obtain both from http://www.freebsd.org/~msmith/RAID -- \\ 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 Thu Mar 2 9:53:18 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by hub.freebsd.org (Postfix) with SMTP id C728F37C5CA for ; Thu, 2 Mar 2000 09:53:14 -0800 (PST) (envelope-from up@3.am) Received: (qmail 8997 invoked by uid 1825); 2 Mar 2000 17:53:12 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 2 Mar 2000 17:53:12 -0000 Date: Thu, 2 Mar 2000 12:53:12 -0500 (EST) From: X-Sender: up@richard2.pil.net To: Mike Smith Cc: scsi@freebsd.org Subject: Re: Can't see DLT4000 In-Reply-To: <200003021743.JAA02472@mass.cdrom.com> 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 Well, it looks like it's time for an RMA for this DLT. Thanks everyone for the help. Whatever happened to SCSI backward compatibility? On Thu, 2 Mar 2000, Mike Smith wrote: > > The only difference I can see is that the DLT is "differential" SCSI, > > which, AFAIK, just allows it to work with a longer bus. Is there > > something that has to be done to the host adapter to accomodate > > differential devices? > > You can't use that DLT with anything other than a HVD differential > controller. Don't confuse this with LVD, which is designed for backwards > support of single-ended devices. > > You can get a quite respectable, low-cost HVD differential controller > from Corpsys - www.corpsys.com. > > -- > \\ 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 > James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 10: 2:36 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (castles502.castles.com [208.214.165.66]) by hub.freebsd.org (Postfix) with ESMTP id C375137BD5A; Thu, 2 Mar 2000 10:02:30 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA02578; Thu, 2 Mar 2000 10:02:47 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003021802.KAA02578@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: up@3.am Cc: Mike Smith , scsi@freebsd.org Subject: Re: Can't see DLT4000 In-reply-to: Your message of "Thu, 02 Mar 2000 12:53:12 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 02 Mar 2000 10:02:12 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Well, it looks like it's time for an RMA for this DLT. Thanks > everyone for the help. > > > Whatever happened to SCSI backward compatibility? > Whatever happened to doing research on a topic? HVD differential has been around for at least a decade; it's never been electrically compatible with single-ended SCSI. -- \\ 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 Thu Mar 2 10:33:13 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by hub.freebsd.org (Postfix) with SMTP id B35A237BDAC for ; Thu, 2 Mar 2000 10:33:10 -0800 (PST) (envelope-from up@3.am) Received: (qmail 13214 invoked by uid 1825); 2 Mar 2000 18:33:09 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 2 Mar 2000 18:33:09 -0000 Date: Thu, 2 Mar 2000 13:33:09 -0500 (EST) From: X-Sender: up@richard2.pil.net To: Mike Smith Cc: scsi@freebsd.org Subject: Re: Can't see DLT4000 In-Reply-To: <200003021802.KAA02578@mass.cdrom.com> 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 Thu, 2 Mar 2000, Mike Smith wrote: > > Well, it looks like it's time for an RMA for this DLT. Thanks > > everyone for the help. > > > > > > Whatever happened to SCSI backward compatibility? > > > > Whatever happened to doing research on a topic? HVD differential has > been around for at least a decade; it's never been electrically > compatible with single-ended SCSI. Please, blame this on my stupidity, not laziness. My research consisted of searching Quantum's site and asking the vendor sales rep if it made a difference. Differential may have been around for years, but this is my first encounter with it... Thanks again, James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 10:44: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 4FA9F37C481; Thu, 2 Mar 2000 10:44:22 -0800 (PST) (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 KAA28686; Thu, 2 Mar 2000 10:44:19 -0800 Date: Thu, 2 Mar 2000 10:44:19 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: up@3.am Cc: Mike Smith , scsi@FreeBSD.ORG Subject: Re: Can't see DLT4000 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 > > > Well, it looks like it's time for an RMA for this DLT. Thanks > > > everyone for the help. > > > > > > > > > Whatever happened to SCSI backward compatibility? > > > > > > > Whatever happened to doing research on a topic? HVD differential has > > been around for at least a decade; it's never been electrically > > compatible with single-ended SCSI. > > Please, blame this on my stupidity, not laziness. My research consisted > of searching Quantum's site and asking the vendor sales rep if it made a > difference. Differential may have been around for years, but this is my > first encounter with it... Mike hasn't had his morning cuppa yet... Look- it's an easy trap to fall into. Just get them to swap you for a single ended model- they *do* have them, or get a diff<>se converter from Parallan. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 10:46:18 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hawkwind.ncsa.uiuc.edu (hawkwind.ncsa.uiuc.edu [141.142.21.154]) by hub.freebsd.org (Postfix) with ESMTP id 9574D37BD5A for ; Thu, 2 Mar 2000 10:46:14 -0800 (PST) (envelope-from koziol@hawkwind.ncsa.uiuc.edu) Received: (from koziol@localhost) by hawkwind.ncsa.uiuc.edu (8.9.3/8.9.2) id MAA23979 for freebsd-scsi@freebsd.org; Thu, 2 Mar 2000 12:46:08 -0600 (CST) (envelope-from koziol) Message-Id: <200003021846.MAA23979@hawkwind.ncsa.uiuc.edu> Subject: Re: RAID controllers in FreeBSD 3.4 In-Reply-To: <200003021746.JAA02499@mass.cdrom.com> from Mike Smith at "Mar 2, 2000 09:46:27 am" To: freebsd-scsi@freebsd.org Date: Thu, 2 Mar 2000 12:46:08 -0600 (CST) From: koziol@ncsa.uiuc.edu Reply-To: koziol@ncsa.uiuc.edu X-Mailer: ELM [version 2.4ME+ PL72 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Howdy, Along these lines, is there a working driver for the DPT SmartRAID V yet? Simon Shapiro was working on one, but I haven't heard anything recently. Thanks, Quincey > > Why there is no AMI driver,Mylex driver for FreeBSD version 3.4. Is > > there any specific reason for that ? > > The drivers have actually been backported to 3.4 (hence some of my > experience with the process), however they're not at this point part of > the system. I don't maintain them as actively as I do the versions in > 4.x, for the reasons I've already given. > > You can obtain both from http://www.freebsd.org/~msmith/RAID > > -- > \\ 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 10:47:37 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 9AA8737BD75; Thu, 2 Mar 2000 10:47:34 -0800 (PST) (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 KAA28715; Thu, 2 Mar 2000 10:47:32 -0800 Date: Thu, 2 Mar 2000 10:47:32 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: up@3.am Cc: Mike Smith , scsi@FreeBSD.ORG Subject: Re: Can't see DLT4000 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 > Mike hasn't had his morning cuppa yet... Look- it's an easy trap to > fall into. Just get them to swap you for a single ended model- they *do* > have them, or get a diff<>se converter from Parallan. Or, as he said, get another controller- although I think people who by from corpsys are contributing to the worldwide lowering of moral standards.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 14:31:21 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from gta.com (gw.gta.com [199.120.225.5]) by hub.freebsd.org (Postfix) with ESMTP id 8ADCD37B598 for ; Thu, 2 Mar 2000 14:31:18 -0800 (PST) (envelope-from lab@gta.com) Received: from gta.com (GTA internal mail system) by gta.com id RAA89000; Thu, 2 Mar 2000 17:32:38 -0500 (EST) Date: Thu, 2 Mar 2000 17:32:38 -0500 (EST) From: Larry Baird Message-Id: <200003022232.RAA89000@gta.com> To: freebsd-scsi@freebsd.org Subject: Re: adaptec 29160? X-Newsgroups: freebsd.scsi In-Reply-To: <20000302090352.A13672@futuresouth.com> <20000302090012.B39306@panzer.kdm.org> Organization: Global Technology Associates, Inc. User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.3-STABLE (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <20000302090012.B39306@panzer.kdm.org> you wrote: > On Thu, Mar 02, 2000 at 09:03:52 -0600, Tim Tsai wrote: >> Is the Adaptec 29160 supported? I didn't find anything on the mailing >> list archives. > Yes, but only in -current, and they'll currently only run at 80MB/sec. Which driver supports the Adaptec 29160? I did some searching through source code and man pages on current recently looking for support for this controller without an luck. Thanks for the info, Larry -- ------------------------------------------------------------------------ Larry Baird | HTTP://www.gnatbox.com Global Technology Associates, Inc. | Orlando, FL Email: lab@gta.com | TEL 407-380-0220, FAX 407-380-6080 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 14:35:37 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 522E437B598 for ; Thu, 2 Mar 2000 14:35:33 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA42235; Thu, 2 Mar 2000 15:35:29 -0700 (MST) (envelope-from ken) Date: Thu, 2 Mar 2000 15:35:29 -0700 From: "Kenneth D. Merry" To: Larry Baird Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: adaptec 29160? Message-ID: <20000302153528.A42192@panzer.kdm.org> References: <20000302090352.A13672@futuresouth.com> <200003022232.RAA89000@gta.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003022232.RAA89000@gta.com>; from lab@gta.com on Thu, Mar 02, 2000 at 05:32:38PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 02, 2000 at 17:32:38 -0500, Larry Baird wrote: > In article <20000302090012.B39306@panzer.kdm.org> you wrote: > > On Thu, Mar 02, 2000 at 09:03:52 -0600, Tim Tsai wrote: > >> Is the Adaptec 29160 supported? I didn't find anything on the mailing > >> list archives. > > > Yes, but only in -current, and they'll currently only run at 80MB/sec. > Which driver supports the Adaptec 29160? I did some searching through > source code and man pages on current recently looking for support > for this controller without an luck. The ahc(4) driver. The adapters are listed in the man page, and the PCI IDs are in the driver. 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 Thu Mar 2 15: 0:44 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from gta.com (gw.gta.com [199.120.225.5]) by hub.freebsd.org (Postfix) with ESMTP id 6235737B549 for ; Thu, 2 Mar 2000 15:00:37 -0800 (PST) (envelope-from lab@gta.com) Received: from gta.com (GTA internal mail system) by gta.com with ESMTP id SAA89791 for ; Thu, 2 Mar 2000 18:02:00 -0500 (EST) Message-ID: <38BEF25A.E8A0121C@gta.com> Date: Thu, 02 Mar 2000 17:59:38 -0500 From: Larry Baird Reply-To: lab@gta.com Organization: GTA, Inc. X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Re: adaptec 29160? References: <20000302090352.A13672@futuresouth.com> <200003022232.RAA89000@gta.com> <20000302153528.A42192@panzer.kdm.org> Content-Type: text/plain; charset=iso-2022-jp Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ken, > The ahc(4) driver. The adapters are listed in the man page, and the PCI > IDs are in the driver. Thanks for the quick feedback. The system I checked against was one cut from the first 4.0 release canidate CD ISO image. The man pages for the ahc(4) don't mention 29160 or aic7899. Neither do the ones for current on www.freebsd.org (http://www.FreeBSD.org/cgi/man.cgi?query=ahc&apropos=0&sektion=0&manpath=FreeBSD+4.0-current&format=html). I'll cvsup this machine up to see if the correct man pages show up. I now realize I was looking at the wrong place for aic source code. I was incorrectly expected the code to be in /sys/pci instead of /sys/dev. It looks like I have been focused on network related devices for too long. (: Time to expand my source code horizons. (: Larry -- ------------------------------------------------------------------------ Larry Baird Global Technology Associates, Inc. | Orlando, FL Email: lab@gta.com | TEL 407-380-0220, FAX 407-380-6080 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 15:18:26 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 0CAAF37BD7B for ; Thu, 2 Mar 2000 15:18:23 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA42578; Thu, 2 Mar 2000 16:18:14 -0700 (MST) (envelope-from ken) Date: Thu, 2 Mar 2000 16:18:14 -0700 From: "Kenneth D. Merry" To: Larry Baird Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: adaptec 29160? Message-ID: <20000302161814.A42521@panzer.kdm.org> References: <20000302090352.A13672@futuresouth.com> <200003022232.RAA89000@gta.com> <20000302153528.A42192@panzer.kdm.org> <38BEF25A.E8A0121C@gta.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38BEF25A.E8A0121C@gta.com>; from lab@gta.com on Thu, Mar 02, 2000 at 05:59:38PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 02, 2000 at 17:59:38 -0500, Larry Baird wrote: > Ken, If you want me to respond, CC it to me. > > The ahc(4) driver. The adapters are listed in the man page, and the PCI > > IDs are in the driver. > Thanks for the quick feedback. The system I checked against was > one cut from the first 4.0 release canidate CD ISO image. The man > pages for the ahc(4) don't mention 29160 or aic7899. Neither do the > ones for current on www.freebsd.org > (http://www.FreeBSD.org/cgi/man.cgi?query=ahc&apropos=0&sektion=0&manpath=FreeBSD+4.0-current&format=html). The man page was updated February 14th. So my guess is that the CD you've got doesn't have that on there, and I suppose the man pages in the web interface are out of date as well. > I'll cvsup this machine up to see if the correct > man pages show up. > > I now realize I was looking at the wrong place for aic source code. I > was incorrectly expected the code to be in /sys/pci instead of > /sys/dev. It looks like I have been focused on network related > devices for too long. (: Time to expand my source code horizons. (: The PCI attach routines for a number of drivers were moved to the drivers' directory in sys/dev recently. (The ahc driver was one of them.) 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 Thu Mar 2 16:25: 7 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 5C23E37BEC2; Thu, 2 Mar 2000 16:25:00 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id BAA24817; Fri, 3 Mar 2000 01:12:15 +0100 (MET) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id AAA01634; Fri, 3 Mar 2000 00:34:24 +0100 (CET) (envelope-from wilko) Date: Fri, 3 Mar 2000 00:34:24 +0100 From: Wilko Bulte To: up@3.am Cc: Mike Smith , scsi@FreeBSD.ORG Subject: Re: Can't see DLT4000 Message-ID: <20000303003424.E1203@yedi.iaf.nl> References: <200003021743.JAA02472@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from up@3.am on Thu, Mar 02, 2000 at 12:53:12PM -0500 X-OS: FreeBSD yedi.iaf.nl 3.4-STABLE FreeBSD 3.4-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 02, 2000 at 12:53:12PM -0500, up@3.am wrote: > > Well, it looks like it's time for an RMA for this DLT. Thanks > everyone for the help. > > > Whatever happened to SCSI backward compatibility? > What happened to people reading manuals and/or standards? Really, this is as old as the SCSI standard. You might be able to find a differential Adaptec, say a 2944 or so. > On Thu, 2 Mar 2000, Mike Smith wrote: > > > > The only difference I can see is that the DLT is "differential" SCSI, > > > which, AFAIK, just allows it to work with a longer bus. Is there > > > something that has to be done to the host adapter to accomodate > > > differential devices? > > > > You can't use that DLT with anything other than a HVD differential > > controller. Don't confuse this with LVD, which is designed for backwards > > support of single-ended devices. > > > > You can get a quite respectable, low-cost HVD differential controller > > from Corpsys - www.corpsys.com. > > > > -- > > \\ 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 -- Wilko Bulte Arnhem, The Netherlands http://www.tcja.nl The FreeBSD Project: http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 21:50:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 5981037BF4D for ; Thu, 2 Mar 2000 21:50:24 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA40109; Thu, 2 Mar 2000 22:50:12 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA21078; Thu, 2 Mar 2000 22:49:59 -0700 (MST) Message-Id: <200003030549.WAA21078@harmony.village.org> To: Tim Tsai Subject: Re: adaptec 29160? Cc: scsi@FreeBSD.ORG In-reply-to: Your message of "Thu, 02 Mar 2000 09:03:52 CST." <20000302090352.A13672@futuresouth.com> References: <20000302090352.A13672@futuresouth.com> Date: Thu, 02 Mar 2000 22:49:59 -0700 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20000302090352.A13672@futuresouth.com> Tim Tsai writes: : Is the Adaptec 29160 supported? I didn't find anything on the mailing : list archives. Yes. Works for me. I have one in my system and it is *FAST*. Now all I need to get 160MB/s disks... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 22: 8:32 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 11EF437B6D0 for ; Thu, 2 Mar 2000 22:08:21 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA40140; Thu, 2 Mar 2000 23:08:13 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA21148; Thu, 2 Mar 2000 23:08:00 -0700 (MST) Message-Id: <200003030608.XAA21148@harmony.village.org> To: "Kenneth D. Merry" Subject: Re: adaptec 29160? Cc: Larry Baird , freebsd-scsi@FreeBSD.ORG In-reply-to: Your message of "Thu, 02 Mar 2000 16:18:14 MST." <20000302161814.A42521@panzer.kdm.org> References: <20000302161814.A42521@panzer.kdm.org> <20000302090352.A13672@futuresouth.com> <200003022232.RAA89000@gta.com> <20000302153528.A42192@panzer.kdm.org> <38BEF25A.E8A0121C@gta.com> Date: Thu, 02 Mar 2000 23:08:00 -0700 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <20000302161814.A42521@panzer.kdm.org> "Kenneth D. Merry" writes: : The man page was updated February 14th. So my guess is that the CD you've : got doesn't have that on there, and I suppose the man pages in the web : interface are out of date as well. Support was added Jan 7, 2000. These were only at U2 speeds, like Ken has already said. I've been using a 19160 since Feb 16 at about 2:00am. It was the cheapest adaptec controller I could find (a white box version was about $160 at Microwarehose at the time). It has two internal and one external connectors. One of the internal ones is LVD, 68pin. The other internal one is 50 pin SE, as is the external connector. The only thing that I'd wish for would be another 68 pin internal connection for SE, but since I have only LVD drives it didn't matter too much. Best deal around, if you want my opinion. The 19160 is so cheap because the Windows driver disables all the features of scsi that make it fast. Good thing the FreeBSD driver doesn't do this and gives you all the speed of a 29160 at $140 less. The 19160 has the same chipset as the 29160. I think you'll be quite happy with yours. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 22: 9: 3 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id BA1F837B919 for ; Thu, 2 Mar 2000 22:08:57 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id XAA40145; Thu, 2 Mar 2000 23:08:54 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id XAA21167; Thu, 2 Mar 2000 23:08:41 -0700 (MST) Message-Id: <200003030608.XAA21167@harmony.village.org> Subject: Re: adaptec 29160? Cc: Tim Tsai , scsi@FreeBSD.ORG In-reply-to: Your message of "Thu, 02 Mar 2000 22:49:59 MST." <200003030549.WAA21078@harmony.village.org> References: <200003030549.WAA21078@harmony.village.org> <20000302090352.A13672@futuresouth.com> Date: Thu, 02 Mar 2000 23:08:41 -0700 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <200003030549.WAA21078@harmony.village.org> Warner Losh writes: : In message <20000302090352.A13672@futuresouth.com> Tim Tsai writes: : : Is the Adaptec 29160 supported? I didn't find anything on the mailing : : list archives. : : Yes. Works for me. I have one in my system and it is *FAST*. Now : all I need to get 160MB/s disks... I hate to followup to myself, but I have the 19160, not the 29160. Same chipset, however. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 23: 7:19 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from procsys.com (PPP-190-83.bng.vsnl.net.in [203.197.190.83]) by hub.freebsd.org (Postfix) with SMTP id 7BBE237B5A3; Thu, 2 Mar 2000 23:07:01 -0800 (PST) (envelope-from nanda@procsys.com) Received: from nanda ([192.168.1.70]) by procsys.com with SMTP; Fri, 03 Mar 2000 12:33:32 +0800 Message-ID: <38BF6460.703A@procsys.com> Date: Fri, 03 Mar 2000 12:36:08 +0530 From: Nanda Kumar Reply-To: nanda@procsys.com X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: Mike Smith Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IOCTL support in SCSI block driver References: <200003010807.AAA04798@mass.cdrom.com> <38BE4879.F41@procsys.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am just resending the mail. After going through the code i am almost lost. I went through the mylex code to find how they implement the control interface. But i have some doubts regarding this. Mainly these doubts come since i am still quiete new to the FreeBSD world and don't have good text books regarding how to write device drivers etc. 1). In the user space how do i specify a controller to communicate with that ? For eg. if i want to open the device and a send an IOCTL how do i specify that ? In our case actual disks will be seen as part of target discovery done through the CAM SCSI interface. 2). I found that the while registering the character device the "softc" structure does not come to picture at all. But later while opening the device the "softc" structure is obtained using "devclass_get_softc". How is it obtained ? If there are some documents regarding these you can tell me and i will go through it. Regards, Nandan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Mar 2 23:49:59 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from netserv1.chg.ru (netserv1.chg.ru [193.233.46.3]) by hub.freebsd.org (Postfix) with ESMTP id 2D9D137B5A5; Thu, 2 Mar 2000 23:49:51 -0800 (PST) (envelope-from dima@netserv1.chg.ru) Received: (from dima@localhost) by netserv1.chg.ru (8.9.3/8.9.3) id KAA86144; Fri, 3 Mar 2000 10:48:53 +0300 (MSK) Date: Fri, 3 Mar 2000 10:48:53 +0300 (MSK) Message-Id: <200003030748.KAA86144@netserv1.chg.ru> From: Dmitry Sivachenko To: jreynold@sedona.ch.intel.com Cc: multimedia@freebsd.org, scsi@freebsd.org Cc: ken@kdm.org In-reply-to: <14525.37362.588361.780967@hip186.ch.intel.com> (message from John Reynolds~ on Wed, 1 Mar 2000 14:56:02 -0700 (MST)) Subject: Re: xpt* vs pass* (was Re: cdrecord ) References: <200003012107.AAA46366@netserv1.chg.ru> <200003012126.e21LQRx04404@orthanc.ab.ca> <14525.36350.446934.308565@hip186.ch.intel.com> <20000301145143.A33812@panzer.kdm.org> <14525.37362.588361.780967@hip186.ch.intel.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It needs both. It needs /dev/xpt0 to get a list of devices in the system, and it needs /dev/pass* to send commands to those devices. Thank you very much for your replies! Now I finally get it working! I burned CD with FreeBSD-4 RC2! The problem was that I didn't have pass0 device enabled in my kernel. Thanks for your help! --dima To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 3 1: 4: 0 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from hermes.mixx.net (hermes.mixx.net [212.84.196.2]) by hub.freebsd.org (Postfix) with ESMTP id 5DCAC37B5C4 for ; Fri, 3 Mar 2000 01:03:57 -0800 (PST) (envelope-from news-list.freebsd.scsi@innominate.de) Received: from mate.bln.innominate.de (gatekeeper.innominate.de [212.5.16.129]) by hermes.mixx.net (Postfix) with ESMTP id 393AA59807 for ; Fri, 3 Mar 2000 10:03:55 +0100 (CET) Received: by mate.bln.innominate.de (Postfix, from userid 9) id DA8D92CA6D; Fri, 3 Mar 2000 10:03:54 +0100 (CET) From: news-list.freebsd.scsi@innominate.de (Thomas Graichen) Reply-To: Thomas Graichen X-Newsgroups: innominate.bln.list.freebsd.scsi Subject: shared scsi busses Date: 3 Mar 2000 09:03:53 GMT Organization: innominate AG, Berlin, Germany Lines: 18 Message-ID: Reply-To: graichen@innominate.de X-Trace: mate.bln.innominate.de 952074233 10057 10.0.0.213 (3 Mar 2000 09:03:53 GMT) X-Complaints-To: news@innominate.de User-Agent: tin/1.4.2-20000205 ("Possession") (UNIX) (FreeBSD/4.0-RELEASE (i386)) To: scsi@FreeBSD.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hello - i'm currently trying to get a shared scsi system running (a disk on a shared scsi line between two computers) but have so far some problems with all this (cabling, bios etc) so i am asking here what one has to keep an eye on and if anyone here has done this already (i think yes - because the tertiary disk project used it i think) - so any experiences, hints, pointers to this topic here ? (btw. my current test environment are two adaptec 2940au on scsi id's 6 & 7 with reset on bootup disabled so far) a lot of thanks in advance t -- graichen@innominate.de innominate AG networking people fon: +49.30.308806-13 fax: -77 web: http://innominate.de pgp: /pgp/tg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 3 11: 9:42 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id 25BC437B64E for ; Fri, 3 Mar 2000 11:09:36 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id UAA22263; Fri, 3 Mar 2000 20:03:37 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id UAA03234; Fri, 3 Mar 2000 20:03:34 +0100 (CET) From: Juergen Lock Date: Fri, 3 Mar 2000 20:03:33 +0100 To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: running a cleaning tape with chio (not!) Message-ID: <20000303200333.B1434@saturn.kn-bremen.de> References: <20000301020107.A1387@saturn.kn-bremen.de> <20000229213126.A27011@panzer.kdm.org> <20000301212812.A30440@saturn.kn-bremen.de> <20000302000359.A36748@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.7i In-Reply-To: <20000302000359.A36748@panzer.kdm.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Mar 02, 2000 at 12:04:00AM -0700, Kenneth D. Merry wrote: > On Wed, Mar 01, 2000 at 21:28:12 +0100, Juergen Lock wrote: > > On Tue, Feb 29, 2000 at 09:31:26PM -0700, Kenneth D. Merry wrote: > > > On Wed, Mar 01, 2000 at 02:01:08 +0100, Juergen Lock wrote: > > > > Hi! > > > > > > > > Is this supposed to work? it didn't for me today, it did load it > > > > and also print on the console its a cleaning tape, but when the > > > > drive ejected it after doing its thing (normal behaviour with > > > > cleaning tapes at least on dds drives), it tried to load it again. :( > > > > > > > > This is a 6-slot hp dds2 autoloader, and 3.4-stable... > > > > > > Did you try to do I/O to the drive while the cleaning tape was in? The > > > > No, no process did anything on /dev/(n)rsa0, the only one that was > > talking to it was the chio. > > Hmm, I guess I'm used to changers where the tape mechanism and the changer > mechanism are relatively separate. In most cases the changer has little > idea about what type of tape it put in the drive. The only thing it might > know is an id from a barcode label. > > Your changer is evidently different, as the error below suggests -- it > indeed came from the changer LUN on the device. > Yep, and this is probably also whats causing the problem... > >[syslog snipped] > >From the logs above, it looks like you tried to move the tape into the > drive twice. > Except of course that i didn't! > Note that the first and second move medium commands are identical -- i.e. > same source and destination. Exactly. I _suspect_ what happens (tho i won't be able to check before next week now) is the drive ejecting the tape causing the move medium to return with a unit attention, or maybe some other kind of returncode that the driver then treats as a temporary failure so it simply retries the command. > > > My guess is that your problem is that your autoloader is configured in > > > autoloader mode instead of changer mode or something. > > > > > Hmm i didn't have the sucker's manual handy to check this, so > > at the moment i can only say that chio does work on it with > > regular tapes... > > Ahh. So you probably have it in changer mode. > Yep i would guess so too. :) Regards, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 3 12: 3:55 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from heras.host4u.net (heras.host4u.net [209.150.128.13]) by hub.freebsd.org (Postfix) with ESMTP id 6F14637B64E for ; Fri, 3 Mar 2000 12:03:47 -0800 (PST) (envelope-from mike@rockatronic.com) Received: from mobile (cr42910-a.slnt1.on.wave.home.com [24.114.50.29]) by heras.host4u.net (8.8.5/8.8.5) with SMTP id OAA27827 for ; Fri, 3 Mar 2000 14:03:36 -0600 Message-ID: <009001bf853d$4f49d040$3517390a@localdomain> From: "Mike" To: Subject: Adaptec AHA2930CU / AIC7859 failure Date: Fri, 3 Mar 2000 13:21:28 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, I've had no success getting a recent vintage North American market Adaptec 2930CU to work. I've CVSuped and tried both the v.3 stable and 4 current source trees. Nothing works. Just times out on probe (dmesg below). The card works fine with Redhat Linux 6.1 and Windows 98. Its not a cabling or term. problem as the other OSes work and the errors remain identical whether there is an external cable and/or device attached or not. There is no internal device. I've tried manual term. as well. I called Adaptec to confirm the controller chip; they say AIC7859 BT. Read the sources, seems to jibe OK, as in AIC7859. Note, on probe Linux loads the AIC7860 not 7859. I tried substituting the 7850, 7855,7860 and 7870 by modifiying the features line in the setup routine for 2930CU in aic7xxx.h. Recompile, test. etc. etc. No success. Also tried all reasonable permutations on Adaptec SCSI setup (ctrl-a) just for "fun". No success. Any insight would be greatly appreciated. Thanks Mike FreeBSD 3.4-STABLE #0: Fri Mar 3 08:54:33 EST 2000 root@stang.localdomain:/usr/src/sys/compile/STANG Timecounter "i8254" frequency 1193182 Hz CPU: Pentium/P55C (232.96-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x543 Stepping = 3 Features=0x8001bf real memory = 67108864 (65536K bytes) avail memory = 61747200 (60300K bytes) Preloaded elf kernel "kernel" at 0xc035c000. Probing for devices on PCI bus 0: chip0: rev 0x01 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip2: rev 0x01 on pci0.7.3 vga0: <3Dfx Voodoo 3 graphics accelerator> rev 0x01 int a irq 0 on pci0.8.0 vr0: rev 0x06 int a irq 10 on pci0.10.0 vr0: Ethernet address: 00:50:ba:c2:a1:73 vr0: autoneg complete, link status good (half-duplex, 100Mbps) ahc0: rev 0x03 int a irq 11 on pci0.11.0 ahc0: aic7859 Single Channel A, SCSI Id=7, 3/255 SCBs Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 fe0 not found at 0x300 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model IntelliMouse, device ID 3 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 4884MB (10003392 sectors), 9924 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordy acd0: drive speed 171 - 8593KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA, packet track acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked wt0 not found at 0x300 mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 ppc0 at 0x378 irq 7 flags 0x40 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 ie0: unknown board_id: f000 ie0 not found at 0x300 ep0 not found at 0x300 ex0 not found le0 not found at 0x300 lnc0 not found at 0x280 cs0 not found at 0x300 ze0 not found at 0x300 zp0 not found at 0x300 adv0 not found at 0x330 bt0 not found at 0x134 aha0 not found at 0x134 aic0 not found vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Intel Pentium detected, installing workaround for F00F bug Waiting 8 seconds for SCSI devices to settle (probe1:ahc0:0:1:0): SCB 0xd - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe1:ahc0:0:1:0): Queuing a BDR SCB (probe1:ahc0:0:1:0): SCB 0xd - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe1:ahc0:0:1:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 6 SCBs aborted (probe2:ahc0:0:2:0): SCB 0xd - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe2:ahc0:0:2:0): Queuing a BDR SCB (probe2:ahc0:0:2:0): SCB 0xd - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe2:ahc0:0:2:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 6 SCBs aborted (probe3:ahc0:0:3:0): SCB 0xd - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe3:ahc0:0:3:0): Queuing a BDR SCB (probe3:ahc0:0:3:0): SCB 0xd - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe3:ahc0:0:3:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 6 SCBs aborted (probe5:ahc0:0:5:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe5:ahc0:0:5:0): Queuing a BDR SCB (probe5:ahc0:0:5:0): SCB 0x8 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe5:ahc0:0:5:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 5 SCBs aborted (probe1:ahc0:0:1:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe1:ahc0:0:1:0): Queuing a BDR SCB (probe1:ahc0:0:1:0): SCB 0xc - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe1:ahc0:0:1:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 4 SCBs aborted (probe3:ahc0:0:3:0): SCB 0x9 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe3:ahc0:0:3:0): Queuing a BDR SCB (probe3:ahc0:0:3:0): SCB 0x9 - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe3:ahc0:0:3:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 3 SCBs aborted (probe1:ahc0:0:1:0): SCB 0xb - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe1:ahc0:0:1:0): Queuing a BDR SCB (probe1:ahc0:0:1:0): SCB 0xb - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe1:ahc0:0:1:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe3:ahc0:0:3:0): SCB 0xb - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe3:ahc0:0:3:0): Queuing a BDR SCB (probe3:ahc0:0:3:0): SCB 0xb - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe3:ahc0:0:3:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe1:ahc0:0:1:0): SCB 0xb - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe1:ahc0:0:1:0): Queuing a BDR SCB (probe1:ahc0:0:1:0): SCB 0xb - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe1:ahc0:0:1:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 2 SCBs aborted (probe1:ahc0:0:1:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe1:ahc0:0:1:0): Queuing a BDR SCB (probe1:ahc0:0:1:0): SCB 0xa - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0x188 (probe1:ahc0:0:1:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted changing root device to wd0s2a To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 3 13:30:12 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 3E49F37B709; Fri, 3 Mar 2000 13:30:03 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id NAA01210; Fri, 3 Mar 2000 13:29:59 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003032129.NAA01210@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: up@3.am, Mike Smith , scsi@FreeBSD.ORG Subject: Re: Can't see DLT4000 In-reply-to: Your message of "Thu, 02 Mar 2000 10:47:32 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Mar 2000 13:29:59 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > Mike hasn't had his morning cuppa yet... Look- it's an easy trap to > > fall into. Just get them to swap you for a single ended model- they *do* > > have them, or get a diff<>se converter from Parallan. > > Or, as he said, get another controller- although I think people who by from > corpsys are contributing to the worldwide lowering of moral standards.. Tell me where else to buy cheap-and-nasty UW controllers that work in Alphas, and I'll never give them another cent. They get my business simply because they have the products I need; more or less the deciding criterion for me. -- \\ 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 Fri Mar 3 13:53:53 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 9384137B6C4; Fri, 3 Mar 2000 13:53:42 -0800 (PST) (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 NAA00319; Fri, 3 Mar 2000 13:53:39 -0800 Date: Fri, 3 Mar 2000 13:53:38 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: Can't see DLT4000 In-Reply-To: <200003032129.NAA01210@mass.cdrom.com> 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 > > > > > Mike hasn't had his morning cuppa yet... Look- it's an easy trap to > > > fall into. Just get them to swap you for a single ended model- they *do* > > > have them, or get a diff<>se converter from Parallan. > > > > Or, as he said, get another controller- although I think people who by from > > corpsys are contributing to the worldwide lowering of moral standards.. > > Tell me where else to buy cheap-and-nasty UW controllers that work in > Alphas, and I'll never give them another cent. They get my business > simply because they have the products I need; more or less the deciding > criterion for me. Work as in 'boot from'? Define 'cheap'. Going to the LSILOGIC web pages http://www.lsilogic.com/products/io_standard/ioshabs/iosbddescrp.htm#HABkits and then following from there, it looks like you can get a SYM875 kit @ Q1 for about 115$ from Insight Electronics: http://www.insight-electronics.com/cgi-bin/catalog.cgi?cart_id=8108825.11228&start=0&first=first&supplier=SYM&category=&keywords=SYM8750SP+&limit=10&search_request_button=BEGIN+SEARCH I dunno if Insight is an enduser seller.. I'm thinking about getting a Calif. reseller id- so maybe it should be 'me' as a place to get this from- I'll buy 5 or so at a time from Bell or Ingram or Insight and resell them @ cost + sales tax- primarily so I can get a better source of Qlogic boards.. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Mar 3 14:31: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 389CA37B538 for ; Fri, 3 Mar 2000 14:31:02 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id OAA01856; Fri, 3 Mar 2000 14:31:39 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003032231.OAA01856@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nanda@procsys.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IOCTL support in SCSI block driver In-reply-to: Your message of "Fri, 03 Mar 2000 12:36:08 +0530." <38BF6460.703A@procsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Mar 2000 14:31:39 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I am just resending the mail. After going through the code i am almost > lost. > > I went through the mylex code to find how they implement the control > interface. But i have some doubts regarding this. Mainly these doubts > come since i am still quiete new to the FreeBSD world and don't have > good text books regarding how to write device drivers etc. > > 1). In the user space how do i specify a controller to communicate with > that ? For eg. if i want to open the device and a send an IOCTL how do > i specify that ? In our case actual disks will be seen as part of target > discovery done through the CAM SCSI interface. The controller code instantiates a device for each controller. The Mylex driver is still doing this the "old" way: /* * Register the control device on first attach. */ if (cdev_registered++ == 0) cdevsw_add(&mlx_cdevsw); It would be more correct for it to use: sc->mlx_dev_t = make_dev(&mlx_cdevsw, device_get_unit(sc->mlx_dev), 0, 0, S_IRUSR|S_IRUSRW, "mlx%d", device_get_unit(sc->mlx_dev)); and then use destroy_dev(sc->mlx_dev_t); in the corresponding detach method. (makes note to self to fix Mylex driver thusly). > 2). I found that the while registering the character device the "softc" > structure does not come to picture at all. But later while opening the > device the "softc" structure is obtained using "devclass_get_softc". > How is it obtained ? If there are some documents regarding these you can > tell me and i will go through it. The bus code is responsible for tracking the softc structure; the minor number for the device maps directly to the controller instance number, so /dev/mlx0 has minor number 0, and thus you ask for the softc pointer for instance 0 of mlx_devclass. -- \\ 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 Fri Mar 3 19: 2:16 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.184]) by hub.freebsd.org (Postfix) with ESMTP id 0867E37B70F for ; Fri, 3 Mar 2000 19:02:13 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id TAA04334; Fri, 3 Mar 2000 19:02:25 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003040302.TAA04334@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Kenneth D. Merry" Cc: scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-reply-to: Your message of "Wed, 01 Mar 2000 23:44:34 MST." <20000301234434.A36537@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 03 Mar 2000 19:02:25 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > In any case, try putting a printf inside the SS_TUR case in > > > cam_periph_error() in cam_periph.c, to see whether the quirk entry is > > > getting matched correctly and therefore whether the test unit ready is > > > getting issued. > > > > Hmm. Trying: > > > > if (((err_action & SS_MASK) == SS_TUR) > > && save_ccb != NULL > > && ccb->ccb_h.retry_count > 0) { > > > > printf("cam_periph_error: sending TUR\n"); > > > > I never see the above message. > > Okay, my guess is that I flubbed the quirk entry somehow. Anyway, try the > attached patch for scsi_all.c. It makes the quirk entry much more generic > in the hopes that it'll match. Still no joy. The quirk strings themselves are matching OK; I've added debugging code sufficient to determine that (slightly reformatted for clarity): (ch0:ahc0:0:3:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 (ch0:ahc0:0:3:0): UNIT ATTENTION asc:29,0 cam_strmatch: compare 'SPECTRA STL-8000 1.940 0 0 ' with ' SPECT*' MATCH cam_strmatch: compare 'STL-8000 1.940 0 0 ' with ' *' MATCH cam_strmatch: compare '1.940 0 0 ' with ' *' MATCH (ch0:ahc0:0:3:0): Power on, reset, or bus device reset occurred For what it's worth, I _only_ get these matches when it's in the middle of printing the "UNIT ATTENTION" messages. -- \\ 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 Sat Mar 4 3: 7:18 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from procsys.com (PPP-190-101.bng.vsnl.net.in [203.197.190.101]) by hub.freebsd.org (Postfix) with SMTP id 0920637B7DD; Sat, 4 Mar 2000 03:06:52 -0800 (PST) (envelope-from nanda@procsys.com) Received: from nanda ([192.168.1.70]) by procsys.com with SMTP; Sat, 04 Mar 2000 14:59:55 +0800 Message-ID: <38C0D83D.5A21@procsys.com> Date: Sat, 04 Mar 2000 15:02:45 +0530 From: Nanda Kumar Reply-To: nanda@procsys.com X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: Mike Smith Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IOCTL support in SCSI block driver References: <200003032231.OAA01856@mass.cdrom.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I didn't find the make_dev() function in FreeBSD 3.4 version. Is there any equivalent function to mak_edev () in 3.4 ? Does the make_dev () creates an inode also for the device ? Regards, Nandan >Mike Smith wrote: > > > I am just resending the mail. After going through the code i am almost > > lost. > > > > I went through the mylex code to find how they implement the control > > interface. But i have some doubts regarding this. Mainly these doubts > > come since i am still quiete new to the FreeBSD world and don't have > > good text books regarding how to write device drivers etc. > > > > 1). In the user space how do i specify a controller to communicate with > > that ? For eg. if i want to open the device and a send an IOCTL how do > > i specify that ? In our case actual disks will be seen as part of target > > discovery done through the CAM SCSI interface. > > The controller code instantiates a device for each controller. The Mylex > driver is still doing this the "old" way: > > /* > * Register the control device on first attach. > */ > if (cdev_registered++ == 0) > cdevsw_add(&mlx_cdevsw); > > It would be more correct for it to use: > > sc->mlx_dev_t = make_dev(&mlx_cdevsw, device_get_unit(sc->mlx_dev), > 0, 0, S_IRUSR|S_IRUSRW, > "mlx%d", device_get_unit(sc->mlx_dev)); > > and then use > > destroy_dev(sc->mlx_dev_t); > > in the corresponding detach method. > > (makes note to self to fix Mylex driver thusly). > > > 2). I found that the while registering the character device the "softc" > > structure does not come to picture at all. But later while opening the > > device the "softc" structure is obtained using "devclass_get_softc". > > How is it obtained ? If there are some documents regarding these you can > > tell me and i will go through it. > > The bus code is responsible for tracking the softc structure; the minor > number for the device maps directly to the controller instance number, so > /dev/mlx0 has minor number 0, and thus you ask for the softc pointer for > instance 0 of mlx_devclass. > > -- > \\ 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 Sat Mar 4 4:37:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id 587BE37B74F for ; Sat, 4 Mar 2000 04:37:05 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id NAA07442; Sat, 4 Mar 2000 13:31:01 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id NAA65939; Sat, 4 Mar 2000 13:32:25 +0100 (CET) Date: Sat, 4 Mar 2000 13:32:25 +0100 (CET) From: Juergen Lock Message-Id: <200003041232.NAA65939@saturn.kn-bremen.de> To: uwe.laverenz@difi.de Subject: Re: Tandberg SLR-50 X-Newsgroups: local.list.freebsd.scsi In-Reply-To: <38BBA179.6DE313AA@difi.de> Organization: home Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <38BBA179.6DE313AA@difi.de> you write: >Hi, > >one of our HP DDS3 streamers died recently and I'd like to replace both >our HP-drives with 2 Tandberg SLR-50 streamers. I think the Tandbergs >(drives and media) are far more robust and reliable. > Yes at least the technology sure is (successor of QIC), no rotatig heads for one... >My questions: is this the right way to go under FreeBSD? Are there any >known problems with these drives? What are your experiences? Well i haven't (yet?) tried such a drive but i wouldn't expect problems. (i only have an old QIC525 drive at home which i got back when my largest disk was 240MB... still works, tho it rarely gets used now cause CDRW media are now much cheaper than QIC525 tapes. but i think i didn't even have to clean the heads yet, the thing just runs and runs...) Regards, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Mar 4 4:37:21 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from blaubaer.kn-bremen.de (blaubaer.kn-bremen.de [195.37.179.254]) by hub.freebsd.org (Postfix) with ESMTP id 9FDA937B78A; Sat, 4 Mar 2000 04:37:10 -0800 (PST) (envelope-from nox@saturn.kn-bremen.de) Received: from saturn.kn-bremen.de (uucp@localhost) by blaubaer.kn-bremen.de (8.9.1/8.9.1) with UUCP id NAA07439; Sat, 4 Mar 2000 13:30:59 +0100 Received: (from nox@localhost) by saturn.kn-bremen.de (8.9.3/8.8.5) id NAA65118; Sat, 4 Mar 2000 13:02:00 +0100 (CET) Date: Sat, 4 Mar 2000 13:02:00 +0100 (CET) From: Juergen Lock Message-Id: <200003041202.NAA65118@saturn.kn-bremen.de> To: smp@csn.net Subject: Re: chio trap with not-ready changer X-Newsgroups: local.list.freebsd.scsi In-Reply-To: <200003011637.JAA10612@Ilsa.StevesCafe.com> References: Organization: home Cc: "Chris D. Faulhaber" , Mike Smith , "Kenneth D. Merry" , scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <200003011637.JAA10612@Ilsa.StevesCafe.com> you write: >> On Tue, 29 Feb 2000, Mike Smith wrote: >> >> > >> > Ok, after some interesting side trips I'm happily up and talking to our >> > new (well, new-old) SpectraLogic STL-8000. There's only one catch so far >> ... >> I used to service/support these beasts (as a VAR) and have found that they >> will cause various OS's (NT/Netware/SCO) to hang if you don't let them >> fully initialize before booting...very poor firmware >> design. Unfortunately, we never found a reasonable work-around other than >> to wait. >> >> ----- >> Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org > >So our sony sdt9000 just died (after several years of hard service) and I >figured I would pop for a sony tsl-s9000 changer, expecting it would "just >work". With all this discussion of funky changers, I decided I should ask, >does anyone successfully use the sony tsl changer with either chio or amanda? Well i think i could try hooking up our sony dds3 to a bsd box to check chio behaviour... (its on a nt box cause amanda can't dump filesystems larger than one tape, so we still have to do those with agent.be. :( ) >Any other DDS changers that someone recommends (lower end of budget)? The hp 6-slot dds2 drive seems to have no problems with chio (and amanda with a small patch), as long as you walk to the box and push front panel buttons when you need to run the cleaning tape. (see other thread. but i haven't yet given up hope that that can't be fixed...) HTH, -- Juergen Lock (remove dot foo from address to reply) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Mar 4 11: 4:45 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (castles511.castles.com [208.214.165.75]) by hub.freebsd.org (Postfix) with ESMTP id 3693537B864 for ; Sat, 4 Mar 2000 11:04:41 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id LAA04384; Sat, 4 Mar 2000 11:05:18 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200003041905.LAA04384@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: nanda@procsys.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IOCTL support in SCSI block driver In-reply-to: Your message of "Sat, 04 Mar 2000 15:02:45 +0530." <38C0D83D.5A21@procsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Mar 2000 11:05:18 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi, > > I didn't find the make_dev() function in FreeBSD 3.4 version. Is there > any equivalent function to mak_edev () > in 3.4 ? Use the cdevsw_add() function in the example below. But remember that you're not writing for 3.4, you're writing for 4.0. > Does the make_dev () creates an inode also for the device ? No. > Regards, > Nandan > > >Mike Smith wrote: > > > > > I am just resending the mail. After going through the code i am almost > > > lost. > > > > > > I went through the mylex code to find how they implement the control > > > interface. But i have some doubts regarding this. Mainly these doubts > > > come since i am still quiete new to the FreeBSD world and don't have > > > good text books regarding how to write device drivers etc. > > > > > > 1). In the user space how do i specify a controller to communicate with > > > that ? For eg. if i want to open the device and a send an IOCTL how do > > > i specify that ? In our case actual disks will be seen as part of target > > > discovery done through the CAM SCSI interface. > > > > The controller code instantiates a device for each controller. The Mylex > > driver is still doing this the "old" way: > > > > /* > > * Register the control device on first attach. > > */ > > if (cdev_registered++ == 0) > > cdevsw_add(&mlx_cdevsw); > > > > It would be more correct for it to use: > > > > sc->mlx_dev_t = make_dev(&mlx_cdevsw, device_get_unit(sc->mlx_dev), > > 0, 0, S_IRUSR|S_IRUSRW, > > "mlx%d", device_get_unit(sc->mlx_dev)); > > > > and then use > > > > destroy_dev(sc->mlx_dev_t); > > > > in the corresponding detach method. > > > > (makes note to self to fix Mylex driver thusly). > > > > > 2). I found that the while registering the character device the "softc" > > > structure does not come to picture at all. But later while opening the > > > device the "softc" structure is obtained using "devclass_get_softc". > > > How is it obtained ? If there are some documents regarding these you can > > > tell me and i will go through it. > > > > The bus code is responsible for tracking the softc structure; the minor > > number for the device maps directly to the controller instance number, so > > /dev/mlx0 has minor number 0, and thus you ask for the softc pointer for > > instance 0 of mlx_devclass. > > > > -- > > \\ 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 > -- \\ 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 Sat Mar 4 15:10:59 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 5603837B89E; Sat, 4 Mar 2000 15:10:55 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA61325; Sat, 4 Mar 2000 16:10:55 -0700 (MST) (envelope-from ken) Date: Sat, 4 Mar 2000 16:10:54 -0700 From: "Kenneth D. Merry" To: Mike Smith Cc: scsi@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: chio trap with not-ready changer Message-ID: <20000304161054.A61108@panzer.kdm.org> References: <20000301234434.A36537@panzer.kdm.org> <200003040302.TAA04334@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003040302.TAA04334@mass.cdrom.com>; from msmith@FreeBSD.ORG on Fri, Mar 03, 2000 at 07:02:25PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Mar 03, 2000 at 19:02:25 -0800, Mike Smith wrote: > > > > In any case, try putting a printf inside the SS_TUR case in > > > > cam_periph_error() in cam_periph.c, to see whether the quirk entry is > > > > getting matched correctly and therefore whether the test unit ready is > > > > getting issued. > > > > > > Hmm. Trying: > > > > > > if (((err_action & SS_MASK) == SS_TUR) > > > && save_ccb != NULL > > > && ccb->ccb_h.retry_count > 0) { > > > > > > printf("cam_periph_error: sending TUR\n"); > > > > > > I never see the above message. > > > > Okay, my guess is that I flubbed the quirk entry somehow. Anyway, try the > > attached patch for scsi_all.c. It makes the quirk entry much more generic > > in the hopes that it'll match. > > Still no joy. The quirk strings themselves are matching OK; I've added > debugging code sufficient to determine that (slightly reformatted for > clarity): > > (ch0:ahc0:0:3:0): MODE SENSE(06). CDB: 1a 0 1d 0 20 0 > (ch0:ahc0:0:3:0): UNIT ATTENTION asc:29,0 > cam_strmatch: compare 'SPECTRA STL-8000 1.940 0 0 ' > with ' SPECT*' > MATCH > cam_strmatch: compare 'STL-8000 1.940 0 0 ' > with ' *' > MATCH > cam_strmatch: compare '1.940 0 0 ' > with ' *' > MATCH > (ch0:ahc0:0:3:0): Power on, reset, or bus device reset occurred > > For what it's worth, I _only_ get these matches when it's in the middle > of printing the "UNIT ATTENTION" messages. scsi_sense_desc() is called from scsi_sense_print(), so that's why you're getting those messages. What this means is that scsi_error_action() isn't getting called from cam_periph_error(). Oooh, I think I know what may be going on here. I suspect you're hitting the following case in cam_periph_error(): } else { /* decrement the number of retries */ retry = ccb->ccb_h.retry_count > 0; if (retry) ccb->ccb_h.retry_count--; /* * If it was aborted with no * clue as to the reason, just * retry it again. */ error = ERESTART; } You hit that when there is a SCSI error, but autosense failed, and there are still retries left. That would explain why the retry count is getting decremented, and ERESTART is returned, and why you never get into scsi_error_action(). So this means that the request sense is failing, likely due to the unit attention condition. That's pretty lame. You might want to put a printf in the above piece of code in cam_periph_error() just to make sure that's what is happening. I don't have any ideas right off on how to solve this without a major kludge. (Like adding an additional probe state in the changer driver that sends a test unit ready before the mode sense..) I'll think about it and run it by Justin (CCed) as well. You might make an ideal beta tester for his error recovery code rewrite. :) (I don't know if it's ready for testers just yet, though.) One of the things I think he's planning on doing is issuing a request sense when autosense fails. I'm not sure how much that would help in this case, but it might. 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 Sat Mar 4 15:25:20 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id CC7C537B8A0; Sat, 4 Mar 2000 15:25:17 -0800 (PST) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id QAA24066; Sat, 4 Mar 2000 16:25:57 -0700 (MST) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <200003042325.QAA24066@caspian.plutotech.com> X-Mailer: exmh version 2.1.0 09/18/1999 To: "Kenneth D. Merry" Cc: Mike Smith , scsi@FreeBSD.ORG, gibbs@FreeBSD.ORG Subject: Re: chio trap with not-ready changer In-reply-to: Your message of "Sat, 04 Mar 2000 16:10:54 MST." <20000304161054.A61108@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 04 Mar 2000 16:25:57 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Oooh, I think I know what may be going on here. I suspect you're hitting >the following case in cam_periph_error(): > > } else { > /* decrement the number of retries */ > retry = ccb->ccb_h.retry_count > 0; > if (retry) > ccb->ccb_h.retry_count--; > /* > * If it was aborted with no > * clue as to the reason, just > * retry it again. > */ > error = ERESTART; > } > >You hit that when there is a SCSI error, but autosense failed, and there >are still retries left. If the autosense failed, the system would not print out "Unit Attention...". You have to have sense information for that. >I'll think about it and run it by Justin (CCed) as well. You might make >an ideal beta tester for his error recovery code rewrite. :) (I don't >know if it's ready for testers just yet, though.) I think it is in good enough shape to send out. I just need to verify one more thing. >One of the things I think he's planning on doing is issuing a request sense >when autosense fails. I'm not sure how much that would help in this case, >but it might. Yes, it does perform sense retrieval in that case. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Mar 4 15:29:31 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 5747537B8D5; Sat, 4 Mar 2000 15:29:28 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA61521; Sat, 4 Mar 2000 16:29:27 -0700 (MST) (envelope-from ken) Date: Sat, 4 Mar 2000 16:29:27 -0700 From: "Kenneth D. Merry" To: "Justin T. Gibbs" Cc: Mike Smith , scsi@FreeBSD.ORG Subject: Re: chio trap with not-ready changer Message-ID: <20000304162927.A61483@panzer.kdm.org> References: <20000304161054.A61108@panzer.kdm.org> <200003042325.QAA24066@caspian.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003042325.QAA24066@caspian.plutotech.com>; from gibbs@FreeBSD.ORG on Sat, Mar 04, 2000 at 04:25:57PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Mar 04, 2000 at 16:25:57 -0700, Justin T. Gibbs wrote: > >Oooh, I think I know what may be going on here. I suspect you're hitting > >the following case in cam_periph_error(): > > > > } else { > > /* decrement the number of retries */ > > retry = ccb->ccb_h.retry_count > 0; > > if (retry) > > ccb->ccb_h.retry_count--; > > /* > > * If it was aborted with no > > * clue as to the reason, just > > * retry it again. > > */ > > error = ERESTART; > > } > > > >You hit that when there is a SCSI error, but autosense failed, and there > >are still retries left. > > If the autosense failed, the system would not print out "Unit Attention...". > You have to have sense information for that. The sense information that Mike included in his mail was from some debugging stuff I told him to put in the driver. Also, the changer driver prints out SCSI sense information if the CAM status is CAM_SCSI_STATUS_ERROR. It doesn't check the CAM_AUTOSNS_VALID status bit. My guess is that the drive is sending back sense information, but maybe it's sending it back with check condition set? > >I'll think about it and run it by Justin (CCed) as well. You might make > >an ideal beta tester for his error recovery code rewrite. :) (I don't > >know if it's ready for testers just yet, though.) > > I think it is in good enough shape to send out. I just need to verify > one more thing. Cool. > >One of the things I think he's planning on doing is issuing a request sense > >when autosense fails. I'm not sure how much that would help in this case, > >but it might. > > Yes, it does perform sense retrieval in that case. That might help. 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 Sat Mar 4 18:38:29 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from sprout.cgf.net (adsl-207-215-8-122.dsl.snfc21.pacbell.net [207.215.8.122]) by hub.freebsd.org (Postfix) with ESMTP id 4C90137B950 for ; Sat, 4 Mar 2000 18:38:23 -0800 (PST) (envelope-from tomb@cgf.net) Received: from cgf.net (localhost.cgf.net [127.0.0.1]) by sprout.cgf.net (8.9.3/8.9.3) with ESMTP id SAA14686 for ; Sat, 4 Mar 2000 18:36:32 -0800 (PST) (envelope-from tomb@cgf.net) Message-ID: <38C1C830.C97EC53E@cgf.net> Date: Sat, 04 Mar 2000 18:36:32 -0800 From: tom brown Organization: Badger Basters (We do it with Lard) X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: scanimage reports "open of device coolscan:/dev/pass4 failed: Invalid argument"] Content-Type: multipart/mixed; boundary="------------1AAA9A2C58AC624F489A5574" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------1AAA9A2C58AC624F489A5574 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi, I originaly sent this to freebsd-hackers but got no reply, maybe you can help. Thanks Tom Brown --------------1AAA9A2C58AC624F489A5574 Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Mozilla-Status2: 00000000 Message-ID: <38B9BC38.65AA1B9E@cgf.net> Date: Sun, 27 Feb 2000 16:07:20 -0800 From: tom brown Organization: Badger Basters (We do it with Lard) X-Mailer: Mozilla 4.61 [en] (X11; U; FreeBSD 3.4-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: hackers@freebsd.org Subject: scanimage reports "open of device coolscan:/dev/pass4 failed: Invalid argument" Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit The story so far: Recompiled the kernel with controller scbus0 # SCSI bus (required) device da0 # Direct Access (disks) device sa0 # Sequential Access (tape etc) device cd0 # CD controller scbus1 device cd1 device pass0 Installed the scanner on the second SCSI channel Feb 27 15:27:09 foobar/kernel: pass4: Removable Scanner SCSI-2 device Feb 27 15:27:09 foobar/kernel: pass4: 3.300MB/s transfers build device node: bash#cd /dev bash#./MAKEDEV pass4 Built sane, xsane, gimp from the ports. The config file for the coolscan /usr/local/etc/sane.d/coolscan.conf scsi Nikon * Scanner /dev/pass4 Added the path: SANE_CONFIG_DIR=/usr/local/etc/sane.d And the /dev/pass4 device has the following permissions crw------- 1 root operator 31, 4 Feb 27 14:17 /dev/pass4 Execute scanimage: bash#scanimage -d coolscan:/dev/pass4 scanimage: open of device coolscan:/dev/pass4 failed: Invalid argument Any ideas? I find the device node permissions suspect, but I don't know what they should be "crw_rw_rw_" prehaps? Thanks Tom --------------1AAA9A2C58AC624F489A5574-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Mar 4 19:23:46 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 6668837B93C for ; Sat, 4 Mar 2000 19:23:42 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id UAA63282; Sat, 4 Mar 2000 20:23:38 -0700 (MST) (envelope-from ken) Date: Sat, 4 Mar 2000 20:23:37 -0700 From: "Kenneth D. Merry" To: tom brown Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: scanimage reports "open of device coolscan:/dev/pass4 failed: Invalid argument"] Message-ID: <20000304202337.A63158@panzer.kdm.org> References: <38C1C830.C97EC53E@cgf.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38C1C830.C97EC53E@cgf.net>; from tomb@cgf.net on Sat, Mar 04, 2000 at 06:36:32PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Mar 04, 2000 at 18:36:32 -0800, tom brown wrote: > Hi, > > I originaly sent this to freebsd-hackers but got no reply, maybe you can > help. > > Thanks > > Tom Brown [ ... ] > The story so far: > > Recompiled the kernel with > > controller scbus0 # SCSI bus (required) > device da0 # Direct Access (disks) > device sa0 # Sequential Access (tape etc) > device cd0 # CD > > controller scbus1 > device cd1 > device pass0 You don't need scbus1 and cd1. > Installed the scanner on the second SCSI channel > > Feb 27 15:27:09 foobar/kernel: pass4: > Removable Scanner SCSI-2 device > Feb 27 15:27:09 foobar/kernel: pass4: 3.300MB/s transfers > > build device node: > > bash#cd /dev > bash#./MAKEDEV pass4 That will only create pass0-pass3, not pass4. > Built sane, xsane, gimp from the ports. > > The config file for the coolscan /usr/local/etc/sane.d/coolscan.conf > > scsi Nikon * Scanner > /dev/pass4 > > Added the path: > > SANE_CONFIG_DIR=/usr/local/etc/sane.d > > > And the /dev/pass4 device has the following permissions > > crw------- 1 root operator 31, 4 Feb 27 14:17 /dev/pass4 So you'll only be able to open the device as root. > Execute scanimage: > > bash#scanimage -d coolscan:/dev/pass4 > scanimage: open of device coolscan:/dev/pass4 failed: Invalid > argument > > Any ideas? I find the device node permissions suspect, but I don't know > what they should be "crw_rw_rw_" prehaps? The permissions are fine if you're running as root. Otherwise, you'll want to make sure the permissions are 666 or something 660 if you're in the operator group. The pass(4) driver will generally only return EINVAL in two scenarios: - it was opened with the O_NONBLOCK flag set. The pass(4) driver doesn't allow non-blocking access. - someone tried to do a read or write on the device (that isn't supported) Look at the dmesg output from your machine, and you will see an error message if SANE tried to open the device in non-blocking mode. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message