From owner-freebsd-scsi Sun Jan 21 03:50:29 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA12990 for freebsd-scsi-outgoing; Sun, 21 Jan 1996 03:50:29 -0800 (PST) Received: from hda.com (hda.com [199.232.40.182]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id DAA12985 Sun, 21 Jan 1996 03:50:25 -0800 (PST) Received: (from dufault@localhost) by hda.com (8.6.11/8.6.9) id GAA06162; Sun, 21 Jan 1996 06:49:36 -0500 From: Peter Dufault Message-Id: <199601211149.GAA06162@hda.com> Subject: Re: nakamichi MBR-7, some bizarre behavior To: jmb@freebsd.org (Jonathan M. Bresler) Date: Sun, 21 Jan 1996 06:49:35 -0500 (EST) Cc: freebsd-scsi@freebsd.org In-Reply-To: from "Jonathan M. Bresler" at Jan 20, 96 10:02:15 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk > > i have a nakamichi MBR-7 scsi-ii 2x cdrom 7 changer. the unit has > internal terminators controlled by a rear panel dip switch. the > rear panel has 2 centronics 50-pin scsi connectors. the scsi card > is an ASUS SC-200. > > regardless of whether the internal scsi terminator are enabled or > i use an external scsi terminator (active) on the lower scsi > connector of the MBR-7, i get scsi phase errors. when the cable > connects the SC-200 to the upper scsi connector on the MBR-7, the > unit reponds normally. Just to let you know - I used this unit for about 24 hours continuously without trouble with an Adaptec 1542C and -stable. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-scsi Sun Jan 21 05:01:51 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA15193 for freebsd-scsi-outgoing; Sun, 21 Jan 1996 05:01:51 -0800 (PST) Received: from Aspen.Woc.Atinc.COM ([198.138.38.206]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA15187 for ; Sun, 21 Jan 1996 05:01:47 -0800 (PST) Received: (from jmb@localhost) by Aspen.Woc.Atinc.COM (8.6.12/8.6.9) id IAA02271; Sun, 21 Jan 1996 08:02:09 -0500 Date: Sun, 21 Jan 1996 08:02:09 -0500 (EST) From: "Jonathan M. Bresler" X-Sender: jmb@Aspen.Woc.Atinc.COM To: Peter Dufault cc: freebsd-scsi@freebsd.org Subject: Re: nakamichi MBR-7, some bizarre behavior In-Reply-To: <199601211149.GAA06162@hda.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk On Sun, 21 Jan 1996, Peter Dufault wrote: > > i use an external scsi terminator (active) on the lower scsi > > connector of the MBR-7, i get scsi phase errors. when the cable > > connects the SC-200 to the upper scsi connector on the MBR-7, the > > unit reponds normally. > > Just to let you know - I used this unit for about 24 hours continuously > without trouble with an Adaptec 1542C and -stable. did you attach to the upper or lower scsi connector on the unit? (i know this is bizarre, guess i will send the report to ripley's believe it or not). the unit is rock-solid, just this one bizarre thing. i will have to place it in the middle of a scsi chain and see the results. Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG From owner-freebsd-scsi Sun Jan 21 06:18:37 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA17460 for freebsd-scsi-outgoing; Sun, 21 Jan 1996 06:18:37 -0800 (PST) Received: from hda.com (hda.com [199.232.40.182]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA17453 Sun, 21 Jan 1996 06:18:34 -0800 (PST) Received: (from dufault@localhost) by hda.com (8.6.11/8.6.9) id JAA06506; Sun, 21 Jan 1996 09:17:52 -0500 From: Peter Dufault Message-Id: <199601211417.JAA06506@hda.com> Subject: Re: nakamichi MBR-7, some bizarre behavior To: jmb@freebsd.org (Jonathan M. Bresler) Date: Sun, 21 Jan 1996 09:17:51 -0500 (EST) Cc: freebsd-scsi@freebsd.org In-Reply-To: from "Jonathan M. Bresler" at Jan 21, 96 08:02:09 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk > > On Sun, 21 Jan 1996, Peter Dufault wrote: > > > > i use an external scsi terminator (active) on the lower scsi > > > connector of the MBR-7, i get scsi phase errors. when the cable > > > connects the SC-200 to the upper scsi connector on the MBR-7, the > > > unit reponds normally. > > > > Just to let you know - I used this unit for about 24 hours continuously > > without trouble with an Adaptec 1542C and -stable. > > did you attach to the upper or lower scsi connector on the unit? > (i know this is bizarre, guess i will send the report to ripley's believe > it or not). the unit is rock-solid, just this one bizarre thing. i > will have to place it in the middle of a scsi chain and see the results. I don't know, since as you know they should be the same and I sent the unit back to Helmuth. Maybe you have a faulty unit and the lower connector is marginal. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-scsi Sun Jan 21 08:21:21 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA23048 for freebsd-scsi-outgoing; Sun, 21 Jan 1996 08:21:21 -0800 (PST) Received: from Aspen.Woc.Atinc.COM ([198.138.38.206]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA23039 for ; Sun, 21 Jan 1996 08:21:05 -0800 (PST) Received: (from jmb@localhost) by Aspen.Woc.Atinc.COM (8.6.12/8.6.9) id LAA04116; Sun, 21 Jan 1996 11:21:08 -0500 Date: Sun, 21 Jan 1996 11:21:07 -0500 (EST) From: "Jonathan M. Bresler" X-Sender: jmb@Aspen.Woc.Atinc.COM To: Peter Dufault cc: freebsd-scsi@freebsd.org Subject: Re: nakamichi MBR-7, some bizarre behavior In-Reply-To: <199601211417.JAA06506@hda.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk On Sun, 21 Jan 1996, Peter Dufault wrote: > > did you attach to the upper or lower scsi connector on the unit? > > (i know this is bizarre, guess i will send the report to ripley's believe > > it or not). the unit is rock-solid, just this one bizarre thing. i > > will have to place it in the middle of a scsi chain and see the results. > > I don't know, since as you know they should be the same and I sent > the unit back to Helmuth. Maybe you have a faulty unit and the lower > connector is marginal. very possible indeed. i am wondering if anyone else has encountered this behavior. Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG From owner-freebsd-scsi Sun Jan 21 08:22:59 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA23155 for freebsd-scsi-outgoing; Sun, 21 Jan 1996 08:22:59 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA23149 for ; Sun, 21 Jan 1996 08:22:50 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id RAA08549; Sun, 21 Jan 1996 17:21:50 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id RAA06792; Sun, 21 Jan 1996 17:21:50 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id QAA26899; Sun, 21 Jan 1996 16:26:52 +0100 (MET) From: J Wunsch Message-Id: <199601211526.QAA26899@uriah.heep.sax.de> Subject: Re: Whew!!!!!!! (MAJOR sigh of relief!) To: freebsd-scsi@freebsd.org Date: Sun, 21 Jan 1996 16:26:51 +0100 (MET) Cc: bde@zeta.org.au, davidg@Root.COM, peter@jhome.DIALix.COM Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601211429.JAA06531@hda.com> from "Peter Dufault" at Jan 21, 96 09:29:04 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk (moved to freebsd-scsi) As Peter Dufault wrote: > After that I plan on moving policy up out of the SCSI board drivers > and into the common code, hopefully reduce some of the common code > in the drivers, and adding common SCSI resource scheduling. > > I have the 1542 and now the NCR covered (though I'm sure Stefan > will help with that) and Justin has the AHC. It will be nice if > some others can step forward to pick up the other boards. If somebody does the initial work (perhaps even blindly), i could alpha-test it for the Buslogic driver. But it's the adaptor in my development machine at home, so i hesitate breaking the code into pieces in any amateurish attempts to stomp into low-level SCSI drivers. :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Mon Jan 22 07:15:14 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA19216 for freebsd-scsi-outgoing; Mon, 22 Jan 1996 07:15:14 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA19184 Mon, 22 Jan 1996 07:14:55 -0800 (PST) Received: by Sysiphos id AA16526 (5.67b/IDA-1.5); Mon, 22 Jan 1996 16:14:22 +0100 Message-Id: <199601221514.AA16526@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Mon, 22 Jan 1996 16:14:20 +0100 In-Reply-To: "Jonathan M. Bresler" "nakamichi MBR-7, some bizarre behavior" (Jan 20, 22:02) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: "Jonathan M. Bresler" Subject: Re: nakamichi MBR-7, some bizarre behavior Cc: freebsd-scsi@freebsd.org, freebsd-hackers@freebsd.org Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk On Jan 20, 22:02, "Jonathan M. Bresler" wrote: } Subject: nakamichi MBR-7, some bizarre behavior } i have a nakamichi MBR-7 scsi-ii 2x cdrom 7 changer. the unit has } internal terminators controlled by a rear panel dip switch. the } rear panel has 2 centronics 50-pin scsi connectors. the scsi card } is an ASUS SC-200. } } regardless of whether the internal scsi terminator are enabled or } i use an external scsi terminator (active) on the lower scsi } connector of the MBR-7, i get scsi phase errors. when the cable } connects the SC-200 to the upper scsi connector on the MBR-7, the } unit reponds normally. Hmmm, you are saying, whether it works depends on which of two external connectors you use ??? That seems to indicate a cable/terminator problem. But you may want to try the latest /sys/pci/ncr.c from -current, which has handshake timeouts disabled. I'm not sure, } } ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ } SC-200 connected to UPPER scsi connector: } } ncr1 rev 1 int a irq 11 on pci0:5 } (ncr1:6:0): "NRC MBR-7 110" type 5 removable SCSI 2 } cd0(ncr1:6:0): CD-ROM } cd0(ncr1:6:0): asynchronous. } cd present.[330927 x 2048 byte records] } (ncr1:6:1): "NRC MBR-7 110" type 5 removable SCSI 2 } cd1(ncr1:6:1): CD-ROM } cd1(ncr1:6:1): asynchronous. } cd present.[208702 x 2048 byte records] } (ncr1:6:2): "NRC MBR-7 110" type 5 removable SCSI 2 } cd2(ncr1:6:2): CD-ROM } cd2(ncr1:6:2): asynchronous. } cd present.[307527 x 2048 byte records] } (ncr1:6:3): "NRC MBR-7 110" type 5 removable SCSI 2 } cd3(ncr1:6:3): CD-ROM } cd3(ncr1:6:3): asynchronous. } cd present.[326402 x 2048 byte records] } (ncr1:6:4): "NRC MBR-7 110" type 5 removable SCSI 2 } cd4(ncr1:6:4): CD-ROM } cd4(ncr1:6:4): asynchronous. } } cd4(ncr1:6:4): NOT READY asc:3a,0 Medium not present } can't get the size } } (ncr1:6:5): "NRC MBR-7 110" type 5 removable SCSI 2 } cd5(ncr1:6:5): CD-ROM } cd5(ncr1:6:5): asynchronous. } } cd5(ncr1:6:5): NOT READY asc:3a,0 Medium not present } can't get the size } } (ncr1:6:6): "NRC MBR-7 110" type 5 removable SCSI 2 } cd6(ncr1:6:6): CD-ROM } cd6(ncr1:6:6): asynchronous. } } cd6(ncr1:6:6): NOT READY asc:3a,0 Medium not present } can't get the size } } ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ } SC-200 connected to LOWER scsi connector: } } ncr1 rev 1 int a irq 11 on pci0:5 } ncr1: SCSI phase error fixup: CCB address mismatch (0xf0688b08 != 0x00000000) ^^^^^^^^^^ That doesn't look right ! None of the operands to the compare should be 0 ... Have never seen this. I will check the sources for an explanation of how this can happen. } ncr1:6: ERROR (80:100) (e-ac-0) (0/13) @ (438:1e000000). } script cmd = 868b0000 This indicates a handshake timeout occured. Please use the most recent ncr.c, or apply the following patch and let me know, whether it helps: Index: /sys/pci/ncr.c =================================================================== RCS file: /usr/cvs/src/sys/pci/ncr.c,v retrieving revision 1.57 retrieving revision 1.58 diff -C2 -r1.57 -r1.58 *** ncr.c 1996/01/15 00:10:15 1.57 --- ncr.c 1996/01/15 23:16:39 1.58 *************** *** 4427,4431 **** OUTB (nc_stest2, EXT ); /* Extended Sreq/Sack filtering */ OUTB (nc_stest3, TE ); /* TolerANT enable */ ! OUTB (nc_stime0, 0xfb ); /* HTH = 1.6sec STO = 0.1 sec. */ /* --- 4427,4431 ---- OUTB (nc_stest2, EXT ); /* Extended Sreq/Sack filtering */ OUTB (nc_stest3, TE ); /* TolerANT enable */ ! OUTB (nc_stime0, 0x0b ); /* HTH = disabled, STO = 0.1 sec. */ /* Regards, STefan -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-scsi Mon Jan 22 08:08:17 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id IAA23590 for freebsd-scsi-outgoing; Mon, 22 Jan 1996 08:08:17 -0800 (PST) Received: from ncd.com (firewall-user@welch.ncd.com [192.43.160.250]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id IAA23579 for ; Mon, 22 Jan 1996 08:08:14 -0800 (PST) Received: by ncd.com; id IAA05049; Mon, 22 Jan 1996 08:46:26 -0800 Received: from z-code.z-code.com(192.82.56.21) by welch.ncd.com via smap (g3.0.1) id xma005043; Mon, 22 Jan 96 08:46:22 -0800 Received: from zolaris.z-code.com (zolaris.z-code.com [192.82.56.41]) by z-code.z-code.com (8.6.9/8.6.9) with SMTP id IAA17715; Mon, 22 Jan 1996 08:05:58 -0800 Received: by zolaris.z-code.com (5.x/SMI-SVR4) id AA27586; Mon, 22 Jan 1996 08:03:48 -0800 From: "Ulf Zimmermann" Message-Id: <9601220803.ZM27584@zolaris.z-code.com> Date: Mon, 22 Jan 1996 08:03:47 -0800 In-Reply-To: Brian Tao "Re: Aaptec 3985 controller" (Jan 19, 12:35) References: X-Mailer: Z-Mail (3.2.0 06sep94) To: Brian Tao , "Andrew V. Stesin" Subject: DPT Raid controller (was Re: Aaptec 3985 controller) Cc: "Justin T. Gibbs" , scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk On Jan 19, 12:35, Brian Tao wrote: > Subject: Re: Aaptec 3985 controller > On Fri, 19 Jan 1996, Andrew V. Stesin wrote: > > > > And I wonder -- did someone of the FreeBSD engineers try > > to talk with DPT? Their controllers are not too costly, > > but specs seem to be better than Adaptec's. And DPT _are_ > > RAIDish, AFAIK. > > This would be more productive in the meantime, while Adaptec beats > around the bush some more. Linux already has DPT drivers, so there is > at least a code base from which to work. I'd love to drop one of > those controllers in with a 64MB cache and run news on it... > -- > Brian Tao (BT300, taob@io.org) > Systems Administrator, Internex Online Inc. > "Though this be madness, yet there is method in't" > >-- End of excerpt from Brian Tao Hmmmmm, ok, I will try to contact DPT, even I have the problem with getting a controller at the moment. Ulf. -- Ulf Zimmermann, NCD Software, 101 Rowland Way, Suite 300, Novato, CA 94945 phone: 415-899-7941, email: ulf@z-code.ncd.com, phone-home: 510-865-0204 ====================================== FreeBSD 2.1.0 is available now! -------------------------------------- FreeBSD: Turning PCs into Workstations ====================================== From owner-freebsd-scsi Mon Jan 22 16:05:53 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA02370 for freebsd-scsi-outgoing; Mon, 22 Jan 1996 16:05:53 -0800 (PST) Received: from enteract.com (root@adam.enteract.com [206.54.252.1]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA02365 Mon, 22 Jan 1996 16:05:48 -0800 (PST) Received: from waz.enteract.com (waz.enteract.com [206.54.252.16]) by enteract.com (8.7.3/8.6.9) with SMTP id RAA11090; Mon, 22 Jan 1996 17:59:06 -0600 (CST) Message-Id: <199601222359.RAA11090@enteract.com> Comments: Authenticated sender is From: "Tracy Snell" Organization: EnterAct, L.L.C. To: questions@freebsd.org, scsi@freebsd.org Date: Mon, 22 Jan 1996 19:05:38 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Adaptic 1522 DAT Phase Errors Priority: normal X-mailer: Pegasus Mail for Windows (v2.23) Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk I get the following when trying to dump to my dat tape: Jan 22 15:57:47 amos /kernel: st0(aic0:6:0): ABORTED COMMAND info:10000 asc:4b,0 Data phase error Jan 22 15:57:47 amos /kernel: st0(aic0:6:0): HARDWARE FAILUREinfo:10000 asc:44,0 Internal targetfailure Jan 22 15:57:47 amos /kernel: st0(aic0:6:0): HARDWARE FAILURE info:10000 asc:44,0 Internal target failure Jan 22 15:57:50 amos /kernel: st0(aic0:6:0): HARDWARE FAILURE info:1 asc:44,0 Internal target failure I am running 2.1, Adaptec 1522, P90, APS External DAT drive. No other device is on the scsi card. Card is terminated and I have tried both active and passive termination on the drive. Any Ideas. -- Tracy Snell EnterAct, L.L.C. Chicagoland Internet Connectivity tsnell@enteract.com http://www.enteract.com W - 312-248-8511 From owner-freebsd-scsi Mon Jan 22 19:40:01 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA23467 for freebsd-scsi-outgoing; Mon, 22 Jan 1996 19:40:01 -0800 (PST) Received: from Aspen.Woc.Atinc.COM (aspen.woc.atinc.com [198.138.38.205]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA23429 Mon, 22 Jan 1996 19:39:44 -0800 (PST) Received: (from jmb@localhost) by Aspen.Woc.Atinc.COM (8.6.12/8.6.9) id WAA00232; Mon, 22 Jan 1996 22:40:00 -0500 Date: Mon, 22 Jan 1996 22:40:00 -0500 (EST) From: "Jonathan M. Bresler" X-Sender: jmb@Aspen.Woc.Atinc.COM To: Stefan Esser cc: freebsd-scsi@FreeBSD.org, freebsd-hackers@FreeBSD.org Subject: Re: nakamichi MBR-7, some bizarre behavior In-Reply-To: <199601221514.AA16526@Sysiphos> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.org Precedence: bulk On Mon, 22 Jan 1996, Stefan Esser wrote: > On Jan 20, 22:02, "Jonathan M. Bresler" wrote: > } Subject: nakamichi MBR-7, some bizarre behavior > } i have a nakamichi MBR-7 scsi-ii 2x cdrom 7 changer. the unit has > } internal terminators controlled by a rear panel dip switch. the > } rear panel has 2 centronics 50-pin scsi connectors. the scsi card > } is an ASUS SC-200. > } > } regardless of whether the internal scsi terminator are enabled or > } i use an external scsi terminator (active) on the lower scsi > } connector of the MBR-7, i get scsi phase errors. when the cable > } connects the SC-200 to the upper scsi connector on the MBR-7, the > } unit reponds normally. > > Hmmm, you are saying, whether it works depends on > which of two external connectors you use ??? > > That seems to indicate a cable/terminator problem. yes, that is exactly what i WAS saying. since then, i have connected and disconnected the cable a number of times, trying different configurations. the cable and the cdrom drive were both brand new. now they work together. it does not matter if i connect to the upper or the lower connector on the cdrom drive. BOTH WORK. sorry, for the false alarm....must have been new equipment flukiness? do the manufacturers coat the connectors with some material? could i have rubbed that material off by repeatedly connecting and disconnecting the cables?? > That doesn't look right ! > None of the operands to the compare should be 0 ... > Have never seen this. I will check the sources for an > explanation of how this can happen. please, dont the problem has disappeared, i cant get it to reoccur. perhaps, the rear panel dip switch that controls internal scsi termination was not working properly. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NOW, the situation is different. i have cdroms in all seven slots of the drive. nonetheless, the boot probe believes that the first few cdrom slots are empty. the following items DO NOT effect this results. --the /sys/pci/ncr.c handshake timeouts disabled patch (patch included after dmesg output below) --which scsi connector is used --which cdrom was mounted and accessed last before shutdown seems as if the boot probe does not wait long enough for the cdrom drive to finish resetting (??) before starting to probe for cdroms. tomorrow night i will recompile a kernel with SCSIDEBUG and provide more information. the present kernel DOES NOT have 'options "SCSI_DELAY=15"'. it has been commented out. dmesg now shows: Rebooting... FreeBSD 2.1-STABLE #1: Wed Jan 10 21:21:24 EST 1996 jmb@Aspen.Woc.Atinc.COM:/home/sup/src/sys/compile/ASPEN CPU: i486DX (486-class CPU) real memory = 16777216 (16384K bytes) avail memory = 15077376 (14724K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 not found at 0x3e8 sio3 not found at 0x2e8 lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found at 0xffffffff fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 ep0 not found at 0x300 npx0 on motherboard npx0: INT 16 interface Probing for devices on the PCI bus: chip0 rev 4 on pci0:0 ncr0 rev 2 int a irq 9 on pci0:1 (ncr0:0:0): "DEC DSP3053LS X442" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 511MB (1046532 512 byte sectors) (ncr0:1:0): "FUJITSU M1606S-512 6220" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1041MB (2131992 512 byte sectors) chip1 rev 3 on pci0:2 vga0 rev 0 on pci0:4 ncr1 rev 1 int a irq 11 on pci0:5 (ncr1:0:0): "NRC MBR-7 110" type 5 removable SCSI 2 cd0(ncr1:0:0): CD-ROM cd0(ncr1:0:0): asynchronous. cd0(ncr1:0:0): NOT READY asc:4,1 cd0(ncr1:0:0): Logical unit is in process of becoming ready can't get the size (ncr1:0:1): "NRC MBR-7 110" type 5 removable SCSI 2 cd1(ncr1:0:1): CD-ROM cd1(ncr1:0:1): asynchronous. cd1(ncr1:0:1): NOT READY asc:4,1 cd1(ncr1:0:1): Logical unit is in process of becoming ready can't get the size (ncr1:0:2): "NRC MBR-7 110" type 5 removable SCSI 2 cd2(ncr1:0:2): CD-ROM cd2(ncr1:0:2): asynchronous. cd2(ncr1:0:2): NOT READY asc:4,1 cd2(ncr1:0:2): Logical unit is in process of becoming ready can't get the size (ncr1:0:3): "NRC MBR-7 110" type 5 removable SCSI 2 cd3(ncr1:0:3): CD-ROM cd3(ncr1:0:3): asynchronous. cd present.[326402 x 2048 byte records] (ncr1:0:4): "NRC MBR-7 110" type 5 removable SCSI 2 cd4(ncr1:0:4): CD-ROM cd4(ncr1:0:4): asynchronous. cd present.[300158 x 2048 byte records] (ncr1:0:5): "NRC MBR-7 110" type 5 removable SCSI 2 cd5(ncr1:0:5): CD-ROM cd5(ncr1:0:5): asynchronous. cd present.[160790 x 2048 byte records] (ncr1:0:6): "NRC MBR-7 110" type 5 removable SCSI 2 cd6(ncr1:0:6): CD-ROM cd6(ncr1:0:6): asynchronous. cd present.[330927 x 2048 byte records] > Index: /sys/pci/ncr.c > =================================================================== > RCS file: /usr/cvs/src/sys/pci/ncr.c,v > retrieving revision 1.57 > retrieving revision 1.58 > diff -C2 -r1.57 -r1.58 > *** ncr.c 1996/01/15 00:10:15 1.57 > --- ncr.c 1996/01/15 23:16:39 1.58 > *************** > *** 4427,4431 **** > OUTB (nc_stest2, EXT ); /* Extended Sreq/Sack filtering */ > OUTB (nc_stest3, TE ); /* TolerANT enable */ > ! OUTB (nc_stime0, 0xfb ); /* HTH = 1.6sec STO = 0.1 sec. */ > > /* > --- 4427,4431 ---- > OUTB (nc_stest2, EXT ); /* Extended Sreq/Sack filtering */ > OUTB (nc_stest3, TE ); /* TolerANT enable */ > ! OUTB (nc_stime0, 0x0b ); /* HTH = disabled, STO = 0.1 sec. */ Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG From owner-freebsd-scsi Mon Jan 22 20:44:02 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id UAA28652 for freebsd-scsi-outgoing; Mon, 22 Jan 1996 20:44:02 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id UAA28645 Mon, 22 Jan 1996 20:43:47 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id PAA22020; Tue, 23 Jan 1996 15:21:57 +1030 From: Michael Smith Message-Id: <199601230451.PAA22020@genesis.atrad.adelaide.edu.au> Subject: Re: Adaptic 1522 DAT Phase Errors To: freebsd@enteract.com (Tracy Snell) Date: Tue, 23 Jan 1996 15:21:57 +1030 (CST) Cc: questions@FreeBSD.org, scsi@FreeBSD.org In-Reply-To: <199601222359.RAA11090@enteract.com> from "Tracy Snell" at Jan 22, 96 07:05:38 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.org Precedence: bulk Tracy Snell stands accused of saying: > > > I get the following when trying to dump to my dat tape: > > Jan 22 15:57:47 amos /kernel: st0(aic0:6:0): ABORTED COMMAND info:10000 asc:4b,0 Data phase error > Jan 22 15:57:47 amos /kernel: st0(aic0:6:0): HARDWARE FAILUREinfo:10000 asc:44,0 Internal targetfailure > Jan 22 15:57:47 amos /kernel: st0(aic0:6:0): HARDWARE FAILURE info:10000 asc:44,0 Internal target failure > Jan 22 15:57:50 amos /kernel: st0(aic0:6:0): HARDWARE FAILURE info:1 > asc:44,0 Internal target failure > > I am running 2.1, Adaptec 1522, P90, APS External DAT drive. No other > device is on the scsi card. Card is terminated and I have tried both > active and passive termination on the drive. Try with a different card; I'm not sure what level of confidence we have in the 1522's driver. If you're still losing, let me know and I'll see if I get the same problem with a 1510. If it's at all an option, ditch the 1522 and get a better SCSI card. > Tracy Snell -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] "Who does BSD?" "We do Chucky, we do." [[ From owner-freebsd-scsi Tue Jan 23 13:38:58 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA19444 for freebsd-scsi-outgoing; Tue, 23 Jan 1996 13:38:58 -0800 (PST) Received: from mailgate.ericsson.se (mailgate.ericsson.se [130.100.2.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA19384 Tue, 23 Jan 1996 13:38:33 -0800 (PST) Received: from egg.lmc.ericsson.se (egg.lmc.ericsson.se [142.133.32.1]) by mailgate.ericsson.se (8.6.11/1.0) with SMTP id WAA26699; Tue, 23 Jan 1996 22:38:00 +0100 Received: from chicago.lmc.ericsson.com (chicago.lmc.ericsson.se) by egg.lmc.ericsson.se (4.1/LME-2.2) id AA26121; Tue, 23 Jan 96 16:37:57 EST Received: by chicago.lmc.ericsson.com (SMI-8.6/SMI-SVR4) id QAA05231; Tue, 23 Jan 1996 16:37:04 -0500 Date: Tue, 23 Jan 1996 16:37:03 -0500 (EST) From: Samy Touati X-Sender: lmcsato@chicago To: Michael Smith Cc: Tracy Snell , questions@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: Adaptic 1522 DAT Phase Errors In-Reply-To: <199601230451.PAA22020@genesis.atrad.adelaide.edu.au> Message-Id: Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk Is it for sure that the 1522 is not supported? I'm in the process of buying a used one, and I would like to know if it's a good move, to use it with a tape backup on fbsd 2.1. Samy On Tue, 23 Jan 1996, Michael Smith wrote: > Tracy Snell stands accused of saying: > > > > > > I get the following when trying to dump to my dat tape: > > > > Jan 22 15:57:47 amos /kernel: st0(aic0:6:0): ABORTED COMMAND info:10000 asc:4b,0 Data phase error > > Jan 22 15:57:47 amos /kernel: st0(aic0:6:0): HARDWARE FAILUREinfo:10000 asc:44,0 Internal targetfailure > > Jan 22 15:57:47 amos /kernel: st0(aic0:6:0): HARDWARE FAILURE info:10000 asc:44,0 Internal target failure > > Jan 22 15:57:50 amos /kernel: st0(aic0:6:0): HARDWARE FAILURE info:1 > > asc:44,0 Internal target failure > > > > I am running 2.1, Adaptec 1522, P90, APS External DAT drive. No other > > device is on the scsi card. Card is terminated and I have tried both > > active and passive termination on the drive. > > Try with a different card; I'm not sure what level of confidence we have in > the 1522's driver. If you're still losing, let me know and I'll see if I > get the same problem with a 1510. > > If it's at all an option, ditch the 1522 and get a better SCSI card. > > > Tracy Snell > > -- > ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ > ]] Genesis Software genesis@atrad.adelaide.edu.au [[ > ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ > ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ > ]] "Who does BSD?" "We do Chucky, we do." [[ > From owner-freebsd-scsi Tue Jan 23 19:49:13 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA15427 for freebsd-scsi-outgoing; Tue, 23 Jan 1996 19:49:13 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id TAA15387 Tue, 23 Jan 1996 19:49:05 -0800 (PST) Received: from msmith@localhost by genesis.atrad.adelaide.edu.au (8.6.12/8.6.9) id OAA25558; Wed, 24 Jan 1996 14:27:38 +1030 From: Michael Smith Message-Id: <199601240357.OAA25558@genesis.atrad.adelaide.edu.au> Subject: Re: Adaptic 1522 DAT Phase Errors To: lmcsato@lmc.ericsson.se (Samy Touati) Date: Wed, 24 Jan 1996 14:27:38 +1030 (CST) Cc: msmith@atrad.adelaide.edu.au, freebsd@enteract.com, questions@FreeBSD.ORG, scsi@FreeBSD.ORG In-Reply-To: from "Samy Touati" at Jan 23, 96 04:37:03 pm MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk Samy Touati stands accused of saying: > > Is it for sure that the 1522 is not supported? Never said it wasn't supported, just that I had no idea how good (or otherwise) the driver was. > I'm in the process of buying a used one, and I would like to know if it's > a good move, to use it with a tape backup on fbsd 2.1. PIO SCSI controllers like the 1522 are a Bad Idea in general. Get a busmaster (1542). > Samy -- ]] Mike Smith, Software Engineer msmith@atrad.adelaide.edu.au [[ ]] Genesis Software genesis@atrad.adelaide.edu.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control (ph/fax) +61-8-267-3039 [[ ]] "Who does BSD?" "We do Chucky, we do." [[ From owner-freebsd-scsi Wed Jan 24 00:56:31 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA11207 for freebsd-scsi-outgoing; Wed, 24 Jan 1996 00:56:31 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA11040 Wed, 24 Jan 1996 00:54:25 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id JAA20423; Wed, 24 Jan 1996 09:53:11 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id JAA00120; Wed, 24 Jan 1996 09:53:11 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id JAA09895; Wed, 24 Jan 1996 09:49:23 +0100 (MET) From: J Wunsch Message-Id: <199601240849.JAA09895@uriah.heep.sax.de> Subject: Re: Adaptic 1522 DAT Phase Errors To: msmith@atrad.adelaide.edu.au (Michael Smith) Date: Wed, 24 Jan 1996 09:49:23 +0100 (MET) Cc: lmcsato@lmc.ericsson.se, msmith@atrad.adelaide.edu.au, freebsd@enteract.com, questions@FreeBSD.ORG, scsi@FreeBSD.ORG Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601240357.OAA25558@genesis.atrad.adelaide.edu.au> from "Michael Smith" at Jan 24, 96 02:27:38 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk As Michael Smith wrote: > > PIO SCSI controllers like the 1522 are a Bad Idea in general. Get a > busmaster (1542). Note that all 154X B's are known to work, while some very old A's are reported to cause troubles. Mine works however, and i know of at least one more 1542A that does also work fine under FreeBSD. For large transfers, the performance isn't worse than that of a 1542B. The 154X driver in FreeBSD is probably one of the most solid SCSI drivers around in the system. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Wed Jan 24 02:23:22 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id CAA17068 for freebsd-scsi-outgoing; Wed, 24 Jan 1996 02:23:22 -0800 (PST) Received: from hda.com (hda.com [199.232.40.182]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id CAA17058 Wed, 24 Jan 1996 02:23:16 -0800 (PST) Received: (from dufault@localhost) by hda.com (8.6.11/8.6.9) id FAA00342; Wed, 24 Jan 1996 05:19:39 -0500 From: Peter Dufault Message-Id: <199601241019.FAA00342@hda.com> Subject: Re: Adaptic 1522 DAT Phase Errors To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 24 Jan 1996 05:19:39 -0500 (EST) Cc: msmith@atrad.adelaide.edu.au, lmcsato@lmc.ericsson.se, freebsd@enteract.com, questions@FreeBSD.org, scsi@FreeBSD.org In-Reply-To: <199601240849.JAA09895@uriah.heep.sax.de> from "J Wunsch" at Jan 24, 96 09:49:23 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.org Precedence: bulk > > As Michael Smith wrote: > > > > PIO SCSI controllers like the 1522 are a Bad Idea in general. Get a > > busmaster (1542). > > Note that all 154X B's are known to work, while some very old A's are > reported to cause troubles. Mine works however, and i know of at > least one more 1542A that does also work fine under FreeBSD. For > large transfers, the performance isn't worse than that of a 1542B. > > The 154X driver in FreeBSD is probably one of the most solid SCSI > drivers around in the system. Note that in addition to Julian's work this is due to the quality of Adaptec's sequencer code. Not to cast aspersions on our sequencer hackers, but "Damn you Adaptec!" for forcing us to write sequencer code. They don't deserve the hard work that Justin has done enabling them to sell a batch of cards into the FreeBSD (and Linux) market. -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267 From owner-freebsd-scsi Wed Jan 24 09:33:07 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA07456 for freebsd-scsi-outgoing; Wed, 24 Jan 1996 09:33:07 -0800 (PST) Received: from jjarray.umd.edu (jjarray.umd.edu [129.2.40.99]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id JAA07439 for ; Wed, 24 Jan 1996 09:32:36 -0800 (PST) Received: (from fcawth@localhost) by jjarray.umd.edu (8.6.12/8.6.12) id MAA00248; Wed, 24 Jan 1996 12:30:23 -0500 From: Fred Cawthorne Message-Id: <199601241730.MAA00248@jjarray.umd.edu> Subject: HP CD Writer To: joerg_wunsch@uriah.heep.sax.de Date: Wed, 24 Jan 1996 12:30:23 -0500 (EST) Cc: freebsd-scsi@freebsd.org In-Reply-To: <199601232021.VAA03867@uriah.heep.sax.de> from "J Wunsch" at Jan 23, 96 09:21:24 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk I just installed an HP Surestore CD writer in my FreeBSD-2.1R box. I have a couple of questions: 1. It is probed like a regular scsi CD rom, i.e. : (ncr0:6:0): "HP C4324/C4325 1.20" type 5 removable SCSI 2 cd1(ncr0:6:0): CD-ROM cd present.[330928 x 2340 byte records] Is this correct?? Will I be able to issue scsi commands to the cd1 device? (i.e. shouldn't I be using the worm device to write CD's) 2. I can mount a cdrom, and it seems to work fine, but it is slower than my 2x toshiba cdrom drive. I thought this thing was supposed to read at 4x speed. 3. When I initially tried to mount a cdrom, I got a bunch of scsi error messages. Then, it seemed to mount fine the second time I tried it. After I moved it to scsi ID 6, it was fine. Maybe it didn't like something when the other devices were accessed right after it was during the probe? Maybe it is a priority thing? Any ideas?? Here's the log: Jan 24 11:55:24 jjarray /kernel: ncr0:4: ERROR (80:140) (8-2a-0) (0/13) @ (544:900b0000). Jan 24 11:55:27 jjarray /kernel: script cmd = 910a0000 Jan 24 11:55:27 jjarray /kernel: reg: da 10 80 13 47 00 04 1f 03 08 84 2a 80 00 02 00. Jan 24 11:55:27 jjarray /kernel: ncr0: handshake timeout Jan 24 11:55:27 jjarray /kernel: cd0(ncr0:4:0): COMMAND FAILED (6 2) @f0a8e400. Jan 24 11:55:27 jjarray /kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Jan 24 11:55:41 jjarray /kernel: sd1(ncr0:1:0): UNIT ATTENTION asc:29,0 Jan 24 11:55:41 jjarray /kernel: sd1(ncr0:1:0): Power on, reset, or bus device reset occurred Jan 24 11:55:42 jjarray /kernel: , retries:4 Anyway, I am going to try to play with this cd writing perl script after my 2.1 gig disk comes. I suspect I will be doing alot of tests with the laser off (: Any suggestions would be greatly appreciated. Fred. From owner-freebsd-scsi Wed Jan 24 11:57:31 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA15762 for freebsd-scsi-outgoing; Wed, 24 Jan 1996 11:57:31 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA15715 for ; Wed, 24 Jan 1996 11:56:34 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA19029; Wed, 24 Jan 1996 20:53:41 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id UAA05117; Wed, 24 Jan 1996 20:53:40 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id UAA11476; Wed, 24 Jan 1996 20:36:17 +0100 (MET) From: J Wunsch Message-Id: <199601241936.UAA11476@uriah.heep.sax.de> Subject: Re: HP CD Writer To: freebsd-scsi@freebsd.org Date: Wed, 24 Jan 1996 20:36:17 +0100 (MET) Cc: fcawth@jjarray.umd.edu (Fred Cawthorne) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601241730.MAA00248@jjarray.umd.edu> from "Fred Cawthorne" at Jan 24, 96 12:30:23 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk As Fred Cawthorne wrote: > > I just installed an HP Surestore CD writer in my FreeBSD-2.1R box. > I have a couple of questions: > > 1. > It is probed like a regular scsi CD rom, i.e. : > (ncr0:6:0): "HP C4324/C4325 1.20" type 5 removable SCSI 2 > cd1(ncr0:6:0): CD-ROM cd present.[330928 x 2340 byte records] > Is this correct?? Will I be able to issue scsi commands to the cd1 > device? (i.e. shouldn't I be using the worm device to write CD's) You need an ``override entry'' in scsiconf.c. Most likely: { T_WORM, T_WORM, T_REMOV, "HP", "C4324/C4325", "*", "worm", SC_ONE_LU }, right after the entry for the YAMAHA CDR100. Let us know if it is found as worm0 then. For FreeBSD 2.1, you also need to rebuild your system with the ``options NEW_SCSICONF'' (verify my spelling in scsiconf.c, please). > 2. I can mount a cdrom, and it seems to work fine, but it is slower than > my 2x toshiba cdrom drive. I thought this thing was supposed to read > at 4x speed. No idea on this. > 3. When I initially tried to mount a cdrom, I got a bunch of scsi > error messages. > Jan 24 11:55:41 jjarray /kernel: sd1(ncr0:1:0): UNIT ATTENTION asc:29,0 > Jan 24 11:55:41 jjarray /kernel: sd1(ncr0:1:0): Power on, reset, or bus device reset occurred As it stands: a unit attention. These drives tend to generate a lot of them. I'm afraid you won't be very successful unless you've also got a copy of the SCSI-2 documentation... Even in printed form, it's not always very easy to understand. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Wed Jan 24 14:33:51 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA26063 for freebsd-scsi-outgoing; Wed, 24 Jan 1996 14:33:51 -0800 (PST) Received: from mail.ruhrgebiet.individual.net (in-ruhr.ruhr.de [193.100.176.38]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id OAA26058 for ; Wed, 24 Jan 1996 14:33:43 -0800 (PST) Received: from robkaos.UUCP (admin@localhost) by mail.ruhrgebiet.individual.net (8.7.1/8.7.1) with UUCP id WAA01357; Wed, 24 Jan 1996 22:37:23 +0100 (MET) Received: by robkaos.ruhr.de (/\oo/\ Smail3.1.29.1 #29.1) id ; Wed, 24 Jan 96 22:33 MET Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: Re: HP CD Writer To: fcawth@jjarray.umd.edu (Fred Cawthorne) Date: Wed, 24 Jan 1996 22:33:43 +0100 (MET) Cc: freebsd-scsi@freebsd.org In-Reply-To: <199601241730.MAA00248@jjarray.umd.edu> from "Fred Cawthorne" at Jan 24, 96 12:30:23 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk > > I just installed an HP Surestore CD writer in my FreeBSD-2.1R box. > I have a couple of questions: > > 1. > It is probed like a regular scsi CD rom, i.e. : > (ncr0:6:0): "HP C4324/C4325 1.20" type 5 removable SCSI 2 > cd1(ncr0:6:0): CD-ROM cd present.[330928 x 2340 byte records] > Is this correct?? Will I be able to issue scsi commands to the cd1 > device? (i.e. shouldn't I be using the worm device to write CD's) > Can you change the SCSI type of the HP (from CD-ROM to WORM)? Is there such a jumper? TIA Robert From owner-freebsd-scsi Wed Jan 24 17:21:13 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA08644 for freebsd-scsi-outgoing; Wed, 24 Jan 1996 17:21:13 -0800 (PST) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA08634 Wed, 24 Jan 1996 17:21:10 -0800 (PST) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA01435; Wed, 24 Jan 1996 18:16:35 -0700 From: Terry Lambert Message-Id: <199601250116.SAA01435@phaeton.artisoft.com> Subject: Re: Adaptic 1522 DAT Phase Errors To: dufault@hda.com (Peter Dufault) Date: Wed, 24 Jan 1996 18:16:35 -0700 (MST) Cc: joerg_wunsch@uriah.heep.sax.de, msmith@atrad.adelaide.edu.au, lmcsato@lmc.ericsson.se, freebsd@enteract.com, questions@freebsd.org, scsi@freebsd.org In-Reply-To: <199601241019.FAA00342@hda.com> from "Peter Dufault" at Jan 24, 96 05:19:39 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk > Note that in addition to Julian's work this is due to the > quality of Adaptec's sequencer code. Not to cast aspersions on our > sequencer hackers, but "Damn you Adaptec!" for forcing us to write > sequencer code. They don't deserve the hard work that Justin has done > enabling them to sell a batch of cards into the FreeBSD (and Linux) market. Not only that, the code has features that the Adaptec code does not. Not to say that the Adaptec code doesn't also have features the code in Justin's driver doesn't (RAID for the 3980?). It's advantageous to combine the code, if possible, but it's currently not possible, thanks to the silly policy. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. From owner-freebsd-scsi Thu Jan 25 00:34:06 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA27093 for freebsd-scsi-outgoing; Thu, 25 Jan 1996 00:34:06 -0800 (PST) Received: from gilberto.physik.rwth-aachen.de (gilberto.physik.rwth-aachen.de [137.226.31.2]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA26642 for ; Thu, 25 Jan 1996 00:31:48 -0800 (PST) Received: (from kuku@localhost) by gilberto.physik.rwth-aachen.de (8.6.11/8.6.9) id JAA05115 for freebsd-scsi@freebsd.org; Thu, 25 Jan 1996 09:34:42 +0100 Date: Thu, 25 Jan 1996 09:34:42 +0100 From: "Christoph P. Kukulies" Message-Id: <199601250834.JAA05115@gilberto.physik.rwth-aachen.de> To: freebsd-scsi@freebsd.org Subject: in situ adding/removing devices Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk Assumed you have two scsi controllers, or one controller and your system disks at a different controller/bus, could FreeBSD cope with changing/adding devices on the SCSI bus. Is there a way to rescan the scsi-bus and assign the found devices into the system? Under VMS you can and I wonder if it is necessary to reboot the system every time you come with your moveable DAT streamer or IOMEGA zip drive. --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-scsi Thu Jan 25 05:32:35 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id FAA22005 for freebsd-scsi-outgoing; Thu, 25 Jan 1996 05:32:35 -0800 (PST) Received: from jjarray.umd.edu (jjarray.umd.edu [129.2.40.99]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id FAA21996 for ; Thu, 25 Jan 1996 05:32:31 -0800 (PST) Received: (from fcawth@localhost) by jjarray.umd.edu (8.6.12/8.6.12) id IAA00908; Thu, 25 Jan 1996 08:32:23 -0500 From: Fred Cawthorne Message-Id: <199601251332.IAA00908@jjarray.umd.edu> Subject: Re: HP CD Writer To: robsch@robkaos.ruhr.de (Robert Schien) Date: Thu, 25 Jan 1996 08:32:23 -0500 (EST) Cc: freebsd-scsi@freebsd.org In-Reply-To: from "Robert Schien" at Jan 24, 96 10:33:43 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk > > > > > I just installed an HP Surestore CD writer in my FreeBSD-2.1R box. > > I have a couple of questions: > > > > 1. > > It is probed like a regular scsi CD rom, i.e. : > > (ncr0:6:0): "HP C4324/C4325 1.20" type 5 removable SCSI 2 > > cd1(ncr0:6:0): CD-ROM cd present.[330928 x 2340 byte records] > > Is this correct?? Will I be able to issue scsi commands to the cd1 > > device? (i.e. shouldn't I be using the worm device to write CD's) > > > Can you change the SCSI type of the HP (from CD-ROM to WORM)? > Is there such a jumper? > No, there is only the termination enable and address jumpers... It will have to be handled as an exception by the scsi drivers, if I can only get that to work. I added an entry in scsiconf.c for this drive, but it still attaches to the cd driver... How can I make something that is type 5 attach itself to the worm driver instead of the cd driver?? Fred. From owner-freebsd-scsi Thu Jan 25 06:05:11 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA23046 for freebsd-scsi-outgoing; Thu, 25 Jan 1996 06:05:11 -0800 (PST) Received: from jjarray.umd.edu (jjarray.umd.edu [129.2.40.99]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA23023 for ; Thu, 25 Jan 1996 06:04:51 -0800 (PST) Received: (from fred@localhost) by jjarray.umd.edu (8.6.12/8.6.12) id IAA00931; Thu, 25 Jan 1996 08:40:35 -0500 From: Fred Cawthorne Message-Id: <199601251340.IAA00931@jjarray.umd.edu> Subject: Re: HP CD Writer To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 25 Jan 1996 08:40:35 -0500 (EST) Cc: freebsd-scsi@FreeBSD.org, fcawth@jjarray.umd.edu In-Reply-To: <199601241936.UAA11476@uriah.heep.sax.de> from "J Wunsch" at Jan 24, 96 08:36:17 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.org Precedence: bulk > > As Fred Cawthorne wrote: > > > > I just installed an HP Surestore CD writer in my FreeBSD-2.1R box. > > I have a couple of questions: > > > > 1. > > It is probed like a regular scsi CD rom, i.e. : > > (ncr0:6:0): "HP C4324/C4325 1.20" type 5 removable SCSI 2 > > cd1(ncr0:6:0): CD-ROM cd present.[330928 x 2340 byte records] > > Is this correct?? Will I be able to issue scsi commands to the cd1 > > device? (i.e. shouldn't I be using the worm device to write CD's) > > You need an ``override entry'' in scsiconf.c. Most likely: > > { > T_WORM, T_WORM, T_REMOV, "HP", "C4324/C4325", "*", > "worm", SC_ONE_LU > }, > I assume there are only supposed to be one of the T_WORM above? At least that is what the other entries look like. Also, what exactly is the format of this thing and how does it work? I can't seem to get it to work. Does it compare the ID strings for every device type, then make it type T_WORM and attach it to the worm driver no matter what device type the drive actually returns? > > For FreeBSD 2.1, you also need to rebuild your system with the > ``options NEW_SCSICONF'' (verify my spelling in scsiconf.c, please). > I did this... > > > 3. When I initially tried to mount a cdrom, I got a bunch of scsi > > error messages. > > > Jan 24 11:55:41 jjarray /kernel: sd1(ncr0:1:0): UNIT ATTENTION asc:29,0 > > Jan 24 11:55:41 jjarray /kernel: sd1(ncr0:1:0): Power on, reset, or bus device reset occurred > > As it stands: a unit attention. These drives tend to generate a lot > of them. > The unit attention seems to be the result of the ncr driver resetting the bus when the handshake timeout occurs. I have disabled the handshake timeout (like it is in the -current driver) and I don't see these problems any more. Fred. From owner-freebsd-scsi Thu Jan 25 07:10:46 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id HAA25580 for freebsd-scsi-outgoing; Thu, 25 Jan 1996 07:10:46 -0800 (PST) Received: from jjarray.umd.edu (jjarray.umd.edu [129.2.40.99]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id HAA25570 for ; Thu, 25 Jan 1996 07:10:42 -0800 (PST) Received: (from fcawth@localhost) by jjarray.umd.edu (8.6.12/8.6.12) id KAA00253 for freebsd-scsi@freebsd.org; Thu, 25 Jan 1996 10:10:52 -0500 From: Fred Cawthorne Message-Id: <199601251510.KAA00253@jjarray.umd.edu> Subject: worm device. To: freebsd-scsi@freebsd.org Date: Thu, 25 Jan 1996 10:10:51 -0500 (EST) X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk Is there a block device for the worm device? (i.e. so I can mount the thing) I hacked the scsiconf.c code so that the type for the HP CD-R drive is forced to T_WORM even though the drive reports itself as T_READONLY. It is now attached to the worm0 driver, but MAKEDEV only makes the rworm0 device. I could read the CD fine with the cd driver when it was probed that way. Thanks, Fred. From owner-freebsd-scsi Thu Jan 25 11:35:48 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA11400 for freebsd-scsi-outgoing; Thu, 25 Jan 1996 11:35:48 -0800 (PST) Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA11376 for ; Thu, 25 Jan 1996 11:35:43 -0800 (PST) Received: (from julian@localhost) by ref.tfs.com (8.6.12/8.6.9) id LAA25238; Thu, 25 Jan 1996 11:34:29 -0800 From: Julian Elischer Message-Id: <199601251934.LAA25238@ref.tfs.com> Subject: Re: in situ adding/removing devices To: kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies) Date: Thu, 25 Jan 1996 11:34:28 -0800 (PST) Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: <199601250834.JAA05115@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at Jan 25, 96 09:34:42 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk FreeBSD cannot remove devices.. but new scsi devices can be added (quiesce the system first ok?) see the -r option to scsi(8) e.g. scsi -f /dev/sd0 -r will ask the scsi system to reprobe julian (p.s. removal will happen soem day but don't hold your breath) > > Assumed you have two scsi controllers, or one controller and your > system disks at a different controller/bus, could FreeBSD > cope with changing/adding devices on the SCSI bus. Is there a > way to rescan the scsi-bus and assign the found devices > into the system? Under VMS you can and I wonder if it is > necessary to reboot the system every time you come with > your moveable DAT streamer or IOMEGA zip drive. > > --Chris Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de > From owner-freebsd-scsi Thu Jan 25 13:58:37 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA09828 for freebsd-scsi-outgoing; Thu, 25 Jan 1996 13:58:37 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA09730 for ; Thu, 25 Jan 1996 13:56:30 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA15753 for ; Thu, 25 Jan 1996 22:55:37 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id WAA19494 for freebsd-scsi@freebsd.org; Thu, 25 Jan 1996 22:55:37 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id WAA15801 for freebsd-scsi@freebsd.org; Thu, 25 Jan 1996 22:52:03 +0100 (MET) From: J Wunsch Message-Id: <199601252152.WAA15801@uriah.heep.sax.de> Subject: Re: worm device. To: freebsd-scsi@freebsd.org Date: Thu, 25 Jan 1996 22:52:03 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601251510.KAA00253@jjarray.umd.edu> from "Fred Cawthorne" at Jan 25, 96 10:10:51 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk As Fred Cawthorne wrote: > > Is there a block device for the worm device? Not yet, and unless somebody is going to merge the CD-ROM driver into the worm driver (or better yet, makes the code shared between both), i don't see any need for it. Anyway, this is something of the least priority i think. Nobody is going to spend that much money to get an expensive CDROM drive. I've started to revamp the worm driver today, i hope i'll have something that would burn me a CD-R without the hackery that is required now, approximately by the weekend. I've taken the approach to add a couple of ioctl's, in order to define disk-wide (actually session-wide) and track-only parameters. All these must be issued via the control device. Once everything has been set, the driver is ready to have the regular device opened, which will cause the track to be opened for writing. All after this is time- critical, until the close of the regular device, which will issue a SYNCHRONIZE CACHE, causing the drive to consider the track being written. This is the end of the time-critical phase. After all tracks have been written, an ioctl must be given to ``fixate'' the session. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Thu Jan 25 13:59:54 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id NAA09935 for freebsd-scsi-outgoing; Thu, 25 Jan 1996 13:59:54 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id NAA09788 for ; Thu, 25 Jan 1996 13:57:54 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id WAA15749; Thu, 25 Jan 1996 22:55:34 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id WAA19491; Thu, 25 Jan 1996 22:55:33 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id WAA15751; Thu, 25 Jan 1996 22:40:31 +0100 (MET) From: J Wunsch Message-Id: <199601252140.WAA15751@uriah.heep.sax.de> Subject: Re: HP CD Writer To: freebsd-scsi@freebsd.org Date: Thu, 25 Jan 1996 22:40:30 +0100 (MET) Cc: joerg_wunsch@uriah.heep.sax.de, freebsd-scsi@freebsd.org, fcawth@jjarray.umd.edu Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601251340.IAA00931@jjarray.umd.edu> from "Fred Cawthorne" at Jan 25, 96 08:40:35 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk As Fred Cawthorne wrote: > > > You need an ``override entry'' in scsiconf.c. Most likely: > > > > { > > T_WORM, T_WORM, T_REMOV, "HP", "C4324/C4325", "*", > > "worm", SC_ONE_LU > > }, > > > I assume there are only supposed to be one of the T_WORM above? At least No, really two of them. Well, actually, the first one must be a T_CDROM, since this is what the INQUIRY string is matched for. The second one is the driver assigned. > that is what the other entries look like. Also, what exactly is the > format of this thing and how does it work? I can't seem to get it to > work. Does it compare the ID strings for every device type, then > make it type T_WORM and attach it to the worm driver no matter what > device type the drive actually returns? Something that way. Alas, i've just checked out the 2.1R code and had to see that these changes to scsiconf.c didn't make it into 2.1. So i'm afraid you will either have to upgrade to some -current system, or to hand-fiddle these changes into your code. > > As it stands: a unit attention. These drives tend to generate a lot > > of them. > > > The unit attention seems to be the result of the ncr driver resetting the > bus when the handshake timeout occurs. I have disabled the handshake > timeout (like it is in the -current driver) and I don't see these problems > any more. Aha, i haven't been using an NCR for this kind of work yet. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Thu Jan 25 14:25:19 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA12485 for freebsd-scsi-outgoing; Thu, 25 Jan 1996 14:25:19 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA12475 for ; Thu, 25 Jan 1996 14:25:11 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA16533; Thu, 25 Jan 1996 23:24:49 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id XAA19915; Thu, 25 Jan 1996 23:24:49 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id XAA15968; Thu, 25 Jan 1996 23:05:42 +0100 (MET) From: J Wunsch Message-Id: <199601252205.XAA15968@uriah.heep.sax.de> Subject: Re: in situ adding/removing devices To: kuku@gilberto.physik.rwth-aachen.de (Christoph P. Kukulies) Date: Thu, 25 Jan 1996 23:05:41 +0100 (MET) Cc: freebsd-scsi@FreeBSD.org Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199601250834.JAA05115@gilberto.physik.rwth-aachen.de> from "Christoph P. Kukulies" at Jan 25, 96 09:34:42 am X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.org Precedence: bulk As Christoph P. Kukulies wrote: > > Assumed you have two scsi controllers, or one controller and your > system disks at a different controller/bus, could FreeBSD > cope with changing/adding devices on the SCSI bus. Is there a > way to rescan the scsi-bus and assign the found devices > into the system? scsi -r Alas, it only seems to work for the aha and bt drivers, and for the latter, most likely only for the non-PCI versions. Since device probing is usually done at system initialization time, the probe code makes several fatal assumptions about the environment it's running in, for example it turns the adapter driver into polled mode. I haven't been able to successfully use it on the ahc driver at work (and i'm rather surprised that it works flawlessly on the aha and bt drivers at home :). Last time we've been discussing this here, the tenor was ``Yes, it needs to be changed.'' ;-) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Thu Jan 25 17:22:55 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id RAA23714 for freebsd-scsi-outgoing; Thu, 25 Jan 1996 17:22:55 -0800 (PST) Received: from Aspen.Woc.Atinc.COM (aspen.woc.atinc.com [198.138.38.205]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA23701 for ; Thu, 25 Jan 1996 17:22:46 -0800 (PST) Received: (from jmb@localhost) by Aspen.Woc.Atinc.COM (8.6.12/8.6.9) id UAA03525; Thu, 25 Jan 1996 20:22:18 -0500 Date: Thu, 25 Jan 1996 20:22:17 -0500 (EST) From: "Jonathan M. Bresler" X-Sender: jmb@Aspen.Woc.Atinc.COM To: Julian Elischer cc: "Christoph P. Kukulies" , freebsd-scsi@FreeBSD.ORG Subject: Re: in situ adding/removing devices In-Reply-To: <199601251934.LAA25238@ref.tfs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk On Thu, 25 Jan 1996, Julian Elischer wrote: > FreeBSD cannot remove devices.. > but new scsi devices can be added (quiesce the system first ok?) > see the -r option to scsi(8) > > e.g. scsi -f /dev/sd0 -r PLEASE note that this will completely occupy your system for a few seconds--in my case 11 seconds--it can be kinda scary! Aspen:[173] date ; scsi -f /dev/sd0 -r ; date Thu Jan 25 20:20:47 EST 1996 Thu Jan 25 20:20:56 EST 1996 Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG From owner-freebsd-scsi Thu Jan 25 19:07:03 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id TAA28702 for freebsd-scsi-outgoing; Thu, 25 Jan 1996 19:07:03 -0800 (PST) Received: from jjarray.umd.edu (jjarray.umd.edu [129.2.40.99]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id TAA28687 for ; Thu, 25 Jan 1996 19:06:44 -0800 (PST) Received: (from fred@localhost) by jjarray.umd.edu (8.6.12/8.6.12) id WAA00200; Thu, 25 Jan 1996 22:06:00 -0500 From: Fred Cawthorne Message-Id: <199601260306.WAA00200@jjarray.umd.edu> Subject: Re: worm device. To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 25 Jan 1996 22:06:00 -0500 (EST) Cc: freebsd-scsi@freebsd.org In-Reply-To: <199601252152.WAA15801@uriah.heep.sax.de> from "J Wunsch" at Jan 25, 96 10:52:03 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk > > As Fred Cawthorne wrote: > > > > Is there a block device for the worm device? > > Not yet, and unless somebody is going to merge the CD-ROM driver into > the worm driver (or better yet, makes the code shared between both), i > don't see any need for it. > Ok. I suppose it just adds more wear-and-tear on the thing anyway... > I've started to revamp the worm driver today, i hope i'll have > something that would burn me a CD-R without the hackery that is > required now, approximately by the weekend. > .. Great. I look forward to seeing it. I am tracking down a problem now where I can't do alot of disk activity on my new DEC scsi drive when the HP CD-R drive is plugged in. I unplugged it from the scsi bus and everything is fine. Plugging in and unplugging my external cdrom and zip drive doesn't change anything. Keep in mind that there is no activity on the HP CD-R side of things. This is really strange... I think I am going to have to plug in an Adaptec 1542 and use that for the HP CD-R drive. Here's what happened when I tried to copy my entire /user directory (600M) into a partiton on the 2 gig DEC drive: First, here's the stuff on my scsi bus. Jan 25 21:14:22 jjarray /kernel: ncr0 rev 1 int a irq 10 on pci0:5 Jan 25 21:14:22 jjarray /kernel: ncr0 waiting for scsi devices to settle Jan 25 21:14:22 jjarray /kernel: (ncr0:0:0): "MICROP 2217-15MQ1001901 HQ30" type 0 fixed SCSI 2 Jan 25 21:14:22 jjarray /kernel: sd0(ncr0:0:0): Direct-Access Jan 25 21:14:22 jjarray /kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Jan 25 21:14:22 jjarray /kernel: 1685MB (3450902 512 byte sectors) Jan 25 21:14:22 jjarray /kernel: (ncr0:2:0): "DEC DSP3210S 436D" type 0 fixed SCSI 2 Jan 25 21:14:22 jjarray /kernel: sd1(ncr0:2:0): Direct-Access Jan 25 21:14:22 jjarray /kernel: sd1(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Jan 25 21:14:22 jjarray /kernel: 2047MB (4194303 512 byte sectors) Jan 25 21:14:22 jjarray /kernel: (ncr0:6:0): "HP C4324/C4325 1.20" type 5 removable SCSI 2 Jan 25 21:14:22 jjarray /kernel: worm0(ncr0:6:0): Write-Once - UNTESTED worm0: oops not queued Jan 25 21:14:23 jjarray /kernel: with 333227 2048 byte blocks. And the error message: (After copying a few hundred megs over) Jan 25 21:45:21 jjarray /kernel: ncr0:2: ERROR (20:40) (8-28-0) (8/13) @ (1150:180000a0). Jan 25 21:45:32 jjarray /kernel: script cmd = 88030000 Jan 25 21:45:32 jjarray /kernel: reg: da 10 80 13 47 08 02 1f 01 08 82 28 00 00 08 00. Jan 25 21:45:32 jjarray /kernel: ncr0: have to clear fifos. Jan 25 21:45:33 jjarray /kernel: ncr0: restart (fatal error). Jan 25 21:45:33 jjarray /kernel: sd1(ncr0:2:0): COMMAND FAILED (9 ff) @f0b5aa00. Jan 25 21:45:34 jjarray /kernel: ncr0: restart (ncr dead ?). Jan 25 21:45:34 jjarray /kernel: sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. Jan 25 21:45:34 jjarray /kernel: sd1(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. I filled the whole 2.1 gig drive up fine when I unplugged the CD-R and rebooted... Any ideas? Fred. From owner-freebsd-scsi Thu Jan 25 21:43:25 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id VAA07061 for freebsd-scsi-outgoing; Thu, 25 Jan 1996 21:43:25 -0800 (PST) Received: from fastlane.net (fastlane.net [204.251.16.10]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id VAA07048 for ; Thu, 25 Jan 1996 21:43:21 -0800 (PST) Received: from jf.fastlane.net (fw39.fastlane.net [206.42.189.39]) by fastlane.net (8.7.3/8.7.3) with SMTP id AAA07577 for ; Fri, 26 Jan 1996 00:38:23 -0600 (CST) Message-ID: <31085C0C.7DA9@fastlane.net> Date: Thu, 25 Jan 1996 23:43:56 -0500 From: James Faubus X-Mailer: Mozilla 2.0b4 (Win95; I) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: scsiconf.c Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk I receintly tried to get a Panasonic PD-1 phase change optical PC/CD drive to work with FreeBSD 2.1. I had an idea that it should work since it worked fine with the sd driver in NetBSD 1.1. However, I added the device to the tables and recompiled, but it was still unrecognized whether NEW_SCSICONF was defined or not. A search of the FreeBSD archives turned this up. ====================================================================== > The first thing I did was add entries to the knowndevs[] of scsiconf.c which > looked like this: > /* Added this one to force my fuji m2521A to device sd */ > { > T_OPTICAL, T_REMOV, "*", "*", "*", > "sd", SC_ONE_LU > }, > and this: > /* Added this one to force my fuji m2521A to device sd */ > { > T_OPTICAL, T_REMOV, "FUJITSU", "any" > ,"any", "sd", SC_ONE_LU > }, > >correct > for each of the defines (it turns out my kernel is compling with > NEW_SCSICONF undefined). > >yes > This resulted in no change of behavior :-( So I added a few printf in > to see what was going on, and the problem is that when > scsi_device_lookup(int type) is called, it checks the type of the device > (T_OPTICAL in my case) against the type specified for the particular > driver (T_DIRECT in the case of the sd driver). Since they never match, > the uk driver is always defaulted to. >eh? this has been changed by someone.....! >I originally wrote it to specifically over-ride the default >type if the tables said to! >damn! >thanks for pointing this out.! > > What I did was cheat, and make scsi_device_lookup() look like this... > > static struct scsi_device * > scsi_device_lookup(int type) > { > struct scsi_device *sd; > if (sd->type == type || > (sd->type == T_DIRECT && type == T_OPTICAL)) { > return sd; > } > } > > return &uk_switch; > }============================== and this ===================================================================== >I don't know if I'm the culprit or not, but scsi_probedev is using >scsi_selectdev to find the bestmatch in the scsi_devs table, and >then it uses the type field in scsi_devs to override the type >returned by the device. Look at the very end of scsi_probedev. >So if you change "T_OPTICAL" to "T_DIRECT" to fake your device out >as a direct device and hook your device up to the sd driver. The >"mx1" entries in scsiconf can't be working correctly. >-- >Peter Dufault Real Time Machine Control and Simulation================================================================== Well I too was able to get the PD to work by making similar changes to scsi_device_register(). But, although this enables the PD to be probed and found, now the CD on lun 1 is not probed or found. (because it relies on uk somehow?) Now, I personaly don't know enough about the scsi driver to be able to fix this problem. I would just like to point out that there is a problem with the way devices are probed. Apparently the tables are useless even when "option NEW_SCSICONF" is defined in the kernel conf, as was receintly pointed out reguarding CD-R drives. The scsi driver seems to be able to handle the newer type removeable and optical type drives just fine, it just seems to have some problems recognizing and assigning the sd device to them. Of course there are some other minor problems, like the "mode sense" error given once in a while, but it is benign and really doesn't keep the driver from functioning just fine. Also, the driver can't handle sensing the drive door opening to auto sense when the media has changed, but that only means you have to umount before switching media. The NetBSD drivers also have the last two problems, but at least they have fixed the device probe stuff to work with a wider range of drives. In this reguard I would like to pass along these diffs someone passed along to me, if they would help anyone else. They are for the NetBSD driver, but they do correct the drive door and mode sense prob. Perhaps someone more familiar with the scsi code could look at the probe prob, and maybe use the NetBSD driver patches to fix the sd driver to support zip, jazz, PD, fuji optical as well. I have seen reference to similar diffs in the od.c file in FreeBSD curent for these same problems, but I have not had time to try them. Until the real problem of device probing is fixed they are secondary to me. ====================================================================== Sorry for the delay ... These are the diffs I am using with NetBSD-current as of Friday. Cheers, Mark - -- Mark Brinicombe amb@physig.ph.kcl.ac.uk Research Associate http://www.ph.kcl.ac.uk/~amb/ Department of Physics tel: 0171 873 2894 King's College London fax: 0171 873 2420 - --PART-BOUNDARY=.19512181747.ZM28312.ph.kcl.ac.uk Encoding: 76 text X-Zm-Content-Name: scsi.sd.c.patch Content-Type: text/plain ; charset=us-ascii *** sd.c.orig Mon Dec 18 03:01:42 1995 - --- sd.c Mon Dec 18 03:01:42 1995 *************** *** 85,90 **** - --- 85,91 ---- #define SDF_WLABEL 0x04 /* label is writable*/ #define SDF_LABELLING 0x08 /* writing label */ #define SDF_ANCIENT 0x10 /* disk is ancient; for minphys */ + #define SDF_OPTICAL 0x20 /* device is optical memory */ struct scsi_link *sc_link; /* contains our targ, lun,etc. */ struct disk_parms { u_char heads; /* number of heads */ *************** *** 175,180 **** - --- 176,190 ---- if ((sa->sa_inqbuf->version &SID_ANSII) == 0) sd->flags |= SDF_ANCIENT; + /* + * Take note if it is an optical device - we need this info later + */ + + if ((sa->sa_inqbuf->device & SID_TYPE) == T_OPTICAL) + sd->flags |= SDF_OPTICAL; + + sd->sc_dk.dk_driver = &sddkdriver; + sd->sc_dk.dk_driver = &sddkdriver; #if !defined(i386) || defined(NEWCONFIG) dk_establish(&sd->sc_dk, &sd->sc_dev); *************** *** 375,380 **** - --- 385,400 ---- scsi_prevent(sd->sc_link, PR_ALLOW, SCSI_IGNORE_ILLEGAL_REQUEST | SCSI_IGNORE_NOT_READY); sd->sc_link->flags &= ~SDEV_OPEN; + + /* + * Some optical devices do not report unit attention messages + * when the media is changed. Thus the disc can be changed + * without SDEV_MEDIA_LOADED being set. + * Instead invalidate the media when the last opening is closed. + */ + + if (sd->sc_link->flags & SDEV_REMOVABLE) + sd->sc_link->flags &= ~SDEV_MEDIA_LOADED; } sdunlock(sd); *************** *** 833,838 **** - --- 853,866 ---- u_long sectors; /* + * Optical memory devices do not support mode sense page 4 + * (According to SCSI2 specs and my drive) + */ + + if (sd->flags & SDF_OPTICAL) + goto fake_it_for_optical; + + /* * do a "mode sense page 4" */ bzero(&scsi_cmd, sizeof(scsi_cmd)); *************** *** 849,854 **** - --- 877,883 ---- printf("%s: could not mode sense (4)", sd->sc_dev.dv_xname); fake_it: printf("; using fictitious geometry\n"); + fake_it_for_optical: /* * use adaptec standard fictitious geometry * this depends on which controller (e.g. 1542C is ---PART-BOUNDARY=.19512181747.ZM28312.ph.kcl.ac.uk-- ------- End of forwarded message ------- =========================================================== Could someone who knows how the sd driver really works please take a look at this along with the info in od.c and NetBSD and try to straiten out the probs with sd.c and scsiconf.c as they relate to adding devices, like removable opticals and CD-R's in FreeBSD. Maybe they already have and I just don't know it. From owner-freebsd-scsi Fri Jan 26 01:35:51 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id BAA26399 for freebsd-scsi-outgoing; Fri, 26 Jan 1996 01:35:51 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id BAA25572 for ; Fri, 26 Jan 1996 01:23:54 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id KAA03310; Fri, 26 Jan 1996 10:22:15 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id KAA26545; Fri, 26 Jan 1996 10:22:14 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id KAA19025; Fri, 26 Jan 1996 10:05:03 +0100 (MET) From: J Wunsch Message-Id: <199601260905.KAA19025@uriah.heep.sax.de> Subject: Re: scsiconf.c To: faubus@fastlane.net (James Faubus) Date: Fri, 26 Jan 1996 10:05:03 +0100 (MET) Cc: freebsd-scsi@FreeBSD.ORG Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <31085C0C.7DA9@fastlane.net> from "James Faubus" at Jan 25, 96 11:43:56 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk As James Faubus wrote: (Peter:) > >I don't know if I'm the culprit or not, but scsi_probedev is using > >scsi_selectdev to find the bestmatch in the scsi_devs table, and > >then it uses the type field in scsi_devs to override the type > >returned by the device. Look at the very end of scsi_probedev. > >So if you change "T_OPTICAL" to "T_DIRECT" to fake your device out > >as a direct device and hook your device up to the sd driver. The > >"mx1" entries in scsiconf can't be working correctly. I've changed this in current, and added actually two fields to the struct. One is used to match the device, and the second one to assign an actual driver for it. This was necessary in order to get the CD-R's probed, and the list archive will have a record from our discussion about dating back around October, 1995. The tenor has been then ``Yes, we should change the matching algorithm.'' > Well I too was able to get the PD to work by making similar changes > to scsi_device_register(). Please, try the `od' driver instead. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Fri Jan 26 06:30:04 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id GAA06683 for freebsd-scsi-outgoing; Fri, 26 Jan 1996 06:30:04 -0800 (PST) Received: from Sysiphos (Sysiphos.MI.Uni-Koeln.DE [134.95.212.10]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id GAA06647 for ; Fri, 26 Jan 1996 06:29:38 -0800 (PST) Received: by Sysiphos id AA08942 (5.67b/IDA-1.5 for freebsd-scsi@freebsd.org); Fri, 26 Jan 1996 15:29:11 +0100 Message-Id: <199601261429.AA08942@Sysiphos> From: se@zpr.uni-koeln.de (Stefan Esser) Date: Fri, 26 Jan 1996 15:29:10 +0100 In-Reply-To: Fred Cawthorne "Re: worm device." (Jan 25, 22:06) X-Mailer: Mail User's Shell (7.2.6 alpha(2) 7/9/95) To: Fred Cawthorne Subject: Re: worm device. Cc: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk On Jan 25, 22:06, Fred Cawthorne wrote: } Subject: Re: worm device. } I am tracking down a problem now where I can't do alot of disk activity } on my new DEC scsi drive when the HP CD-R drive is plugged in. I unplugged } it from the scsi bus and everything is fine. Plugging in and unplugging } my external cdrom and zip drive doesn't change anything. Keep in mind that } there is no activity on the HP CD-R side of things. This is really } strange... I think I am going to have to plug in an Adaptec 1542 and } use that for the HP CD-R drive. } Here's what happened when I tried to copy my entire /user directory (600M) } into a partiton on the 2 gig DEC drive: } } First, here's the stuff on my scsi bus. } ncr0 rev 1 int a irq 10 on pci0:5 } ncr0 waiting for scsi devices to settle } (ncr0:0:0): "MICROP 2217-15MQ1001901 HQ30" type 0 fixed SCSI 2 } sd0(ncr0:0:0): Direct-Access } sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. } 1685MB (3450902 512 byte sectors) } (ncr0:2:0): "DEC DSP3210S 436D" type 0 fixed SCSI 2 } sd1(ncr0:2:0): Direct-Access } sd1(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. } 2047MB (4194303 512 byte sectors) } (ncr0:6:0): "HP C4324/C4325 1.20" type 5 removable SCSI 2 } worm0(ncr0:6:0): Write-Once - UNTESTED worm0: oops not queued } with 333227 2048 byte blocks. } And the error message: (After copying a few hundred megs over) } ncr0:2: ERROR (20:40) (8-28-0) (8/13) @ (1150:180000a0). The status 20:40 indicates a Bus Fault, i.e. a PCI bus transaction did not succeed within a certain number of bus cycles. This may be a chip set problem (have seen it on the old rev. 2 of the Saturn, if PCI Bursts are enabled) or may be caused by the NCR trying to access a memory address outside the actually installed DRAM range. No other error bit is set (the 20 is BF, the 40 is CMP and indicates that the SCSI target is connected, i.e. Arbitration Complete). } script cmd = 88030000 } reg: da 10 80 13 47 08 02 1f 01 08 82 28 00 00 08 00. } ncr0: have to clear fifos. } ncr0: restart (fatal error). } sd1(ncr0:2:0): COMMAND FAILED (9 ff) @f0b5aa00. } ncr0: restart (ncr dead ?). } sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. } sd1(ncr0:2:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. The NCR was successfully reinitialized, but the ongoing SCSI transaction had been interrupted. } I filled the whole 2.1 gig drive up fine when I unplugged the CD-R and rebooted... } Any ideas? I doubt that the BF is caused by a driver error. This has been observed before on systems with chip sets that can't actually support bus-master controllers under high load, if all PCI performance options have been enabled. This doesn't seem to be an issue with current chip sets, AFAIK, but please let me know, what you are using ... Regards, -- Stefan Esser, Zentrum fuer Paralleles Rechnen Tel: +49 221 4706021 Universitaet zu Koeln, Weyertal 80, 50931 Koeln FAX: +49 221 4705160 ============================================================================== http://www.zpr.uni-koeln.de/~se From owner-freebsd-scsi Fri Jan 26 14:13:37 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA01409 for freebsd-scsi-outgoing; Fri, 26 Jan 1996 14:13:37 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA01400 for ; Fri, 26 Jan 1996 14:13:27 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id XAA28515 for ; Fri, 26 Jan 1996 23:13:03 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id XAA19736 for freebsd-scsi@freebsd.org; Fri, 26 Jan 1996 23:13:02 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id XAA20513 for freebsd-scsi@freebsd.org; Fri, 26 Jan 1996 23:06:38 +0100 (MET) From: J Wunsch Message-Id: <199601262206.XAA20513@uriah.heep.sax.de> Subject: Problem with SDEV_ONCE_ONLY devices To: freebsd-scsi@freebsd.org Date: Fri, 26 Jan 1996 23:06:37 +0100 (MET) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk While playing with the new worm driver (it's already getting into a better shape!), i noticed the following annoying bug several times. It becomes especially apparent for devices that have the SDEV_ONCE_ONLY flag set, as the worm driver has. The device is being opened normally, but for one or the other reason, a SCSI error occurs. Either by playing with the control device and scsi(8), or in my case today, by some buggy code inside the driver. Anyway, after this happens, it seems that the function scsi_close() is never actually being called, so the SDEV_IS_OPEN flag is never reset. Any subsequent attempts to open the device end up in an EBUSY. Clearing the flag using DDB or kgdb cures the problem, so it's defin- ately the SDEV_IS_OPEN flag. I have no idea why scsi_close() is not called however. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Sat Jan 27 11:23:56 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id LAA27083 for freebsd-scsi-outgoing; Sat, 27 Jan 1996 11:23:56 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id LAA27070 Sat, 27 Jan 1996 11:23:50 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id UAA26398; Sat, 27 Jan 1996 20:22:30 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id UAA03170; Sat, 27 Jan 1996 20:22:17 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id UAA24170; Sat, 27 Jan 1996 20:20:44 +0100 (MET) From: J Wunsch Message-Id: <199601271920.UAA24170@uriah.heep.sax.de> Subject: FreeBSD CD-R driver alpha available To: announce@freebsd.org, scsi@freebsd.org, peter@taronga.com Date: Sat, 27 Jan 1996 20:20:43 +0100 (MET) Reply-To: scsi@freebsd.org Newsgroups: comp.unix.bsd.freebsd.announce X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk Hi all, i've just checked in the vastly revamped worm driver. The API has been totally restructured, and the usage does now almost resemble the other SCSI drivers, with the minor exception that you are required to tell the driver about your intentions with respect to the CD-R you are about to burn. There's a wormcontrol(8) utility (usr.sbin/wormcontrol) as well for this. The driver has by now only been tested on a heavily tweaked 2.0.5R system against a Plasmon RF4100 recorder. However, note that this driver is based on some other recent changes in the SCSI code, so you would have a hard time backporting it to 2.1R. Usage of -current is recommended. Fitting hooks for other burners should not be too difficult, but you would best do this only with a certain understanding of the SCSI command-level protocol, and with a SCSI reference manual for your drive. Chances are good that HP or Philips drives could be easily cloned from the Plasmon part, since they are rather similar. Other drives will certainly require more work. There are still a lot of bugs in it, and i consider the driver still highly experimental. Suggestions and discussion about the archi- tecture are welcome. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)