From owner-freebsd-scsi Sun Dec 6 02:11:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA07461 for freebsd-scsi-outgoing; Sun, 6 Dec 1998 02:11:57 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from k6n1.znh.org (dialup2.gaffaneys.com [208.155.161.52]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA07440 for ; Sun, 6 Dec 1998 02:11:33 -0800 (PST) (envelope-from zach@gaffaneys.com) Received: (from zach@localhost) by k6n1.znh.org (8.9.1/8.9.1) id KAA89504; Sun, 6 Dec 1998 10:08:37 GMT (envelope-from zach) Message-ID: <19981206040837.A89496@znh.org> Date: Sun, 6 Dec 1998 04:08:37 -0600 From: Zach Heilig To: mjacob@feral.com, Matthew Patton Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CAM vs traditional devices References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: ; from Matthew Jacob on Sat, Dec 05, 1998 at 04:15:22PM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Dec 05, 1998 at 04:15:22PM -0800, Matthew Jacob wrote: > This isn't a SCSI issue. This is a slice issue. And I sure wish I could > figure it out sometimes. You probably need to ask freebsd-current about > this. No No, don't ask over there. It is a slice question, but it should have gone to -questions. What you need to do is: sh MAKEDEV da0s1a ^ could be any letter a-g, I think... to make all the partitions for SCSI disk 0 Slice 1. -- Zach Heilig (zach@gaffaneys.com) Our one strength was that our senior officers were more flexible than theirs... How's that? We can customize our colonels. [ Illiad in User Friendly, Dec. 1, 1998 ] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Dec 6 06:51:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA03683 for freebsd-scsi-outgoing; Sun, 6 Dec 1998 06:51:51 -0800 (PST) (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 GAA03678 for ; Sun, 6 Dec 1998 06:51:49 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id PAA12887; Sun, 6 Dec 1998 15:51:41 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id PAA14237; Sun, 6 Dec 1998 15:42:53 +0100 (MET) (envelope-from j) Message-ID: <19981206154252.46310@uriah.heep.sax.de> Date: Sun, 6 Dec 1998 15:42:52 +0100 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Cc: Matthew Patton Subject: Re: CAM vs traditional devices 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 Jacob on Sat, Dec 05, 1998 at 04:15:22PM -0800 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 Jacob wrote: > This isn't a SCSI issue. This is a slice issue. And I sure wish I could > figure it out sometimes. You probably need to ask freebsd-current about > this. > > The kernel still thinks the root device is "sd0s1a". Why is that? Also how > > come none of the "da" devices have trailing partition letters? eg. there is > > "da0s1" and "da0a" but no "da0s1a". I am simply too far behind? The > > /dev/MAKEDEV script doesn't build them. Well, /dev/MAKEDEV is supposed to build the partition device names for slices iff (and only if) you call it like `MAKEDEV da0s1a' (building da0s1 alone doesn't suffice). Also, the name of the boot device is passed up from the bootstrap, so you need to reinstall the bootstrap (disklabel -B da0s1) in order to get it to new names. (IMHO) -- 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 Sun Dec 6 07:44:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA07804 for freebsd-scsi-outgoing; Sun, 6 Dec 1998 07:44:25 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from godzilla.zeta.org.au ([203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA07799 for ; Sun, 6 Dec 1998 07:44:22 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id CAA19883; Mon, 7 Dec 1998 02:44:09 +1100 Date: Mon, 7 Dec 1998 02:44:09 +1100 From: Bruce Evans Message-Id: <199812061544.CAA19883@godzilla.zeta.org.au> To: freebsd-scsi@FreeBSD.ORG, j@uriah.heep.sax.de Subject: Re: CAM vs traditional devices Cc: patton@sysnet.net Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> This isn't a SCSI issue. This is a slice issue. And I sure wish I could >> figure it out sometimes. You probably need to ask freebsd-current about >> this. This is mainly a great renaming issue. >> > The kernel still thinks the root device is "sd0s1a". Why is that? Also how This is backwards. The root device is the only device for which the old "sd" name no longer works. The kernel looks up the device by number in bdevsw[] and only finds the new name "da" (driver name = device name prefix). >... >Also, the name of the boot device is passed up from the bootstrap, so >you need to reinstall the bootstrap (disklabel -B da0s1) in order to >get it to new names. (IMHO) Not true. The _number_ of the boot device is passed up from the bootstrap. The name in the bootstrap only affects what you have to type there to override the default. Sample mixed up configuration (for a dangerously dedicated disk): Name Where Why ---- ----- --- 1:sd(0,a)kernel /boot.config old bootstrap doesn't have "da" da0a root mount struct kernel doesn't have "sd" in bdevsw[] da0a /etc/disktab must match name in root mount struct sd0e /etc/disktab old disktab, only needed to change rootdev Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 7 17:27:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA16455 for freebsd-scsi-outgoing; Mon, 7 Dec 1998 17:27:51 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (ppp6.portal.net.au [202.12.71.106]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA16449 for ; Mon, 7 Dec 1998 17:27:48 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id QAA00732; Sun, 6 Dec 1998 16:05:49 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199812070005.QAA00732@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Joerg Wunsch cc: freebsd-scsi@FreeBSD.ORG, Matthew Patton Subject: Re: CAM vs traditional devices In-reply-to: Your message of "Sun, 06 Dec 1998 15:42:52 +0100." <19981206154252.46310@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 06 Dec 1998 16:05:49 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Also, the name of the boot device is passed up from the bootstrap, so > you need to reinstall the bootstrap (disklabel -B da0s1) in order to > get it to new names. (IMHO) The name isn't passed up (yet). The original poster may simply be working with an outdated /etc/fstab. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 8 08:25:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14329 for freebsd-scsi-outgoing; Tue, 8 Dec 1998 08:25:52 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ninbox.ml.org (hsv1-116.airnet.net [207.242.81.116]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14321 for ; Tue, 8 Dec 1998 08:25:49 -0800 (PST) (envelope-from kris@airnet.net) Received: from airnet.net (localhost [127.0.0.1]) by ninbox.ml.org (8.9.1/8.8.5) with ESMTP id KAA00845 for ; Tue, 8 Dec 1998 10:25:36 -0600 (CST) Message-ID: <366D5300.CBCAB303@airnet.net> Date: Tue, 08 Dec 1998 10:25:36 -0600 From: Kris Kirby Organization: Absolutely None! X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: FreeBSD-SCSI@FreeBSD.ORG Subject: Tandberg TDC 3600 on CAM, 3.0-R Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org sa0 at adv0 bus 0 target 2 lun 0 sa0: Removable Sequential Access SCSI1 device sa0: 3.300MB/s transfers I'm using an Advansys SCSI controller (i542). This drive doesn't appear to like FreeBSD, as it just kinda sits there hung. I'd be happy to do anything to get this drive working. I'm no programmer, but I have the resources to go -current. If interested, I'll happily supply all the info I can. I don't have the drive info though. -- Kris Kirby UAH Mail UAH CS Home WWW ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 8 11:51:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02605 for freebsd-scsi-outgoing; Tue, 8 Dec 1998 11:51:02 -0800 (PST) (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 LAA02599 for ; Tue, 8 Dec 1998 11:51:00 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id UAA21815; Tue, 8 Dec 1998 20:50:37 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id UAA23355; Tue, 8 Dec 1998 20:40:37 +0100 (MET) (envelope-from j) Message-ID: <19981208204035.28318@uriah.heep.sax.de> Date: Tue, 8 Dec 1998 20:40:35 +0100 From: J Wunsch To: Kris Kirby Cc: FreeBSD-SCSI@FreeBSD.ORG Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R Reply-To: Joerg Wunsch References: <366D5300.CBCAB303@airnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <366D5300.CBCAB303@airnet.net>; from Kris Kirby on Tue, Dec 08, 1998 at 10:25:36AM -0600 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 Kris Kirby wrote: > sa0 at adv0 bus 0 target 2 lun 0 > sa0: Removable Sequential Access SCSI1 device > sa0: 3.300MB/s transfers > > I'm using an Advansys SCSI controller (i542). This drive doesn't appear > to like FreeBSD, as it just kinda sits there hung. I'd be happy to do > anything to get this drive working. This belongs into the typical group of SCSI1 tape drive problems. I've fixed this shortly after 3.0R while getting a colleague's machine up to -current. The drive is working flawlessly again. NB: I'm not sure blocking the entire `A07:' class of revisions is either necessary or sufficient (i. e. it's also possible some `A08:' firmware might experience the same symptoms, or newer `A07:' versions wouldn't require it -- Tandberg uses 6-char version strings), but it helped in my case, and i'm positive it'll help you as well. Index: cam/cam_xpt.c =================================================================== RCS file: /home/ncvs/src/sys/cam/cam_xpt.c,v retrieving revision 1.26 retrieving revision 1.27 diff -u -u -r1.26 -r1.27 --- cam_xpt.c 1998/11/04 19:56:24 1.26 +++ cam_xpt.c 1998/11/25 13:50:10 1.27 @@ -368,6 +368,17 @@ "EXB-8200*", "*" }, CAM_QUIRK_NOSERIAL|CAM_QUIRK_NOLUNS, /*mintags*/0, /*maxtags*/0 + }, + { + /* + * This old revision of the TDC3600 is also SCSI-1, and + * hangs upon serial number probing. + */ + { + T_SEQUENTIAL, SIP_MEDIA_REMOVABLE, "TANDBERG", + " TDC 3600", "U07:" + }, + CAM_QUIRK_NOSERIAL, /*mintags*/0, /*maxtags*/0 }, { /* Default tagged queuing parameters for all devices */ Index: cam/scsi/scsi_sa.c =================================================================== RCS file: /home/ncvs/src/sys/cam/scsi/scsi_sa.c,v retrieving revision 1.5 retrieving revision 1.6 diff -u -u -r1.5 -r1.6 --- scsi_sa.c 1998/11/22 23:44:47 1.5 +++ scsi_sa.c 1998/11/26 10:47:52 1.6 @@ -161,6 +161,10 @@ { { T_SEQUENTIAL, SIP_MEDIA_REMOVABLE, "ARCHIVE", "Python 25601*", "*"}, /*quirks*/SA_QUIRK_NOCOMP + }, + { + { T_SEQUENTIAL, SIP_MEDIA_REMOVABLE, "TANDBERG", + " TDC 3600", "U07:"}, /*quirks*/SA_QUIRK_NOCOMP } }; -- 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 Dec 8 13:55:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16516 for freebsd-scsi-outgoing; Tue, 8 Dec 1998 13:55:56 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from europe.std.com (europe.std.com [199.172.62.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16496 for ; Tue, 8 Dec 1998 13:55:50 -0800 (PST) (envelope-from kwc@world.std.com) Received: from world.std.com by europe.std.com (8.7.6/BZS-8-1.0) id QAA16973; Tue, 8 Dec 1998 16:55:44 -0500 (EST) Received: by world.std.com (TheWorld/Spike-2.0) id AA09717; Tue, 8 Dec 1998 16:55:44 -0500 Date: Tue, 8 Dec 1998 16:55:44 -0500 From: kwc@world.std.com (Kenneth W Cochran) Message-Id: <199812082155.AA09717@world.std.com> To: freebsd-scsi@FreeBSD.ORG Subject: MultiOS, multi-disk booting Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello... I could use some advice as to a strategy for setting up my Drives. I can ask someplace besides -scsi if that's more appropriate. (-questions seems a bit noisy... :) Current disk config: HBA is DPT. 1gb hdd, HP 5400rpm C-3323: 1. DOS ('95/'98?) FAT 127mb (starting cylinder 2) 2. Extended, more FAT drives/filesystems 3. 512mb, empty, to become non-system filesystem(s) for fbsd ie, a "data" drive 2gb hdd, Seagate 7200rpm Barracuda ("system" drive): 1: FreeBSD 2.2.7, 1gb (/, swap, /var, /usr, /home) 2: Linux?, 1gb (similar fs layout; dunno, maybe -current? :-) Goals (if possible... :-) Either drive bootable, even if I disconnect one (or one malfunctions). Keep a default OS "active" in the partition table, ie. not updating the "active flag" when booting. I did this with Interactive Unix; it was marked active & booting DOS was a menu selection. I could "turn Unix off" by changing the active flag with fdisk. I can do all this with LILO, too, by installing LILO in Linux's root partition. I can make LILO boot FreeBSD or Linux as I wish here, but it does require more typing; it would be nice if I could choose with a function key, for example. I'd rather not have a bootmanager in the masterboot if I don't really have to... Question: (Likely my *real* question... :-) Can my DOS/FAT/Win95 partition be booted from a different drive (ie. LILO, BootEasy, etc.), for example, with my DOS/FAT drive not "primary?" Doc & FAQ pointers are welcome; I've already read a bunch of them (probably not the "right" one just yet :-). Many thanks, -kc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 8 14:28:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA20841 for freebsd-scsi-outgoing; Tue, 8 Dec 1998 14:28:43 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA20818 for ; Tue, 8 Dec 1998 14:28:38 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id XAA27539 for FreeBSD-SCSI@FreeBSD.ORG; Tue, 8 Dec 1998 23:28:30 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 8B7C41564; Tue, 8 Dec 1998 23:20:10 +0100 (CET) Date: Tue, 8 Dec 1998 23:20:10 +0100 From: Ollivier Robert To: FreeBSD-SCSI@FreeBSD.ORG Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R Message-ID: <19981208232010.A16918@keltia.freenix.fr> Mail-Followup-To: FreeBSD-SCSI@FreeBSD.ORG References: <366D5300.CBCAB303@airnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.16i In-Reply-To: <366D5300.CBCAB303@airnet.net>; from Kris Kirby on Tue, Dec 08, 1998 at 10:25:36AM -0600 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4871 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Kris Kirby: > sa0 at adv0 bus 0 target 2 lun 0 > sa0: Removable Sequential Access SCSI1 device > sa0: 3.300MB/s transfers I have the same drive although with an updated BIOS that makes it SCSI2 compatible: sa1 at ncr0 bus 0 target 4 lun 0 sa1: Removable Sequential Access SCSI2 device sa1: 3.300MB/s transfers I use an ASUS SC-875 and it works fine. Can you try to get an updated EPROM ? -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #2: Sun Nov 8 01:22:20 CET 1998 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 9 14:45:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA07247 for freebsd-scsi-outgoing; Wed, 9 Dec 1998 14:45:52 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA07235 for ; Wed, 9 Dec 1998 14:45:49 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id XAA01241; Wed, 9 Dec 1998 23:45:40 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA23483 (5.67b/IDA-1.5); Wed, 9 Dec 1998 23:42:47 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id XAA01240; Wed, 9 Dec 1998 23:27:38 +0100 (CET) From: Wilko Bulte Message-Id: <199812092227.XAA01240@yedi.iaf.nl> Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R In-Reply-To: <19981208232010.A16918@keltia.freenix.fr> from Ollivier Robert at "Dec 8, 98 11:20:10 pm" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Wed, 9 Dec 1998 23:27:38 +0100 (CET) Cc: FreeBSD-SCSI@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (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 As Ollivier Robert wrote... > According to Kris Kirby: > > sa0 at adv0 bus 0 target 2 lun 0 > > sa0: Removable Sequential Access SCSI1 device > > sa0: 3.300MB/s transfers > > I have the same drive although with an updated BIOS that makes it SCSI2 > compatible: > > sa1 at ncr0 bus 0 target 4 lun 0 > sa1: Removable Sequential Access SCSI2 device > sa1: 3.300MB/s transfers > > I use an ASUS SC-875 and it works fine. Can you try to get an updated EPROM ? Probably means you have to pull the eprom from your's and send an image of it's contents to Kris... Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 9 15:39:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13285 for freebsd-scsi-outgoing; Wed, 9 Dec 1998 15:39:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13279 for ; Wed, 9 Dec 1998 15:39:11 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id PAA26462; Wed, 9 Dec 1998 15:29:43 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdj26457; Wed Dec 9 23:29:43 1998 Message-ID: <366F079C.31DFF4F5@whistle.com> Date: Wed, 09 Dec 1998 15:28:28 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: Charlie Root CC: cayford@bigwoop.vicor-nb.com, conor@bigwoop.vicor-nb.com, daver@bigwoop.vicor-nb.com, jason@idiom.com, larry@bigwoop.vicor-nb.com, lorraine@idiom.com, scott@bigwoop.vicor-nb.com, scsi@FreeBSD.ORG Subject: Re: any recovery from these disk errors? References: <199812092300.PAA00404@bigwoop.vicor-nb.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Charlie Root wrote: > > We've been getting lots of scsi errors on freebsd here at vicor. From > what I can tell, they are unrecoverable. I'm hoping that you'll have > some additional insight/ideas to try. > > We tried moving the disk to another machine -- same errors; we > tried to change the bios settings which also didn't help. > > thanks > > -lorraine Venner? > > Dec 9 09:22:50 bigwoop /kernel.old: sd2(ahc0:2:0): NOT READY asc:4,1 > Dec 9 09:22:50 bigwoop /kernel.old: sd2(ahc0:2:0): Logical unit is in process of becoming ready field replaceable unit: 2 > Dec 9 09:22:50 bigwoop /kernel.old: , retries:2 are there other retries other than 2? it abandos the operation after 4 retries so if you only see a 2nd retry it probably got it's act together and successfully completed the operation. This is under what? 2.2.7? The device being not ready is interesting.. the DRIVE itself supplies this information... what kind of device is it? One of the RAIDs? Possibly it's busy handling a bad-block remapping or something. > Dec 9 09:22:50 bigwoop /kernel.old: sd2(ahc0:2:0): NOT READY asc:4,1 > Dec 9 09:22:50 bigwoop /kernel.old: sd2(ahc0:2:0): Logical unit is in process of becoming ready field replaceable unit: 2 > > Dec 9 09:22:51 bigwoop /kernel.old: , FAILURE > Dec 9 09:22:51 bigwoop /kernel.old: sd2(ahc0:2:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 This was a known bug in the aha driver at one stage, not usually 'fatal' however. Justin Gibbs (the author) is busy making his new stuff work in 3.0 so he's rather orphanned the 2.2 code but he does respond to bug reports. > Dec 9 09:22:51 bigwoop /kernel.old: SEQADDR = 0x5 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0xa > Dec 9 09:22:51 bigwoop /kernel.old: Ordered Tag queued That's a normal operation.. I wonder why it reported it. > Dec 9 09:22:51 bigwoop /kernel.old: sd2(ahc0:2:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 > Dec 9 09:22:51 bigwoop /kernel.old: SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x0 SSTAT1 = 0xa > Dec 9 09:22:51 bigwoop /kernel.old: sd2(ahc0:2:0): Queueing an Abort SCB > Dec 9 09:22:51 bigwoop /kernel.old: sd2(ahc0:2:0): Abort Message Sent > Dec 9 09:22:51 bigwoop /kernel.old: sd2(ahc0:2:0): SCB 0x2 - timed out in message out phase, SCSISIGI == 0xa4 > Dec 9 09:22:51 bigwoop /kernel.old: SEQADDR = 0xa1 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0x2 > Dec 9 09:22:51 bigwoop /kernel.old: sd2(ahc0:2:0): no longer in timeout > Dec 9 09:22:51 bigwoop /kernel.old: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted > Dec 9 09:22:51 bigwoop /kernel.old: sd2(ahc0:2:0): UNIT ATTENTION asc:29,0 > Dec 9 09:22:51 bigwoop /kernel.old: sd2(ahc0:2:0): Power on, reset, or bus device reset occurred field replaceable unit: 1 > Dec 9 09:22:51 bigwoop /kernel.old: , retries:2 > Dec 9 09:22:51 bigwoop /kernel.old: sd2(ahc0:2:0): NOT READY asc:4,1 > Dec 9 09:22:52 bigwoop /kernel.old: sd2(ahc0:2:0): Logical unit is in process of becoming ready field replaceable unit: 2 > > ... . > does "..." mean that you got the same error again immediatly or more of the same after some delay? > thanks again... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 9 15:46:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA13994 for freebsd-scsi-outgoing; Wed, 9 Dec 1998 15:46:27 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA13989 for ; Wed, 9 Dec 1998 15:46:25 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA06233; Wed, 9 Dec 1998 16:46:07 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812092346.QAA06233@panzer.plutotech.com> Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R In-Reply-To: <199812092227.XAA01240@yedi.iaf.nl> from Wilko Bulte at "Dec 9, 98 11:27:38 pm" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Wed, 9 Dec 1998 16:46:07 -0700 (MST) Cc: roberto@keltia.freenix.fr, 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 Wilko Bulte wrote... > As Ollivier Robert wrote... > > According to Kris Kirby: > > > sa0 at adv0 bus 0 target 2 lun 0 > > > sa0: Removable Sequential Access SCSI1 device > > > sa0: 3.300MB/s transfers > > > > I have the same drive although with an updated BIOS that makes it SCSI2 > > compatible: > > > > sa1 at ncr0 bus 0 target 4 lun 0 > > sa1: Removable Sequential Access SCSI2 device > > sa1: 3.300MB/s transfers > > > > I use an ASUS SC-875 and it works fine. Can you try to get an updated EPROM ? > > Probably means you have to pull the eprom from your's and send an image of > it's contents to Kris... It would probably be quicker and easier to try Joerg's quirk entries for that drive and see if they work. (you might have to adjust the firmware revision number for it to work) 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 Dec 9 16:07:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA17771 for freebsd-scsi-outgoing; Wed, 9 Dec 1998 16:07:07 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from bigwoop.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA17752 for ; Wed, 9 Dec 1998 16:07:02 -0800 (PST) (envelope-from conor@bigwoop.vicor-nb.com) Received: (from conor@localhost) by bigwoop.vicor-nb.com (8.8.5/8.7.3) id QAA00963; Wed, 9 Dec 1998 16:06:39 -0800 (PST) Date: Wed, 9 Dec 1998 16:06:39 -0800 (PST) From: Conor Dixon Message-Id: <199812100006.QAA00963@bigwoop.vicor-nb.com> To: julian@whistle.com, root@bigwoop.vicor-nb.com Subject: Re: any recovery from these disk errors? Cc: cayford@bigwoop.vicor-nb.com, conor@bigwoop.vicor-nb.com, daver@bigwoop.vicor-nb.com, jason@idiom.com, larry@bigwoop.vicor-nb.com, lorraine@idiom.com, scott@bigwoop.vicor-nb.com, scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks for answering Julian... oh and hello.. >re there other retries other than 2? Yes there were plenty of retries, no joy anytime >it abandos the operation after 4 retries so if you only see a 2nd >retry it probably got it's act together and successfully completed >the operation. This is under what? 2.2.7? We tried it on 2 machines , one with FreeBSD 2.2.2-RELEASE #0: and the other with FreeBSD 2.1-STABLE #0: Same results with both the device itself is a regular 4.3gig barracuda scsi disk Dave Robison was here on Sunday mapping bad blocks after a complete blackout due to the storm Saturday night. bigwoop did come up fine on Monday (including this disk) Conor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 9 16:12:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA18985 for freebsd-scsi-outgoing; Wed, 9 Dec 1998 16:12:50 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from idiom.com (idiom.com [209.157.64.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA18980 for ; Wed, 9 Dec 1998 16:12:49 -0800 (PST) (envelope-from jason@idiom.com) Received: from idiom.com (jason@localhost [127.0.0.1]) by idiom.com (8.8.8/8.8.5) with ESMTP id QAA23357; Wed, 9 Dec 1998 16:12:41 -0800 (PST) Message-Id: <199812100012.QAA23357@idiom.com> To: Conor Dixon cc: julian@whistle.com, root@bigwoop.vicor-nb.com, cayford@bigwoop.vicor-nb.com, daver@bigwoop.vicor-nb.com, larry@bigwoop.vicor-nb.com, lorraine@idiom.com, scott@bigwoop.vicor-nb.com, scsi@FreeBSD.ORG Subject: Re: any recovery from these disk errors? In-reply-to: Your message of "Wed, 09 Dec 1998 16:06:39 PST." <199812100006.QAA00963@bigwoop.vicor-nb.com> Date: Wed, 09 Dec 1998 16:12:41 -0800 From: Jason Venner Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org More to the point, lorraine modified the bios params on the controller to send the autostart command, and the bios probe returned 'auto start timed out' on that drive, and the controller bios verify media command failed. > From conor@bigwoop.vicor-nb.com Wed Dec 9 16:06:43 1998 > Date: Wed, 9 Dec 1998 16:06:39 -0800 (PST) > From: Conor Dixon > To: julian@whistle.com, root@bigwoop.vicor-nb.com > Subject: Re: any recovery from these disk errors? > Cc: cayford@bigwoop.vicor-nb.com, conor@bigwoop.vicor-nb.com, > daver@bigwoop.vicor-nb.com, jason@idiom.com, > larry@bigwoop.vicor-nb.com, lorraine@idiom.com, > scott@bigwoop.vicor-nb.com, scsi@freebsd.org > > Thanks for answering Julian... oh and hello.. > > >re there other retries other than 2? > > Yes there were plenty of retries, no joy anytime > > >it abandos the operation after 4 retries so if you only see a 2nd > >retry it probably got it's act together and successfully completed > >the operation. This is under what? 2.2.7? > > We tried it on 2 machines , one with FreeBSD 2.2.2-RELEASE #0: > and the other with FreeBSD 2.1-STABLE #0: > Same results with both > > the device itself is a regular 4.3gig barracuda scsi disk > > Dave Robison was here on Sunday mapping bad blocks after a complete > blackout due to the storm Saturday night. bigwoop did come up fine on > Monday (including this disk) > > Conor > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 9 16:29:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20821 for freebsd-scsi-outgoing; Wed, 9 Dec 1998 16:29:27 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20815 for ; Wed, 9 Dec 1998 16:29:25 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA28836; Wed, 9 Dec 1998 16:27:20 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdb28828; Thu Dec 10 00:27:10 1998 Message-ID: <366F1515.237C228A@whistle.com> Date: Wed, 09 Dec 1998 16:25:57 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: Conor Dixon CC: root@bigwoop.vicor-nb.com, cayford@bigwoop.vicor-nb.com, daver@bigwoop.vicor-nb.com, jason@idiom.com, larry@bigwoop.vicor-nb.com, lorraine@idiom.com, scott@bigwoop.vicor-nb.com, scsi@FreeBSD.ORG Subject: Re: any recovery from these disk errors? References: <199812100006.QAA00963@bigwoop.vicor-nb.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Conor Dixon wrote: > > Thanks for answering Julian... oh and hello.. > > >re there other retries other than 2? > > Yes there were plenty of retries, no joy anytime > > >it abandos the operation after 4 retries so if you only see a 2nd > >retry it probably got it's act together and successfully completed > >the operation. This is under what? 2.2.7? > > We tried it on 2 machines , one with FreeBSD 2.2.2-RELEASE #0: > and the other with FreeBSD 2.1-STABLE #0: > Same results with both hmmm 2.2.2 and 2.1.... I would suggest that maybe now that 2.2.8 is out youmight try at least the 2.2.7 cdrom. 2.2.5 fixed quite a few AHC related bugs. > > the device itself is a regular 4.3gig barracuda scsi disk ok.. > > Dave Robison was here on Sunday mapping bad blocks after a complete > blackout due to the storm Saturday night. bigwoop did come up fine on > Monday (including this disk) > > Conor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 9 16:57:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24151 for freebsd-scsi-outgoing; Wed, 9 Dec 1998 16:57:47 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from bigwoop.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24145 for ; Wed, 9 Dec 1998 16:57:44 -0800 (PST) (envelope-from conor@bigwoop.vicor-nb.com) Received: (from conor@localhost) by bigwoop.vicor-nb.com (8.8.5/8.7.3) id QAA01116; Wed, 9 Dec 1998 16:49:41 -0800 (PST) Date: Wed, 9 Dec 1998 16:49:41 -0800 (PST) From: Conor Dixon Message-Id: <199812100049.QAA01116@bigwoop.vicor-nb.com> To: conor@bigwoop.vicor-nb.com, julian@whistle.com Subject: Re: any recovery from these disk errors? Cc: cayford@bigwoop.vicor-nb.com, daver@bigwoop.vicor-nb.com, jason@idiom.com, larry@bigwoop.vicor-nb.com, larryc@bigwoop.vicor-nb.com, lorraine@idiom.com, root@bigwoop.vicor-nb.com, scott@bigwoop.vicor-nb.com, scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >More to the point, lorraine modified the bios params on the controller >to send the autostart command, and the bios probe returned 'auto start >timed out' on that drive, and the controller bios verify media command > failed. thanks again Julian, cerainly worth a try. Jason is going to take a look at the disk tonight to see if it can't be resuccitated I'ld be inclined to agree with Jason's coment above which would point to a disk that is way beyond "field serviceable ready" :-) i.e toast Conor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 9 17:07:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA25720 for freebsd-scsi-outgoing; Wed, 9 Dec 1998 17:07:40 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from flag.blackened.net (flag.blackened.net [208.206.78.232]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA25703 for ; Wed, 9 Dec 1998 17:07:37 -0800 (PST) (envelope-from daver@flag.blackened.net) Received: (from daver@localhost) by flag.blackened.net (8.8.8/8.8.5) id RAA09639; Wed, 9 Dec 1998 17:07:23 -0800 (PST) Date: Wed, 9 Dec 1998 17:07:23 -0800 (PST) From: Pomegranate Message-Id: <199812100107.RAA09639@flag.blackened.net> To: conor@bigwoop.vicor-nb.com, julian@whistle.com, root@bigwoop.vicor-nb.com Subject: Re: any recovery from these disk errors? Cc: cayford@bigwoop.vicor-nb.com, daver@bigwoop.vicor-nb.com, jason@idiom.com, larry@bigwoop.vicor-nb.com, lorraine@idiom.com, scott@bigwoop.vicor-nb.com, scsi@FreeBSD.ORG In-Reply-To: <199812100006.QAA00963@bigwoop.vicor-nb.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Julian, is it conceivable that mounting this disk on a cam-enabled 3.0 system might help? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 9 17:31:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA29674 for freebsd-scsi-outgoing; Wed, 9 Dec 1998 17:31:30 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA29666 for ; Wed, 9 Dec 1998 17:31:27 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id QAA28934; Wed, 9 Dec 1998 16:29:12 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdv28932; Thu Dec 10 00:29:11 1998 Message-ID: <366F158F.2F1CF0FB@whistle.com> Date: Wed, 09 Dec 1998 16:27:59 -0800 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386) MIME-Version: 1.0 To: Conor Dixon CC: root@bigwoop.vicor-nb.com, cayford@bigwoop.vicor-nb.com, daver@bigwoop.vicor-nb.com, jason@idiom.com, larry@bigwoop.vicor-nb.com, lorraine@idiom.com, scott@bigwoop.vicor-nb.com, scsi@FreeBSD.ORG Subject: Re: any recovery from these disk errors? References: <199812100006.QAA00963@bigwoop.vicor-nb.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Conor Dixon wrote: > > Thanks for answering Julian... oh and hello.. > > >re there other retries other than 2? > > Yes there were plenty of retries, no joy anytime > > >it abandos the operation after 4 retries so if you only see a 2nd > >retry it probably got it's act together and successfully completed > >the operation. This is under what? 2.2.7? > > We tried it on 2 machines , one with FreeBSD 2.2.2-RELEASE #0: > and the other with FreeBSD 2.1-STABLE #0: > Same results with both If you tried exactly the same drive on 2 machines, I'd suspect the drive.... > > the device itself is a regular 4.3gig barracuda scsi disk we're only talking about a single specific drive, not all baracuda's right? > > Dave Robison was here on Sunday mapping bad blocks after a complete > blackout due to the storm Saturday night. bigwoop did come up fine on > Monday (including this disk) > > Conor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 9 17:33:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00178 for freebsd-scsi-outgoing; Wed, 9 Dec 1998 17:33:33 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from bigwoop.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00164 for ; Wed, 9 Dec 1998 17:33:31 -0800 (PST) (envelope-from conor@bigwoop.vicor-nb.com) Received: (from conor@localhost) by bigwoop.vicor-nb.com (8.8.5/8.7.3) id RAA01329; Wed, 9 Dec 1998 17:33:23 -0800 (PST) Date: Wed, 9 Dec 1998 17:33:23 -0800 (PST) From: Conor Dixon Message-Id: <199812100133.RAA01329@bigwoop.vicor-nb.com> To: conor@bigwoop.vicor-nb.com, julian@whistle.com Subject: Re: any recovery from these disk errors? Cc: cayford@bigwoop.vicor-nb.com, daver@bigwoop.vicor-nb.com, jason@idiom.com, larry@bigwoop.vicor-nb.com, larryc@bigwoop.vicor-nb.com, lorraine@idiom.com, root@bigwoop.vicor-nb.com, scott@bigwoop.vicor-nb.com, scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >we're only talking about a single specific drive, not all >baracuda's right? yes, just one single specific drive Conor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 9 17:37:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA00725 for freebsd-scsi-outgoing; Wed, 9 Dec 1998 17:37:17 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ninbox.ml.org (hsv1-243.airnet.net [207.242.81.243]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA00716 for ; Wed, 9 Dec 1998 17:37:14 -0800 (PST) (envelope-from kris@airnet.net) Received: from airnet.net (localhost [127.0.0.1]) by ninbox.ml.org (8.9.1/8.8.5) with ESMTP id TAA02223 for ; Wed, 9 Dec 1998 19:37:06 -0600 (CST) Message-ID: <366F25C2.456C182F@airnet.net> Date: Wed, 09 Dec 1998 19:37:06 -0600 From: Kris Kirby Organization: Absolutely None! X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: FreeBSD-SCSI@FreeBSD.ORG Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R References: <199812092346.QAA06233@panzer.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry wrote: > > Probably means you have to pull the eprom from your's and send an image of > > it's contents to Kris... 1. I have a copy of the latest firmware and am preparing to burn it. > It would probably be quicker and easier to try Joerg's quirk entries for > that drive and see if they work. (you might have to adjust the firmware > revision number for it to work) 2. Already tried Joerg's patch, no change :-(. -- Kris Kirby UAH Mail UAH CS Home WWW ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 9 18:55:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA13291 for freebsd-scsi-outgoing; Wed, 9 Dec 1998 18:55:04 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA13286 for ; Wed, 9 Dec 1998 18:55:02 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id TAA07368; Wed, 9 Dec 1998 19:54:50 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812100254.TAA07368@panzer.plutotech.com> Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R In-Reply-To: <366F25C2.456C182F@airnet.net> from Kris Kirby at "Dec 9, 98 07:37:06 pm" To: kris@airnet.net (Kris Kirby) Date: Wed, 9 Dec 1998 19:54:50 -0700 (MST) 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 Kris Kirby wrote... > Kenneth D. Merry wrote: > > > Probably means you have to pull the eprom from your's and send an image of > > > it's contents to Kris... > > 1. I have a copy of the latest firmware and am preparing to burn it. > > > It would probably be quicker and easier to try Joerg's quirk entries for > > that drive and see if they work. (you might have to adjust the firmware > > revision number for it to work) > > 2. Already tried Joerg's patch, no change :-(. I assume you changed it so that it would work with your drive? Your firmware revisions aren't the same, so the quirk entry wouldn't match your drive without modificiation. 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 Dec 9 23:53:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA16897 for freebsd-scsi-outgoing; Wed, 9 Dec 1998 23:53:38 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from magnet.geophysik.tu-freiberg.de (magnet.geophysik.tu-freiberg.de [139.20.128.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA16892 for ; Wed, 9 Dec 1998 23:53:34 -0800 (PST) (envelope-from freebsd@magnet.geophysik.tu-freiberg.de) Received: (from freebsd@localhost) by magnet.geophysik.tu-freiberg.de (8.9.1/8.7.3) id IAA01592 for freebsd-scsi@freebsd.org; Thu, 10 Dec 1998 08:53:24 +0100 (CET) From: Holm Tiffe Message-Id: <199812100753.IAA01592@magnet.geophysik.tu-freiberg.de> Subject: CAM, cdrecord and PLASMON RF4100 anyone ? To: freebsd-scsi@FreeBSD.ORG Date: Thu, 10 Dec 1998 08:53:24 +0100 (CET) Reply-To: freebsd@magnet.geophysik.tu-freiberg.de X-Mailer: ELM [version 2.4ME+ PL26 (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 Hi, yesterday I have for the first time tried cdrecord from the ports to burn an CDR on my oldish PLASMON RF4100. The machine I use was previously non-CAM an I've used FreeBSD's own worm driver to write my CDR's. First, it seems that my PLASMON doesn't like the write_track() cmd in the file drv_philips.c around the line 504. After removing that, I was able to burn my first CDR. But wat the hell ist this ? 00000000 b3 b3 b3 f7 f7 f7 f7 a2 a2 a2 a2 c2 c2 c2 c2 8c |................| 00000010 8c 8c 8c 9b 9b 9b 9b 1f 1f 1f 1f f6 f6 f6 f6 42 |...............B| 00000020 42 42 42 24 24 24 24 3b 3b 3b 3b 9d 9d 9d 9d be |BBB$$$$;;;;.....| 00000030 be be be 34 34 34 34 be be be be 44 44 44 44 55 |...4444....DDDDU| 00000040 55 55 55 60 60 60 60 4e 4e 4e 4e 17 17 17 17 84 |UUU````NNNN.....| 00000050 84 84 84 e9 e9 e9 e9 b4 b4 b4 b4 66 66 66 66 1f |...........ffff.| 00000060 1f 1f 1f a6 a6 a6 a6 23 23 23 23 8a 8a 8a 8a 8a |.......####.....| 00000070 8a 8a 8a fa fa fa fa 11 11 11 11 35 35 35 35 2e |...........5555.| 00000080 2e 2e 2e 59 59 59 59 93 93 93 93 6d 6d 6d 6d 5d |...YYYY....mmmm]| 00000090 5d 5d 5d d2 d2 d2 d2 79 79 79 79 b9 b9 b9 b9 85 |]]]....yyyy.....| 000000a0 85 85 85 a9 a9 a9 a9 00 00 00 00 70 70 70 70 eb |...........pppp.| 000000b0 eb eb eb 24 24 24 24 1b 1b 1b 1b 77 77 77 77 ca |...$$$$....wwww.| 000000c0 ca ca ca fe fe fe fe 30 30 30 30 8f 8f 8f 8f ab |.......0000.....| 000000d0 ab ab ab c0 c0 c0 c0 3c 3c 3c 3c 2c 2c 2c 2c a9 |.......<<<<,,,,.| 000000e0 a9 a9 a9 70 70 70 70 9b 9b 9b 9b cf cf cf cf 3f |...pppp........?| 000000f0 3f 3f 3f 6c 6c 6c 6c bd bd bd bd 34 34 34 34 ce |???llll....4444.| 00000100 ce ce ce bf bf bf bf 24 24 24 24 6b 6b 6b 6b fc |.......$$$$kkkk.| 00000110 fc fc fc 10 10 10 10 85 85 85 85 d9 d9 d9 d9 eb |................| 00000120 eb eb eb 54 54 54 54 f0 f0 f0 f0 53 53 53 53 d1 |...TTTT....SSSS.| 00000130 d1 d1 d1 89 89 89 89 fa fa fa fa 71 71 71 71 9b |...........qqqq.| 00000140 9b 9b 9b 4f 4f 4f 4f 97 97 97 97 ec ec ec ec 95 |...OOOO.........| 00000150 95 95 95 5c 5c 5c 5c 32 32 32 32 bf bf bf bf a4 |...\\\\2222.....| 00000160 a4 a4 a4 a3 a3 a3 a3 82 82 82 82 58 58 58 58 73 |...........XXXXs| this is a dump from the first bytes of my CDR, the entire CDR contains now this sort of junk. The ISO-fs I was trying to burn is totally intact, an I can mount it using the vn devices. here are the first bytes from it: 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| * 00008000 01 43 44 30 30 31 01 00 46 72 65 65 42 53 44 20 |.CD001..FreeBSD | 00008010 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | | 00008020 20 20 20 20 20 20 20 20 2f 75 73 72 38 20 20 20 | /usr8 | 00008030 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | | 00008040 20 20 20 20 20 20 20 20 00 00 00 00 00 00 00 00 | ........| 00008050 67 fc 04 00 00 04 fc 67 00 00 00 00 00 00 00 00 |g......g........| 00008060 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00008070 00 00 00 00 00 00 00 00 01 00 00 01 01 00 00 01 |................| 00008080 00 08 08 00 30 36 00 00 00 00 36 30 12 00 00 00 |....06....60....| 00008090 00 00 00 00 00 00 00 1a 00 00 00 00 22 00 22 00 |............".".| 000080a0 00 00 00 00 00 22 00 10 00 00 00 00 10 00 62 0c |....."........b.| 000080b0 09 09 05 14 04 02 00 00 01 00 00 01 01 00 20 20 |.............. | 000080c0 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | | * 00008130 20 20 20 20 20 20 20 20 20 20 20 20 20 20 48 6f | Ho| 00008140 6c 6d 20 20 20 20 20 20 20 20 20 20 20 20 20 20 |lm | 00008150 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | | * 00008320 20 20 20 20 20 20 20 20 20 20 20 20 20 31 39 39 | 199| 00008330 38 31 32 30 39 30 39 30 35 32 30 30 30 04 31 39 |8120909052000.19| 00008340 39 38 31 32 30 39 30 39 30 35 32 30 30 30 04 30 |98120909052000.0| Has anyone seen this before ? Any suggestions ? The cmd to write the CDR was cdrecord -data dev=0,4,0 usr8.cd Cdrecord has successfully detected the burner's model and the firmware version: Cdrecord release 1.6.1 Copyright (C) 1995-1998 Jrg Schilling scsidev: '0,4,0' scsibus: 0 target: 4 lun: 0 Device type : Removable WORM Version : 2 Response Format: 2 Capabilities : SYNC Vendor_info : 'PLASMON ' Identifikation : 'RF4100 ' Revision : '1.26' Device seems to be: Plasmon RF-4100. Using driver for Plasmon RF 4100 (plasmon_rf4100). Driver flags : Starting to write CD/DVD at speed 1 in write mode for single session. Thanks in Advance, Holm -- ******************************************************************************* * Holm Tiffe holm@geophysik.tu-freiberg.de * * Freiberger Strasse 24 * * 09600 Kleinschirma, Germany Microsoft is not the Answer - * * Tel.: 49 3731 74233 Microsoft is the Question, * * UUCP: 49 3731 73719 unicorn!holm and the Answer is no ! * ******************************************************************************* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 10 00:21:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19877 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 00:21:14 -0800 (PST) (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 AAA19872 for ; Thu, 10 Dec 1998 00:21:04 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id JAA17055; Thu, 10 Dec 1998 09:20:48 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id JAA29300; Thu, 10 Dec 1998 09:15:14 +0100 (MET) (envelope-from j) Message-ID: <19981210091512.30601@uriah.heep.sax.de> Date: Thu, 10 Dec 1998 09:15:12 +0100 From: J Wunsch To: Kris Kirby Cc: FreeBSD-SCSI@FreeBSD.ORG Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R Reply-To: Joerg Wunsch References: <199812092346.QAA06233@panzer.plutotech.com> <366F25C2.456C182F@airnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <366F25C2.456C182F@airnet.net>; from Kris Kirby on Wed, Dec 09, 1998 at 07:37:06PM -0600 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 Kris Kirby wrote: > 2. Already tried Joerg's patch, no change :-(. Sorry, i missed the detail your firmware rev was different. :( Replace the "U07:" by an "A07:" in my patch. Ken, what about your ideas to avoid serial number probing for all SCSI-1 level devices? (This would still leave the problem with the compression page, but that could be dealt by setting the `no compression' quirk flag automatically upon receipt of the ILLEGAL REQUEST error after the first mode select.) -- 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 Thu Dec 10 01:36:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA27880 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 01:36:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA27875 for ; Thu, 10 Dec 1998 01:36:14 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id BAA09825; Thu, 10 Dec 1998 01:35:27 -0800 Date: Thu, 10 Dec 1998 01:35:27 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Joerg Wunsch cc: Kris Kirby , FreeBSD-SCSI@FreeBSD.ORG Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R In-Reply-To: <19981210091512.30601@uriah.heep.sax.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The 'no compression' stuff is separate from probing. The tape driver changes which I will integrate soonest has some changes to accomodate some SCSI-1 devices more graciously- but probably won't fix this. I'm kind of inclined to believe that if < SCSI2 that VPD info is very likely not there (that's serial #). On Thu, 10 Dec 1998, J Wunsch wrote: > As Kris Kirby wrote: > > > 2. Already tried Joerg's patch, no change :-(. > > Sorry, i missed the detail your firmware rev was different. :( > > Replace the "U07:" by an "A07:" in my patch. > > Ken, what about your ideas to avoid serial number probing for all > SCSI-1 level devices? (This would still leave the problem with the > compression page, but that could be dealt by setting the `no > compression' quirk flag automatically upon receipt of the ILLEGAL > REQUEST error after the first mode select.) > > -- > 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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 10 04:46:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA18091 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 04:46:52 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from www.langen.bull.de (www.langen.bull.de [193.141.50.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA18085 for ; Thu, 10 Dec 1998 04:46:49 -0800 (PST) (envelope-from luettgen@swh600.langen.bull.de) Received: from swh600.langen.bull.de (swh600.langen.bull.de [193.141.50.50]) by www.langen.bull.de (8.9.1/8.9.1) with SMTP id NAA06852 for ; Thu, 10 Dec 1998 13:46:39 +0100 Received: from [129.181.212.59] by swh600.langen.bull.de (AIX 3.2/UCB 5.64/4.03) id AA18786; Thu, 10 Dec 1998 13:45:06 +0100 Message-Id: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit Mime-Version: 1.0 Date: Thu, 10 Dec 1998 13:46:37 +0100 (CET) From: "Ralf.Luettgen" To: freebsd-scsi@FreeBSD.ORG Subject: scsiformat under 3.0 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, on my new FreeBSD 3.0 box there is no scsiformat. Can I do it with camcontrol Thanks Ralf ---------------------------------- E-Mail: Ralf.Luettgen Date: 10-Dec-98 Time: 13:45:44 This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 10 08:51:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA14393 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 08:51:27 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA14382 for ; Thu, 10 Dec 1998 08:51:25 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id LAA28412 for ; Thu, 10 Dec 1998 11:51:13 -0500 (EST) Date: Thu, 10 Dec 1998 11:51:13 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: freebsd-scsi@FreeBSD.ORG Subject: options FAILSAFE 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 always wondered exactly what it does... Is it strictly a scsi thing or does it touch other bits and pieces? LINT says it enables tag queueing on the ncr. Does anyone know what else it does, and whether it does anything if you're running CAM? Thanks, Charles --- Charles Sprickman spork@super-g.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 10 09:42:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19501 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 09:42:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19495 for ; Thu, 10 Dec 1998 09:42:35 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id EAA20595; Fri, 11 Dec 1998 04:42:26 +1100 Date: Fri, 11 Dec 1998 04:42:26 +1100 From: Bruce Evans Message-Id: <199812101742.EAA20595@godzilla.zeta.org.au> To: freebsd-scsi@FreeBSD.ORG, spork@super-g.com Subject: Re: options FAILSAFE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I've always wondered exactly what it does... Is it strictly a scsi thing >or does it touch other bits and pieces? LINT says it enables tag queueing >on the ncr. Does anyone know what else it does, and whether it does >anything if you're running CAM? It rots. In -current, it has no effect except to disable one obscure initialization of Cyrix CPUs. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 10 09:43:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19753 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 09:43:17 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA19738 for ; Thu, 10 Dec 1998 09:43:15 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id KAA10879; Thu, 10 Dec 1998 10:32:50 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812101732.KAA10879@panzer.plutotech.com> Subject: Re: scsiformat under 3.0 In-Reply-To: from "Ralf.Luettgen" at "Dec 10, 98 01:46:37 pm" To: luettgen@swh600.langen.bull.de (Ralf.Luettgen) Date: Thu, 10 Dec 1998 10:32:50 -0700 (MST) 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 Ralf.Luettgen wrote... > Hi, > > on my new FreeBSD 3.0 box there is no scsiformat. > Can I do it with camcontrol Yes, you can. Try this: camcontrol cmd -v -n da -u 2 -t 3600 -c "4 0 0 0 0 0" "-v" tells camcontrol to print sense information if the command fails "-n" specifies the device name "-u" specifies the unit number (i.e., da2) "-t" specifies the timeout for the command in seconds. If you suspect your disk will need more than an hour, increase it. "-c" specifies the SCSI CDB I plan on adding a 'camcontrol format' command, but haven't gotten around to it yet. The above command should give you more or less the functionality of scsiformat, but without the seatbelt. 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 Thu Dec 10 09:51:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21031 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 09:51:35 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21025 for ; Thu, 10 Dec 1998 09:51:31 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id KAA11062; Thu, 10 Dec 1998 10:50:14 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812101750.KAA11062@panzer.plutotech.com> Subject: Re: CAM, cdrecord and PLASMON RF4100 anyone ? In-Reply-To: <199812100753.IAA01592@magnet.geophysik.tu-freiberg.de> from Holm Tiffe at "Dec 10, 98 08:53:24 am" To: freebsd@magnet.geophysik.tu-freiberg.de Date: Thu, 10 Dec 1998 10:50:14 -0700 (MST) 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 Holm Tiffe wrote... > Hi, > > yesterday I have for the first time tried cdrecord from the ports > to burn an CDR on my oldish PLASMON RF4100. The machine I use > was previously non-CAM an I've used FreeBSD's own worm driver to > write my CDR's. > > First, it seems that my PLASMON doesn't like the write_track() cmd > in the file drv_philips.c around the line 504. > After removing that, I was able to burn my first CDR. > But wat the hell ist this ? > > 00000000 b3 b3 b3 f7 f7 f7 f7 a2 a2 a2 a2 c2 c2 c2 c2 8c |................| > 00000010 8c 8c 8c 9b 9b 9b 9b 1f 1f 1f 1f f6 f6 f6 f6 42 |...............B| > 00000020 42 42 42 24 24 24 24 3b 3b 3b 3b 9d 9d 9d 9d be |BBB$$$$;;;;.....| [ ... ] Looks kinda like garbage. > this is a dump from the first bytes of my CDR, the entire CDR contains now this > sort of junk. > > The ISO-fs I was trying to burn is totally intact, an I can mount it using > the vn devices. > > here are the first bytes from it: > > 00000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| > * > 00008000 01 43 44 30 30 31 01 00 46 72 65 65 42 53 44 20 |.CD001..FreeBSD | > 00008010 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 | | [ ... ] And that looks okay. > > Has anyone seen this before ? Any suggestions ? > > The cmd to write the CDR was cdrecord -data dev=0,4,0 usr8.cd I doubt this is the problem, but what happens if you reverse the arguments: cdrecord dev=0,4,0 -data usr8.cd You don't have to try it, since it's unlikely that that's the problem. The cdrecord usage information kinda indicates that things subsequent to the "-data" are tracks to burn. > Cdrecord has successfully detected the burner's model and the > firmware version: > > Cdrecord release 1.6.1 Copyright (C) 1995-1998 Jrg Schilling > scsidev: '0,4,0' > scsibus: 0 target: 4 lun: 0 > Device type : Removable WORM > Version : 2 > Response Format: 2 > Capabilities : SYNC > Vendor_info : 'PLASMON ' > Identifikation : 'RF4100 ' > Revision : '1.26' > Device seems to be: Plasmon RF-4100. > Using driver for Plasmon RF 4100 (plasmon_rf4100). > Driver flags : > Starting to write CD/DVD at speed 1 in write mode for single session. Well, it appears that cdrecord is able to talk to the drive, since it gets back the correct inquiry information. So, I doubt this is a CAM problem. I would suggest contacting Joerg Schilling , the author of cdrecord. He may know of issues with that particular drive, or cdrecord, that would cause the above problem. Sorry I can't help more, 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 Thu Dec 10 09:53:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21434 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 09:53:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21429 for ; Thu, 10 Dec 1998 09:53:16 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id KAA11080; Thu, 10 Dec 1998 10:52:37 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812101752.KAA11080@panzer.plutotech.com> Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R In-Reply-To: <19981210091512.30601@uriah.heep.sax.de> from J Wunsch at "Dec 10, 98 09:15:12 am" To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 10 Dec 1998 10:52:37 -0700 (MST) Cc: kris@airnet.net, 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 J Wunsch wrote... > As Kris Kirby wrote: > > > 2. Already tried Joerg's patch, no change :-(. > > Sorry, i missed the detail your firmware rev was different. :( > > Replace the "U07:" by an "A07:" in my patch. > > Ken, what about your ideas to avoid serial number probing for all > SCSI-1 level devices? (This would still leave the problem with the > compression page, but that could be dealt by setting the `no > compression' quirk flag automatically upon receipt of the ILLEGAL > REQUEST error after the first mode select.) I think that's a good idea, and in fact we've been planning on doing it for a while. The idea is to add a SCSI revision field to the quirk entry format, and then just not send serial number requests to anything < 2. We could probably do something similar for the compression page stuff in the tape driver. 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 Thu Dec 10 09:57:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21925 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 09:57:53 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21913 for ; Thu, 10 Dec 1998 09:57:49 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id KAA11112; Thu, 10 Dec 1998 10:57:26 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812101757.KAA11112@panzer.plutotech.com> Subject: Re: options FAILSAFE In-Reply-To: from spork at "Dec 10, 98 11:51:13 am" To: spork@super-g.com (spork) Date: Thu, 10 Dec 1998 10:57:26 -0700 (MST) 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 spork wrote... > I've always wondered exactly what it does... Is it strictly a scsi thing > or does it touch other bits and pieces? LINT says it enables tag queueing > on the ncr. Does anyone know what else it does, and whether it does > anything if you're running CAM? It doesn't do anything to affect the SCSI subsystem if you're running CAM. The best way to find out what it does is: cd /usr/src/sys find . -name "*.[ch]" -print |xargs grep FAILSAFE It appears that it only affects some Cyrix options now. (I could have missed something by only looking at *.c and *.h, though.) 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 Thu Dec 10 10:37:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27280 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 10:37:13 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from laker.net (jet.laker.net [205.245.74.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27270 for ; Thu, 10 Dec 1998 10:37:08 -0800 (PST) (envelope-from sfriedri@laker.net) Received: from nt (digital-fll-185.laker.net [205.245.75.85]) by laker.net (8.9.0/8.9.LAKERNET.NO-SPAM.SPAMMERS.AND.RELAYS.WILL.BE.TRACKED.AND.PROSECUTED.) with SMTP id NAA17978 for ; Thu, 10 Dec 1998 13:36:57 -0500 Message-Id: <199812101836.NAA17978@laker.net> From: "Steve Friedrich" To: "FreeBSD SCSI" Date: Thu, 10 Dec 1998 13:34:17 -0500 Reply-To: "Steve Friedrich" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: audio CDs with nca driver Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I can't play audio CDs on my Media Vision PAS16 (NEC 84 CDROM). I think it's because the nca driver doesn't support it. Can anyone confirm? Unix systems measure "uptime" in years, Winblows measures it in minutes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 10 10:46:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28437 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 10:46:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28432 for ; Thu, 10 Dec 1998 10:46:09 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id KAA02228; Thu, 10 Dec 1998 10:45:53 -0800 Date: Thu, 10 Dec 1998 10:45:53 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Kenneth D. Merry" cc: FreeBSD-SCSI@FreeBSD.ORG Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R In-Reply-To: <199812101752.KAA11080@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 > > I think that's a good idea, and in fact we've been planning on doing it for > a while. The idea is to add a SCSI revision field to the quirk entry > format, and then just not send serial number requests to anything < 2. You don't need a quirk entry. You know what revisions the device is when you do the initial inquiry. > > We could probably do something similar for the compression page stuff in > the tape driver. > I'll own that. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 10 11:50:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06353 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 11:50:43 -0800 (PST) (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 LAA06338 for ; Thu, 10 Dec 1998 11:50:31 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id UAA25152 for FreeBSD-SCSI@FreeBSD.ORG; Thu, 10 Dec 1998 20:50:21 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id UAA00662; Thu, 10 Dec 1998 20:38:55 +0100 (MET) (envelope-from j) Message-ID: <19981210203853.46005@uriah.heep.sax.de> Date: Thu, 10 Dec 1998 20:38:53 +0100 From: J Wunsch To: FreeBSD-SCSI@FreeBSD.ORG Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R Reply-To: Joerg Wunsch References: <19981210091512.30601@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: ; from Matthew Jacob on Thu, Dec 10, 1998 at 01:35:27AM -0800 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 Jacob wrote: > The 'no compression' stuff is separate from probing. The tape driver Sure. It happens the first time the tape drive is attempted to be opened. The mode select failure is fatal however, so it wouldn't have helped my colleague much to not fix this one. ;-) I was merely suggesting that setting the quirk bit for `don't ask for the compression page' could be automated, instead of depending it on some firmware revision (as i did by now). Iff the first mode select in saopen() fails, and that quirk bit ain't set already, set the bit, and retry the mode select. If you're lucky, it gets through, and you can remember it next time. > I'm kind of inclined to believe that if < SCSI2 that VPD info is very > likely not there (that's serial #). I also think so, and i remember one comment from Kenneth (or was it Justin, i eventually forgot) that they were seeking some solution like this (but there wasn't enough time left before 3.0R was due). -- 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 Thu Dec 10 11:51:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06483 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 11:51:21 -0800 (PST) (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 LAA06472 for ; Thu, 10 Dec 1998 11:51:16 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id UAA25173; Thu, 10 Dec 1998 20:51:03 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id UAA00711; Thu, 10 Dec 1998 20:47:05 +0100 (MET) (envelope-from j) Message-ID: <19981210204704.28265@uriah.heep.sax.de> Date: Thu, 10 Dec 1998 20:47:04 +0100 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Cc: spork Subject: Re: options FAILSAFE 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 spork on Thu, Dec 10, 1998 at 11:51:13AM -0500 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 spork wrote: > I've always wondered exactly what it does... Is it strictly a scsi thing > or does it touch other bits and pieces? LINT says it enables tag queueing > on the ncr. Does anyone know what else it does, and whether it does > anything if you're running CAM? It was intended to enable `most defensive' kernel parameters. It turned off tagged queuing in the NCR driver, since there used to be a number of disks like older HP drives that choked on tagged queuing even though they claimed to accept them. Since this is a show-stopper during installation, Stefan Esser once created this option. I don't remember it ever changing more than just this. I haven't read the CAM sources for the ncr driver, but would assume the option degraded to a no-op now. -- 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 Thu Dec 10 13:15:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18046 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 13:15:11 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from bigwoop.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18039 for ; Thu, 10 Dec 1998 13:15:08 -0800 (PST) (envelope-from conor@bigwoop.vicor-nb.com) Received: (from conor@localhost) by bigwoop.vicor-nb.com (8.8.5/8.7.3) id NAA04666; Thu, 10 Dec 1998 13:14:58 -0800 (PST) Date: Thu, 10 Dec 1998 13:14:58 -0800 (PST) From: Conor Dixon Message-Id: <199812102114.NAA04666@bigwoop.vicor-nb.com> To: julian@whistle.com, scsi@FreeBSD.ORG Subject: barracuda 4.3gig SCSI Cc: jason@idiom.com Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org yesterday you recieved mail about one of our SCSI disks which was misbehaving. Well jason took it to a place that recovers disks and they pronounced the drive irretrievably lost due to mechanical problems, so there was nothing FreeBSD coulda done to talk to it. thanks for your time and support Conor To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 10 14:21:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28315 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 14:21:19 -0800 (PST) (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 OAA28308 for ; Thu, 10 Dec 1998 14:21:18 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id PAA02711; Thu, 10 Dec 1998 15:13:26 -0700 (MST) Date: Thu, 10 Dec 1998 15:13:26 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199812102213.PAA02711@narnia.plutotech.com> To: mjacob@feral.com cc: scsi@FreeBSD.ORG Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: >> >> I think that's a good idea, and in fact we've been planning on doing it for >> a while. The idea is to add a SCSI revision field to the quirk entry >> format, and then just not send serial number requests to anything < 2. > > You don't need a quirk entry. You know what revisions the device is when > you do the initial inquiry. As long as there are no SCSI 1 devices that support that feature, sure, but I don't really know if this is the case for every SCSI I (or SCSI III) quirk or feature. The idea was to have a generic SCSI I devive quirk entry that disabled all likely "unimplemented in SCSI I" features, allowing you to add overriding entries for more advanced SCSI I devices. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 10 14:23:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA28814 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 14:23:22 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA28809 for ; Thu, 10 Dec 1998 14:23:20 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id OAA00718; Thu, 10 Dec 1998 14:23:11 -0800 Date: Thu, 10 Dec 1998 14:23:11 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R In-Reply-To: <199812102213.PAA02711@narnia.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 If it prior to CCS, it won't have VPD info. I really don't follow what the quirk is supposed to accomplish. On Thu, 10 Dec 1998, Justin T. Gibbs wrote: > In article you wrote: > >> > >> I think that's a good idea, and in fact we've been planning on doing it for > >> a while. The idea is to add a SCSI revision field to the quirk entry > >> format, and then just not send serial number requests to anything < 2. > > > > You don't need a quirk entry. You know what revisions the device is when > > you do the initial inquiry. > > As long as there are no SCSI 1 devices that support that feature, > sure, but I don't really know if this is the case for every SCSI > I (or SCSI III) quirk or feature. The idea was to have a generic > SCSI I devive quirk entry that disabled all likely "unimplemented > in SCSI I" features, allowing you to add overriding entries for > more advanced SCSI I devices. > > -- > Justin > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 10 14:31:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA29875 for freebsd-scsi-outgoing; Thu, 10 Dec 1998 14:31:10 -0800 (PST) (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 OAA29862 for ; Thu, 10 Dec 1998 14:31:05 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id PAA14426; Thu, 10 Dec 1998 15:30:55 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199812102230.PAA14426@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: mjacob@feral.com cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R In-reply-to: Your message of "Thu, 10 Dec 1998 14:23:11 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 10 Dec 1998 15:23:13 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > >If it prior to CCS, it won't have VPD info. > >I really don't follow what the quirk is supposed to accomplish. The quirks would remain 'Don't fetch the compression page' or 'Don't get VPD info', or whatever. The proposed change is that the inquiry quirk matching function allows you to specify the revision of the device to match so you can add a 'default SCSI I quirk entry' or a 'default SCSI III' quirk table entry. That way, instead of hard coding places in the code based on device revision, you continue to operate based on device 'feature' or 'quirk'. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 06:28:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA11462 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 06:28:56 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ninbox.ml.org (hsv1-96.airnet.net [207.242.81.96]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA11457 for ; Fri, 11 Dec 1998 06:28:53 -0800 (PST) (envelope-from kris@airnet.net) Received: from airnet.net (localhost [127.0.0.1]) by ninbox.ml.org (8.9.1/8.8.5) with ESMTP id IAA06815; Fri, 11 Dec 1998 08:28:34 -0600 (CST) Message-ID: <36712C12.54EF6F96@airnet.net> Date: Fri, 11 Dec 1998 08:28:34 -0600 From: Kris Kirby Organization: Absolutely None! X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: "Kenneth D. Merry" CC: FreeBSD-SCSI@FreeBSD.ORG Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R References: <199812100254.TAA07368@panzer.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry wrote: > I assume you changed it so that it would work with your drive? Your > firmware revisions aren't the same, so the quirk entry wouldn't match your > drive without modificiation. The first time, no. But then I got to looking at it and noticed I was running a different revision. I changed it, and no change. I somehow think the problem is not FreeBSD and serial numbers, but tar sure doesn't like the drive. mt will rewind and erase (I think). I suddenly get the feeling I have blamed the problem on the wrong part. Am still going to upgrade the firmware after finals (next week). -- Kris Kirby UAH Mail UAH CS Home WWW ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 08:33:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA26187 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 08:33:17 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26177 for ; Fri, 11 Dec 1998 08:33:14 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id IAA03565; Fri, 11 Dec 1998 08:32:42 -0800 Date: Fri, 11 Dec 1998 08:32:42 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Kris Kirby cc: "Kenneth D. Merry" , FreeBSD-SCSI@FreeBSD.ORG Subject: Re: Tandberg TDC 3600 on CAM, 3.0-R In-Reply-To: <36712C12.54EF6F96@airnet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It just smacked me in the head- I just committed a fix last night which may fix this (QIC == FIXED BLOCKS)- please try this today... On Fri, 11 Dec 1998, Kris Kirby wrote: > Kenneth D. Merry wrote: > > I assume you changed it so that it would work with your drive? Your > > firmware revisions aren't the same, so the quirk entry wouldn't match your > > drive without modificiation. > > The first time, no. But then I got to looking at it and noticed I was > running a different revision. I changed it, and no change. I somehow > think the problem is not FreeBSD and serial numbers, but tar sure > doesn't like the drive. mt will rewind and erase (I think). I suddenly > get the feeling I have blamed the problem on the wrong part. Am still > going to upgrade the firmware after finals (next week). > -- > Kris Kirby > UAH Mail UAH CS > Home WWW > ------------------------------------------- > TGIFreeBSD... 'Nuff said. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 10:15:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06935 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 10:15:26 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA06929 for ; Fri, 11 Dec 1998 10:15:23 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.9.1/8.8.8) id LAA22126 for freebsd-scsi@freebsd.org; Fri, 11 Dec 1998 11:56:04 -0500 (EST) (envelope-from larry) Date: Fri, 11 Dec 1998 11:56:04 -0500 From: "Larry S. Marso" To: freebsd-scsi@FreeBSD.ORG Subject: cd write failure Message-ID: <19981211115604.C21942@marso.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.13i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I get the following cd write failures writing at speeds above 1x on a Yamaha 4260 with max 4x write speed: After such an error, the cdr is ruined. This outcome does *not* occur immediately after rebooting the system. But after writing just one time, it begins (and seems to get worse). Eventually, even 1x has created this error. I'm using CAM 3.0-R aout. Best regards -- Larry S. Marso larry@marso.com Device seems to be: Generic mmc CD-RW. Using generic SCSI-3/mmc CD-R driver (mmc_cdr). Driver flags : SWABAUDIO cdrecord: Undefined error: 0. WARNING: RR-scheduler not available, disabling. Starting to write CD/DVD at speed 4 in write mode for multi session. Last chance to quit, starting real write in 1 seconds. cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error CDB: 2A 00 00 00 00 00 00 00 1F 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 04 D1 D9 00 00 0A 00 00 00 00 09 01 00 00 00 00 00 00 00 08 00 00 00 00 00 00 08 00 01 06 Sense Key: 0x4 Hardware Error, Segment 0 Sense Code: 0x09 Qual 0x01 (tracking servo failure) Fru 0x0 Sense flags: Blk -774307840 (not valid) resid: 63488 cmd finished after 14.068s timeout 40s write track data: error after 0 bytes Sense Bytes: 70 00 00 00 00 00 00 0A 00 00 00 00 00 00 00 00 00 00 cdrecord: Input/output error. close track/session: scsi sendcmd: retryable error CDB: 5B 00 02 00 00 00 00 00 00 00 status: 0x2 (CHECK CONDITION) Sense Bytes: 70 00 05 00 00 00 00 0A 00 00 00 00 2C 04 00 00 00 00 00 00 00 08 00 00 00 00 00 00 08 00 01 06 Sense Key: 0x5 Illegal Request, Segment 0 Sense Code: 0x2C Qual 0x04 (current program area is empty) Fru 0x0 Sense flags: Blk 0 (not valid) cmd finished after 0.003s timeout 480s To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 10:15:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA06964 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 10:15:32 -0800 (PST) (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 KAA06948 for ; Fri, 11 Dec 1998 10:15:29 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id LAA04613; Fri, 11 Dec 1998 11:07:29 -0700 (MST) Date: Fri, 11 Dec 1998 11:07:29 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199812111807.LAA04613@narnia.plutotech.com> To: Tom Wadlow cc: scsi@FreeBSD.ORG Subject: Re: A problem with SCSI X-Newsgroups: pluto.freebsd.hackers In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > > I built a system on 3.0-RELEASE, with a SCSI disk. This is a SCSI issue. Message moved to the appropriate list. > occasionally, the da driver says: "Invalidating pack", and drops > the disk offline and everything hangs. This is unfortunate. Certainly is. What kind of hardware are you using (SCSI controller, devices on the bus, CPU, etc.)? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 11:15:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA14181 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 11:15:44 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail-oak-1.pilot.net (mail-oak-1.pilot.net [198.232.147.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA14176 for ; Fri, 11 Dec 1998 11:15:42 -0800 (PST) (envelope-from wadlow@pilot.net) Received: from corsair.pilot.net (corsair.pilot.net [204.48.17.12]) by mail-oak-1.pilot.net with ESMTP id LAA08844; Fri, 11 Dec 1998 11:15:33 -0800 (PST) Received: from arrow.pilot.net (arrow.pilot.net [204.48.17.29]) by corsair.pilot.net with ESMTP id LAA01932; Fri, 11 Dec 1998 11:15:27 -0800 (PST) Received: from localhost (wadlow@localhost) by arrow.pilot.net (arrow) with ESMTP id LAA06452; Fri, 11 Dec 1998 11:15:27 -0800 (PST) Date: Fri, 11 Dec 1998 11:15:26 -0800 (PST) From: Tom Wadlow To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG Subject: Re: A problem with SCSI In-Reply-To: <199812111807.LAA04613@narnia.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 > Date: Fri, 11 Dec 1998 11:07:29 -0700 (MST) > From: Justin T. Gibbs > Subject: Re: A problem with SCSI > > > occasionally, the da driver says: "Invalidating pack", and drops > > the disk offline and everything hangs. This is unfortunate. > > Certainly is. What kind of hardware are you using (SCSI controller, > devices on the bus, CPU, etc.)? I've built out several systems from 3.0-RELEASE that all seeem to manifest this problem. Two die on a regular basis. The third gets strange messsages but seems to stay up. Machines dying with "Invalidating pack" A) Pentium 100MHz 64MB RAM BusLogic 496 SCSI controller 4GB Connor SCSI (only device on the SCSI chain) Ethernet Floppy B) Pentium 120MHz 96MB RAM BusLogic 496 SCSI controller 1GB Connor SCSI (only device on the SCSI chain) Ethernet Floppy Machine with strange messages: Pentium II 330 MHz 128MB RAM HP SCSI CDROM Seagate 4GB SCSI (boot device) Seagate 9GB SCSI Ethernet The strange messages this machine is getting look like this: (da0:ahc0:0:0:0): tagged openings now 64 (da0:ahc0:0:0:0): tagged openings now 63 (da1:ahc0:0:1:0): tagged openings now 64 (da1:ahc0:0:1:0): tagged openings now 63 (da1:ahc0:0:1:0): tagged openings now 62 (da1:ahc0:0:1:0): tagged openings now 61 (da1:ahc0:0:1:0): tagged openings now 60 (da1:ahc0:0:1:0): tagged openings now 59 (da1:ahc0:0:1:0): tagged openings now 58 (da1:ahc0:0:1:0): tagged openings now 57 (da1:ahc0:0:1:0): tagged openings now 56 (da1:ahc0:0:1:0): tagged openings now 55 (da1:ahc0:0:1:0): tagged openings now 54 (da1:ahc0:0:1:0): tagged openings now 53 (da1:ahc0:0:1:0): tagged openings now 52 (da1:ahc0:0:1:0): tagged openings now 51 (da1:ahc0:0:1:0): tagged openings now 50 (da1:ahc0:0:1:0): tagged openings now 49 but it hasn't crashed yet. Which is good, as this is my primary workstation. Machine B above has been updated to 3.0-CURRENT (as of last night), but still exhibits the problem. All are running the GENERIC kernel. --Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 11:57:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA19480 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 11:57:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA19468 for ; Fri, 11 Dec 1998 11:57:51 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id MAA17481; Fri, 11 Dec 1998 12:57:30 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812111957.MAA17481@panzer.plutotech.com> Subject: Re: cd write failure In-Reply-To: <19981211115604.C21942@marso.com> from "Larry S. Marso" at "Dec 11, 98 11:56:04 am" To: larry@marso.com (Larry S. Marso) Date: Fri, 11 Dec 1998 12:57:29 -0700 (MST) 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 Larry S. Marso wrote... > I get the following cd write failures writing at speeds above 1x on a > Yamaha 4260 with max 4x write speed: > > After such an error, the cdr is ruined. > > This outcome does *not* occur immediately after rebooting the system. But > after writing just one time, it begins (and seems to get worse). > Eventually, even 1x has created this error. > > I'm using CAM 3.0-R aout. Well, here's your problem: > Device seems to be: Generic mmc CD-RW. > Using generic SCSI-3/mmc CD-R driver (mmc_cdr). > Driver flags : SWABAUDIO > cdrecord: Undefined error: 0. WARNING: RR-scheduler not available, > disabling. > Starting to write CD/DVD at speed 4 in write mode for multi session. > Last chance to quit, starting real write in 1 seconds. > cdrecord: Input/output error. write_g1: scsi sendcmd: retryable error > CDB: 2A 00 00 00 00 00 00 00 1F 00 > status: 0x2 (CHECK CONDITION) > Sense Bytes: 70 00 04 D1 D9 00 00 0A 00 00 00 00 09 01 00 00 00 00 00 00 00 > 08 00 00 00 00 00 00 08 00 01 06 > Sense Key: 0x4 Hardware Error, Segment 0 > Sense Code: 0x09 Qual 0x01 (tracking servo failure) Fru 0x0 > Sense flags: Blk -774307840 (not valid) > resid: 63488 > cmd finished after 14.068s timeout 40s > write track data: error after 0 bytes You got a hardware error. Specifically, it's a "Tracking servo failure". This is probably not a CAM problem, but most likely a problem with your drive. I suggest that you: 1. Contact Joerg Schilling , the author of cdrecord. He may know of specific issues with that drive that would cause it to spit out the above error. 2. Contact Yamaha tech support, and see what they say about it. 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 Fri Dec 11 12:02:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA20303 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 12:02:51 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA20153 for ; Fri, 11 Dec 1998 12:02:46 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id PAA10961; Fri, 11 Dec 1998 15:02:37 -0500 (EST) Date: Fri, 11 Dec 1998 15:02:37 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: freebsd-scsi@FreeBSD.ORG Subject: CAM and -stable 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 Hi, I'm about to put two new machines in production, and they're both "core" machines; main dns/auth/mail and a shell machine. Currently the machines we use in this capacity are 2.1.7.1, and it's been very stable. Now the new machines share a RAID array hung off of a CMD CRD-5440. I patched our usual build (980825 -stable) with the July CAM patchkit, as the existing AHC driver couldn't detect any LUNs beyond the first one. All has been well so far, I've tried to stress the machines as much as possible by running some disk benchmarks over and over, but yesterday one locked up (console frozen) with the following messages being the last thing on the console: Dec 10 18:13:15 shell /kernel: (da0:ahc0:0:0:0): SCB 0x1e - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 Dec 10 18:13:18 shell /kernel: SEQADDR == 0xa Dec 10 18:13:18 shell /kernel: SSTAT1 == 0xb Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Dec 10 18:13:18 shell /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 34b Dec 10 18:13:18 shell /kernel: ahc0: Bus Device Reset Sent. 2 SCBs aborted I had to give it a hard reset at this point. So my questions are: Is this a known issue? Does it point to a possible hardware problem? Will there be a newer cam patchkit for -stable? I don't think it's a cabling issue, as this is the first I've seen of any anomolies with the scsi subsystem, and the only cabling in question here is a high quality 2' external UW scsi cable from the back of this machine to the RAID array. The other machine that uses the other host port on the RAID array remained functional during this glitch... Any ideas? I was very comfortable with CAM before, but now I'm a little nervous about moving this into production. Would it be better to try and back out of the patches and use the ahc driver? Let me know if there's any other info needed. Following are the boot messages... Thanks, Charles Dec 10 19:27:32 shell /kernel: Copyright (c) 1992-1998 FreeBSD Inc. Dec 10 19:27:32 shell /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Dec 10 19:27:32 shell /kernel: The Regents of the University of California. All rights reserved. Dec 10 19:27:32 shell /kernel: Dec 10 19:27:32 shell /kernel: FreeBSD 2.2.7-19980825-SNAP #0: Thu Dec 10 12:02:45 EST 1998 Dec 10 19:27:32 shell /kernel: spork@shell.inch.com:/usr/src/sys/compile/SHELL Dec 10 19:27:32 shell /kernel: CPU: Pentium II (quarter-micron) (350.80-MHz 686-class CPU) Dec 10 19:27:32 shell /kernel: Origin = "GenuineIntel" Id = 0x651 Stepping=1 Dec 10 19:27:32 shell /kernel: Features=0x183f9ff,,MMX,> Dec 10 19:27:32 shell /kernel: real memory = 268435456 (262144K bytes) Dec 10 19:27:32 shell /kernel: avail memory = 261144576 (255024K bytes) Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 0: Dec 10 19:27:32 shell /kernel: chip0 rev 2 on pci0:0:0 Dec 10 19:27:32 shell /kernel: chip1 rev 2 on pci0:1:0 Dec 10 19:27:32 shell /kernel: chip2 rev 2 on pci0:4:0 Dec 10 19:27:32 shell /kernel: chip3 rev 1 on pci0:4:1 Dec 10 19:27:32 shell /kernel: chip4 rev 1 int d irq 12 on pci0:4:2 Dec 10 19:27:32 shell /kernel: chip5 rev 2 on pci0:4:3 Dec 10 19:27:32 shell /kernel: fxp0 rev 5 int a irq 10 on pci0:7:0 Dec 10 19:27:32 shell /kernel: fxp0: Ethernet address 00:e0:18:90:36:4d Dec 10 19:27:32 shell /kernel: ahc0 rev 1 int a irq 12 on pci0:9:0 Dec 10 19:27:32 shell /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Dec 10 19:27:32 shell /kernel: fxp1 rev 5 int a irq 10 on pci0:10:0 Dec 10 19:27:32 shell /kernel: fxp1: Ethernet address 00:a0:c9:e7:ac:7d Dec 10 19:27:32 shell /kernel: vga0 rev 211 int a irq 11 on pci0:11:0 Dec 10 19:27:32 shell /kernel: Probing for devices on PCI bus 1: Dec 10 19:27:32 shell /kernel: Probing for devices on the ISA bus: Dec 10 19:27:32 shell /kernel: sc0 at 0x60-0x6f irq 1 on motherboard Dec 10 19:27:32 shell /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Dec 10 19:27:32 shell /kernel: sio0 at 0x3f8-0x3ff irq 4 on isa Dec 10 19:27:32 shell /kernel: sio0: type 16550A Dec 10 19:27:32 shell /kernel: sio1 at 0x2f8-0x2ff irq 3 on isa Dec 10 19:27:32 shell /kernel: sio1: type 16550A Dec 10 19:27:32 shell /kernel: lpt0 at 0x378-0x37f irq 7 on isa Dec 10 19:27:32 shell /kernel: lpt0: Interrupt-driven port Dec 10 19:27:32 shell /kernel: lp0: TCP/IP capable interface Dec 10 19:27:32 shell /kernel: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Dec 10 19:27:32 shell /kernel: fdc0: FIFO enabled, 8 bytes threshold Dec 10 19:27:32 shell /kernel: fd0: 1.44MB 3.5in Dec 10 19:27:32 shell /kernel: npx0 flags 0x1 on motherboard Dec 10 19:27:32 shell /kernel: npx0: INT 16 interface Dec 10 19:27:32 shell /kernel: IP packet filtering initialized, divert enabled, logging limited to 200 packets/entry Dec 10 19:27:32 shell /kernel: da0 at ahc0 bus 0 target 0 lun 0 Dec 10 19:27:32 shell /kernel: da0: Fixed Direct Access SCSI2 device Dec 10 19:27:32 shell /kernel: da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled Dec 10 19:27:32 shell /kernel: da0: 6999MB (14335872 512 byte sectors: 64H 32S/T 6999C) Dec 10 19:27:32 shell /kernel: da1 at ahc0 bus 0 target 0 lun 1 Dec 10 19:27:32 shell /kernel: da1: Fixed Direct Access SCSI2 device Dec 10 19:27:32 shell /kernel: da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled Dec 10 19:27:32 shell /kernel: da1: 10431MB (21362688 512 byte sectors: 64H 32S/T 10431C) Dec 10 19:27:32 shell /kernel: WARNING: / was not properly dismounted. Dec 10 19:27:32 shell /kernel: nfs server 10.0.0.1:/var/mail: not responding Dec 10 19:27:32 shell savecore: no core dump --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 12:12:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA21515 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 12:12:24 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA21510 for ; Fri, 11 Dec 1998 12:12:22 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.9.1/8.8.8) id PAA22810 for freebsd-scsi@freebsd.org; Fri, 11 Dec 1998 15:13:43 -0500 (EST) (envelope-from larry) Date: Fri, 11 Dec 1998 15:13:43 -0500 From: "Larry S. Marso" To: freebsd-scsi@FreeBSD.ORG Subject: cdrecord and caching issue Message-ID: <19981211151343.B22555@marso.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.13i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I wrote a couple of trial cdrecord sessions using -dummy. I then executed a third, real cdrecord session. It failed (fortunately, before writing anything to the disk), complaining that "insufficient space left on media". I then executed a cdcontrol info, which reported that two previous sessions were already recorded to the disk. In actual fact, the disk was still blank; this I confirmed by shutting down and rebooting, then successfully writing to the cdr. So, there is some sort of caching going on that mistakenly thinks a -dummy write is a real write. Might this not cause trouble? Best regards -- Larry S. Marso larry@marso.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 12:33:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24553 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 12:33:56 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail-oak-1.pilot.net (mail-oak-1.pilot.net [198.232.147.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA24543 for ; Fri, 11 Dec 1998 12:33:54 -0800 (PST) (envelope-from wadlow@pilot.net) Received: from corsair.pilot.net (corsair.pilot.net [204.48.17.12]) by mail-oak-1.pilot.net with ESMTP id MAA28188; Fri, 11 Dec 1998 12:33:43 -0800 (PST) Received: from arrow.pilot.net (arrow.pilot.net [204.48.17.29]) by corsair.pilot.net with ESMTP id MAA05577; Fri, 11 Dec 1998 12:33:43 -0800 (PST) Received: from localhost (wadlow@localhost) by arrow.pilot.net (arrow) with ESMTP id MAA07200; Fri, 11 Dec 1998 12:33:42 -0800 (PST) Date: Fri, 11 Dec 1998 12:33:42 -0800 (PST) From: Tom Wadlow To: Matthew Jacob cc: scsi@FreeBSD.ORG Subject: Re: A problem with SCSI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The ones that crashed said "Invalidating pack" and then died. The "tagged" messages were coming from the one that didn't crash, but was doing things that seemed odd to me (i.e. generating these tagged messages was new behavior. Sounds like it was just debugging info and not anything to worry about from your description). Also, the one that didn't crash is using an Adaptec SCSI controller (sorry, I just noticed that I forgot to include that in my earlier message). --tom On Fri, 11 Dec 1998, Matthew Jacob wrote: > Date: Fri, 11 Dec 1998 11:50:09 -0800 (PST) > From: Matthew Jacob > To: Tom Wadlow > Cc: scsi@FreeBSD.ORG > Subject: Re: A problem with SCSI > > > Any other messages when it crashed? The 'tagged openings' message is just > the process of throttling down the # of cmds outstanding per device.. > > > On Fri, 11 Dec 1998, Tom Wadlow wrote: > > > > > > Date: Fri, 11 Dec 1998 11:07:29 -0700 (MST) > > > From: Justin T. Gibbs > > > Subject: Re: A problem with SCSI > > > > > > > occasionally, the da driver says: "Invalidating pack", and drops > > > > the disk offline and everything hangs. This is unfortunate. > > > > > > Certainly is. What kind of hardware are you using (SCSI controller, > > > devices on the bus, CPU, etc.)? > > > > I've built out several systems from 3.0-RELEASE that all seeem to manifest this problem. > > Two die on a regular basis. The third gets strange messsages but seems to stay up. > > > > Machines dying with "Invalidating pack" > > A) Pentium 100MHz > > 64MB RAM > > BusLogic 496 SCSI controller > > 4GB Connor SCSI (only device on the SCSI chain) > > Ethernet > > Floppy > > > > B) Pentium 120MHz > > 96MB RAM > > BusLogic 496 SCSI controller > > 1GB Connor SCSI (only device on the SCSI chain) > > Ethernet > > Floppy > > > > Machine with strange messages: > > Pentium II 330 MHz > > 128MB RAM > > HP SCSI CDROM > > Seagate 4GB SCSI (boot device) > > Seagate 9GB SCSI > > Ethernet > > > > The strange messages this machine is getting look like this: > > > > (da0:ahc0:0:0:0): tagged openings now 64 > > (da0:ahc0:0:0:0): tagged openings now 63 > > (da1:ahc0:0:1:0): tagged openings now 64 > > (da1:ahc0:0:1:0): tagged openings now 63 > > (da1:ahc0:0:1:0): tagged openings now 62 > > (da1:ahc0:0:1:0): tagged openings now 61 > > (da1:ahc0:0:1:0): tagged openings now 60 > > (da1:ahc0:0:1:0): tagged openings now 59 > > (da1:ahc0:0:1:0): tagged openings now 58 > > (da1:ahc0:0:1:0): tagged openings now 57 > > (da1:ahc0:0:1:0): tagged openings now 56 > > (da1:ahc0:0:1:0): tagged openings now 55 > > (da1:ahc0:0:1:0): tagged openings now 54 > > (da1:ahc0:0:1:0): tagged openings now 53 > > (da1:ahc0:0:1:0): tagged openings now 52 > > (da1:ahc0:0:1:0): tagged openings now 51 > > (da1:ahc0:0:1:0): tagged openings now 50 > > (da1:ahc0:0:1:0): tagged openings now 49 > > > > but it hasn't crashed yet. Which is good, as this is my primary workstation. > > > > Machine B above has been updated to 3.0-CURRENT (as of last night), but still exhibits the > > problem. All are running the GENERIC kernel. > > > > --Tom > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 12:40:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25381 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 12:40:27 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25371 for ; Fri, 11 Dec 1998 12:40:24 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id MAA04384; Fri, 11 Dec 1998 12:40:00 -0800 Date: Fri, 11 Dec 1998 12:39:59 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Tom Wadlow cc: scsi@FreeBSD.ORG Subject: Re: A problem with SCSI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Invalidating pack can come about if a there's a I/O error on that drive. That's what we're trying to gather info about. On Fri, 11 Dec 1998, Tom Wadlow wrote: > The ones that crashed said "Invalidating pack" and then died. The "tagged" messages were > coming from the one that didn't crash, but was doing things that seemed odd to me (i.e. > generating these tagged messages was new behavior. Sounds like it was just debugging info > and not anything to worry about from your description). > > Also, the one that didn't crash is using an Adaptec SCSI controller (sorry, I just noticed > that I forgot to include that in my earlier message). > > --tom > > On Fri, 11 Dec 1998, Matthew Jacob wrote: > > > Date: Fri, 11 Dec 1998 11:50:09 -0800 (PST) > > From: Matthew Jacob > > To: Tom Wadlow > > Cc: scsi@FreeBSD.ORG > > Subject: Re: A problem with SCSI > > > > > > Any other messages when it crashed? The 'tagged openings' message is just > > the process of throttling down the # of cmds outstanding per device.. > > > > > > On Fri, 11 Dec 1998, Tom Wadlow wrote: > > > > > > > > > Date: Fri, 11 Dec 1998 11:07:29 -0700 (MST) > > > > From: Justin T. Gibbs > > > > Subject: Re: A problem with SCSI > > > > > > > > > occasionally, the da driver says: "Invalidating pack", and drops > > > > > the disk offline and everything hangs. This is unfortunate. > > > > > > > > Certainly is. What kind of hardware are you using (SCSI controller, > > > > devices on the bus, CPU, etc.)? > > > > > > I've built out several systems from 3.0-RELEASE that all seeem to manifest this problem. > > > Two die on a regular basis. The third gets strange messsages but seems to stay up. > > > > > > Machines dying with "Invalidating pack" > > > A) Pentium 100MHz > > > 64MB RAM > > > BusLogic 496 SCSI controller > > > 4GB Connor SCSI (only device on the SCSI chain) > > > Ethernet > > > Floppy > > > > > > B) Pentium 120MHz > > > 96MB RAM > > > BusLogic 496 SCSI controller > > > 1GB Connor SCSI (only device on the SCSI chain) > > > Ethernet > > > Floppy > > > > > > Machine with strange messages: > > > Pentium II 330 MHz > > > 128MB RAM > > > HP SCSI CDROM > > > Seagate 4GB SCSI (boot device) > > > Seagate 9GB SCSI > > > Ethernet > > > > > > The strange messages this machine is getting look like this: > > > > > > (da0:ahc0:0:0:0): tagged openings now 64 > > > (da0:ahc0:0:0:0): tagged openings now 63 > > > (da1:ahc0:0:1:0): tagged openings now 64 > > > (da1:ahc0:0:1:0): tagged openings now 63 > > > (da1:ahc0:0:1:0): tagged openings now 62 > > > (da1:ahc0:0:1:0): tagged openings now 61 > > > (da1:ahc0:0:1:0): tagged openings now 60 > > > (da1:ahc0:0:1:0): tagged openings now 59 > > > (da1:ahc0:0:1:0): tagged openings now 58 > > > (da1:ahc0:0:1:0): tagged openings now 57 > > > (da1:ahc0:0:1:0): tagged openings now 56 > > > (da1:ahc0:0:1:0): tagged openings now 55 > > > (da1:ahc0:0:1:0): tagged openings now 54 > > > (da1:ahc0:0:1:0): tagged openings now 53 > > > (da1:ahc0:0:1:0): tagged openings now 52 > > > (da1:ahc0:0:1:0): tagged openings now 51 > > > (da1:ahc0:0:1:0): tagged openings now 50 > > > (da1:ahc0:0:1:0): tagged openings now 49 > > > > > > but it hasn't crashed yet. Which is good, as this is my primary workstation. > > > > > > Machine B above has been updated to 3.0-CURRENT (as of last night), but still exhibits the > > > problem. All are running the GENERIC kernel. > > > > > > --Tom > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > with "unsubscribe freebsd-scsi" in the body of the message > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 12:41:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25490 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 12:41:36 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25481 for ; Fri, 11 Dec 1998 12:41:34 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id LAA04242; Fri, 11 Dec 1998 11:50:09 -0800 Date: Fri, 11 Dec 1998 11:50:09 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Tom Wadlow cc: scsi@FreeBSD.ORG Subject: Re: A problem with SCSI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Any other messages when it crashed? The 'tagged openings' message is just the process of throttling down the # of cmds outstanding per device.. On Fri, 11 Dec 1998, Tom Wadlow wrote: > > > Date: Fri, 11 Dec 1998 11:07:29 -0700 (MST) > > From: Justin T. Gibbs > > Subject: Re: A problem with SCSI > > > > > occasionally, the da driver says: "Invalidating pack", and drops > > > the disk offline and everything hangs. This is unfortunate. > > > > Certainly is. What kind of hardware are you using (SCSI controller, > > devices on the bus, CPU, etc.)? > > I've built out several systems from 3.0-RELEASE that all seeem to manifest this problem. > Two die on a regular basis. The third gets strange messsages but seems to stay up. > > Machines dying with "Invalidating pack" > A) Pentium 100MHz > 64MB RAM > BusLogic 496 SCSI controller > 4GB Connor SCSI (only device on the SCSI chain) > Ethernet > Floppy > > B) Pentium 120MHz > 96MB RAM > BusLogic 496 SCSI controller > 1GB Connor SCSI (only device on the SCSI chain) > Ethernet > Floppy > > Machine with strange messages: > Pentium II 330 MHz > 128MB RAM > HP SCSI CDROM > Seagate 4GB SCSI (boot device) > Seagate 9GB SCSI > Ethernet > > The strange messages this machine is getting look like this: > > (da0:ahc0:0:0:0): tagged openings now 64 > (da0:ahc0:0:0:0): tagged openings now 63 > (da1:ahc0:0:1:0): tagged openings now 64 > (da1:ahc0:0:1:0): tagged openings now 63 > (da1:ahc0:0:1:0): tagged openings now 62 > (da1:ahc0:0:1:0): tagged openings now 61 > (da1:ahc0:0:1:0): tagged openings now 60 > (da1:ahc0:0:1:0): tagged openings now 59 > (da1:ahc0:0:1:0): tagged openings now 58 > (da1:ahc0:0:1:0): tagged openings now 57 > (da1:ahc0:0:1:0): tagged openings now 56 > (da1:ahc0:0:1:0): tagged openings now 55 > (da1:ahc0:0:1:0): tagged openings now 54 > (da1:ahc0:0:1:0): tagged openings now 53 > (da1:ahc0:0:1:0): tagged openings now 52 > (da1:ahc0:0:1:0): tagged openings now 51 > (da1:ahc0:0:1:0): tagged openings now 50 > (da1:ahc0:0:1:0): tagged openings now 49 > > but it hasn't crashed yet. Which is good, as this is my primary workstation. > > Machine B above has been updated to 3.0-CURRENT (as of last night), but still exhibits the > problem. All are running the GENERIC kernel. > > --Tom > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 12:47:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26703 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 12:47:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26671 for ; Fri, 11 Dec 1998 12:47:51 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id NAA17849; Fri, 11 Dec 1998 13:47:39 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812112047.NAA17849@panzer.plutotech.com> Subject: Re: cdrecord and caching issue In-Reply-To: <19981211151343.B22555@marso.com> from "Larry S. Marso" at "Dec 11, 98 03:13:43 pm" To: larry@marso.com (Larry S. Marso) Date: Fri, 11 Dec 1998 13:47:38 -0700 (MST) 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 Larry S. Marso wrote... > I wrote a couple of trial cdrecord sessions using -dummy. > > I then executed a third, real cdrecord session. It failed (fortunately, > before writing anything to the disk), complaining that "insufficient space > left on media". > > I then executed a cdcontrol info, which reported that two previous sessions > were already recorded to the disk. In actual fact, the disk was still > blank; this I confirmed by shutting down and rebooting, then successfully > writing to the cdr. > > So, there is some sort of caching going on that mistakenly thinks a -dummy > write is a real write. Might this not cause trouble? If there is caching going on, it is by the drive, not by the SCSI layer. The information you get from cdcontrol is what it gets from the CD driver via an ioctl. That information is obtained directly from the drive via SCSI commands. It could be that the drive saves some state to pretend that the dummy "write" actually succeeded. One way you might try to erase the state is by ejecting the CD and then put it back in. That should invalidate any previous state the drive cached about the disk. 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 Fri Dec 11 12:52:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27427 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 12:52:09 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail-oak-1.pilot.net (mail-oak-1.pilot.net [198.232.147.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27419 for ; Fri, 11 Dec 1998 12:52:07 -0800 (PST) (envelope-from wadlow@pilot.net) Received: from corsair.pilot.net (corsair.pilot.net [204.48.17.12]) by mail-oak-1.pilot.net with ESMTP id MAA07615; Fri, 11 Dec 1998 12:51:58 -0800 (PST) Received: from arrow.pilot.net (arrow.pilot.net [204.48.17.29]) by corsair.pilot.net with ESMTP id MAA06284; Fri, 11 Dec 1998 12:51:56 -0800 (PST) Received: from localhost (wadlow@localhost) by arrow.pilot.net (arrow) with ESMTP id MAA07294; Fri, 11 Dec 1998 12:51:55 -0800 (PST) Date: Fri, 11 Dec 1998 12:51:55 -0800 (PST) From: Tom Wadlow To: Matthew Jacob cc: scsi@FreeBSD.ORG Subject: Re: A problem with SCSI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Unfortunately, I can't force the problem to occur. I don't remember anything else with "Invalidating pack", and nothing was recorded in the log files (no big surprise there, if the disk is not writeable), but I will keep an eye out and see if I can spot something else the next time it occurs. --Tom On Fri, 11 Dec 1998, Matthew Jacob wrote: > Date: Fri, 11 Dec 1998 12:39:59 -0800 (PST) > From: Matthew Jacob > To: Tom Wadlow > Cc: scsi@FreeBSD.ORG > Subject: Re: A problem with SCSI > > > Invalidating pack can come about if a there's a I/O error on that drive. > That's what we're trying to gather info about. > > On Fri, 11 Dec 1998, Tom Wadlow wrote: > > > The ones that crashed said "Invalidating pack" and then died. The "tagged" messages were > > coming from the one that didn't crash, but was doing things that seemed odd to me (i.e. > > generating these tagged messages was new behavior. Sounds like it was just debugging info > > and not anything to worry about from your description). > > > > Also, the one that didn't crash is using an Adaptec SCSI controller (sorry, I just noticed > > that I forgot to include that in my earlier message). > > > > --tom > > > > On Fri, 11 Dec 1998, Matthew Jacob wrote: > > > > > Date: Fri, 11 Dec 1998 11:50:09 -0800 (PST) > > > From: Matthew Jacob > > > To: Tom Wadlow > > > Cc: scsi@FreeBSD.ORG > > > Subject: Re: A problem with SCSI > > > > > > > > > Any other messages when it crashed? The 'tagged openings' message is just > > > the process of throttling down the # of cmds outstanding per device.. > > > > > > > > > On Fri, 11 Dec 1998, Tom Wadlow wrote: > > > > > > > > > > > > Date: Fri, 11 Dec 1998 11:07:29 -0700 (MST) > > > > > From: Justin T. Gibbs > > > > > Subject: Re: A problem with SCSI > > > > > > > > > > > occasionally, the da driver says: "Invalidating pack", and drops > > > > > > the disk offline and everything hangs. This is unfortunate. > > > > > > > > > > Certainly is. What kind of hardware are you using (SCSI controller, > > > > > devices on the bus, CPU, etc.)? > > > > > > > > I've built out several systems from 3.0-RELEASE that all seeem to manifest this problem. > > > > Two die on a regular basis. The third gets strange messsages but seems to stay up. > > > > > > > > Machines dying with "Invalidating pack" > > > > A) Pentium 100MHz > > > > 64MB RAM > > > > BusLogic 496 SCSI controller > > > > 4GB Connor SCSI (only device on the SCSI chain) > > > > Ethernet > > > > Floppy > > > > > > > > B) Pentium 120MHz > > > > 96MB RAM > > > > BusLogic 496 SCSI controller > > > > 1GB Connor SCSI (only device on the SCSI chain) > > > > Ethernet > > > > Floppy > > > > > > > > Machine with strange messages: > > > > Pentium II 330 MHz > > > > 128MB RAM > > > > HP SCSI CDROM > > > > Seagate 4GB SCSI (boot device) > > > > Seagate 9GB SCSI > > > > Ethernet > > > > > > > > The strange messages this machine is getting look like this: > > > > > > > > (da0:ahc0:0:0:0): tagged openings now 64 > > > > (da0:ahc0:0:0:0): tagged openings now 63 > > > > (da1:ahc0:0:1:0): tagged openings now 64 > > > > (da1:ahc0:0:1:0): tagged openings now 63 > > > > (da1:ahc0:0:1:0): tagged openings now 62 > > > > (da1:ahc0:0:1:0): tagged openings now 61 > > > > (da1:ahc0:0:1:0): tagged openings now 60 > > > > (da1:ahc0:0:1:0): tagged openings now 59 > > > > (da1:ahc0:0:1:0): tagged openings now 58 > > > > (da1:ahc0:0:1:0): tagged openings now 57 > > > > (da1:ahc0:0:1:0): tagged openings now 56 > > > > (da1:ahc0:0:1:0): tagged openings now 55 > > > > (da1:ahc0:0:1:0): tagged openings now 54 > > > > (da1:ahc0:0:1:0): tagged openings now 53 > > > > (da1:ahc0:0:1:0): tagged openings now 52 > > > > (da1:ahc0:0:1:0): tagged openings now 51 > > > > (da1:ahc0:0:1:0): tagged openings now 50 > > > > (da1:ahc0:0:1:0): tagged openings now 49 > > > > > > > > but it hasn't crashed yet. Which is good, as this is my primary workstation. > > > > > > > > Machine B above has been updated to 3.0-CURRENT (as of last night), but still exhibits the > > > > problem. All are running the GENERIC kernel. > > > > > > > > --Tom > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-scsi" in the body of the message > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 13:10:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00298 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 13:10:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail-oak-1.pilot.net (mail-oak-1.pilot.net [198.232.147.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00288 for ; Fri, 11 Dec 1998 13:10:09 -0800 (PST) (envelope-from wadlow@pilot.net) Received: from corsair.pilot.net (corsair.pilot.net [204.48.17.12]) by mail-oak-1.pilot.net with ESMTP id NAA17642; Fri, 11 Dec 1998 13:10:00 -0800 (PST) Received: from arrow.pilot.net (arrow.pilot.net [204.48.17.29]) by corsair.pilot.net with ESMTP id NAA07125; Fri, 11 Dec 1998 13:09:59 -0800 (PST) Received: from localhost (wadlow@localhost) by arrow.pilot.net (arrow) with ESMTP id NAA07334; Fri, 11 Dec 1998 13:09:59 -0800 (PST) Date: Fri, 11 Dec 1998 13:09:58 -0800 (PST) From: Tom Wadlow To: Matthew Jacob cc: scsi@FreeBSD.ORG Subject: Re: A problem with SCSI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org One more bit of info about this that I just discovered. I had installed 3.0-RELEASE on the A machine below, and it was dying occasionally with the "Invalidating pack" problem. Same thing for the B machine. So just now, in an attempt to build a stable platform, I tried to install 2.2.8-RELEASE on the A machine, and discovered that the 2.2.8 boot floppy cannot see the BusLogic SCSI controller, whereas the the 3.0 boot floppy can. So that seems to imply that the SCSI driver code has been updated in ways relevant to this problem between the 2 and 3 releases. --Tom On Fri, 11 Dec 1998, Matthew Jacob wrote: > Date: Fri, 11 Dec 1998 12:39:59 -0800 (PST) > From: Matthew Jacob > To: Tom Wadlow > Cc: scsi@FreeBSD.ORG > Subject: Re: A problem with SCSI > > > Invalidating pack can come about if a there's a I/O error on that drive. > That's what we're trying to gather info about. > > On Fri, 11 Dec 1998, Tom Wadlow wrote: > > > The ones that crashed said "Invalidating pack" and then died. The "tagged" messages were > > coming from the one that didn't crash, but was doing things that seemed odd to me (i.e. > > generating these tagged messages was new behavior. Sounds like it was just debugging info > > and not anything to worry about from your description). > > > > Also, the one that didn't crash is using an Adaptec SCSI controller (sorry, I just noticed > > that I forgot to include that in my earlier message). > > > > --tom > > > > On Fri, 11 Dec 1998, Matthew Jacob wrote: > > > > > Date: Fri, 11 Dec 1998 11:50:09 -0800 (PST) > > > From: Matthew Jacob > > > To: Tom Wadlow > > > Cc: scsi@FreeBSD.ORG > > > Subject: Re: A problem with SCSI > > > > > > > > > Any other messages when it crashed? The 'tagged openings' message is just > > > the process of throttling down the # of cmds outstanding per device.. > > > > > > > > > On Fri, 11 Dec 1998, Tom Wadlow wrote: > > > > > > > > > > > > Date: Fri, 11 Dec 1998 11:07:29 -0700 (MST) > > > > > From: Justin T. Gibbs > > > > > Subject: Re: A problem with SCSI > > > > > > > > > > > occasionally, the da driver says: "Invalidating pack", and drops > > > > > > the disk offline and everything hangs. This is unfortunate. > > > > > > > > > > Certainly is. What kind of hardware are you using (SCSI controller, > > > > > devices on the bus, CPU, etc.)? > > > > > > > > I've built out several systems from 3.0-RELEASE that all seeem to manifest this problem. > > > > Two die on a regular basis. The third gets strange messsages but seems to stay up. > > > > > > > > Machines dying with "Invalidating pack" > > > > A) Pentium 100MHz > > > > 64MB RAM > > > > BusLogic 496 SCSI controller > > > > 4GB Connor SCSI (only device on the SCSI chain) > > > > Ethernet > > > > Floppy > > > > > > > > B) Pentium 120MHz > > > > 96MB RAM > > > > BusLogic 496 SCSI controller > > > > 1GB Connor SCSI (only device on the SCSI chain) > > > > Ethernet > > > > Floppy > > > > > > > > Machine with strange messages: > > > > Pentium II 330 MHz > > > > 128MB RAM > > > > HP SCSI CDROM > > > > Seagate 4GB SCSI (boot device) > > > > Seagate 9GB SCSI > > > > Ethernet > > > > > > > > The strange messages this machine is getting look like this: > > > > > > > > (da0:ahc0:0:0:0): tagged openings now 64 > > > > (da0:ahc0:0:0:0): tagged openings now 63 > > > > (da1:ahc0:0:1:0): tagged openings now 64 > > > > (da1:ahc0:0:1:0): tagged openings now 63 > > > > (da1:ahc0:0:1:0): tagged openings now 62 > > > > (da1:ahc0:0:1:0): tagged openings now 61 > > > > (da1:ahc0:0:1:0): tagged openings now 60 > > > > (da1:ahc0:0:1:0): tagged openings now 59 > > > > (da1:ahc0:0:1:0): tagged openings now 58 > > > > (da1:ahc0:0:1:0): tagged openings now 57 > > > > (da1:ahc0:0:1:0): tagged openings now 56 > > > > (da1:ahc0:0:1:0): tagged openings now 55 > > > > (da1:ahc0:0:1:0): tagged openings now 54 > > > > (da1:ahc0:0:1:0): tagged openings now 53 > > > > (da1:ahc0:0:1:0): tagged openings now 52 > > > > (da1:ahc0:0:1:0): tagged openings now 51 > > > > (da1:ahc0:0:1:0): tagged openings now 50 > > > > (da1:ahc0:0:1:0): tagged openings now 49 > > > > > > > > but it hasn't crashed yet. Which is good, as this is my primary workstation. > > > > > > > > Machine B above has been updated to 3.0-CURRENT (as of last night), but still exhibits the > > > > problem. All are running the GENERIC kernel. > > > > > > > > --Tom > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-scsi" in the body of the message > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 13:20:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA01934 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 13:20:24 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from qix.jmz.org (hibou.obs-besancon.fr [193.52.184.7]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA01921 for ; Fri, 11 Dec 1998 13:20:18 -0800 (PST) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix.jmz.org (8.9.1/8.8.7) id WAA13091; Fri, 11 Dec 1998 22:20:53 +0100 (MET) Date: Fri, 11 Dec 1998 22:20:53 +0100 (MET) Message-Id: <199812112120.WAA13091@qix.jmz.org> X-Authentication-Warning: qix.jmz.org: jmz set sender to jmz@qix.jmz.org using -f From: Jean-Marc Zucconi To: larry@marso.com CC: freebsd-scsi@FreeBSD.ORG In-reply-to: <19981211151343.B22555@marso.com> (larry@marso.com) Subject: Re: cdrecord and caching issue X-Mailer: Emacs Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> Larry S Marso writes: > I wrote a couple of trial cdrecord sessions using -dummy. > I then executed a third, real cdrecord session. It failed (fortunately, > before writing anything to the disk), complaining that "insufficient space > left on media". > I then executed a cdcontrol info, which reported that two previous sessions > were already recorded to the disk. In actual fact, the disk was still > blank; this I confirmed by shutting down and rebooting, then successfully > writing to the cdr. > So, there is some sort of caching going on that mistakenly thinks a -dummy > write is a real write. Might this not cause trouble? This is probably a problem specific to your drive, which does not not reset its internal TOC after a dummy write. Try to open/close the tray after a dummy write to reset it. This works with my CDD2600. Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 13:52:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA05817 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 13:52:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA05804 for ; Fri, 11 Dec 1998 13:52:02 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.9.1/8.8.8) id QAA23105 for freebsd-scsi@freebsd.org; Fri, 11 Dec 1998 16:53:24 -0500 (EST) (envelope-from larry) Date: Fri, 11 Dec 1998 16:53:23 -0500 From: "Larry S. Marso" To: freebsd-scsi@FreeBSD.ORG Subject: cdrecord and softupdates Message-ID: <19981211165323.A23093@marso.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.13i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Any reason to suspect softupdates might interfere with the cdrecord buffer mechanism, particularly on a relatively low RAM machine? Best regards -- Larry S. Marso larry@marso.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 18:50:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA04324 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 18:50:34 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sv01.cet.co.jp (sv01.cet.co.jp [210.171.56.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA04318 for ; Fri, 11 Dec 1998 18:50:32 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by sv01.cet.co.jp (8.8.8/8.8.8) with SMTP id CAA23473 for ; Sat, 12 Dec 1998 02:45:40 GMT (envelope-from michaelh@cet.co.jp) Date: Sat, 12 Dec 1998 11:45:40 +0900 (JST) From: Michael Hancock To: freebsd-scsi@FreeBSD.ORG Subject: CPQ Smart-2 PCI Disk Array Controllers 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 http://www.insync.net/~frantzc/cpqarray.html It's for Linux and GPL'ed but at least source is available and Compaq appears to be providing specs to the author. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 19:12:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA06064 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 19:12:05 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA06056 for ; Fri, 11 Dec 1998 19:12:00 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id NAA14618; Sat, 12 Dec 1998 13:41:34 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id NAA46557; Sat, 12 Dec 1998 13:41:32 +1030 (CST) Message-ID: <19981212134131.M457@freebie.lemis.com> Date: Sat, 12 Dec 1998 13:41:31 +1030 From: Greg Lehey To: Michael Hancock , freebsd-scsi@FreeBSD.ORG Cc: Mark Dawson Subject: Re: CPQ Smart-2 PCI Disk Array Controllers References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Michael Hancock on Sat, Dec 12, 1998 at 11:45:40AM +0900 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 Saturday, 12 December 1998 at 11:45:40 +0900, Michael Hancock wrote: > http://www.insync.net/~frantzc/cpqarray.html > > It's for Linux and GPL'ed but at least source is available and Compaq > appears to be providing specs to the author. I haven't looked at it, but a couple of weeks ago Mark Dawson noted: > An update for the 'ida' driver for FreeBSD-3.0 is available at: > > http://www.doc.ic.ac.uk/~md/ida/ > > As I don't run FreeBSD-3.0 in production it is relatively untested > (feedback would be appreciated). It runs up happily on the latest > Compaq SMART controller, FYI: > > http://www.compaq.com/products/servers/storage/3200-description.html > > A floppy boot image may be forthcoming soon (courtesy of David James at > BT). > > It would be great if the FreeBSD team would allocate us major and minor > device numbers for the 'id' (Intelligent Disk [Array]) as this would > make it easier to get the native (i.e. non-cuckooing) support sorted. Jordan gave him block major 29. I don't know what happened with the character major, which he'll also need, so possibly he hasn't got very far. Greg -- See complete headers for address, home page 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 Fri Dec 11 21:23:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16497 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 21:23:47 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16491 for ; Fri, 11 Dec 1998 21:23:35 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.9.1/8.8.8) id AAA23858 for freebsd-scsi@freebsd.org; Sat, 12 Dec 1998 00:24:54 -0500 (EST) (envelope-from larry) Date: Sat, 12 Dec 1998 00:24:53 -0500 From: "Larry S. Marso" To: freebsd-scsi@FreeBSD.ORG Subject: can't "cp /dev/cd0c" after CAM Message-ID: <19981212002453.A23854@marso.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.13i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Pre-CAM, I could simply issue a: cp /dev/cd0c image.raw Then: cdrecord dev=2,0 image.raw. Since moving to a CAM system, the cp command yields: cp: /dev/cd0c: Invalid argument Tosha works fine, if I specify pass0 as the device. But that's designed to rip audio tracks. Don't think that's appropriate for this, a MAC format cd. (For which the pre-CAM approach worked fine). Best regards -- Larry S. Marso larry@marso.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 21:25:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA16665 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 21:25:48 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from second.dialup.access.net (lsmarso.dialup.access.net [166.84.254.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA16660 for ; Fri, 11 Dec 1998 21:25:37 -0800 (PST) (envelope-from larry@marso.com) Received: (from larry@localhost) by second.dialup.access.net (8.9.1/8.8.8) id AAA23867 for freebsd-scsi@freebsd.org; Sat, 12 Dec 1998 00:26:57 -0500 (EST) (envelope-from larry) Date: Sat, 12 Dec 1998 00:26:57 -0500 From: "Larry S. Marso" To: freebsd-scsi@FreeBSD.ORG Subject: can't use hfs since CAM Message-ID: <19981212002657.B23854@marso.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.13i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Pre-CAM, xhfs (the MAC analog of the mtools package) worked fine if you simply specified: /dev/cd0c as the target, and put in a MAC format cdrom, which uses aufs format. Since CAM, it no longer recognizes /dev/cd0c as MAC format. Best regards -- Larry S. Marso larry@marso.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 22:37:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22756 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 22:37:43 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail-oak-1.pilot.net (mail-oak-1.pilot.net [198.232.147.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22749 for ; Fri, 11 Dec 1998 22:37:41 -0800 (PST) (envelope-from wadlow@pilot.net) Received: from corsair.pilot.net (corsair.pilot.net [204.48.17.12]) by mail-oak-1.pilot.net with ESMTP id WAA16939; Fri, 11 Dec 1998 22:37:31 -0800 (PST) Received: from arrow.pilot.net (arrow.pilot.net [204.48.17.29]) by corsair.pilot.net with ESMTP id WAA27603; Fri, 11 Dec 1998 22:37:31 -0800 (PST) Received: from localhost (wadlow@localhost) by arrow.pilot.net (arrow) with ESMTP id WAA09914; Fri, 11 Dec 1998 22:37:29 -0800 (PST) Date: Fri, 11 Dec 1998 22:37:29 -0800 (PST) From: Tom Wadlow To: Matthew Jacob cc: scsi@FreeBSD.ORG Subject: Re: A problem with SCSI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org More info. I had two crashes, both with "Invalidating pack" and the following: (da0:bt0:0:0:0) CCB 0xf49e06c0 - timed out (da0:bt0:0:0:0) CCB 0xf49e0140 - timed out The machine froze after that so nothing else was printed or logged. --Tom On Fri, 11 Dec 1998, Matthew Jacob wrote: > Date: Fri, 11 Dec 1998 12:39:59 -0800 (PST) > From: Matthew Jacob > To: Tom Wadlow > Cc: scsi@FreeBSD.ORG > Subject: Re: A problem with SCSI > > > Invalidating pack can come about if a there's a I/O error on that drive. > That's what we're trying to gather info about. > > On Fri, 11 Dec 1998, Tom Wadlow wrote: > > > The ones that crashed said "Invalidating pack" and then died. The "tagged" messages were > > coming from the one that didn't crash, but was doing things that seemed odd to me (i.e. > > generating these tagged messages was new behavior. Sounds like it was just debugging info > > and not anything to worry about from your description). > > > > Also, the one that didn't crash is using an Adaptec SCSI controller (sorry, I just noticed > > that I forgot to include that in my earlier message). > > > > --tom > > > > On Fri, 11 Dec 1998, Matthew Jacob wrote: > > > > > Date: Fri, 11 Dec 1998 11:50:09 -0800 (PST) > > > From: Matthew Jacob > > > To: Tom Wadlow > > > Cc: scsi@FreeBSD.ORG > > > Subject: Re: A problem with SCSI > > > > > > > > > Any other messages when it crashed? The 'tagged openings' message is just > > > the process of throttling down the # of cmds outstanding per device.. > > > > > > > > > On Fri, 11 Dec 1998, Tom Wadlow wrote: > > > > > > > > > > > > Date: Fri, 11 Dec 1998 11:07:29 -0700 (MST) > > > > > From: Justin T. Gibbs > > > > > Subject: Re: A problem with SCSI > > > > > > > > > > > occasionally, the da driver says: "Invalidating pack", and drops > > > > > > the disk offline and everything hangs. This is unfortunate. > > > > > > > > > > Certainly is. What kind of hardware are you using (SCSI controller, > > > > > devices on the bus, CPU, etc.)? > > > > > > > > I've built out several systems from 3.0-RELEASE that all seeem to manifest this problem. > > > > Two die on a regular basis. The third gets strange messsages but seems to stay up. > > > > > > > > Machines dying with "Invalidating pack" > > > > A) Pentium 100MHz > > > > 64MB RAM > > > > BusLogic 496 SCSI controller > > > > 4GB Connor SCSI (only device on the SCSI chain) > > > > Ethernet > > > > Floppy > > > > > > > > B) Pentium 120MHz > > > > 96MB RAM > > > > BusLogic 496 SCSI controller > > > > 1GB Connor SCSI (only device on the SCSI chain) > > > > Ethernet > > > > Floppy > > > > > > > > Machine with strange messages: > > > > Pentium II 330 MHz > > > > 128MB RAM > > > > HP SCSI CDROM > > > > Seagate 4GB SCSI (boot device) > > > > Seagate 9GB SCSI > > > > Ethernet > > > > > > > > The strange messages this machine is getting look like this: > > > > > > > > (da0:ahc0:0:0:0): tagged openings now 64 > > > > (da0:ahc0:0:0:0): tagged openings now 63 > > > > (da1:ahc0:0:1:0): tagged openings now 64 > > > > (da1:ahc0:0:1:0): tagged openings now 63 > > > > (da1:ahc0:0:1:0): tagged openings now 62 > > > > (da1:ahc0:0:1:0): tagged openings now 61 > > > > (da1:ahc0:0:1:0): tagged openings now 60 > > > > (da1:ahc0:0:1:0): tagged openings now 59 > > > > (da1:ahc0:0:1:0): tagged openings now 58 > > > > (da1:ahc0:0:1:0): tagged openings now 57 > > > > (da1:ahc0:0:1:0): tagged openings now 56 > > > > (da1:ahc0:0:1:0): tagged openings now 55 > > > > (da1:ahc0:0:1:0): tagged openings now 54 > > > > (da1:ahc0:0:1:0): tagged openings now 53 > > > > (da1:ahc0:0:1:0): tagged openings now 52 > > > > (da1:ahc0:0:1:0): tagged openings now 51 > > > > (da1:ahc0:0:1:0): tagged openings now 50 > > > > (da1:ahc0:0:1:0): tagged openings now 49 > > > > > > > > but it hasn't crashed yet. Which is good, as this is my primary workstation. > > > > > > > > Machine B above has been updated to 3.0-CURRENT (as of last night), but still exhibits the > > > > problem. All are running the GENERIC kernel. > > > > > > > > --Tom > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-scsi" in the body of the message > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Dec 11 23:28:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA27944 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 23:28:20 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA27939 for ; Fri, 11 Dec 1998 23:28:18 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id AAA35341; Sat, 12 Dec 1998 00:28:07 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812120728.AAA35341@panzer.plutotech.com> Subject: Re: can't "cp /dev/cd0c" after CAM In-Reply-To: <19981212002453.A23854@marso.com> from "Larry S. Marso" at "Dec 12, 98 00:24:53 am" To: larry@marso.com (Larry S. Marso) Date: Sat, 12 Dec 1998 00:28:07 -0700 (MST) 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 Larry S. Marso wrote... > Pre-CAM, I could simply issue a: > > cp /dev/cd0c image.raw > > Then: > > cdrecord dev=2,0 image.raw. > > Since moving to a CAM system, the cp command yields: > > cp: /dev/cd0c: Invalid argument Works fine for me. Do you see any error messages on the console? What happens if you try the raw device? > Tosha works fine, if I specify pass0 as the device. But that's designed to > rip audio tracks. Don't think that's appropriate for this, a MAC format > cd. (For which the pre-CAM approach worked fine). Hmm, wait a minute. What happens if you specify the CD device? Can you even mount this CD? What does the dmesg on your system look like? 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 Fri Dec 11 23:29:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA28073 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 23:29:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA28068 for ; Fri, 11 Dec 1998 23:29:10 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id AAA35354; Sat, 12 Dec 1998 00:28:59 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812120728.AAA35354@panzer.plutotech.com> Subject: Re: can't use hfs since CAM In-Reply-To: <19981212002657.B23854@marso.com> from "Larry S. Marso" at "Dec 12, 98 00:26:57 am" To: larry@marso.com (Larry S. Marso) Date: Sat, 12 Dec 1998 00:28:59 -0700 (MST) 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 Larry S. Marso wrote... > Pre-CAM, xhfs (the MAC analog of the mtools package) worked fine > if you simply specified: > > /dev/cd0c > > as the target, and put in a MAC format cdrom, which uses aufs format. > > Since CAM, it no longer recognizes /dev/cd0c as MAC format. Send the dmesg output from your system. I suspect something may be wrong with 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 Sat Dec 12 03:13:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA11530 for freebsd-scsi-outgoing; Sat, 12 Dec 1998 03:13:03 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from fox.doc.ic.ac.uk (fox.doc.ic.ac.uk [146.169.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA11524 for ; Sat, 12 Dec 1998 03:13:02 -0800 (PST) (envelope-from md@doc.ic.ac.uk) Received: from dialup09.doc.ic.ac.uk ([146.169.43.72] helo=doc.ic.ac.uk ident=md) by fox.doc.ic.ac.uk with esmtp (Exim 2.05 #1) id 0zomyT-0006MP-00; Sat, 12 Dec 1998 11:12:38 +0000 Message-ID: <36725B3C.A3651482@doc.ic.ac.uk> Date: Sat, 12 Dec 1998 12:02:04 +0000 From: Mark Dawson Organization: Department of Computing, Imperial College, London. X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.34 i586) MIME-Version: 1.0 To: Greg Lehey CC: Michael Hancock , freebsd-scsi@FreeBSD.ORG Subject: Re: CPQ Smart-2 PCI Disk Array Controllers References: <19981212134131.M457@freebie.lemis.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Saturday, 12 December 1998 at 11:45:40 +0900, Michael Hancock wrote: > > http://www.insync.net/~frantzc/cpqarray.html > > > > It's for Linux and GPL'ed but at least source is available and Compaq > > appears to be providing specs to the author. It includes helpful headers describing all the controller commands. As the email contact given is 'arrays@compaq.com' I suspect that the author is a Compaq employee. > Jordan gave him block major 29. I don't know what happened with the > character major, which he'll also need, so possibly he hasn't got very far. I now have block#29 and character#109 and will use these for the "non-cuckoo version" of the driver (i.e. the driver steals the vectors of the wdc if it sees a Smart controller on boot - this allows me to install FreeBSD in the usual way on a pure-RAID system - details at ). I should add that, using this driver, FreeBSD has been running on the Compaq Smart family of controllers without snags for over three years now. Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 12 03:21:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA11921 for freebsd-scsi-outgoing; Sat, 12 Dec 1998 03:21:02 -0800 (PST) (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 DAA11916 for ; Sat, 12 Dec 1998 03:21:00 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id MAA03204; Sat, 12 Dec 1998 12:20:56 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id MAA07029; Sat, 12 Dec 1998 12:01:58 +0100 (MET) (envelope-from j) Message-ID: <19981212120158.09620@uriah.heep.sax.de> Date: Sat, 12 Dec 1998 12:01:58 +0100 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Cc: larry@marso.com Subject: Re: cdrecord and caching issue Reply-To: Joerg Wunsch References: <19981211151343.B22555@marso.com> <199812112120.WAA13091@qix.jmz.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <199812112120.WAA13091@qix.jmz.org>; from Jean-Marc Zucconi on Fri, Dec 11, 1998 at 10:20:53PM +0100 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 Jean-Marc Zucconi wrote: > This is probably a problem specific to your drive, which does not not > reset its internal TOC after a dummy write. Try to open/close the tray > after a dummy write to reset it. This works with my CDD2600. Just as an additional datapoint: reloading the medium is the only documented way to get rid of the cached TOC for my old Plasmon burner. -- 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 Sat Dec 12 04:17:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA19525 for freebsd-scsi-outgoing; Sat, 12 Dec 1998 04:17:43 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sv01.cet.co.jp (sv01.cet.co.jp [210.171.56.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA19519 for ; Sat, 12 Dec 1998 04:17:42 -0800 (PST) (envelope-from michaelh@cet.co.jp) Received: from localhost (michaelh@localhost) by sv01.cet.co.jp (8.8.8/8.8.8) with SMTP id MAA24868; Sat, 12 Dec 1998 12:17:32 GMT (envelope-from michaelh@cet.co.jp) Date: Sat, 12 Dec 1998 21:17:32 +0900 (JST) From: Michael Hancock To: Mark Dawson cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CPQ Smart-2 PCI Disk Array Controllers In-Reply-To: <36725B3C.A3651482@doc.ic.ac.uk> 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 Mark, I knew about this driver, but it was unclear if there were any legal issues w/ Compaq. Aside from the block and character numbers are there any issues that would prevent this code from being committed to the CVS repository? I'd like to run FBSD on the Proliant 1850R. Regards, Mike Hancock On Sat, 12 Dec 1998, Mark Dawson wrote: > > On Saturday, 12 December 1998 at 11:45:40 +0900, Michael Hancock wrote: > > > http://www.insync.net/~frantzc/cpqarray.html > > > > > > It's for Linux and GPL'ed but at least source is available and Compaq > > > appears to be providing specs to the author. > > It includes helpful headers describing all the controller commands. As the > email contact given is 'arrays@compaq.com' I suspect that the author is a Compaq > employee. > > > Jordan gave him block major 29. I don't know what happened with the > > character major, which he'll also need, so possibly he hasn't got very far. > > I now have block#29 and character#109 and will use these for the > "non-cuckoo version" of the driver (i.e. the driver steals the vectors > of the wdc if it sees a Smart controller on boot - this allows me to > install FreeBSD in the usual way on a pure-RAID system - details at > ). > > I should add that, using this driver, FreeBSD has been running on the Compaq > Smart family of controllers without snags for over three years now. > > Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 12 05:08:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA22071 for freebsd-scsi-outgoing; Sat, 12 Dec 1998 05:08:40 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pigeon.doc.ic.ac.uk (pigeon.doc.ic.ac.uk [146.169.5.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA22066 for ; Sat, 12 Dec 1998 05:08:38 -0800 (PST) (envelope-from md@doc.ic.ac.uk) Received: from dialup09.doc.ic.ac.uk ([146.169.43.72] helo=doc.ic.ac.uk ident=md) by pigeon.doc.ic.ac.uk with esmtp (Exim 1.890 #1) id 0zoomX-0005fO-00; Sat, 12 Dec 1998 13:08:26 +0000 Message-ID: <36727661.5ECD7FCC@doc.ic.ac.uk> Date: Sat, 12 Dec 1998 13:57:53 +0000 From: Mark Dawson X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.34 i586) MIME-Version: 1.0 To: Michael Hancock CC: freebsd-scsi@FreeBSD.ORG Subject: Re: CPQ Smart-2 PCI Disk Array Controllers References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Michael, > I knew about this driver, but it was unclear if there were any legal > issues w/ Compaq. When I enquired about this through a Compaq support person two years ago I received an email saying there was no need to be concerned. Indeed the santified release of the Linux driver means they have now put the controller interface in the public domain. > Aside from the block and character numbers are there > any issues that would prevent this code from being committed to the CVS > repository? My main requirement is that I can install FreeBSD on hardware that only has RAID disks. For this to work the installation boot floppy needs to know about Smart as a boot device. David James has built a series of such cuckoo-enabled floppies for FreeBSD-2.x. He also has patches that allow FBSD to boot natively and these would also need to be merged and committed. > I'd like to run FBSD on the Proliant 1850R. Should be no problem. Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 12 09:05:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA09170 for freebsd-scsi-outgoing; Sat, 12 Dec 1998 09:05:01 -0800 (PST) (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 JAA09155 for ; Sat, 12 Dec 1998 09:04:59 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id KAA05364; Sat, 12 Dec 1998 10:04:57 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199812121704.KAA05364@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Tom Wadlow cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: A problem with SCSI In-reply-to: Your message of "Fri, 11 Dec 1998 11:15:26 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 12 Dec 1998 09:57:14 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I've built out several systems from 3.0-RELEASE that all seeem to manifest thi >s problem. >Two die on a regular basis. The third gets strange messsages but seems to sta >y up. > >Machines dying with "Invalidating pack" > A) Pentium 100MHz > 64MB RAM > BusLogic 496 SCSI controller > 4GB Connor SCSI (only device on the SCSI chain) > Ethernet > Floppy This is most likely a bad interaction between your buslogic 946 and the Connor drives. Can you mail me the dmesg output from your machine just after boot? There have been several bug fixes to the Buslogic driver since 3.0R. Your problem may be solved by running a more recent SNAPSHOT or using CVSup to pull -current. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message