From owner-freebsd-scsi Sun Jul 12 04:01:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA14841 for freebsd-scsi-outgoing; Sun, 12 Jul 1998 04:01:10 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from news1.gtn.com (news1.gtn.com [194.77.0.15]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA14836 for ; Sun, 12 Jul 1998 04:01:06 -0700 (PDT) (envelope-from andreas@klemm.gtn.com) Received: (from uucp@localhost) by news1.gtn.com (8.8.6/8.8.6) with UUCP id NAA07750; Sun, 12 Jul 1998 13:00:04 +0200 (MET DST) Received: (from andreas@localhost) by klemm.gtn.com (8.8.8/8.8.8) id MAA16049; Sun, 12 Jul 1998 12:24:57 +0200 (CEST) (envelope-from andreas) Message-ID: <19980712122457.A14554@klemm.gtn.com> Date: Sun, 12 Jul 1998 12:24:57 +0200 From: Andreas Klemm To: Michael Richards , scsi@FreeBSD.ORG Subject: Re: SCSI errors? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Michael Richards on Sat, Jul 11, 1998 at 11:19:40PM -0300 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-CURRENT SMP Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jul 11, 1998 at 11:19:40PM -0300, Michael Richards wrote: > Hi. > I just noticed a few thousand errors about a hard drive on our system... > > s:80,4a > Jul 11 23:39:26 frodo /kernel: , retries:4 > Jul 11 23:39:26 frodo /kernel: , retries:4 > Jul 11 23:39:28 frodo /kernel: sd1(ahc0:1:0): MEDIUM ERROR info:0x10222c0 > csi:ff,ff,ff,ff asc:11,1 Read retries exhausted sks:80,4a > Jul 11 23:39:28 frodo /kernel: sd1(ahc0:1:0): MEDIUM ERROR info:0x10222c0 > csi:ff,ff,ff,ff asc:11,1 Read retries exhausted sks:80,4a > Jul 11 23:39:28 frodo /kernel: , retries:3 > Jul 11 23:39:28 frodo /kernel: , retries:3 > Jul 11 23:39:30 frodo /kernel: sd1(ahc0:1:0): MEDIUM ERROR info:0x10222c0 > csi:ff,ff,ff,ff asc:11,1 Read retries exhausted sks:80,4a > Jul 11 23:39:30 frodo /kernel: sd1(ahc0:1:0): MEDIUM ERROR info:0x10222c0 > csi:ff,ff,ff,ff asc:11,1 Read retries exhausted sks:80,4a > Jul 11 23:39:30 frodo /kernel: , retries:2 > Jul 11 23:39:30 frodo /kernel: , retries:2 > Jul 11 23:39:32 frodo /kernel: sd1(ahc0:1:0): MEDIUM ERROR info:0x10222c0 > csi:ff,ff,ff,ff asc:11,1 Read retries exhausted sks:80,4a > Jul 11 23:39:32 frodo /kernel: sd1(ahc0:1:0): MEDIUM ERROR info:0x10222c0 > csi:ff,ff,ff,ff asc:11,1 Read retries exhausted sks:80,4a > Jul 11 23:39:32 frodo /kernel: , retries:1 If I remember right a MEDIUM error is more severe ... Perhaps look in single user mode, if the drive is allowed to heal soft errors itself: scsi -f /dev/rsd0c -m 1 -e -P 3 AWRE (Auto Write Reallocation Enbld): 1 ARRE (Auto Read Reallocation Enbld): 1 Just as one quick shot to check the settings ... If I were you I'd perform immediately a level 0 dump. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 12 13:05:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA07998 for freebsd-scsi-outgoing; Sun, 12 Jul 1998 13:05:29 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from fledge.watson.org (shafeeq@COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07981 for ; Sun, 12 Jul 1998 13:05:22 -0700 (PDT) (envelope-from shafeeq@cyrus.watson.org) Received: from localhost (shafeeq@localhost) by fledge.watson.org (8.8.8/8.8.8) with SMTP id QAA04349; Sun, 12 Jul 1998 16:05:13 -0400 (EDT) X-Authentication-Warning: fledge.watson.org: shafeeq owned process doing -bs Date: Sun, 12 Jul 1998 16:05:13 -0400 (EDT) From: Shafeeq Sinnamohideen X-Sender: shafeeq@fledge.watson.org To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG, gibbs@pluto.plutotech.com Subject: Re: disappearing cdrom w/ Bt948+CAM In-Reply-To: <199807102039.OAA15605@panzer.plutotech.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 Fri, 10 Jul 1998, Kenneth D. Merry wrote: > > Jul 8 20:37:19 luthien /kernel: got an error back while probing the CDROM > > Jul 8 20:37:19 luthien /kernel: (probe6:bt0:0:6:0): INQUIRY. CDB: 12 0 0 0 24 0 > > Jul 8 20:37:19 luthien /kernel: (probe6:bt0:0:6:0): error code 0 The CAM status is 0x4a regardless of whether the cdrom is on or not. Shafeeq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 12 14:32:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA14669 for freebsd-scsi-outgoing; Sun, 12 Jul 1998 14:32:56 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA14662 for ; Sun, 12 Jul 1998 14:32:54 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id PAA29415; Sun, 12 Jul 1998 15:32:44 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807122132.PAA29415@panzer.plutotech.com> Subject: Re: disappearing cdrom w/ Bt948+CAM In-Reply-To: from Shafeeq Sinnamohideen at "Jul 12, 98 04:05:13 pm" To: shafeeq@cyrus.watson.org (Shafeeq Sinnamohideen) Date: Sun, 12 Jul 1998 15:32:44 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG, gibbs@pluto.plutotech.com X-Mailer: ELM [version 2.4ME+ PL28s (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 Shafeeq Sinnamohideen wrote... > > > On Fri, 10 Jul 1998, Kenneth D. Merry wrote: > > > Jul 8 20:37:19 luthien /kernel: got an error back while probing the CDROM > > > Jul 8 20:37:19 luthien /kernel: (probe6:bt0:0:6:0): INQUIRY. CDB: 12 0 0 0 24 0 > > > Jul 8 20:37:19 luthien /kernel: (probe6:bt0:0:6:0): error code 0 > > The CAM status is 0x4a regardless of whether the cdrom is on or not. What ID is your BusLogic card on? Can you send the full dmesg output from your system? (not from /var/log/messages, the real dmesg output...the syslog crud makes things more difficult to see sometimes) If your adapter is on ID 6 for some reason, that could explain why you're having trouble talking to your CDROM drive. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 12 14:48:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16175 for freebsd-scsi-outgoing; Sun, 12 Jul 1998 14:48:45 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16170 for ; Sun, 12 Jul 1998 14:48:43 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id PAA29521; Sun, 12 Jul 1998 15:48:38 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807122148.PAA29521@panzer.plutotech.com> Subject: Re: disappearing cdrom w/ Bt948+CAM In-Reply-To: from Shafeeq Sinnamohideen at "Jul 12, 98 04:05:13 pm" To: shafeeq@cyrus.watson.org (Shafeeq Sinnamohideen) Date: Sun, 12 Jul 1998 15:48:38 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG, gibbs@pluto.plutotech.com X-Mailer: ELM [version 2.4ME+ PL28s (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 Shafeeq Sinnamohideen wrote... > > > On Fri, 10 Jul 1998, Kenneth D. Merry wrote: > > > Jul 8 20:37:19 luthien /kernel: got an error back while probing the CDROM > > > Jul 8 20:37:19 luthien /kernel: (probe6:bt0:0:6:0): INQUIRY. CDB: 12 0 0 0 24 0 > > > Jul 8 20:37:19 luthien /kernel: (probe6:bt0:0:6:0): error code 0 > > The CAM status is 0x4a regardless of whether the cdrom is on or not. One other thing you can try, assuming your adapter isn't on ID 6, is to increase the bus settle delay. You can do that by adding something like this to your config file: options SCSI_DELAY=15 The default bus settle delay in CAM is 2 seconds, if you don't have SCSI_DELAY defined. (it is set to 15 seconds in GENERIC, though) 0x4a means that we're getting a selection timeout when we try to access the device. (and that the queue is frozen, but that's another matter) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 13 07:03:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA03222 for freebsd-scsi-outgoing; Mon, 13 Jul 1998 07:03:02 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA03217 for ; Mon, 13 Jul 1998 07:03:00 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id KAA01245 for ; Mon, 13 Jul 1998 10:02:55 -0400 (EDT) Date: Mon, 13 Jul 1998 10:02:55 -0400 (EDT) From: The Hermit Hacker To: scsi@FreeBSD.ORG Subject: CAM drivers...? 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 Morning... Just curious as to whether or not there are any upcoming snapshots? last one was may20th, I think? or did I just miss an announcement? :( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 13 08:36:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15997 for freebsd-scsi-outgoing; Mon, 13 Jul 1998 08:36:52 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15970 for ; Mon, 13 Jul 1998 08:36:49 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id JAA03322; Mon, 13 Jul 1998 09:36:34 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807131536.JAA03322@panzer.plutotech.com> Subject: Re: CAM drivers...? In-Reply-To: from The Hermit Hacker at "Jul 13, 98 10:02:55 am" To: scrappy@hub.org (The Hermit Hacker) Date: Mon, 13 Jul 1998 09:36:34 -0600 (MDT) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 The Hermit Hacker wrote... > > Morning... > > Just curious as to whether or not there are any upcoming > snapshots? last one was may20th, I think? or did I just miss an > announcement? :( You didn't miss it. The announcement will be on this list when the snapshot comes out, and the snapshot itself will be in the same places it's been before. (ftp://ftp.FreeBSD.ORG/pub/FreeBSD/cam and ftp://ftp.kdm.org/pub/FreeBSD/cam) We're working on the snapshot now, and have been for a while. The problem is that Justin keeps finding and fixing bugs, which delays things a bit. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 13 16:27:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03335 for freebsd-scsi-outgoing; Mon, 13 Jul 1998 16:27:22 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03302; Mon, 13 Jul 1998 16:27:18 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id RAA11828; Mon, 13 Jul 1998 17:27:14 -0600 (MDT) Message-Id: <199807132327.RAA11828@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: scsi@FreeBSD.ORG cc: current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: 11980712 CAM snapshot now available. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Jul 1998 17:22:01 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Complete information about this snapshot may be obtains from: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/README or ftp://ftp.kdm.org/pub/FreeBSD/cam/README The snapshot is currently available in diff form only, but a full 3.0SNAP binary release should be available on ftp.FreeBSD.org tonight or tomorrow morning. A release for 2.2-stable should follow a day later. Changes for the 19980712 Snapshot: - Ports collection now includes Tosha, cdrecord, and xmcd 2.3. - Added devstat(3) and devstat(9) man page. - Some bug fixes to the hard-wiring code. - Added preliminary Adaptec 174X driver. - Aic7xxx driver improvements: Attempt to read SEEPROM data in both formats before failing. This should allow the driver to detect a SEEPROM on many mother board controllers. Correct the setting of the SCSIID for ULTRA2 chips if we can't find a SEEPROM. Fix hang in dataphase on Rev B. aic7880 parts. Correct some LVD/Ultra2 bugs. LVD support has now been tested on a 2940U2W with both Seagate Cheetah and Quantum Atlas II LVD drives. Corrected incorrect sync rate setting for all non-ULTRA2 adapters for rates other than 20MHz or 10MHz. This was a bug introduced in the last snapshot. Fixed a few error recovery bugs. Added support for reading the SEEPROM from aic7850 based cards like the 2910C. - Corrected several bugs in the AdvanSys driver's command completion and timeout handling code as well as fully convert it to bus_dma. Thanks to John-Mark Gurney for being a patient tester. - Corrected several bugs in the BusLogic MultiMaster driver's command completion and timeout handling code. Thanks again to John-Mark Gurney for being a patient tester. - Incorperated a few bug fixes from Stefan Esser for the NCR driver. Some experimental fixes to the QUEUE FULL handler are also included. - QLogic ISP driver integrated by Matthew Jacob - Allow the CD driver to attach to WORM devices. - Corrected devstat(9) support in the floppy driver. - Added support for "short erase" as "mt erase 0". The sa driver defaults to a "long erase" as is the behavior of the st driver it replaces. - Be smarter about tape devices that lack a compression page. Corrects a problem reported by Joey Miller where the driver refused to access an Archive DDS1 drive. - Add support for PC98 geometry conversion based on code provided by KATO Takenori . - Mode page editing features have been incorporated into the camcontrol utility. - libcam now knows how to parse arbitrary command strings just like the old SCSI library. - Use 10byte CDBs for CDROM reads and writes. The spec lists 6byte CDBs as optional. - The XPT layer no longer caches sync rate information. Instead it asks the SIM driver when it wants it. This should ensure that mailbox based and cards with similar interfaces don't have to jump through hoops to provide this information via an async callback. It should make the information provided by the bt and isp drivers acurate. - Fixed several problems in the CAM_GET_PASSTHROUGH xpt ioctl. >From Hans Huebner - Updated the ch(4) driver and chio(1) command to include volume tag support. These changes have been tested with a Breeze Hill Q47 DLT and a DEC DLT2500 media changer. The latter has no volume tag support. - The chio(1) command was updated to include various flags to the status subcommand. These flags can be used to select additional information to be displayed (like volume tags). - A new chio(1) subcommand named 'voltag' has been added which allows for changes to volume tags inside the media changer controller. This could not be tested as the Q47 does not provide the functio- nality. - The ch(4) manual page was updated to include more information about the reality of this driver. - usr.sbin/rmt/rmt.c has been updated to include the V command, which is used by SGI's xfsdump to verify the rmt servers version number. -- Justin T. Gibbs Kenneth D. Merry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 13 16:43:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA06302 for freebsd-scsi-outgoing; Mon, 13 Jul 1998 16:43:44 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from kaori.communique.net (kaori.communique.net [204.27.67.55]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA06293 for ; Mon, 13 Jul 1998 16:43:40 -0700 (PDT) (envelope-from rzig@verio.net) Received: by kaori.INTERNAL with Internet Mail Service (5.0.1458.49) id ; Mon, 13 Jul 1998 18:43:02 -0500 Message-ID: From: Raul Zighelboim To: "'freebsd-scsi@freebsd.org'" Subject: FW: Another question about DPT Date: Mon, 13 Jul 1998 18:43:01 -0500 X-Priority: 3 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.0.1458.49) Content-Type: text/plain Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Here we go! > -----Original Message----- > From: Simon Shapiro [SMTP:shimon@simon-shapiro.org] > Sent: Monday, July 13, 1998 7:42 PM > To: Raul Zighelboim > Subject: RE: Another question about DPT > > > On 12-Jul-98 Raul Zighelboim wrote: > > > > Hello Smon; I ran into this extension of the DPT controller: > > http://www.dpt.com/dpt-dbus.htm > > Will FreeBSD support this configuration with 2 independet servers > > sharing the spool array ? > > Sorry for the delay... > > The dual-bus simply allows you to split the bus of a disk shelf/bay > into > two electrically independant bays. I use this option frequently to > increase perfromace; The true capacity of a SCSI bus (for random > access, > RDBMS type work) is about 4 drives. This option also increases > availability as there are two busses instead of one. > > The other part of your question is different. To hook up a SCSI bus > to two > HBAs require careful consideration of bus termination (DPT can supply > you > with an adapter which will allow you to split the bus), bus mastering, > etc. > The hardware is all there. Another consideration, DPT-specific, is > which > HBA ``owns'' the RAID arrays at any given moment. This is > particularly > critical in the case of RAID-5 and RAID-1, which need parity (or > mirrror) > writes, etc. Things get messy quickly when you consider hot standby, > automatic rebuild, etc. > > Much of the core work for this was already done, but overall, the > solution > is not complete yet. > > I have suspended this work until we complete moving the DPT driver to > CAM. > It makes little sense to do it twice. > > If you agree, please forward this reply to freebsd-scsi@freebsd.org. > It > may be of interest to others. > > > > Sincerely Yours, > > Simon Shapiro > Shimon@Simon-Shapiro.ORG > 770.265.7340 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 13 22:13:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA18872 for freebsd-scsi-outgoing; Mon, 13 Jul 1998 22:13:37 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from minotaur.com (www.minotaur.com [209.70.17.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA18863 for ; Mon, 13 Jul 1998 22:13:34 -0700 (PDT) (envelope-from jon@minotaur.com) Received: (qmail 27096 invoked from network); 14 Jul 1998 05:12:28 -0000 Received: from roaming.minotaur.com (HELO roaming) (209.70.17.100) by www.minotaur.com with SMTP; 14 Jul 1998 05:12:28 -0000 From: "Jon E. Mitchiner" To: "Justin T. Gibbs" , Cc: Subject: RE: 11980712 CAM snapshot now available. Date: Tue, 14 Jul 1998 01:13:21 -0400 Message-ID: <00a201bdaee6$1ea01280$641146d1@roaming.minotaur.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <199807132327.RAA11828@pluto.plutotech.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Are there any plans to integrate DPT PM3334UW RAID Controller to the CAM drivers in the near future? I realize most of the driver work was developed by Simon Shapiro, but I was wondering if this would happen anytime in the near future. Thanks! Jon > -----Original Message----- > From: owner-freebsd-current@FreeBSD.ORG > [mailto:owner-freebsd-current@FreeBSD.ORG]On Behalf Of Justin T. Gibbs > Sent: Monday, July 13, 1998 7:22 PM > To: scsi@FreeBSD.ORG > Cc: current@FreeBSD.ORG; stable@FreeBSD.ORG > Subject: 11980712 CAM snapshot now available. > > > Complete information about this snapshot may be obtains from: > > ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/README > > or > > ftp://ftp.kdm.org/pub/FreeBSD/cam/README > > The snapshot is currently available in diff form only, but a full > 3.0SNAP binary release should be available on ftp.FreeBSD.org tonight > or tomorrow morning. A release for 2.2-stable should follow a day > later. > > Changes for the 19980712 Snapshot: > > - Ports collection now includes Tosha, cdrecord, and xmcd 2.3. > > - Added devstat(3) and devstat(9) man page. > > - Some bug fixes to the hard-wiring code. > > - Added preliminary Adaptec 174X driver. > > - Aic7xxx driver improvements: > Attempt to read SEEPROM data in both formats before > failing. This should allow the driver to detect a > SEEPROM on many mother board controllers. > > Correct the setting of the SCSIID for ULTRA2 chips > if we can't find a SEEPROM. > > Fix hang in dataphase on Rev B. aic7880 parts. > > Correct some LVD/Ultra2 bugs. LVD support has now been > tested on a 2940U2W with both Seagate Cheetah and > Quantum Atlas II LVD drives. > > Corrected incorrect sync rate setting for all non-ULTRA2 > adapters for rates other than 20MHz or 10MHz. This was > a bug introduced in the last snapshot. > > Fixed a few error recovery bugs. > > Added support for reading the SEEPROM from aic7850 based > cards like the 2910C. > > - Corrected several bugs in the AdvanSys driver's command > completion and timeout handling code as well as fully convert > it to bus_dma. Thanks to John-Mark Gurney for being a patient > tester. > > - Corrected several bugs in the BusLogic MultiMaster driver's > command completion and timeout handling code. Thanks again to > John-Mark Gurney for being a patient tester. > > - Incorperated a few bug fixes from Stefan Esser for the NCR > driver. Some experimental fixes to the QUEUE FULL handler > are also included. > > - QLogic ISP driver integrated by Matthew Jacob > > - Allow the CD driver to attach to WORM devices. > > - Corrected devstat(9) support in the floppy driver. > > - Added support for "short erase" as "mt erase 0". The > sa driver defaults to a "long erase" as is the behavior > of the st driver it replaces. > > - Be smarter about tape devices that lack a compression > page. Corrects a problem reported by Joey Miller where > the driver refused to access an Archive DDS1 drive. > > - Add support for PC98 geometry conversion based on code provided > by KATO Takenori . > > - Mode page editing features have been incorporated into the > camcontrol utility. > > - libcam now knows how to parse arbitrary command strings just > like the old SCSI library. > > - Use 10byte CDBs for CDROM reads and writes. The spec lists > 6byte CDBs as optional. > > - The XPT layer no longer caches sync rate information. Instead > it asks the SIM driver when it wants it. This should ensure that > mailbox based and cards with similar interfaces don't have to > jump through hoops to provide this information via an async > callback. It should make the information provided by the bt > and isp drivers acurate. > > - Fixed several problems in the CAM_GET_PASSTHROUGH xpt ioctl. > > >From Hans Huebner > - Updated the ch(4) driver and chio(1) command to include volume > tag support. These changes have been tested with a Breeze Hill > Q47 DLT and a DEC DLT2500 media changer. The latter has no > volume tag support. > > - The chio(1) command was updated to include various flags to the > status subcommand. These flags can be used to select additional > information to be displayed (like volume tags). > > - A new chio(1) subcommand named 'voltag' has been added > which allows > for changes to volume tags inside the media changer controller. > This could not be tested as the Q47 does not provide the functio- > nality. > > - The ch(4) manual page was updated to include more information > about the reality of this driver. > > - usr.sbin/rmt/rmt.c has been updated to include the V command, > which is used by SGI's xfsdump to verify the rmt servers version > number. > > -- > Justin T. Gibbs > Kenneth D. Merry > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" 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 Mon Jul 13 22:17:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19651 for freebsd-scsi-outgoing; Mon, 13 Jul 1998 22:17:38 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19642 for ; Mon, 13 Jul 1998 22:17:37 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id XAA01398; Mon, 13 Jul 1998 23:17:27 -0600 (MDT) Message-Id: <199807140517.XAA01398@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Jon E. Mitchiner" cc: scsi@FreeBSD.ORG Subject: Re: 11980712 CAM snapshot now available. In-reply-to: Your message of "Tue, 14 Jul 1998 01:13:21 EDT." <00a201bdaee6$1ea01280$641146d1@roaming.minotaur.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 13 Jul 1998 23:12:15 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Are there any plans to integrate DPT PM3334UW RAID Controller to the CAM >drivers in the near future? I realize most of the driver work was developed >by Simon Shapiro, but I was wondering if this would happen anytime in the >near future. It depends on what your interpretation of "near future" is. It will be integrated before 3.0 is released, but when exactly depends on when I have the spare time to do it. The DPT driver is competing with the 1742, 1542, and aic6260/6360 for my attention. Right now I'm working on the 1742 driver. Which driver I do next I haven't decided, but they will all be integrated before 3.0. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 13 23:21:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA26004 for freebsd-scsi-outgoing; Mon, 13 Jul 1998 23:21:52 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA25999 for ; Mon, 13 Jul 1998 23:21:46 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id IAA28543; Tue, 14 Jul 1998 08:21:41 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id IAA11281; Tue, 14 Jul 1998 08:20:09 +0200 (MET DST) Message-ID: <19980714082009.64422@uriah.heep.sax.de> Date: Tue, 14 Jul 1998 08:20:09 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Cc: Matthew Patton Subject: Re: ZIP support in 2.2.6 Reply-To: Joerg Wunsch References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Matthew Patton on Thu, Jul 02, 1998 at 02:55:25AM -0400 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Matthew Patton wrote: > I looked thru the recent archives and I haven't seen much in they > way of dealing with ZIP drives. My external SCSI version shows up as > an "sd" device. So is software eject supported? What's the command > to use? One probably can't call it exactly `supported', but scsi -f /dev/rsdN.ctl -c "1b 0 0 0 2 0" is supposed to work. It's a START STOP UNIT command, with the Start bit being 0 (== `stop'), and the LoEj bit being 1 (== Eject). Put it into a setuid perl script by now to make it a command more convenient to use. Don't forget to set $ENV{PATH} on top, or suidperl will refuse to run your system() command. -- 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. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 07:01:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06098 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 07:01:32 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from enigami.com (enigami.com [208.140.182.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06079 for ; Tue, 14 Jul 1998 07:01:17 -0700 (PDT) (envelope-from ckempf@enigami.com) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by enigami.com (8.9.0/8.9.0) with ESMTP id KAA28096 for ; Tue, 14 Jul 1998 10:00:37 -0400 (EDT) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id KAA00506; Tue, 14 Jul 1998 10:00:33 -0400 (EDT) To: freebsd-scsi@FreeBSD.ORG Subject: CAM, dewfs, camcontrol, CD's X-Copyright: Copyright (C) 1998 Cory Kempf. All Rights Reserved X-PGP-Fingerprint: 191E 2FB7 E27D 76C3 8E79 4D26 2B3B B20F 2A9C 1E1A X-PGP-Keyloc: ; finger ckempf@enigami.com From: Cory Kempf Date: 13 Jul 1998 23:32:42 -0400 In-Reply-To: "Justin T. Gibbs"'s message of "Mon, 13 Jul 1998 17:22:01 -0600" Message-ID: Lines: 21 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I could swear I have posted this at least twice now, but the original doesn't seem to be on my machine for some reason. And if the answer has changed with the new snapshot, well, it is downloading now. OK, I am poking into CAM, trying to get the SCSI card that came with my scanner to work (see other message). I noticed that the CD ROM drive, which seems to be identified via dmesg, and mounts CDs, doesn't seem to exist in devfs. Has this simply not been done yet? On a related note, camcontrol -l doesn't list my CD drive either. +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 07:01:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06114 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 07:01:35 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from enigami.com (enigami.com [208.140.182.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06106 for ; Tue, 14 Jul 1998 07:01:32 -0700 (PDT) (envelope-from ckempf@enigami.com) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by enigami.com (8.9.0/8.9.0) with ESMTP id KAA28100 for ; Tue, 14 Jul 1998 10:00:53 -0400 (EDT) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id KAA00509; Tue, 14 Jul 1998 10:00:49 -0400 (EDT) To: freebsd-scsi@FreeBSD.ORG Subject: 'Domex' SCSI bus? References: <199807132327.RAA11828@pluto.plutotech.com> X-Copyright: Copyright (C) 1998 Cory Kempf. All Rights Reserved X-PGP-Fingerprint: 191E 2FB7 E27D 76C3 8E79 4D26 2B3B B20F 2A9C 1E1A X-PGP-Keyloc: ; finger ckempf@enigami.com From: Cory Kempf Date: 13 Jul 1998 23:38:29 -0400 In-Reply-To: "Justin T. Gibbs"'s message of "Mon, 13 Jul 1998 17:22:01 -0600" Message-ID: Lines: 31 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I could swear I have posted this at least twice now, but the original doesn't seem to be on my machine for some reason. And if the answer has changed with the new snapshot, well, it is downloading now. I just bought a Umax Astra 1220S scanner, with the intention of making it and SANE work with CAM. The scanner came with a SCSI card that is labled 'Domex'. I am running on a DK440LX, which has a pair of 7895's that work OK, but well, to use the internal SCSI, I would need to build a ribbon cable to export the narrow SCSI. Plugging in the card seemed easier... So, I plug in the card, but it doesn't seem to want to work. At least, it isn't recognized on boot. Anyone know how to make this card work with CAM? Or do I need to try and build a ribbon cable? Thanks, +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 07:01:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06138 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 07:01:52 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from enigami.com (enigami.com [208.140.182.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06131 for ; Tue, 14 Jul 1998 07:01:50 -0700 (PDT) (envelope-from ckempf@enigami.com) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by enigami.com (8.9.0/8.9.0) with ESMTP id KAA28104 for ; Tue, 14 Jul 1998 10:01:14 -0400 (EDT) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id KAA00512; Tue, 14 Jul 1998 10:01:10 -0400 (EDT) To: freebsd-scsi@FreeBSD.ORG Subject: cam/scsi include files X-Copyright: Copyright (C) 1998 Cory Kempf. All Rights Reserved X-PGP-Fingerprint: 191E 2FB7 E27D 76C3 8E79 4D26 2B3B B20F 2A9C 1E1A X-PGP-Keyloc: ; finger ckempf@enigami.com From: Cory Kempf Date: 13 Jul 1998 23:45:01 -0400 In-Reply-To: "Justin T. Gibbs"'s message of "Mon, 13 Jul 1998 17:22:01 -0600" Message-ID: Lines: 32 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I could swear I have posted this at least twice now, but the original doesn't seem to be on my machine for some reason. And if the answer has changed with the new snapshot, well, it is downloading now. While perusing the SANE source, I noticed that it checks for the existance of files under /usr/include/scsi... and if it finds them, determines that it should use the BSD SCSI interface. On my machine, it finds them, and builds successfully (haven't tried running, as the SCSI bus isn't quite working yet... see other message). Is /usr/include/scsi obsolete with CAM? Assuming it is, perhaps it might be a good idea to include a shell script to move that (and any other obsolete files... e.g. libraries?) to say, scsi.old or some such? On a related note, I noticed that DEC's CAM interface stores its include files under /usr/include/io/cam... shouldn't we also? Personally, I find it rather annoying when different vendor's unixes stick things in different locations. It makes writing portable stuffs more difficult. +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 08:10:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16270 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 08:10:48 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA16249; Tue, 14 Jul 1998 08:10:45 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id JAA24833; Tue, 14 Jul 1998 09:10:39 -0600 (MDT) Message-Id: <199807141510.JAA24833@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: scsi@FreeBSD.ORG cc: stable@FreeBSD.ORG Subject: Bug in 2.2CAM-19980712-SNAP.diffs.gz Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Jul 1998 09:05:26 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The paths for new files in this diff file were screwed up, and I have uploaded a corrected version. Sorry for the inconvenience. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 08:36:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA19866 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 08:36:03 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA19829 for ; Tue, 14 Jul 1998 08:36:01 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id JAA08707; Tue, 14 Jul 1998 09:35:46 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807141535.JAA08707@panzer.plutotech.com> Subject: Re: CAM, dewfs, camcontrol, CD's In-Reply-To: from Cory Kempf at "Jul 13, 98 11:32:42 pm" To: ckempf@enigami.com (Cory Kempf) Date: Tue, 14 Jul 1998 09:35:46 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Cory Kempf wrote... > I could swear I have posted this at least twice now, but the original > doesn't seem to be on my machine for some reason. And if the answer > has changed with the new snapshot, well, it is downloading now. > > OK, I am poking into CAM, trying to get the SCSI card that came with > my scanner to work (see other message). I noticed that the CD ROM > drive, which seems to be identified via dmesg, and mounts CDs, doesn't > seem to exist in devfs. > > Has this simply not been done yet? That's correct, CAM doesn't coexist with devfs yet. Just use the standard device nodes and you should be fine. > On a related note, camcontrol -l doesn't list my CD drive either. A common misconception. camcontrol -l is not supposed to list every SCSI device in your system. I've gotten this same question numerous times. The -l option only lists peripheral drivers attached to a particular physical device. I've got another camcontrol option planned that *will* list every CAM device, but it's not in there yet. Here are a few examples of how camcontrol -l works: {roadwarrior:/usr/home/ken:11:0} camcontrol -l pass0: generation: 4 index: 1 status: MORE da0: generation: 4 index: 2 status: LAST {roadwarrior:/usr/home/ken:12:0} camcontrol -n da -u 1 -l pass1: generation: 4 index: 1 status: MORE da1: generation: 4 index: 2 status: LAST {roadwarrior:/usr/home/ken:13:0} camcontrol -n cd -l pass2: generation: 4 index: 1 status: MORE cd0: generation: 4 index: 2 status: LAST So, you see, it just lists the (in this case) two peripheral drivers attached to each physical device in the system. If you want to see *every* device in the system, I'd suggest getting the 'ds.c' program on the ftp sites. It prints out the entire devstat table, which includes device name/unit number. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 08:38:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20262 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 08:38:22 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20257 for ; Tue, 14 Jul 1998 08:38:20 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id JAA08720; Tue, 14 Jul 1998 09:38:11 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807141538.JAA08720@panzer.plutotech.com> Subject: Re: 'Domex' SCSI bus? In-Reply-To: from Cory Kempf at "Jul 13, 98 11:38:29 pm" To: ckempf@enigami.com (Cory Kempf) Date: Tue, 14 Jul 1998 09:38:11 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Cory Kempf wrote... > I could swear I have posted this at least twice now, but the original > doesn't seem to be on my machine for some reason. And if the answer > has changed with the new snapshot, well, it is downloading now. > > I just bought a Umax Astra 1220S scanner, with the intention of making > it and SANE work with CAM. Good, we need that ported. :) > The scanner came with a SCSI card that is labled 'Domex'. > > I am running on a DK440LX, which has a pair of 7895's that work OK, > but well, to use the internal SCSI, I would need to build a ribbon > cable to export the narrow SCSI. Plugging in the card seemed > easier... > > So, I plug in the card, but it doesn't seem to want to work. At > least, it isn't recognized on boot. > > Anyone know how to make this card work with CAM? Or do I need to try > and build a ribbon cable? I've never heard of a "Domex" card. My guess is that it's either based on either an Advansys or NCR chip. Look on the card, and see what kind of chip it has. That should give you an idea as to whether it's supported or not. If you can't do that, find a web site for "Domex", and look at the card specs there. They'll usually tell you what sort of SCSI chip they have on the board. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 08:45:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA20743 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 08:45:24 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA20736 for ; Tue, 14 Jul 1998 08:45:21 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id JAA08757; Tue, 14 Jul 1998 09:44:47 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807141544.JAA08757@panzer.plutotech.com> Subject: Re: cam/scsi include files In-Reply-To: from Cory Kempf at "Jul 13, 98 11:45:01 pm" To: ckempf@enigami.com (Cory Kempf) Date: Tue, 14 Jul 1998 09:44:47 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Cory Kempf wrote... > I could swear I have posted this at least twice now, but the original > doesn't seem to be on my machine for some reason. And if the answer > has changed with the new snapshot, well, it is downloading now. > > While perusing the SANE source, I noticed that it checks for the > existance of files under /usr/include/scsi... and if it finds them, > determines that it should use the BSD SCSI interface. There's no /usr/include/scsi directory, even with the old SCSI code. > On my machine, it finds them, and builds successfully (haven't tried > running, as the SCSI bus isn't quite working yet... see other > message). > > Is /usr/include/scsi obsolete with CAM? Assuming it is, perhaps it > might be a good idea to include a shell script to move that (and any > other obsolete files... e.g. libraries?) to say, scsi.old or some > such? It is, and isn't obsolete. It's actually "/usr/include/scsi.h". One or two people have asked for a compatibility interface with the old SCSI code under CAM. If that happens, we'll need the old code as well as the new. If you're concerned about porting stuff to CAM, I would suggest testing for the presence of /usr/include/camlib.h. That's what I did in the cdrecord, tosha and xmcd ports. > On a related note, I noticed that DEC's CAM interface stores its > include files under /usr/include/io/cam... shouldn't we also? > > Personally, I find it rather annoying when different vendor's unixes > stick things in different locations. It makes writing portable stuffs > more difficult. I don't see any real reason to stick things in the same place DEC's CAM implementation does. It isn't defined in the spec (AFAIK), and our data structures differ from theirs anyways. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 11:32:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA17859 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 11:32:13 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from fledge.watson.org (shafeeq@COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA17811 for ; Tue, 14 Jul 1998 11:32:09 -0700 (PDT) (envelope-from shafeeq@cyrus.watson.org) Received: from localhost (shafeeq@localhost) by fledge.watson.org (8.8.8/8.8.8) with SMTP id OAA10761; Tue, 14 Jul 1998 14:31:57 -0400 (EDT) X-Authentication-Warning: fledge.watson.org: shafeeq owned process doing -bs Date: Tue, 14 Jul 1998 14:31:57 -0400 (EDT) From: Shafeeq Sinnamohideen X-Sender: shafeeq@fledge.watson.org To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG, gibbs@pluto.plutotech.com Subject: Re: disappearing cdrom w/ Bt948+CAM In-Reply-To: <199807122148.PAA29521@panzer.plutotech.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 > options SCSI_DELAY=15 > > The default bus settle delay in CAM is 2 seconds, if you don't have > SCSI_DELAY defined. (it is set to 15 seconds in GENERIC, though) > > 0x4a means that we're getting a selection timeout when we try to > access the device. (and that the queue is frozen, but that's another > matter) > So here is the full dmesg with SCSI_DELAY=15 (it was 5 before) : Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #3: Tue Jul 14 14:14:09 EDT 1998 shafeeq@luthien.watson.org:/data/freebsd/current-cam/src/sys/compile/LUTHIEN-SMP-CAM-SOFT Timecounter "i8254" frequency 1193182 Hz cost 2756 ns CPU: Pentium (586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x3bf real memory = 67108864 (65536K bytes) avail memory = 62296064 (60836K bytes) FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00030010, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00030010, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 de0: rev 0x22 int a irq 19 on pci0.17.0 de0: 21140A [10-100Mb/s] pass 2.2 de0: address 00:40:05:51:1d:58 vga0: rev 0x01 int a irq 18 on pci0.18.0 bt0: rev 0x08 int a irq 17 on pci0.19.0 bt0: BT-948 FW Rev. 5.06I Ultra Narrow SCSI Host Adapter, SCSI ID 7, 192 CCBs Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <8 virtual consoles, flags=0x0> ed0 at 0x360-0x37f irq 11 maddr 0xd8000 msize 8192 on isa ed0: address 00:e0:29:03:b7:83, type SMC8416C/SMC8416BT (16 bit) ed1 at 0x300-0x31f irq 10 maddr 0xd0000 msize 16384 on isa ed1: address 00:00:c0:6a:81:bc, type SMC8216T (16 bit) sio0 not found at 0x3f8 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A adv0 not found bt: unit number (1) too high bt1 not found npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at ? drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: opl0 at 0x388 on isa snd0: stray irq 7 Intel Pentium F00F detected, installing workaround struct nfsmount bloated (> 512bytes) Try reducing NFS_MUIDHASHSIZ APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert disabled, logging disabled SMP: AP CPU #1 Launched! got an error back while probing the CDROM (probe6:bt0:0:6:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe6:bt0:0:6:0): error code 0 CAM status is 0x4a sa0 at bt0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: Serial Number DR055JT sa0: 6.756MB/s transfers (6.756MHz, offset 15) da0 at bt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 3.300MB/s transfers da0: 257MB (528354 512 byte sectors: 64H 32S/T 257C) da3 at bt0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI2 device da3: Serial Number 174718930168 da3: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da3: 4345MB (8899737 512 byte sectors: 255H 63S/T 553C) da1 at bt0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: Serial Number 0000A00000 da1: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da1: 1001MB (2051000 512 byte sectors: 64H 32S/T 1001C) da2 at bt0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI2 device da2: 10.0MB/s transfers (10.0MHz, offset 8) da2: 516MB (1057616 512 byte sectors: 64H 32S/T 516C) changing root device to da0s1a de0: enabling 10baseT port cd0 at bt0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 6.756MB/s transfers (6.756MHz, offset 15) cd0: cd present [314673 x 2048 byte records] This is still with the 980520 CAM snap, I haven't yet gotten to try the latest one, but will probably do so very soon. Thanks, Shafeeq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 12:09:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25906 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 12:09:58 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mailhub.fokus.gmd.de ([193.174.154.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25888 for ; Tue, 14 Jul 1998 12:09:35 -0700 (PDT) (envelope-from schilling@fokus.gmd.de) Received: from sherwood.gmd.de (sherwood [193.175.133.102]) by mailhub.fokus.gmd.de (8.8.8/8.8.8) with ESMTP id VAA07385; Tue, 14 Jul 1998 21:08:38 +0200 (MET DST) Received: (from jes@localhost) by sherwood.gmd.de (8.8.8+Sun/8.8.8) id VAA28697; Tue, 14 Jul 1998 21:07:30 +0200 (MET DST) Date: Tue, 14 Jul 1998 21:07:30 +0200 (MET DST) From: Joerg Schilling Message-Id: <199807141907.VAA28697@sherwood.gmd.de> To: freebsd-scsi@FreeBSD.ORG Cc: schilling@fokus.gmd.de Subject: RE: 11980712 CAM snapshot now available. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am not subscribed to this list, leave me in the Cc: Some notes: About tosha: Did you ever try to compile the actual cdda2wav? ftp://ftp.fokus.gmd.de/pub/unix/cdrecord/alpha If you replace the SCSI transport, it should work as cdrecord - it uses the cdrecord SCSI transport library. About /etc/rmt : It seems that many companies (in this case SGI) did not understand the rmt protocol right. From peeking into the SGI /etc/rmt binary, it seems that there is no real RMT V2 protocol but a plain old BSD 4.2 V.0 rmt with a funny V command. But how about adding support for the rmt V1 protocol defined with SYSVr4. This add real interesting new features: - Support for the rmtioctl commands bejond 0..7 (WARNING: even 0..7 are violated by Linux & AIX) - Byteorder and structure size independent fetching of the rmt status structure If you arre interested to implement this, first have a look into the file star/remote.c in the star distribution. ftp://ftp.fokus.gmd.de/pub/unix/star If you have questions, ask me. If you like to be in the star mailing list, send mail to: majordomo@fokus.gmd.de and include: subscribe star in the mail body. This list is for discussing: - Bugs and new features of star. - Enhancements to the POSIX-1003.1 tar archive format (such as files > 2 GB, the FreeBSD minor device node problematic, access control lists, special file status flags from BSD-4.4) Jörg EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin js@cs.tu-berlin.de (uni) If you don't have iso-8859-1 schilling@fokus.gmd.de (work) chars I am J"org Schilling URL: http://www.fokus.gmd.de/usr/schilling ftp://ftp.fokus.gmd.de/pub/unix To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 12:40:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01337 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 12:40:57 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01318; Tue, 14 Jul 1998 12:40:54 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id NAA07875; Tue, 14 Jul 1998 13:40:48 -0600 (MDT) Message-Id: <199807141940.NAA07875@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: scsi@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: 3.0CAM-19980712-SNAP release availalable Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 14 Jul 1998 13:35:35 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org A full CAM release is now available at: ftp://ftp.FreeBSD.org/pub/cam/3.0CAM-19980712-SNAP/ -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 13:07:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05778 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 13:07:02 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05772 for ; Tue, 14 Jul 1998 13:06:59 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id OAA09972; Tue, 14 Jul 1998 14:06:50 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807142006.OAA09972@panzer.plutotech.com> Subject: Re: disappearing cdrom w/ Bt948+CAM In-Reply-To: from Shafeeq Sinnamohideen at "Jul 14, 98 02:31:57 pm" To: shafeeq@cyrus.watson.org (Shafeeq Sinnamohideen) Date: Tue, 14 Jul 1998 14:06:50 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG, gibbs@pluto.plutotech.com X-Mailer: ELM [version 2.4ME+ PL28s (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 Shafeeq Sinnamohideen wrote... > > options SCSI_DELAY=15 > > > > The default bus settle delay in CAM is 2 seconds, if you don't have > > SCSI_DELAY defined. (it is set to 15 seconds in GENERIC, though) > > > > 0x4a means that we're getting a selection timeout when we try to > > access the device. (and that the queue is frozen, but that's another > > matter) > > > So here is the full dmesg with SCSI_DELAY=15 (it was 5 before) : [ ... ] > bt0: rev 0x08 int a irq 17 on pci0.19.0 > bt0: BT-948 FW Rev. 5.06I Ultra Narrow SCSI Host Adapter, SCSI ID 7, 192 CCBs That looks right -- ID 7. > SMP: AP CPU #1 Launched! > got an error back while probing the CDROM > (probe6:bt0:0:6:0): INQUIRY. CDB: 12 0 0 0 24 0 > (probe6:bt0:0:6:0): error code 0 > CAM status is 0x4a And that's as expected -- selection timeout. [ ... ] > This is still with the 980520 CAM snap, I haven't yet gotten to try the > latest one, but will probably do so very soon. If you do, let me know how it goes. I'm really not sure what your problem is. If things don't work properly for you with the new snapshot, my guess is that the only way to find out what's going on will be to send us the drive. (we can hook it up to a bus analyzer and try to see what the problem is) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 14:18:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16073 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 14:18:14 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA16065 for ; Tue, 14 Jul 1998 14:18:11 -0700 (PDT) (envelope-from rhh@ct.picker.com) Received: from ct.picker.com by whqvax.picker.com with SMTP; Tue, 14 Jul 1998 17:17:29 -0400 (EDT) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA26074; Tue, 14 Jul 98 17:17:29 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id RAA03267; Tue, 14 Jul 1998 17:16:56 -0400 Message-Id: <19980714171656.A3254@ct.picker.com> Date: Tue, 14 Jul 1998 17:16:56 -0400 From: Randall Hopper To: Matthew Patton , freebsd-scsi@FreeBSD.ORG Subject: Re: ZIP support in 2.2.6 Mail-Followup-To: Matthew Patton , freebsd-scsi@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Matthew Patton on Thu, Jul 02, 1998 at 02:55:25AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Patton: |I looked thru the recent archives and I haven't seen much in they way of |dealing with ZIP drives. My external SCSI version shows up as an "sd" |device. So is software eject supported? What's the command to use? There |doesn't seem to be any flags for "umount" or an "eject" command for that |matter. | |Please respond directly, I'm not subscribed to the list just yet. Thanks. scsi -f /dev/rsd0.ctl -s 30 -c '1b 0 0 0 0:b6 v:b1 v:b1 0' 1 0 I picked this off the list archives a while back, and I use it in my "umountzip" Perl script with my SCSI ZIP. Randall To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 19:25:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA27700 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 19:25:42 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA27691 for ; Tue, 14 Jul 1998 19:25:37 -0700 (PDT) (envelope-from semen@iclub.nsu.ru) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id JAA08420 for ; Wed, 15 Jul 1998 09:30:10 +0700 (NSS) Date: Wed, 15 Jul 1998 09:30:10 +0700 (NSS) From: Ustimenko Semen To: Subject: About to reset single device on SCSI bus 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 Hello! Does anybody know how to reinitialize SCSI device without reinitialization of all bus? The problem is that SDT-7000 (DDS-2 Tape) somehow gets in stupid mode, when it works with the speed of 15-20 Kb/s, else in doesn't whant to read tapes written in normal state and etc. But after reset the computer, it works just fine. So I think Subject can help me to avoid reboot and to get SDT-7000 in normal state. Thanks in forward. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 21:42:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14637 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 21:42:09 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14632 for ; Tue, 14 Jul 1998 21:42:06 -0700 (PDT) (envelope-from dan@math.berkeley.edu) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id VAA02653; Tue, 14 Jul 1998 21:41:59 -0700 (PDT) Date: Tue, 14 Jul 1998 21:41:59 -0700 (PDT) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199807150441.VAA02653@math.berkeley.edu> To: semen@iclub.nsu.ru Subject: Re: About to reset single device on SCSI bus Cc: dan@math.berkeley.edu, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Does anybody know how to reinitialize SCSI device without > reinitialization of all bus? The problem is that SDT-7000 > (DDS-2 Tape) somehow gets in stupid mode, when it works with > the speed of 15-20 Kb/s, else in doesn't whant to read tapes > written in normal state and etc. But after reset the computer, > it works just fine. So I think Subject can help me to avoid > reboot and to get SDT-7000 in normal state. I don't see an option to the scsi(8) command that does this. There is an SCIOCRESET ioctl() that might might apply to a single device. There is a SCSI message for resetting a single device, but I don't if this ioctl() actually sends it or if it is likely to work. I assume it is worth a try. You might have to open the ".ctl" device to make this work. I have a program that will do this, but it just keeps saying "SCIOCRESET: Inappropriate ioctl for device" which I think offhand is error ENOTTY. I have not scoured the kernel scsi device drivers to determine what they really want from me. Dan Strick dan@math.berkeley.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 22:04:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA17362 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 22:04:03 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gjp.erols.com (root@alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA17326 for ; Tue, 14 Jul 1998 22:03:59 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id BAA13146 for ; Wed, 15 Jul 1998 01:03:52 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: From: "Gary Palmer" Subject: recent cam snapshot Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Jul 1998 01:03:52 -0400 Message-ID: <13142.900479032@gjp.erols.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I just installed the latest SNAP on -currnent (via make world) and have a question about camcontrol. I tried using it and fast ran into a brick wall. root@gjp:~/cam> camcontrol -l camcontrol: cam_real_open_device: CAMGETPASSTHRU ioctl failed cam_real_open_device: No such file or directory I've tried numerous argument combinations with no luck so far. Similarly with ``camcontrol -i''. Anyone got any hints as to how to use the command? I also guess that the new support for devfs causes the scsi chains to be probed at the end of the kernel bootstrap? Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #1: Wed Jul 15 00:02:32 EDT 1998 root@gjp.erols.com:/d0/src/sys/compile/HOME-SMP Timecounter "i8254" frequency 1193182 Hz cost 3378 ns CPU: Pentium Pro (686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff real memory = 268435456 (262144K bytes) avail memory = 258445312 (252388K bytes) FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 1, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 0, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 vga0: rev 0x00 int a irq 15 on pci0.10.0 fxp0: rev 0x02 int a irq 19 on pci0.11.0 fxp0: Ethernet address 00:a0:c9:8a:ee:cc chip2: rev 0x01 on pci0.13.0 fxp1: rev 0x02 int a irq 16 on pci0.14.0 fxp1: Ethernet address 00:a0:c9:8a:d2:c7 Probing for devices on PCI bus 1: ahc0: rev 0x00 int a irq 17 on pci1.4.0 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 18 on pci1.5.0 ahc1: aic7880 Single Channel B, SCSI Id=7, 16/255 SCBs Probing for PnP devices: CSN 1 Vendor ID: CTL00c1 [0xc1008c0e] Serial 0x0082a879 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 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: model Generic PS/2 mouse, device ID 0 pca0 on motherboard pca0: PC speaker audio driver fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at ? drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: awe0 at 0x620 on isa AWE32: not detected APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 IP packet filtering initialized, divert enabled, rule-based forwarding disabled, logging disabled SMP: AP CPU #1 Launched! (probe7:ahc1:0:0:0): Sending SDTR!! changing root device to da0s1a da1 at ahc1 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da1: 519MB (1064268 512 byte sectors: 64H 32S/T 519C) da2 at ahc0 bus 0 target 1 lun 0 da2: Fixed Direct Access SCSI2 device da2: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da2: 4095MB (8386733 512 byte sectors: 255H 63S/T 522C) da3 at ahc1 bus 0 target 1 lun 0 da3: Fixed Direct Access SCSI2 device da3: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da3: 4095MB (8386733 512 byte sectors: 255H 63S/T 522C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da0: 4136MB (8471232 512 byte sectors: 255H 63S/T 527C) cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present (da0:ahc0:0:0:0): tagged openings now 8 (da3:ahc1:0:1:0): tagged openings now 63 The CDROM was detected noticably later than the disks, I guess because of the timeout trying to probe the size? What is the default number of tags per device? It logs the fact that they've changed, but doesn't indicate if its a change down or up, and what the previous value was... Thanks, Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jul 14 22:48:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22870 for freebsd-scsi-outgoing; Tue, 14 Jul 1998 22:48:30 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22865; Tue, 14 Jul 1998 22:48:25 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id XAA01518; Tue, 14 Jul 1998 23:48:18 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807150548.XAA01518@panzer.plutotech.com> Subject: Re: recent cam snapshot In-Reply-To: <13142.900479032@gjp.erols.com> from Gary Palmer at "Jul 15, 98 01:03:52 am" To: (Gary Palmer) Date: Tue, 14 Jul 1998 23:48:18 -0600 (MDT) Cc: X-Mailer: ELM [version 2.4ME+ PL28s (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 Gary Palmer wrote... > > Hi, > > I just installed the latest SNAP on -currnent (via make world) and have > a question about camcontrol. I tried using it and fast ran into a > brick wall. > > root@gjp:~/cam> camcontrol -l > camcontrol: cam_real_open_device: CAMGETPASSTHRU ioctl failed > cam_real_open_device: No such file or directory > > I've tried numerous argument combinations with no luck so far. Similarly > with ``camcontrol -i''. Anyone got any hints as to how to use > the command? Generally, it should work. Make sure your copy of libcam is up to date, and make sure that your camcontrol binary was linked against it. Also make sure your kernel is up to date. There have been some changes in the CAMGETPASSTHRU ioctl in the transport layer recently. Basically, what it's telling you above is that for whatever reason it can't find one of three things: - the general type of peripheral driver you're looking for, which is in this case "da", since you didn't specify any other argument for camcontrol. - the particular peripheral driver you're looking for, which is in this case da0, since you didn't specify any arguments. - the passthrough driver associated with da0. I'm not sure why you'd be having trouble with this, unless something is out of date or the snapshot is somehow messed up. I know that the first sets of diffs Justin put up for both -current and -stable last night didn't apply cleanly, but surely you would have noticed a problem when you applied the patch. Try specifying the device you want, like this: camcontrol -t -n cd -u 0 camcontrol -i -n da -u 2 > I also guess that the new support for devfs causes the scsi chains > to be probed at the end of the kernel bootstrap? New support for DEVFS? No. The reason scsi devices appear at the end of the kernel boot messages, and often out of order, is that they are probed once interrupts are enabled. Devices are probed in ascending order by bus, target, and lun, but they appear in the order that they respond to the probe commands. > (probe7:ahc1:0:0:0): Sending SDTR!! > changing root device to da0s1a > da1 at ahc1 bus 0 target 0 lun 0 > da1: Fixed Direct Access SCSI2 device > da1: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled > da1: 519MB (1064268 512 byte sectors: 64H 32S/T 519C) > da2 at ahc0 bus 0 target 1 lun 0 > da2: Fixed Direct Access SCSI2 device > da2: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled > da2: 4095MB (8386733 512 byte sectors: 255H 63S/T 522C) > da3 at ahc1 bus 0 target 1 lun 0 > da3: Fixed Direct Access SCSI2 device > da3: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled > da3: 4095MB (8386733 512 byte sectors: 255H 63S/T 522C) > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI2 device > da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled > da0: 4136MB (8471232 512 byte sectors: 255H 63S/T 527C) > cd0 at ahc0 bus 0 target 6 lun 0 > cd0: Removable CD-ROM SCSI2 device > cd0: 3.300MB/s transfers > cd0: Attempt to query device size failed: NOT READY, Medium not present > (da0:ahc0:0:0:0): tagged openings now 8 > (da3:ahc1:0:1:0): tagged openings now 63 > > The CDROM was detected noticably later than the disks, I guess > because of the timeout trying to probe the size? It's more likely that the CDROM drive was just slower to respond. We do ask twice for the size, though, and only fail after the second negative response. So I guess that would also cause it to come back last. Generally, my CDROM drives probe last, even if they do have media in them. > What is the default number of tags per device? It logs the fact > that they've changed, but doesn't indicate if its a change down > or up, and what the previous value was... The default number of tags is 64. I'm surprised you only see "tagged openings now 8" for your Fireball ST. I would think that you would see more log messages than that. There are some drives for which the default number of tags is lower, mainly the Quantum Atlas II's. Look at the xpt_quirk_table in src/sys/cam/cam_xpt.c Ken -- Kenneth Merry Ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 00:18:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA05405 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 00:18:20 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA05400 for ; Wed, 15 Jul 1998 00:18:18 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id JAA06612; Wed, 15 Jul 1998 09:18:01 +0200 (MET DST) Date: Wed, 15 Jul 1998 09:17:59 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Randall Hopper cc: Matthew Patton , freebsd-scsi@FreeBSD.ORG Subject: Re: ZIP support in 2.2.6 In-Reply-To: <19980714171656.A3254@ct.picker.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 I've written a tool that will do an eject of JAZ drives upon request, a removable media daemon for CDROMs (IDE, SCSI) and JAZ drives (SCSI). So it might work on ZIP drives as well. http://www.etla.net/~n_hibma/rmd/ Let me know if it does (or does not). Nick > |I looked thru the recent archives and I haven't seen much in they way of > |dealing with ZIP drives. My external SCSI version shows up as an "sd" > |device. So is software eject supported? What's the command to use? There > |doesn't seem to be any flags for "umount" or an "eject" command for that > |matter. > | > |Please respond directly, I'm not subscribed to the list just yet. Thanks. > > scsi -f /dev/rsd0.ctl -s 30 -c '1b 0 0 0 0:b6 v:b1 v:b1 0' 1 0 > > I picked this off the list archives a while back, and I use it in my > "umountzip" Perl script with my SCSI ZIP. > > Randall > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > -- building: 27A address: STA-ISIS, T.P.270, Joint Research Centre, 21020 Ispra, Italy tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 01:19:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA12662 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 01:19:31 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from top.worldcontrol.com (surf52.cruzers.com [205.215.232.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA12655 for ; Wed, 15 Jul 1998 01:19:29 -0700 (PDT) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 9708 invoked by uid 100); 15 Jul 1998 08:19:59 -0000 Message-ID: <19980715011956.A9688@top.worldcontrol.com> Date: Wed, 15 Jul 1998 01:19:56 -0700 To: Subject: CAM 19980712 build troubles Mail-Followup-To: freebsd-scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been running CAM since it first showed up on -current. I'm trying to move from 19980520 to 19980712 without much luck. I'm not CTM literate so I can't grab the 19980712 current, thus I instead grabbed ftp://ftp.cdrom.com/pub/FreeBSD/cam/3.0CAM-19980712-SNAP/src/* and untar'ed it all into a blank /usr/src I then basically followed the CAM README instructions. (skipping the patch, it seems to already be applied) make buildworld dies running mtree complaining that it doesn't recognize 'nochange' on line 58. I recompiled and re-installed mtree but it did not help. Even if you ignore that error, buildworld dies elsewhere: cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/uss/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/uss/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /uss/src/lib/libc/../libc/gen/lockf.c -o lockf.o /uss/src/lib/libc/../libc/gen/lockf.c: In function `lockf': /uss/src/lib/libc/../libc/gen/lockf.c:62: `F_ULOCK' undeclared (first use this f I also tried building a kernel. This worked fine, but the kernel panic'ed when trying to boot the root device just after it said /kernel: changing root device to sd0s2a. which seemed unusual to me. The 19980520 CAM kernel says /kernel.old: changing root device to da0s2a which makes more sense to me. Basically, I am lost as to how to proceed. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 01:54:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA16350 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 01:54:21 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gjp.erols.com (root@alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA16343 for ; Wed, 15 Jul 1998 01:54:20 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id EAA13891; Wed, 15 Jul 1998 04:54:11 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: "Kenneth D. Merry" cc: From: "Gary Palmer" Subject: Re: recent cam snapshot In-reply-to: Your message of "Tue, 14 Jul 1998 23:48:18 MDT." <199807150548.XAA01518@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 15 Jul 1998 04:54:10 -0400 Message-ID: <13887.900492850@gjp.erols.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" wrote in message ID <199807150548.XAA01518@panzer.plutotech.com>: > Generally, it should work. Make sure your copy of libcam is up to > date, and make sure that your camcontrol binary was linked against it. Also > make sure your kernel is up to date. There has never been CAM on this machine before. I upgraded by doing a CVS `co' of the appropriate -current source (with a -D flag that I hope would specify the matching source tree to the patches), and then following the instructions in the README file. The only problem I had was when I rebooted and I realised I had forgotten a patch to i386/i386/mp_machdep.c that correctly wires the IRQ's for my PCI bridged 3940 card (which the bios doesn't do correclty in the MP table) Since camcontrol is not dynamic, I am not sure how to check, but it seems unlikely that it would have picked up the wrong libcam where there is only one version on my system :) > I'm not sure why you'd be having trouble with this, unless > something is out of date or the snapshot is somehow messed up. I know that > the first sets of diffs Justin put up for both -current and -stable last > night didn't apply cleanly, but surely you would have noticed a problem > when you applied the patch. The NCR driver had two rejects (which I didn't care about since I don't use NCR/Symbios cards), and it complained that it couldn't patch /sys/i386/conf/ASLAN. I have the full patch output if you are interested (tee is your friend :) ) > Try specifying the device you want, like this: > > camcontrol -t -n cd -u 0 root@gjp:~> camcontrol -t -n cd -u 0 camcontrol: cam_real_open_device: CAMGETPASSTHRU ioctl failed cam_real_open_device: No such file or directory > camcontrol -i -n da -u 2 root@gjp:~> camcontrol -i -n da -u 2 camcontrol: cam_real_open_device: CAMGETPASSTHRU ioctl failed cam_real_open_device: No such file or directory > New support for DEVFS? No. The reason scsi devices appear at the > end of the kernel boot messages, and often out of order, is that they are > probed once interrupts are enabled. Devices are probed in ascending order > by bus, target, and lun, but they appear in the order that they respond to > the probe commands. Ah, sorry, I thought I saw something from Justin in passing on one of the lists saying he was trying to support devfs's insert/remove sequence. Maybe I mis-remembered him mentioning it in relation to this snapshot. > > What is the default number of tags per device? It logs the fact > > that they've changed, but doesn't indicate if its a change down > > or up, and what the previous value was... > > The default number of tags is 64. I'm surprised you only see > "tagged openings now 8" for your Fireball ST. I would think that you > would see more log messages than that. There are some drives for which the > default number of tags is lower, mainly the Quantum Atlas II's. Look at > the xpt_quirk_table in src/sys/cam/cam_xpt.c Since this is my home `workstation'/gateway/server I don't beat on it much :) I've noticed a message about all of the drives except the Fujitsu. Since I only use that to hold my CVS tree, I doubt I'll see a message until the next time I do a cvsup or a full tree update. Hrm. Or maybe not. I'm doing a cvsup and a find /home/ncvs across it and it seems to not be complaining. Weird. Maybe Fujitsu has 64 or more tags? Thanks Ken, Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 05:54:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13572 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 05:54:19 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from enigami.com (enigami.com [208.140.182.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13567 for ; Wed, 15 Jul 1998 05:54:17 -0700 (PDT) (envelope-from ckempf@enigami.com) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by enigami.com (8.9.0/8.9.0) with ESMTP id IAA01520 for ; Wed, 15 Jul 1998 08:53:39 -0400 (EDT) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id IAA16379; Wed, 15 Jul 1998 08:53:35 -0400 (EDT) Date: Wed, 15 Jul 1998 08:53:35 -0400 (EDT) Message-Id: <199807151253.IAA16379@singularity.enigami.com> From: Cory Kempf To: freebsd-scsi@FreeBSD.ORG Subject: Can I say NO to LUNs? Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My scanner doesn't seem to support LUNs. Is there a way that I can say not to poke at them? >From dmesg: ahc1:A:2: refuses synchronous negotiation. Using asynchronous transfers ahc1:A:5: refuses synchronous negotiation. Using asynchronous transfers (probe2:ahc1:0:5:1): INQUIRY. CDB: 12 20 0 0 24 0 (probe2:ahc1:0:5:1): ILLEGAL REQUEST asc:25,0 (probe2:ahc1:0:5:1): Logical unit not supported (probe2:ahc1:0:5:2): INQUIRY. CDB: 12 40 0 0 24 0 (probe2:ahc1:0:5:2): ILLEGAL REQUEST asc:25,0 (probe2:ahc1:0:5:2): Logical unit not supported (probe2:ahc1:0:5:3): INQUIRY. CDB: 12 60 0 0 24 0 (probe2:ahc1:0:5:3): ILLEGAL REQUEST asc:25,0 (probe2:ahc1:0:5:3): Logical unit not supported (probe2:ahc1:0:5:4): INQUIRY. CDB: 12 80 0 0 24 0 (probe2:ahc1:0:5:4): ILLEGAL REQUEST asc:25,0 (probe2:ahc1:0:5:4): Logical unit not supported (probe2:ahc1:0:5:5): INQUIRY. CDB: 12 a0 0 0 24 0 (probe2:ahc1:0:5:5): ILLEGAL REQUEST asc:25,0 (probe2:ahc1:0:5:5): Logical unit not supported (probe2:ahc1:0:5:6): INQUIRY. CDB: 12 c0 0 0 24 0 (probe2:ahc1:0:5:6): ILLEGAL REQUEST asc:25,0 (probe2:ahc1:0:5:6): Logical unit not supported (probe2:ahc1:0:5:7): INQUIRY. CDB: 12 e0 0 0 24 0 (probe2:ahc1:0:5:7): ILLEGAL REQUEST asc:25,0 (probe2:ahc1:0:5:7): Logical unit not supported pass3 at ahc1 bus 0 target 5 lun 0 pass3: Fixed Scanner SCSI2 device pass3: 3.300MB/s transfers da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 64H 32S/T 8683C) +C To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 05:59:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA14117 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 05:59:28 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from enigami.com (enigami.com [208.140.182.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA14112 for ; Wed, 15 Jul 1998 05:59:26 -0700 (PDT) (envelope-from ckempf@enigami.com) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by enigami.com (8.9.0/8.9.0) with ESMTP id IAA01524 for ; Wed, 15 Jul 1998 08:58:49 -0400 (EDT) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id IAA16441; Wed, 15 Jul 1998 08:58:45 -0400 (EDT) Date: Wed, 15 Jul 1998 08:58:45 -0400 (EDT) Message-Id: <199807151258.IAA16441@singularity.enigami.com> From: Cory Kempf To: freebsd-scsi@FreeBSD.ORG Subject: CDR doesn't like LUN 0?? Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am getting the following at boot time / dmesg: cd1: fatal error: ILLEGAL REQUEST, Logical unit not supported -- failed to attac h to device (cd1:ahc1:0:2:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd1:ahc1:0:2:0): ILLEGAL REQUEST asc:25,0 (cd1:ahc1:0:2:0): Logical unit not supported cd0 at ahc1 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 10.0MB/s transfers (10.0MHz, offset 15) cd0: cd present [306323 x 2048 byte records] Can anyone tell me what is it trying to tell me about CD1? (I have trouble believing that it cannot grok LUN 0. This may be related, but when I try to MAKEDEV cd1, no cd1 device is created. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 09:46:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA12673 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 09:46:00 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA12663 for ; Wed, 15 Jul 1998 09:45:55 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id KAA03157; Wed, 15 Jul 1998 10:40:07 -0600 (MDT) Date: Wed, 15 Jul 1998 10:40:07 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807151640.KAA03157@narnia.plutotech.com> To: Cory Kempf cc: scsi@FreeBSD.ORG Subject: Re: Can I say NO to LUNs? Newsgroups: pluto.freebsd.scsi In-Reply-To: <199807151253.IAA16379@singularity.enigami.com> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199807151253.IAA16379@singularity.enigami.com> you wrote: > My scanner doesn't seem to support LUNs. Is there a way that I can > say not to poke at them? Does poking them crash your system? Or are you simply complaining about the verbosity of the messages poking them creates? If a device hangs the system up because it doesn't properly report that it doesn't support high luns, we can add a quirk entry for that device. In the case of you scanner, it does behave in a mostly correct fashion and we can simply change the code to shut up about the failure. Here are some sample patches that should do this: -- Justin ==== //depot/cam/sys/cam/cam_xpt.c#119 - /a/perforce/src/sys/cam/cam_xpt.c ==== *** /tmp/tmp.3143.0 Wed Jul 15 10:39:12 1998 --- /a/perforce/src/sys/cam/cam_xpt.c Wed Jul 15 10:36:10 1998 *************** *** 3400,3406 **** break; } } ! } else if (cam_periph_error(done_ccb, 0, SF_RETRY_UA, &softc->saved_ccb) == ERESTART) { return; } else if ((done_ccb->ccb_h.status & CAM_SIM_QFRZN) != 0) { --- 3400,3409 ---- break; } } ! } else if (cam_periph_error(done_ccb, 0, ! done_ccb->ccb_h.target_lun > 0 ! ? SF_RETRY_UA|SF_QUIET_IR ! : SF_RETRY_UA, &softc->saved_ccb) == ERESTART) { return; } else if ((done_ccb->ccb_h.status & CAM_SIM_QFRZN) != 0) { ==== //depot/cam/sys/cam/scsi/scsi_all.c#43 - /a/perforce/src/sys/cam/scsi/scsi_all.c ==== *** /tmp/tmp.3143.1 Wed Jul 15 10:39:12 1998 --- /a/perforce/src/sys/cam/scsi/scsi_all.c Wed Jul 15 10:34:52 1998 *************** *** 2110,2117 **** error = 0; break; - case SSD_KEY_NOT_READY: case SSD_KEY_ILLEGAL_REQUEST: case SSD_KEY_DATA_PROTECT: case SSD_KEY_VOLUME_OVERFLOW: case SSD_KEY_BLANK_CHECK: /* should be filtered out by --- 2110,2121 ---- error = 0; break; case SSD_KEY_ILLEGAL_REQUEST: + if ((sense_flags & SF_QUIET_IR) != 0) + print_sense = FALSE; + + /* FALLTHROUGH */ + case SSD_KEY_NOT_READY: case SSD_KEY_DATA_PROTECT: case SSD_KEY_VOLUME_OVERFLOW: case SSD_KEY_BLANK_CHECK: /* should be filtered out by ==== //depot/cam/sys/cam/scsi/scsi_all.h#30 - /a/perforce/src/sys/cam/scsi/scsi_all.h ==== *** /tmp/tmp.3143.2 Wed Jul 15 10:39:12 1998 --- /a/perforce/src/sys/cam/scsi/scsi_all.h Wed Jul 15 10:34:46 1998 *************** *** 599,604 **** --- 599,605 ---- #define SF_RETRY_UA 0x01 #define SF_NO_PRINT 0x02 + #define SF_QUIET_IR 0x04 /* Be quiet about Illegal Request reponses */ void scsi_print_inquiry(struct scsi_inquiry_data *inq_data); To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 10:13:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15870 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 10:13:52 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15865 for ; Wed, 15 Jul 1998 10:13:50 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id LAA03281; Wed, 15 Jul 1998 11:08:19 -0600 (MDT) Date: Wed, 15 Jul 1998 11:08:19 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807151708.LAA03281@narnia.plutotech.com> To: brian@worldcontrol.com cc: scsi@FreeBSD.ORG Subject: Re: CAM 19980712 build troubles Newsgroups: pluto.freebsd.scsi In-Reply-To: <19980715011956.A9688@top.worldcontrol.com> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Even if you ignore that error, buildworld dies elsewhere: > > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/uss/src/lib/libc/include -D__DBINTERFACE_PRIVATE -DPOSIX_MISTAKE -I/uss/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -I/usr/obj/usr/src/tmp/usr/include -c /uss/src/lib/libc/../libc/gen/lockf.c -o lockf.o > /uss/src/lib/libc/../libc/gen/lockf.c: In function `lockf': > /uss/src/lib/libc/../libc/gen/lockf.c:62: `F_ULOCK' undeclared (first use this f This looks very strange. It seems you are building in /uss/src, but the build is pulling includes from /usr/obj/usr/src/tmp/usr/include which may be stale. I would expect it to be looking in /usr/obj/uss/src/tmp/usr/include. > I also tried building a kernel. This worked fine, but the > kernel panic'ed when trying to boot the root device just after > it said > /kernel: changing root device to sd0s2a. > which seemed unusual to me. Certainly does. That sounds like a normal -current kernel to me, not a CAM one. Perhaps you mixed up /uss/src with /usr/src?? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 10:14:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA16509 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 10:14:58 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA16376; Wed, 15 Jul 1998 10:14:48 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id LAA03772; Wed, 15 Jul 1998 11:14:37 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807151714.LAA03772@panzer.plutotech.com> Subject: Re: recent cam snapshot In-Reply-To: <13887.900492850@gjp.erols.com> from Gary Palmer at "Jul 15, 98 04:54:10 am" To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Wed, 15 Jul 1998 11:14:37 -0600 (MDT) Cc: scsi@FreeBSD.ORG, gibbs@pluto.plutotech.com X-Mailer: ELM [version 2.4ME+ PL28s (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 Gary Palmer wrote... > "Kenneth D. Merry" wrote in message ID > <199807150548.XAA01518@panzer.plutotech.com>: > > Try specifying the device you want, like this: > > > > camcontrol -t -n cd -u 0 > > root@gjp:~> camcontrol -t -n cd -u 0 > camcontrol: cam_real_open_device: CAMGETPASSTHRU ioctl failed > cam_real_open_device: No such file or directory > > > camcontrol -i -n da -u 2 > > root@gjp:~> camcontrol -i -n da -u 2 > camcontrol: cam_real_open_device: CAMGETPASSTHRU ioctl failed > cam_real_open_device: No such file or directory I have an idea of what your problem is. Do you have the following in your kernel config file: device pass0 And have you made the transport layer device and the passthrough devices? cd /dev sh MAKEDEV xpt1 sh MAKEDEV pass8 > > > What is the default number of tags per device? It logs the fact > > > that they've changed, but doesn't indicate if its a change down > > > or up, and what the previous value was... > > > > The default number of tags is 64. I'm surprised you only see > > "tagged openings now 8" for your Fireball ST. I would think that you > > would see more log messages than that. There are some drives for which the > > default number of tags is lower, mainly the Quantum Atlas II's. Look at > > the xpt_quirk_table in src/sys/cam/cam_xpt.c > > Since this is my home `workstation'/gateway/server I don't beat on it > much :) I've noticed a message about all of the drives except the > Fujitsu. Since I only use that to hold my CVS tree, I doubt I'll see > a message until the next time I do a cvsup or a full tree update. > > Hrm. Or maybe not. I'm doing a cvsup and a find /home/ncvs across it > and it seems to not be complaining. Weird. Maybe Fujitsu has 64 or more > tags? It could very well be that the Fujitsu has a bunch of tags. Seagates generally have 63 tags. Justin says that the reason you got the "tagged openings now 8" message for your Fireball ST is because it returned Queue Full as soon as we tried to give it 9 outstanding transactions. That fits with my experience -- those drives can only handle 8 tags. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 11:27:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA27785 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 11:27:53 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from fledge.watson.org (shafeeq@COPLAND.CODA.CS.CMU.EDU [128.2.222.48]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA27774 for ; Wed, 15 Jul 1998 11:27:52 -0700 (PDT) (envelope-from shafeeq@cyrus.watson.org) Received: from localhost (shafeeq@localhost) by fledge.watson.org (8.8.8/8.8.8) with SMTP id OAA15946; Wed, 15 Jul 1998 14:27:37 -0400 (EDT) X-Authentication-Warning: fledge.watson.org: shafeeq owned process doing -bs Date: Wed, 15 Jul 1998 14:27:37 -0400 (EDT) From: Shafeeq Sinnamohideen X-Sender: shafeeq@fledge.watson.org To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG, gibbs@pluto.plutotech.com Subject: Re: disappearing cdrom w/ Bt948+CAM In-Reply-To: <199807142006.OAA09972@panzer.plutotech.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, 14 Jul 1998, Kenneth D. Merry wrote: > If you do, let me know how it goes. I'm really not sure what your > problem is. If things don't work properly for you with the new snapshot, > my guess is that the only way to find out what's going on will be to send > us the drive. (we can hook it up to a bus analyzer and try to see what the > problem is) > I'd be happy to do that if it'll help the project, on the other hand, is it worth the fuss over a device that's fairly out of date ? If it weren't for the fact that it still works with a non-CAM kernel, I'd suspect it of having flaked out. Shafeeq To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 14:36:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20213 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 14:36:20 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from top.worldcontrol.com (surf21.cruzers.com [205.215.232.21]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA20203 for ; Wed, 15 Jul 1998 14:36:18 -0700 (PDT) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 10950 invoked by uid 100); 15 Jul 1998 21:36:51 -0000 Message-ID: <19980715143647.A10933@top.worldcontrol.com> Date: Wed, 15 Jul 1998 14:36:47 -0700 To: freebsd-scsi@FreeBSD.ORG Subject: 3.0-CAM-19980712/src all screwed up Mail-Followup-To: freebsd-scsi@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I may be misunderstanding something, but 3.0CAM-1990712-SNAP/src seems to be a mess to me. Having downloaded and unarchived everything in that directory, I find that src/include/unistd.h does not include the definitions for F_LOCK and friends. This breaks many things. Looking at the 3.0CAM-19980712-SNAP.diffs.gz one finds *** src/include/unistd.h.orig --- src/include/unistd.h *************** *** 49,58 **** #endif #ifndef _POSIX_SOURCE ! #define F_ULOCK 0 /* unlock locked section */ ! #define F_LOCK 1 /* lock a section for exclusive use */ ! #define F_TLOCK 2 /* test and lock a section for exclusive use */ ! #define F_TEST 3 /* test a section for locks by other pro cs */ #endif __BEGIN_DECLS --- 49,58 ---- #endif #ifndef _POSIX_SOURCE ! #define F_ULOCK 0 /* unlock locked section */ ! #define F_LOCK 1 /* lock a section for exclusive use */ ! #define F_TLOCK 2 /* test and lock a section for exclusive use */ ! #define F_TEST 3 /* test a section for locks by other processes * / #endif __BEGIN_DECLS However, it can't be applied because the prerequisite doesn't exist in include/unistd.h. Not that I want to apply the diffs. It seems half the diffs are already applied, and half are broken for various reasons. There are hundreds of similar problems. What is going on? -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 15:09:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA24155 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 15:09:33 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA24149 for ; Wed, 15 Jul 1998 15:09:31 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id QAA08621; Wed, 15 Jul 1998 16:04:09 -0600 (MDT) Date: Wed, 15 Jul 1998 16:04:09 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807152204.QAA08621@narnia.plutotech.com> To: Shafeeq Sinnamohideen cc: scsi@FreeBSD.ORG Subject: Re: disappearing cdrom w/ Bt948+CAM Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > On Tue, 14 Jul 1998, Kenneth D. Merry wrote: >> If you do, let me know how it goes. I'm really not sure what your >> problem is. If things don't work properly for you with the new snapshot, >> my guess is that the only way to find out what's going on will be to send >> us the drive. (we can hook it up to a bus analyzer and try to see what the >> problem is) >> > I'd be happy to do that if it'll help the project, on the other hand, > is it worth the fuss over a device that's fairly out of date ? If it > weren't for the fact that it still works with a non-CAM kernel, I'd > suspect it of having flaked out. > > Shafeeq What is most puzzling about this problem is that the BusLogic driver has no control over the command once it is sent to the card. The firmware on the card executes it for us, and seems to be providing a perfectly reasonable error code. The only thing I can think of is that we might be somehow, indavertantly, setting the selection timeout lower on the card, but I somehow doubt this. Sending us the device may help, but, since I'm now without any PCI BusLogic cards, I'd probably need the card too. Have you investigated updating the firmware on your card? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 15:17:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25072 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 15:17:47 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25067 for ; Wed, 15 Jul 1998 15:17:45 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id QAA04822; Wed, 15 Jul 1998 16:17:27 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199807152217.QAA04822@panzer.plutotech.com> Subject: Re: 3.0-CAM-19980712/src all screwed up In-Reply-To: <19980715143647.A10933@top.worldcontrol.com> from "brian@worldcontrol.com" at "Jul 15, 98 02:36:47 pm" To: brian@worldcontrol.com Date: Wed, 15 Jul 1998 16:17:26 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG, gibbs@pluto.plutotech.com X-Mailer: ELM [version 2.4ME+ PL28s (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 brian@worldcontrol.com wrote... > I may be misunderstanding something, but 3.0CAM-1990712-SNAP/src seems > to be a mess to me. > > Having downloaded and unarchived everything in that directory, I > find that src/include/unistd.h does not include the definitions for > F_LOCK and friends. That is wrong. I just downloaded it, and does have the correct definitions for F_LOCK, etc.: #ifndef _POSIX_SOURCE #define F_ULOCK 0 /* unlock locked section */ #define F_LOCK 1 /* lock a section for exclusive use */ #define F_TLOCK 2 /* test and lock a section for exclusive use */ #define F_TEST 3 /* test a section for locks by other processes */ #endif > This breaks many things. > > Looking at the 3.0CAM-19980712-SNAP.diffs.gz one finds > > *** src/include/unistd.h.orig > --- src/include/unistd.h > *************** > *** 49,58 **** > #endif > > #ifndef _POSIX_SOURCE > ! #define F_ULOCK 0 /* unlock locked section */ > ! #define F_LOCK 1 /* lock a section for exclusive use */ > ! #define F_TLOCK 2 /* test and lock a section for exclusive > use */ > ! #define F_TEST 3 /* test a section for locks by other pro > cs */ > #endif > > __BEGIN_DECLS > --- 49,58 ---- > #endif > > #ifndef _POSIX_SOURCE > ! #define F_ULOCK 0 /* unlock locked section */ > ! #define F_LOCK 1 /* lock a section for exclusive use */ > ! #define F_TLOCK 2 /* test and lock a section for exclusive use */ > ! #define F_TEST 3 /* test a section for locks by other processes * > / > #endif > > __BEGIN_DECLS > > > However, it can't be applied because the prerequisite doesn't exist > in include/unistd.h. Not that I want to apply the diffs. It seems > half the diffs are already applied, and half are broken for various > reasons. > > There are hundreds of similar problems. > > What is going on? I think you've really got something screwed up. I don't see anything like that in the diffs I just pulled off ftp.kdm.org: {roadwarrior:/usr/home/ken/src/camtest:3:0} grep POSIX_SOURCE 3.0* {roadwarrior:/usr/home/ken/src/camtest:4:1} grep F_ULOCK 3.0* {roadwarrior:/usr/home/ken/src/camtest:5:1} I think what you're trying to do is one of two things, both of which are plain wrong: - you're either trying to apply the diffs to the source tree you got from the CAM snapshot release - or you're trying to apply the diffs to a -current source tree that is NOT from around ~0200 PDT on July 11th. The diffs above look to be something along the lines of the differences between revision 1.21 and 1.22 of unistd.h. On July 11th, Bruce made some white space changes to the file. If you had the earlier version of the diffs, from Monday night, you should re-get them. Justin fixed a problem in the diffs, and re-uploaded them Tuesday. In any case, you shouldn't be trying to apply any diffs to the source tree in the release, it's already a CAM source tree. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 17:29:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA13023 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 17:29:26 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from top.worldcontrol.com (surf21.cruzers.com [205.215.232.21]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA13017 for ; Wed, 15 Jul 1998 17:29:24 -0700 (PDT) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 11148 invoked by uid 100); 16 Jul 1998 00:29:27 -0000 Message-ID: <19980715172923.A11119@top.worldcontrol.com> Date: Wed, 15 Jul 1998 17:29:23 -0700 To: "Kenneth D. Merry" , brian@worldcontrol.com Cc: freebsd-scsi@FreeBSD.ORG, gibbs@pluto.plutotech.com Subject: Re: 3.0-CAM-19980712/src all screwed up Mail-Followup-To: "Kenneth D. Merry" , brian@worldcontrol.com, freebsd-scsi@FreeBSD.ORG, gibbs@pluto.plutotech.com References: <19980715143647.A10933@top.worldcontrol.com> <199807152217.QAA04822@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: <199807152217.QAA04822@panzer.plutotech.com>; from Kenneth D. Merry on Wed, Jul 15, 1998 at 04:17:26PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > brian@worldcontrol.com wrote... > > I may be misunderstanding something, but 3.0CAM-1990712-SNAP/src seems > > to be a mess to me. > > > > Having downloaded and unarchived everything in that directory, I > > find that src/include/unistd.h does not include the definitions for > > F_LOCK and friends. On %M 0, "Kenneth D. Merry" wrote: > That is wrong. I just downloaded it, and does have the correct > definitions for F_LOCK, etc.: Looking at some of the file lengths on the ftp site and on my site there are some differences: -rw-r--r-- 1 2035 207 181741 May 21 18:03 susbin.ao -rw-r--r-- 1 brian wheel 239820 Jul 14 10:11 susbin.ao How they got there I do not know. Looking further some of the files are the correct CAM ones and others are apparently from someplace else. I've /bin/rm'ed the entire hierarchy and started downloading again. Thanks for the help, -- Brian@Litzinger.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 19:18:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA26417 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 19:18:12 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from freebie.lemis.com (freebie.lemis.com [139.130.136.133]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA26398 for ; Wed, 15 Jul 1998 19:18:03 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA23268; Thu, 16 Jul 1998 11:47:43 +0930 (CST) Message-ID: <19980716114743.Z15083@freebie.lemis.com> Date: Thu, 16 Jul 1998 11:47:43 +0930 From: Greg Lehey To: freebsd-scsi@FreeBSD.ORG Subject: Re: 3.0-CAM-19980712/src all screwed up References: <19980715143647.A10933@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <19980715143647.A10933@top.worldcontrol.com>; from brian@worldcontrol.com on Wed, Jul 15, 1998 at 02:36:47PM -0700 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wednesday, 15 July 1998 at 14:36:47 -0700, brian@worldcontrol.com wrote: > I may be misunderstanding something, but 3.0CAM-1990712-SNAP/src seems > to be a mess to me. > > Having downloaded and unarchived everything in that directory, I > find that src/include/unistd.h does not include the definitions for > F_LOCK and friends. F_LOCK and friends are recent introductions to -current. I'd guess that your version of -current is too old. It worked fine with my version supped on Monday. Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 22:14:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA14854 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 22:14:15 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gjp.erols.com (root@alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA14849 for ; Wed, 15 Jul 1998 22:14:13 -0700 (PDT) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.8.8/8.8.7) with ESMTP id BAA01335; Thu, 16 Jul 1998 01:14:01 -0400 (EDT) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: "Kenneth D. Merry" cc: scsi@FreeBSD.ORG, gibbs@pluto.plutotech.com From: "Gary Palmer" Subject: Re: recent cam snapshot In-reply-to: Your message of "Wed, 15 Jul 1998 11:14:37 MDT." <199807151714.LAA03772@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 16 Jul 1998 01:14:01 -0400 Message-ID: <1331.900566041@gjp.erols.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" wrote in message ID <199807151714.LAA03772@panzer.plutotech.com>: > I have an idea of what your problem is. Do you have the following > in your kernel config file: > > device pass0 D'OH!!!! Somehoe when looking for new CAM options I missed putting that one in (even though I spotted it in the readme) *blush* sorry :) > It could very well be that the Fujitsu has a bunch of tags. > Seagates generally have 63 tags. Justin says that the reason you got the > "tagged openings now 8" message for your Fireball ST is because it returned > Queue Full as soon as we tried to give it 9 outstanding transactions. That > fits with my experience -- those drives can only handle 8 tags. Yeah, the Quantum goes down to 8, the Seagates to 63 and the Fujitsu never gets a message no matter how hard I try. Thanks for your help Ken, Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jul 15 23:51:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA25678 for freebsd-scsi-outgoing; Wed, 15 Jul 1998 23:51:08 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from top.worldcontrol.com (surf52.cruzers.com [205.215.232.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA25658 for ; Wed, 15 Jul 1998 23:50:49 -0700 (PDT) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 11592 invoked by uid 100); 16 Jul 1998 06:51:15 -0000 Message-ID: <19980715235110.A11579@top.worldcontrol.com> Date: Wed, 15 Jul 1998 23:51:10 -0700 To: freebsd-scsi@FreeBSD.ORG Subject: Re: 3.0-CAM-19980712/src all screwed up [resolved] Mail-Followup-To: freebsd-scsi@freebsd.org References: <19980715143647.A10933@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: <19980715143647.A10933@top.worldcontrol.com>; from Brian Litzinger on Wed, Jul 15, 1998 at 02:36:47PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I wrote: > I may be misunderstanding something, but 3.0CAM-1990712-SNAP/src seems > to be a mess to me. Well the code I had fetched was a strange mix of FreeBSD versions. I haven't the slightest idea how it came to be. I had ftp'ed the data via an ncftpget of the whole directory. I erased everything, redownloaded everything, and all is proceeding much as I would normally expect. Thanks to those that offered advice, -- Brian@Litzinger.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 16 04:29:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26666 for freebsd-scsi-outgoing; Thu, 16 Jul 1998 04:29:38 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA26633; Thu, 16 Jul 1998 04:29:25 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id HAA17762; Thu, 16 Jul 1998 07:29:11 -0400 (EDT) Date: Thu, 16 Jul 1998 07:29:11 -0400 (EDT) From: The Hermit Hacker To: scsi@FreeBSD.ORG cc: current@FreeBSD.ORG Subject: hub security check output (fwd) 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 Morning... I woke up this morning to see this in my mailbox, and am wondering if anyone can comment on it. The two drives referred to below are: hub# dmesg | egrep "da1|da2" da1 at ahc1 bus 0 target 0 lun 0 da1: Fixed Direct Access SCSI2 device da1: Serial Number PCB=20-113000-02; HDA=184701310988 da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) da2 at ahc1 bus 0 target 1 lun 0 da2: Fixed Direct Access SCSI2 device da2: Serial Number PCB=20-113000-02; HDA=184709110359 da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) Now, these drives are less then 2 months old, da2 being less then a couple of weeks old (we've already replaced it once). Both drives are running off the same SCSI controller: ahc1: rev 0x01 int a irq 11 on pci0.12.0 ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs My kernel is a Jun10th-CURRENT with the May20th CAM drivers installed. The question(s) are: 1. could this be caused by a bug in CURRENT or those CAM drivers? 2. could this be caused by a bad SCSI controller? 3. or am I just having real bad luck with SCSI drives? Thanks... ---------- Forwarded message ---------- Date: Thu, 16 Jul 1998 02:00:04 -0400 (EDT) From: Superuser To: undisclosed-recipients: ; Subject: hub security check output checking setuid files and devices: checking for uids of 0: root 0 hub kernel log messages: > (da1:ahc1:0:0:0): SCB 0x32 - timed out in dataout phase, SCSISIGI == 0xe6 > SEQADDR == 0x115 > SSTAT1 == 0x13 > (da1:ahc1:0:0:0): BDR message in message buffer > (da1:ahc1:0:0:0): SCB 0x32 - timed out in dataout phase, SCSISIGI == 0xf6 > SEQADDR == 0x115 > SSTAT1 == 0x13 > (da1:ahc1:0:0:0): no longer in timeout, status = 34b > ahc1: Issued Channel A Bus Reset. 4 SCBs aborted > (da1:ahc1:0:0:0): SCB 0x32 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR == 0x18b > SSTAT1 == 0x0 > (da1:ahc1:0:0:0): Queuing a BDR SCB > (da1:ahc1:0:0:0): SCB 0x32 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > SEQADDR == 0x18b > SSTAT1 == 0x0 > (da1:ahc1:0:0:0): no longer in timeout, status = 34b > ahc1: Issued Channel A Bus Reset. 2 SCBs aborted > (da2:ahc1:0:1:0): READ(10). CDB: 28 0 0 40 13 38 0 0 8 0 > (da2:ahc1:0:1:0): UNIT ATTENTION asc:29,2 > (da2:ahc1:0:1:0): Scsi bus reset occurred > (da1:ahc1:0:0:0): WRITE(06). CDB: a e be 60 10 0 > (da1:ahc1:0:0:0): UNIT ATTENTION asc:29,2 > (da1:ahc1:0:0:0): Scsi bus reset occurred > spec_getpages: I/O read failure: (error code=5) > size: 4096, resid: 4096, a_count: 4096, valid: 0x0 > nread: 0, reqpage: 0, pindex: 464671, pcount: 1 > vm_fault: pager input (probably hardware) error, PID 26899 failure To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 16 08:00:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21825 for freebsd-scsi-outgoing; Thu, 16 Jul 1998 08:00:05 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA21820 for ; Thu, 16 Jul 1998 08:00:03 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id IAA21005; Thu, 16 Jul 1998 08:52:57 -0600 (MDT) Date: Thu, 16 Jul 1998 08:52:57 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807161452.IAA21005@narnia.plutotech.com> To: The Hermit Hacker cc: scsi@FreeBSD.ORG Subject: Re: hub security check output (fwd) Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Both drives are running off the same SCSI controller: > > ahc1: rev 0x01 int a irq 11 on pci0.12.0 > ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > You need the latest CAM snapshot which includes a work around for a bug in the Rev B aic7880 silicon. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 16 11:09:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19458 for freebsd-scsi-outgoing; Thu, 16 Jul 1998 11:09:56 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19451 for ; Thu, 16 Jul 1998 11:09:54 -0700 (PDT) (envelope-from mreimer@vpop.net) Received: from vpop.net (bilbo.vpop.net [206.117.152.4]) by boromir.vpop.net (8.8.5/8.8.5) with ESMTP id LAA28155 for ; Thu, 16 Jul 1998 11:09:36 -0700 (PDT) Message-ID: <35AE41F1.18E0FC12@vpop.net> Date: Thu, 16 Jul 1998 18:09:53 +0000 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 2.2.6-STABLE i386) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD-scsi@FreeBSD.ORG Subject: Problem building with ch and CAM 19980712 snapshot Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to build 2.2-STABLE (cvsup'ed yesterday) with support for the media changer ch0, but the build is failing like this: --------- cc -c -O -Wreturn-type -Wcomment -Wredundant-decls -Wimplicit -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -nostdinc -I- -I. -I../.. -I../../../include -DCOMPAT_43 -DNFS -DFFS -DINET -DKERNEL ../../cam/scsi/scsi_ch.c ../../cam/scsi/scsi_ch.c:688: conflicting types for `chioctl' ../../cam/scsi/scsi_ch.c:176: previous declaration of `chioctl' *** Error code 1 Stop. --------- It looks like the definition of d_ioctl_t in sys/conf.h is different in 3.0 versus 2.2: sys/conf.h in 2.2: typedef int d_ioctl_t __P((dev_t dev, int cmd, caddr_t data, int fflag, struct proc *p)); sys/conf.h in 3.0 typedef int d_ioctl_t __P((dev_t dev, u_long cmd, caddr_t data, int fflag, struct proc *p)); referenced from scsi_ch.c: static int chioctl(dev_t dev, u_long cmd, caddr_t addr, int flag, struct proc *p) { It compiles fine if I change the definition for chioctl above to int from u_long, but is this safe? Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 16 12:41:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA01747 for freebsd-scsi-outgoing; Thu, 16 Jul 1998 12:41:18 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA01737 for ; Thu, 16 Jul 1998 12:41:16 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id NAA07357; Thu, 16 Jul 1998 13:35:41 -0600 (MDT) Date: Thu, 16 Jul 1998 13:35:41 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199807161935.NAA07357@narnia.plutotech.com> To: Matthew Reimer cc: scsi@FreeBSD.ORG Subject: Re: Problem building with ch and CAM 19980712 snapshot Newsgroups: pluto.freebsd.scsi In-Reply-To: <35AE41F1.18E0FC12@vpop.net> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <35AE41F1.18E0FC12@vpop.net> you wrote: > > It looks like the definition of d_ioctl_t in sys/conf.h is different in > 3.0 versus 2.2: Yes. I just screwed up the merge when I brought scsi_ch.c in from our current CAM branch into the stable one. The change you propose is the correct one and should be safe. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 16 15:05:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27158 for freebsd-scsi-outgoing; Thu, 16 Jul 1998 15:05:33 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from top.worldcontrol.com (surf52.cruzers.com [205.215.232.52]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA27152 for ; Thu, 16 Jul 1998 15:05:31 -0700 (PDT) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 12626 invoked by uid 100); 16 Jul 1998 22:06:00 -0000 Message-ID: <19980716150556.A12444@top.worldcontrol.com> Date: Thu, 16 Jul 1998 15:05:56 -0700 To: freebsd-scsi@FreeBSD.ORG Subject: Re: AIC 7880, CAM, CD-burning success Mail-Followup-To: freebsd-scsi@freebsd.org References: <19980706014617.A544@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: <19980706014617.A544@top.worldcontrol.com>; from Brian Litzinger on Mon, Jul 06, 1998 at 01:46:17AM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On %M 0, Brian Litzinger wrote: > I had previously posted of troubles using cdrecord 1.6 with an > aic7880 (Adaptec 2940UW) controller. It basically failed in > the middle of burning 100% of the time, but the same > setup succeeded 100% of the time with an aic7870 (2940W) controller. > This occured on both a non-CAM and a 19980520 CAM system. Using the 19980712 CAM snapshot I have successfully burned a CD on the aic7880 based controller, using the CAM port of cdrecord. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 16 16:49:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17867 for freebsd-scsi-outgoing; Thu, 16 Jul 1998 16:49:23 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from rm-rstar.sfu.ca (root@rm-rstar.sfu.ca [142.58.120.21]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17859 for ; Thu, 16 Jul 1998 16:49:21 -0700 (PDT) (envelope-from wolstena@sfu.ca) Received: from beaufort.sfu.ca (wolstena@beaufort.sfu.ca [192.168.0.110]) by rm-rstar.sfu.ca (8.8.7/8.8.7/SFU-4.0H) with SMTP id QAA25631 for ; Thu, 16 Jul 1998 16:49:11 -0700 (PDT) From: Paul Wolstenholme Received: by beaufort.sfu.ca (951211.SGI.8.6.12.PATCH1502/SFU-2.7C) id QAA23729 for freebsd-scsi@freebsd.org (from wolstena@sfu.ca); Thu, 16 Jul 1998 16:49:10 -0700 Date: Thu, 16 Jul 1998 16:49:10 -0700 Message-Id: <199807162349.QAA23729@beaufort.sfu.ca> Apparently-To: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, I have just purchaed a new PC runn FreeBSD 2.2.6. The computer is using: ASUS P2L97-S with onboard AIC 7880 128 MB RAM WD 4.3 GB UWide SCSI HD HP C1533A 9406 Dat drive (DDS 1) external The first time I installed the OS everything ran fine for a couple of days and then ... it died. A bunck of SCSI message looped across the console and then it would not boot and I could not reinstall the OS. I got a panic: not going anywhere without my init. I was able to get things up again by removing the tape drive from the SCSI chain. I was able to put the tape drive back on the chain after I replaced the terminator? Now that the computer is up again, I was hoping thatsomeone might be apble to confirm that I have done things correctly or not. Especially in reqard to the DAT unit which is not ultra wide. The tape drive is connected to the external port using a 68 pin cable with a 68-> 50 ping gender changer which is used to connect to the drive. Is this a bad thing to do? I have modified the SCSI card config for the tape drive (device #5) so that it does not initiate sync negotiatiion and I have reduced the sync transfer rate down to 10MB/s. The rest is factory including the Iniate Wide negotiation which I wasn't sure whether I should disable or not. This is an old device so I thought it might be better to tune things down a bit. Have I done the right things here or am I pissing in the to the wind. The SCSI card config is terminated with LOW ON and HIGH ON. The EXtended Bio Translation is disabled. On the first go it was enabled but I read in one of the archives that if you were having problems try disabling it so I did. The rest is factory. Both the HD and external port are connect via the 68 pin cable. The 50 pin is not used. The hard drive and external tape drive are both terminated. Is this correct? Or should only one be terminated. The cabling seems a bit bizaar to me. The HD and External ports are at opposite ends of the cable. I have only set up 50pin devices before where the SCSI card is at one end and you terminate the card and last device. If anyone can see any obvious mistakes or has any suggestions on how to I might make it more stable I would be greatly apreciative. As it stands, I would rather forget this week. /Paul To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 17 09:31:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA08913 for freebsd-scsi-outgoing; Fri, 17 Jul 1998 09:31:51 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA08872 for ; Fri, 17 Jul 1998 09:31:47 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id KAA07646 for ; Fri, 17 Jul 1998 10:31:32 -0600 (MDT) Message-Id: <199807171631.KAA07646@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: scsi@FreeBSD.ORG Subject: 19980716 CAM Snapshot now available. Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 17 Jul 1998 10:26:19 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This snapshot is available in full release format for 2.2-stable as well as diffs for both 2.2-stable and 3.0-current. Complete information about CAM can be found at: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam/README or ftp://ftp.kdm.org/pub/FreeBSD/cam/README Full CAM releases are available at: ftp://ftp.FreeBSD.org/pub/FreeBSD/cam Changes for the 19980716 Snapshot: - Corrected chioctl definition in the SCSI Changer driver for -stable. - Corrected support for using "left over BIOS settings" for aic7890 chips embedded on motherboards. This should allow these systems to operate at full LVD Ultra2 speeds. - Fixed a few more bugs in the AdvanSys driver's error recovery code. - Quieted error messages from devices that return INVALID REQUEST for inquiry commands to luns above zero. -- Justin T. Gibbs Kenneth D. Merry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 17 10:15:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA15639 for freebsd-scsi-outgoing; Fri, 17 Jul 1998 10:15:19 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from rigel.cs.pdx.edu (root@rigel.cs.pdx.edu [131.252.220.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA15630 for ; Fri, 17 Jul 1998 10:15:16 -0700 (PDT) (envelope-from rotan@cs.pdx.edu) Received: from sirius.cs.pdx.edu (root@sirius.cs.pdx.edu [131.252.220.13]) by rigel.cs.pdx.edu (8.8.6/8.8.6) with ESMTP id KAA23193; Fri, 17 Jul 1998 10:15:01 -0700 (PDT) Received: from localhost (rotan@localhost [127.0.0.1]) by sirius.cs.pdx.edu (8.8.6/8.8.6) with ESMTP id KAA08787; Fri, 17 Jul 1998 10:15:00 -0700 (PDT) Message-Id: <199807171715.KAA08787@sirius.cs.pdx.edu> To: scsi@FreeBSD.ORG cc: rotan@cs.pdx.edu Subject: AHA-2940UW Date: Fri, 17 Jul 1998 10:14:59 -0700 From: robert t tan Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a Micron Millenium system that *ran fine* with RELEASE 2.2.2, and win95. At that time I had a Buslogic SCSI controller that ran my hard drive (8 bit) and cdrom drive (8 bit). I replaced my old ( crashed ) hard drive with a new 2G, Western Digital ( SCSI Wide ), and the Buslogic card, with an Adaptec (AHA-2940UW), BIOS v1.32 (http://www.adaptec.com/products/overview/aha2940uw.html) The result is that I can't boot FreeBSD. I terminated all right, Win95 has no problems getting up, and has a partition of 250M. I Disabled the following options in the BIOS. . > 1 GB . Plug And Play Operating System ( both in mainboard and adapter ) I have tried the following: 1: Taking out the adapter and booting untill 'No Operating System' then putting the adapter back in ( same, or other slot), and try again. 2: Taking out all other cards, exept AHA-2940, and Video card. 3: Put a video card, in a ISA slot, xor PCI slot 4: Disconnecting CDROM drive, so only hard drive is connected to controller. 5: Disabling sync, and disconnect in SCSISelect, for cdrom and drive. I am getting the following system messages when my system is trying to boot, RELEASE2.2.6/updates/boot.flp. ( about 7/8/98 ). DPT: RAID Manager driver, version 1.0.1 Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0:0 chip1 rev 2 on pci0:0:0 ahc0: rev 1 in 1 irq 11 on pci0:17:0 ahc0: aic7880 Wide Channel, SCSI Id=7, 116 SCBs ahc0: waiting for SCSI devices to settle ahc0: board is not responding cmd fail (ahc0:0:0): SCB 0x1 timed out with recovery in progress (ahc0:0:0): "unknown unknown ????" type 13 fixed SCSI 0 uk1 (ahc0:0:1): Unknown ahc0: board is not repsonding .. I noticed people are having problems with this card, in maybe similar ways. But I haven't found a specific response yet that seems to solve it. Also don't know what else to try Did get a note somewhere in the FreeBSD, newsgroup search. that maybe downgrading the controller BIOS from v1.32 to v1.25. I don't know how to do this or if this is actully a good idea. So what is the fix to this ? Tnx, robert t tan. ( rotan@cs.pdx.edu ) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Jul 17 19:54:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA08410 for freebsd-scsi-outgoing; Fri, 17 Jul 1998 19:54:08 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from a486n1.znh.org (dialup4.gaffaneys.com [208.155.161.54]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA08347 for ; Fri, 17 Jul 1998 19:54:02 -0700 (PDT) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by a486n1.znh.org (8.8.8/8.8.8) id LAA06892; Fri, 17 Jul 1998 11:41:02 -0500 (CDT) (envelope-from zach) Message-ID: <19980717114102.A6647@znh.org.> Date: Fri, 17 Jul 1998 11:41:02 -0500 From: Zach Heilig To: Donald Burr , FreeBSD SCSI Subject: Re: what the heck is going on with my scanner? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Donald Burr on Sat, Jul 11, 1998 at 12:08:08AM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Jul 11, 1998 at 12:08:08AM -0700, Donald Burr wrote: > ahc0:A:5: refuses synchronous negotiation. Using asynchronous transfers > (ahc0:5:0): "UMAX Astra 1200S V2.9" type 6 fixed SCSI 2 > uk0(ahc0:5:0): Unknown > (ahc0:5:1): "UMAX Astra 1200S V2.9" type 6 fixed SCSI 2 > uk1(ahc0:5:1): Unknown I have seen these symptoms caused by improper termination, or the SCSI device on the same ID as the host adapter. -- Zach Heilig -- zach@gaffaneys.com Real Programs don't use shared text. Otherwise, how can they use functions for scratch space after they are finished calling them? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 18 00:39:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA29442 for freebsd-scsi-outgoing; Sat, 18 Jul 1998 00:39:19 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from top.worldcontrol.com (surf56.cruzers.com [205.215.232.56]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA29437 for ; Sat, 18 Jul 1998 00:39:16 -0700 (PDT) (envelope-from brian@worldcontrol.com) From: brian@worldcontrol.com Received: (qmail 14067 invoked by uid 100); 18 Jul 1998 07:39:42 -0000 Message-ID: <19980718003939.A14055@top.worldcontrol.com> Date: Sat, 18 Jul 1998 00:39:39 -0700 To: freebsd-scsi@FreeBSD.ORG Subject: Re: AIC 7880, CAM, CD-burning 21 out of 22 successful Mail-Followup-To: freebsd-scsi@freebsd.org References: <19980706014617.A544@top.worldcontrol.com> <19980716150556.A12444@top.worldcontrol.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91i In-Reply-To: <19980716150556.A12444@top.worldcontrol.com>; from Brian Litzinger on Thu, Jul 16, 1998 at 03:05:56PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On %M 0, Brian Litzinger wrote: > Using the 19980712 CAM snapshot I have successfully burned a CD > on the aic7880 based controller, using the CAM port of cdrecord. I ran 22 dummy burns on my CD-RW. burn #4 was the only failure out of 22 burns. Burn 4 failed due the system doing the daily security scan. I've found even with the cdrecord processes running rtprio 16 it stills ends up getting starved out of disk access. -- Brian Litzinger To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message