From owner-freebsd-scsi Sat May 8 14: 2:38 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 196A0151FB for ; Sat, 8 May 1999 14:02:26 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA27221; Sat, 8 May 1999 22:05:36 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA50530; Sat, 8 May 1999 21:31:49 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905081931.VAA50530@yedi.iaf.nl> Subject: Re: Question - Onstream SCSI Streamer In-Reply-To: from Matthew Jacob at "May 8, 1999 11: 4:38 am" To: mjacob@feral.com Date: Sat, 8 May 1999 21:31:49 +0200 (CEST) Cc: karl@Denninger.Net, darrylo@sr.hp.com, 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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Matthew Jacob wrote ... > > > > > > The drive. > > > > Yikes. What got broken? Leader pickup? Head? > > Leader pickup is easy- that happens regularly. You pop the drive upon and > put the leader pickup back on the spring. The heads probably. It never was Yep, leaders are easy. If you know how to do it obviously. I got my DLT4000 that way. "Does nothing, blinks all leds". Bought it for US$ 25 because they thought is was scrap. I did not not know what the culprit was, but when I found out I had a *good* day. I still smile when I use it ;-) The heads are also one of the most expensive parts of the whole drive. So.. > ATL (the drives were in a large ATL jukebox ~500 slots, 3 DLT2000) that it > wasn't working. Shame on us. ATLs are cool stuff, I agree. I've played with the 260 cartridge variant. They become less funny when you open the door and it does a full inventory .. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 8 16: 5:42 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id F168215053 for ; Sat, 8 May 1999 16:05:39 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA01413 for freebsd-scsi@freebsd.org; Sun, 9 May 1999 00:58:01 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id BAA01664 for freebsd-scsi@freebsd.org; Sun, 9 May 1999 01:04:27 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905082304.BAA01664@yedi.iaf.nl> Subject: problem with non-rewinding device on DLT / using dump ? To: freebsd-scsi@freebsd.org (FreeBSD SCSI hackers) Date: Sun, 9 May 1999 01:04:27 +0200 (CEST) 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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is it me or? 3.1-stable, running a DLT4000/TZ88 on a ncr810. The same config worked fine with 2.2.8. I do something like: dump 0ubBf 64 1000000 /dev/nrsa2 / dump 0ubBf 64 1000000 /dev/nrsa2 /usr dump 0ubBf 64 1000000 /dev/nrsa2 /var dump 0ubBf 64 1000000 /dev/nrsa2 /local Dump happily does it's thing. What fails is: su-2.02# restore -s 3 -i -f /dev/nrsa2 resync restore, skipped 32 blocks Cannot find file dump list su-2.02# mt tells me: su-2.02# mt -f /dev/rsa2 status Mode Density Blocksize bpi Compression Current: 0x81 variable 0 IDRC ---------available modes--------- 0: 0x81 variable 0 IDRC 1: 0x81 variable 0 IDRC 2: 0x81 variable 0 IDRC 3: 0x81 variable 0 IDRC --------------------------------- Current Driver State: at rest. --------------------------------- File Number: 2 Record Number: 3 su-2.02# I've tar-red a couple of gigs to/from the tape and that works OK. Using the tape with (0x81 is with) or without compression does not make a difference. Any clues? Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 8 16:24:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pcpsj.pfcs.com (harlan.clark.net [168.143.10.179]) by hub.freebsd.org (Postfix) with ESMTP id 59D121517F for ; Sat, 8 May 1999 16:24:04 -0700 (PDT) (envelope-from Harlan.Stenn@pfcs.com) Received: from mumps.pfcs.com [192.52.69.11] (HELO mumps.pfcs.com) by pcpsj.pfcs.com (8.9.3/8.9.3) via ESMTP id for ; Sat, 8 May 1999 19:24:02 -0400 (EDT) Received: from brown.pfcs.com [192.52.69.44] (HELO brown.pfcs.com) by mumps.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Sat, 8 May 1999 16:24:01 -0700 (PDT) Received: from localhost [127.0.0.1] (HELO brown.pfcs.com) by brown.pfcs.com (8.8.8/8.8.8) via ESMTP id for ; Sat, 8 May 1999 19:24:01 -0400 (EDT) X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@freebsd.org Subject: DVD-RAM? X-Face: "csXK}xnnsH\h_ce`T#|pM]tG,6Xu.{3Rb\]&XJgVyTS'w{E+|-(}n:c(Cc* $cbtusxDP6T)Hr'k&zrwq0.3&~bAI~YJco[r.mE+K|(q]F=ZNXug:s6tyOk{VTqARy0#axm6BWti9C d Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 08 May 1999 19:24:00 -0400 Message-ID: <11293.926205840@brown.pfcs.com> From: Harlan Stenn Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anybody have a DVD-RAM drive working with FreeBSD? Comments about the different DVD-RAM models? H To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 8 17:35: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 752C114C0B for ; Sat, 8 May 1999 17:35:05 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id SAA11529; Sat, 8 May 1999 18:25:13 -0600 (MDT) Date: Sat, 8 May 1999 18:25:13 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199905090025.SAA11529@narnia.plutotech.com> To: Wilko Bulte Cc: scsi@FreeBSD.org Subject: Re: Getting Pioneer CD changer to work X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <199905072129.XAA32584@yedi.iaf.nl> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199905072129.XAA32584@yedi.iaf.nl> you wrote: > I can still get the system to lock up with the default CHANGER_MIN_BUSY_SECONDS > and CHANGER_MAX_BUSY_SECONDS. > > A kernel built with > > # Pioneer cdloader > options CHANGER_MIN_BUSY_SECONDS=5 > options CHANGER_MAX_BUSY_SECONDS=15 Can you get at this system with remote gdb when it hangs? My guess is that there is still a race condition somewhere in the changer code and I'd like to squash it. We don't happen to have any changers here at the moment to test on and you seem to have a convenient setup with which to reproduce the problem. 8-) -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 9 7:35:53 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 82CCF150FF for ; Sun, 9 May 1999 07:35:50 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id QAA30058 for freebsd-scsi@FreeBSD.ORG; Sun, 9 May 1999 16:28:45 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id PAA09975; Sun, 9 May 1999 15:52:53 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905091352.PAA09975@yedi.iaf.nl> Subject: Re: problem with non-rewinding device on DLT / using dump ? In-Reply-To: <199905082304.BAA01664@yedi.iaf.nl> from Wilko Bulte at "May 9, 1999 1: 4:27 am" To: wilko@yedi.iaf.nl (Wilko Bulte) Date: Sun, 9 May 1999 15:52:53 +0200 (CEST) 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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Wilko Bulte wrote ... > Is it me or? Yes, it was :-( > > I do something like: > dump 0ubBf 64 1000000 /dev/nrsa2 / > dump 0ubBf 64 1000000 /dev/nrsa2 /usr > dump 0ubBf 64 1000000 /dev/nrsa2 /var > dump 0ubBf 64 1000000 /dev/nrsa2 /local > > Dump happily does it's thing. > > What fails is: > > su-2.02# restore -s 3 -i -f /dev/nrsa2 make that: restore -s 3 -b64 -i -f /dev/nrsa2 and it works a whole lot better. Sorry for the wasted bandwith Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 9 10: 4:33 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id C748315CC0 for ; Sun, 9 May 1999 10:04:08 -0700 (PDT) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id TAA00636 for freebsd-scsi@FreeBSD.ORG; Sun, 9 May 1999 19:04:06 +0200 (CEST) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 6A794885D; Sun, 9 May 1999 17:48:28 +0200 (CEST) (envelope-from roberto) Date: Sun, 9 May 1999 17:48:28 +0200 From: Ollivier Robert To: freebsd-scsi@FreeBSD.ORG Subject: Re: problem with non-rewinding device on DLT / using dump ? Message-ID: <19990509174828.A55040@keltia.freenix.fr> Mail-Followup-To: freebsd-scsi@FreeBSD.ORG References: <199905082304.BAA01664@yedi.iaf.nl> <199905091352.PAA09975@yedi.iaf.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.95.5i In-Reply-To: <199905091352.PAA09975@yedi.iaf.nl>; from Wilko Bulte on Sun, May 09, 1999 at 03:52:53PM +0200 X-Operating-System: FreeBSD 4.0-CURRENT/ELF ctm#5307 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Wilko Bulte: > make that: restore -s 3 -b64 -i -f /dev/nrsa2 > > and it works a whole lot better. I thought restore(8) was supposed to find the blocksize itself... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #2: Fri Apr 16 22:37:03 CEST 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 9 14:14: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 41CF3158AC for ; Sun, 9 May 1999 14:13:39 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA11404; Sun, 9 May 1999 23:01:30 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA99359; Sun, 9 May 1999 20:49:39 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905091849.UAA99359@yedi.iaf.nl> Subject: Re: problem with non-rewinding device on DLT / using dump ? In-Reply-To: <19990509174828.A55040@keltia.freenix.fr> from Ollivier Robert at "May 9, 1999 5:48:28 pm" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Sun, 9 May 1999 20:49:39 +0200 (CEST) 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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Ollivier Robert wrote ... > According to Wilko Bulte: > > make that: restore -s 3 -b64 -i -f /dev/nrsa2 > > > > and it works a whole lot better. > > I thought restore(8) was supposed to find the blocksize itself... Well... with -b64 I can restore things, without I can't. So I guess restore can not do it. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 10 3:57:15 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from project.m2.ntu.edu.tw (project.m2.ntu.edu.tw [140.112.213.32]) by hub.freebsd.org (Postfix) with ESMTP id 6C7C115178 for ; Mon, 10 May 1999 03:57:07 -0700 (PDT) (envelope-from tyl@project.m2.ntu.edu.tw) Received: from localhost (tyl@localhost) by project.m2.ntu.edu.tw (8.9.1/8.9.1) with ESMTP id SAA19376; Mon, 10 May 1999 18:55:41 +0800 (CST) (envelope-from tyl@project.m2.ntu.edu.tw) Date: Mon, 10 May 1999 18:55:41 +0800 (CST) From: tyl To: Lars Fredriksen Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AHA 2940 U/UW waiting fail? In-Reply-To: <3733037A.C2C64778@odin-corporation.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 7 May 1999, Lars Fredriksen wrote: > > I have disconnected all the HDs and CDROMs, but FreeBSD still halt at the > > "waiting 15 seconds". It seems the problem is on the card? > > No, I don't think it is a problem with the card per se. However, it might be > an issue with how we configure interrupts. Thanks for your reply first !! In your opinion, that is some problem aboout interrupt / IRQs? Maybe I have to move the card to another computer and try... > Hm, it is interssting that you see the problem on UP when I don't. > What does your mptable output look like? Excuse me, what is "mptable" :) Due to I can boot normally with 4.0-0408, I have use boot -v and see something interesting but I do not understand, is that what you want? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 10 13:36:51 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 7528615D45 for ; Mon, 10 May 1999 13:36:26 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA09475; Mon, 10 May 1999 22:34:07 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA46689; Sun, 9 May 1999 23:16:27 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905092116.XAA46689@yedi.iaf.nl> Subject: Re: Getting Pioneer CD changer to work In-Reply-To: <199905090025.SAA11529@narnia.plutotech.com> from "Justin T. Gibbs" at "May 8, 1999 6:25:13 pm" To: gibbs@narnia.plutotech.com (Justin T. Gibbs) Date: Sun, 9 May 1999 23:16:27 +0200 (CEST) Cc: 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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Justin T. Gibbs wrote ... > In article <199905072129.XAA32584@yedi.iaf.nl> you wrote: > > I can still get the system to lock up with the default CHANGER_MIN_BUSY_SECONDS > > and CHANGER_MAX_BUSY_SECONDS. > > > > A kernel built with > > > > # Pioneer cdloader > > options CHANGER_MIN_BUSY_SECONDS=5 > > options CHANGER_MAX_BUSY_SECONDS=15 > > Can you get at this system with remote gdb when it hangs? My guess is > that there is still a race condition somewhere in the changer code and > I'd like to squash it. We don't happen to have any changers here at > the moment to test on and you seem to have a convenient setup with > which to reproduce the problem. 8-) I'll try to find some time later this week to build a test setup. I did not have a whole lot of luck with remote gdb earlier though.. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 10 15: 9:47 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 256B514C86 for ; Mon, 10 May 1999 15:09:39 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id PAA14753; Mon, 10 May 1999 15:59:49 -0600 (MDT) Date: Mon, 10 May 1999 15:59:49 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199905102159.PAA14753@narnia.plutotech.com> To: Jim Cassata Cc: scsi@FreeBSD.org Subject: Re: scsi timeouts X-Newsgroups: pluto.freebsd.stable In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Moved to the SCSI list where it belongs... > Hi, I am wondering if any other Buslogic BT-948 users out there are > experiencing this problem. On a Dual P2 machine running up to 3.0-SNAP i > had my workstations running perfect (Dual pentium at home, same card and 6 > gig quantum scsi) Upon installing 3.0-RELEASE, i started to get scsi > timeouts on both boxes, a la: > > Homer.Web-Ex.com kernel log messages: >> (da0:bt0:0:0:0): CCB 0xf5544b40 - timed out >> (da0:bt0:0:0:0): CCB 0xf5544b40 - timed out >> bt0: No longer in timeout What kind of drive is this? The last time I heard of this problem, the guess was that the BusLogic firmware doesn't deal with 'Queue FULL' very well, so you have to limit the number of transactions sent to the drive to something smaller than CAM's default. Add a quirk entry in sys/cam/cam_xpt.c that reduces the tag count to ~32 (depending on the drive) and your problem will likely go away. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 10 17:43:25 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id A710B14C89 for ; Mon, 10 May 1999 17:43:15 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id RAA79253; Mon, 10 May 1999 17:52:57 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905102352.RAA79253@panzer.plutotech.com> Subject: camcontrol changes available To: scsi@FreeBSD.ORG Date: Mon, 10 May 1999 17:52:57 -0600 (MDT) Cc: joerg_wunsch@interface-business.de X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Joerg Wunsch and I have made some changes to camcontrol(8) that allow devices to be specified in a couple of new ways. Previously, you could only specify devices like this: camcontrol tur -n da -u 3 -v Now, you can specify devices like this: camcontrol tur da3 -v camcontrol tur 0:3 -v [ the lun defaults to 0 here ] camcontrol tur 0:3:0 -v The original syntax is still fully supported, and should continue to work. These enhancements only apply to camcontrol arguments that previously operated with the "-n -u" syntax. rescan, reset and debug, by design, will still only work with bus or bus:target:lun type syntax. Anyway, we've tested these changes and believe they work fine in all scenarios, but it wouldn't hurt to have more people tinker with them. So, if anyone feels like testing it out, please do! The changes are available now in -current and -stable. One other change we made was to shorten the default usage statement to fit in a 24 line terminal. The full usage statement is available by using the camcontrol "help", "-h", or "-?" arguments. If you find any problems, please either send mail to the list or send mail to _both_ Joerg and me! (If there are problems we'll want to get them fixed before 3.2 goes out the door on the 15th.) Thanks, Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 11 0:59:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from gorgias.uchicago.edu (gorgias.uchicago.edu [128.135.21.6]) by hub.freebsd.org (Postfix) with ESMTP id 2CFED14F8C for ; Tue, 11 May 1999 00:59:16 -0700 (PDT) (envelope-from sfarrell@palefire.org) Received: from couatl.palefire.org (couatl.cs.uchicago.edu [128.135.11.38]) by gorgias.uchicago.edu (8.9.2/8.9.0) with ESMTP id CAA20568 for ; Tue, 11 May 1999 02:59:15 -0500 (CDT) Received: by couatl.palefire.org (Postfix, from userid 30209) id 77A13BE45; Tue, 11 May 1999 02:59:14 -0500 (CDT) To: freebsd-scsi@freebsd.org Subject: Problems after adding CD (CRW4416S) From: stephen farrell Date: 11 May 1999 02:59:14 -0500 Message-ID: Lines: 67 User-Agent: Gnus/5.070084 (Pterodactyl Gnus v0.84) XEmacs/20.4 (Emerald) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Since adding a CD-RW (Yamaha CRW4416S), I have been having major problems with my SCSI bus. In fact, I have resigned to disconnecting the CD until I can figure out the problem. Here is the problem: SCSI timeouts either on boot or shortly after we have some disk load. Here is the setup: FreeBSD 3.1-STABLE #6: Mon Apr 26 12:30:18 CDT 1999 CPU: Pentium II/Xeon/Celeron (400.91-MHz 686-class CPU) ASUS P2B-D motherboard w/BX chipset (only one cpu) ahc0: rev 0x01 int a irq 10 on pci0.11.0 ahc0: aic7860 Single Channel A, SCSI Id=7, 3/255 SCBs [adaptec bios revision 1.30] da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da1: 2048MB (4194304 512 byte sectors: 255H 63S/T 261C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da2: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 4339MB (8887200 512 byte sectors: 255H 63S/T 553C) cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 8.333MB/s transfers (8.333MHz, offset 15) cd0: cd present [191788 x 2048 byte records] All drives are mounted internally. There is one cable, it is adaptec brand, and it has 4 connectors (+ host). da0 (the cheetah) is the last drive on the chain. It has termination turned on with the jumper (on j2, there are jumpers in location 2 and 8, which correspond to term power from drive and term enabled, respectively); all other drives have termination turned off. I've tried a number of different arrangements of the bus, but the one which works the best seems to be CD -> da2 -> da1 -> da0. I was able to get this setup to run for a while (with the CD) by fiddling with the adaptec bios setup utility. I disabled Ultra SCSI on the CDROM only, and set its transfer speeds down to 5MB/sec. This seemed to work, but it made the rest of the drives awfully slow. (Presumably they too were running at 5MB/sec?) It seems that with any other settings, it is guaranteed to have SCSI timeouts, often during fsck at boot. If I remove the CD all problems go away. (This is my current state). I cannot imagine that it would be so much trouble to add a CDROM. Can anyone suggest what I might try to fix this problem? Thanks for any help! -- Steve Farrell To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 11 1: 8: 8 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id A13F115D8B for ; Tue, 11 May 1999 01:07:59 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id SAA01379; Tue, 11 May 1999 18:07:23 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (4.1) id xma001369; Tue, 11 May 99 18:06:53 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id SAA09861; Tue, 11 May 1999 18:06:53 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id SAA23315; Tue, 11 May 1999 18:06:52 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id SAA28834; Tue, 11 May 1999 18:06:50 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199905110806.SAA28834@nymph.detir.qld.gov.au> To: Wilko Bulte Cc: freebsd-scsi@freebsd.org, syssgm@detir.qld.gov.au, roberto@keltia.freenix.fr (Ollivier Robert) Subject: Re: problem with non-rewinding device on DLT / using dump ? References: <199905091849.UAA99359@yedi.iaf.nl> In-Reply-To: <199905091849.UAA99359@yedi.iaf.nl> from Wilko Bulte at "Sun, 09 May 1999 20:49:39 +0200" Date: Tue, 11 May 1999 18:06:50 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sunday, 9th May 1999, Wilko Bulte wrote: >As Ollivier Robert wrote ... >> According to Wilko Bulte: >> > make that: restore -s 3 -b64 -i -f /dev/nrsa2 >> > >> > and it works a whole lot better. >> >> I thought restore(8) was supposed to find the blocksize itself... > >Well... with -b64 I can restore things, without I can't. So I guess restore >can not do it. It can guess as high as 32KB, but no higher. Changing HIGHDENSITYTREC to 64 would cause dump to write in 64KB blocks for most devices and cause restore to guess as large as 64KB. But, I think that some QIC tape devices will fail because 64KB blocks are illegal in some modes. I find that 32KB works for me for all drive types that I use (QIC old and new, Exabyte 8200 thru 8505). Any reason why you don't use 32KB? Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 11 7: 9: 4 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from munin.odin-corporation.com (fredriks-2.pr.mcs.net [205.164.50.242]) by hub.freebsd.org (Postfix) with ESMTP id E8D2D15127 for ; Tue, 11 May 1999 07:09:00 -0700 (PDT) (envelope-from lars@odin-corporation.com) Received: from odin-corporation.com (localhost [127.0.0.1]) by munin.odin-corporation.com (8.9.3/8.9.1) with ESMTP id JAA89541; Tue, 11 May 1999 09:08:50 -0500 (CDT) (envelope-from lars@odin-corporation.com) Message-ID: <373839F1.F897919D@odin-corporation.com> Date: Tue, 11 May 1999 09:08:50 -0500 From: Lars Fredriksen Organization: Odin Corporation X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 4.0-CURRENT i386) X-Accept-Language: no, en MIME-Version: 1.0 To: tyl Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AHA 2940 U/UW waiting fail? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org tyl wrote: > On Fri, 7 May 1999, Lars Fredriksen wrote: > > > > I have disconnected all the HDs and CDROMs, but FreeBSD still halt at the > > > "waiting 15 seconds". It seems the problem is on the card? > > > > No, I don't think it is a problem with the card per se. However, it might be > > an issue with how we configure interrupts. > > Thanks for your reply first !! > In your opinion, that is some problem aboout interrupt / IRQs? That is my guess, yes. > > Maybe I have to move the card to another computer and try... Just using an older kernel might be all you need to test the cards. My assumption here is that you have been running FreeBSD for a while, and that upgrading to current was what got you into this state. > > > > Hm, it is interssting that you see the problem on UP when I don't. > > What does your mptable output look like? > > Excuse me, what is "mptable" :) Do a man on mptable :-). It is a utility that shows what your interrupt routing etc looks like. It is supposed to work on UP kernels as well, so give it a whirl. (Of course this assumes that you can boot a FreeBSD kernel that doesn't hang on you ). > > Due to I can boot normally with 4.0-0408, I have use boot -v and see > something interesting but I do not understand, is that what you want? It never hurts to capture the boot -v sequence when you are having trouble. I am in the process of collecting that my self, but my remote console setup is currently broken. Once I have that fixed, I'll get a boot -v captured for my system as well. Of course there is a chance that this whole problem might go away if someone else stumbles upon the problem first :-) Lars > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 11 9: 8:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 02DCA14CA9 for ; Tue, 11 May 1999 09:08:32 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id RAA00807; Tue, 11 May 1999 17:51:17 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id QAA01469; Tue, 11 May 1999 16:28:51 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905111428.QAA01469@yedi.iaf.nl> Subject: Re: problem with non-rewinding device on DLT / using dump ? In-Reply-To: <199905110806.SAA28834@nymph.detir.qld.gov.au> from Stephen McKay at "May 11, 1999 6: 6:50 pm" To: syssgm@detir.qld.gov.au (Stephen McKay) Date: Tue, 11 May 1999 16:28:51 +0200 (CEST) Cc: freebsd-scsi@FreeBSD.ORG, syssgm@detir.qld.gov.au, roberto@keltia.freenix.fr 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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Stephen McKay wrote ... > On Sunday, 9th May 1999, Wilko Bulte wrote: > > >As Ollivier Robert wrote ... > >> According to Wilko Bulte: > >> > make that: restore -s 3 -b64 -i -f /dev/nrsa2 > >> > > >> > and it works a whole lot better. > >> > >> I thought restore(8) was supposed to find the blocksize itself... > > > >Well... with -b64 I can restore things, without I can't. So I guess restore > >can not do it. > > It can guess as high as 32KB, but no higher. Changing HIGHDENSITYTREC to > 64 would cause dump to write in 64KB blocks for most devices and cause > restore to guess as large as 64KB. > > But, I think that some QIC tape devices will fail because 64KB blocks are > illegal in some modes. I find that 32KB works for me for all drive types > that I use (QIC old and new, Exabyte 8200 thru 8505). Any reason why > you don't use 32KB? DLTs stream better using bigger block sizes. Groeten / Cheers, | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 11 9:30:29 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from scanman.cinesite.co.uk (cinesite1.sohonet.co.uk [193.203.80.4]) by hub.freebsd.org (Postfix) with ESMTP id D405F14BEE for ; Tue, 11 May 1999 09:30:26 -0700 (PDT) (envelope-from hxpro@cinesite.co.uk) Received: from servalan.cinesite.co.uk (servalan.cinesite.co.uk [10.123.10.65]) by scanman.cinesite.co.uk (8.9.1a/8.9.1) with SMTP id RAA11207 for <@scanman.cinesite.co.uk:freebsd-scsi@FreeBSD.ORG>; Tue, 11 May 1999 17:30:26 +0100 (BST) Received: from cinesite.co.uk by servalan.cinesite.co.uk via ESMTP (950413.SGI.8.6.12/930416.SGI) for id RAA10313; Tue, 11 May 1999 17:30:25 +0100 Message-ID: <37385B21.8884356D@cinesite.co.uk> Date: Tue, 11 May 1999 17:30:25 +0100 From: "Kevin (HxPro) Wheatley" Organization: Cinesite Digital Studios X-Mailer: Mozilla 4.51 [en] (X11; I; IRIX 6.2 IP22) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: Emulating a SCSI tape device ... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I was was wondering about the possibility of using FreeBSD to emulate a SCSI tape device, with the view to buffer files on disc, before writing to slow tape devices, accessing via NFS etc. Has anybody got any pointers to this sort of thing ?? Thanks Kevin -- | Kevin Wheatley | These are the opinions of nobody | | Technical Services Manager | and are not shared by my employers | | Cinesite Digital Studios | | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 11 10: 2:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 075C4155B1 for ; Tue, 11 May 1999 10:02:38 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id LAA29185; Tue, 11 May 1999 11:02:32 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905111702.LAA29185@panzer.plutotech.com> Subject: Re: Emulating a SCSI tape device ... In-Reply-To: <37385B21.8884356D@cinesite.co.uk> from "Kevin (HxPro) Wheatley" at "May 11, 1999 5:30:25 pm" To: hxpro@cinesite.co.uk (Kevin (HxPro) Wheatley) Date: Tue, 11 May 1999 11:02:32 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kevin (HxPro) Wheatley wrote... > Hi, > > I was was wondering about the possibility of using FreeBSD to emulate a > SCSI tape device, with the view to buffer files on disc, before writing > to slow tape devices, accessing via NFS etc. Has anybody got any > pointers to this sort of thing ?? You could do it by writing a target mode tape driver to act like a tape drive and accept the data. Then it would pass the data to a userland program for storage on disk somewhere. Then you can grab the data off the disk and write it to the slow tape drive. I think the only controllers that we support target mode for now are the Adaptec 7890 and probably the 7895. Justin would know for sure. I think some of the Qlogic boards support target mode as well, I don't know if Matt has gotten the hooks in the driver yet. The practicality of doing something like this would depend on what you're trying to use to write the data. It would probably be a good bit easier to write the data over a network to the FreeBSD box, if that's possible. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 11 10:18: 2 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from scanman.cinesite.co.uk (cinesite1.sohonet.co.uk [193.203.80.4]) by hub.freebsd.org (Postfix) with ESMTP id C077D155A5 for ; Tue, 11 May 1999 10:17:59 -0700 (PDT) (envelope-from hxpro@cinesite.co.uk) Received: from servalan.cinesite.co.uk (servalan.cinesite.co.uk [10.123.10.65]) by scanman.cinesite.co.uk (8.9.1a/8.9.1) with SMTP id SAA11632; Tue, 11 May 1999 18:17:58 +0100 (BST) Received: from cinesite.co.uk by servalan.cinesite.co.uk via ESMTP (950413.SGI.8.6.12/930416.SGI) id SAA12064; Tue, 11 May 1999 18:17:56 +0100 Message-ID: <37386644.AAB8BB5@cinesite.co.uk> Date: Tue, 11 May 1999 18:17:56 +0100 From: "Kevin (HxPro) Wheatley" Organization: Cinesite Digital Studios X-Mailer: Mozilla 4.51 [en] (X11; I; IRIX 6.2 IP22) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Emulating a SCSI tape device ... References: <199905111702.LAA29185@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 think the only controllers that we support target mode for now are the > Adaptec 7890 and probably the 7895. Justin would know for sure. I think > some of the Qlogic boards support target mode as well, I don't know if Matt > has gotten the hooks in the driver yet. > > The practicality of doing something like this would depend on what you're > trying to use to write the data. It would probably be a good bit easier to > write the data over a network to the FreeBSD box, if that's possible. > I'm unable to do this, otherwise I'd just use one of our SGIs (which can't easily be put into target mode BTW). I'm basically talking about a data rate of a few MB/s (max circa 10MB/s I think) from a film scanner, each file is written in tar format to tape, with files generally 12MB in size, although 100MB+ are possible. Normally we'd use either SONY DTF GY-2120 (12 MB/s) or Ampex DST (15+MB/s) tape drives, but because of the lack of streaming from such a low data rate, and the tape drives not having a big enough RAM buffer, the tape drives get quite a bit of wear on them. Using a DLT 7000, of a Mamouth Drive, have a different problem, they slow the scanner down due to the seek times. I thought that an emulation system would just plug in place of one of the tape drives. Kevin -- | Kevin Wheatley | These are the opinions of nobody | | Technical Services Manager | and are not shared by my employers | | Cinesite Digital Studios | | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 11 18:23: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id AB5AD150E7 for ; Tue, 11 May 1999 18:22:11 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id KAA10147; Wed, 12 May 1999 10:51:43 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <37385B21.8884356D@cinesite.co.uk> Date: Wed, 12 May 1999 10:51:42 +0930 (CST) From: "Daniel O'Connor" To: "Kevin (HxPro) Wheatley" Subject: RE: Emulating a SCSI tape device ... Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 11-May-99 Kevin (HxPro) Wheatley wrote: > I was was wondering about the possibility of using FreeBSD to emulate a > SCSI tape device, with the view to buffer files on disc, before writing > to slow tape devices, accessing via NFS etc. Has anybody got any > pointers to this sort of thing ?? You could try team (ports/misc/team) it doesn't buffer on disk (rather in memory) but it is quite handy for speeding slow tapes by feeding the continuously. --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 11 21: 3:15 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from revolution.3-cities.com (revolution.3-cities.com [204.203.224.155]) by hub.freebsd.org (Postfix) with ESMTP id 3103B14BCF for ; Tue, 11 May 1999 21:03:12 -0700 (PDT) (envelope-from msmith@revolution.3-cities.com) Received: (from msmith@localhost) by revolution.3-cities.com (8.9.3/8.9.3) id VAA14253 for freebsd-scsi@freebsd.org; Tue, 11 May 1999 21:03:12 -0700 (PDT) From: Mark D Smith Message-Id: <199905120403.VAA14253@revolution.3-cities.com> Subject: NEC SCSI CD problems To: freebsd-scsi@freebsd.org Date: Tue, 11 May 1999 21:03:12 -0700 (PDT) X-Mailer: ELM [version 2.4 PL25] 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 Greetings, Below is some snippage from my messages file. I have an NEC 462, firmware rev 1.15, CD ROM player that won't work with cdcontrol! The system is an ASUS P55T2P4S with the Adaptec AIC7880 UW SCSI chip. 1. cdcdontrol and the music cd will play in the plextor. 2. windoze 95 and NT and DOS will play the music disk in the NEC. 3. the NEC will mount and read a data only CD just fine. 4. the ONLY problem is when I try to use the NEC to play a music cd and use cdcontrol to do it with, then I get the following: May 9 23:57:13 mark /kernel: (cd1:ahc0:0:2:0): PLAY AUDIO(12). CDB: a5 0 0 0 0 0 0 3 a5 9 0 0 May 9 23:57:13 mark /kernel: (cd1:ahc0:0:2:0): ILLEGAL REQUEST asc:64,0 May 9 23:57:13 mark /kernel: (cd1:ahc0:0:2:0): Illegal mode for this track This is how the boot probe shows May 9 23:26:38 mark /kernel: cd0: Removable CD-RO M SCSI-2 device May 9 23:26:38 mark /kernel: cd0: 10.0MB/s transfers (10.0MHz, offset 15) May 9 23:26:38 mark /kernel: cd0: Attempt to query device size failed: NOT READ Y, Medium not present May 9 23:26:37 mark /kernel: cd1 at ahc0 bus 0 target 2 lun 0 May 9 23:26:38 mark /kernel: cd1: Removable CD-ROM SCSI-2 device May 9 23:26:38 mark /kernel: cd1: 10.0MB/s transfers (10.0MHz, offset 15) May 9 23:26:38 mark /kernel: cd1: cd present [238857 x 2048 byte records] Any ideas? Mark -- ========================================================================= For sale: 1978 VW Van, Champaign Edition, 13,000 miles on new engine with fuel injection. $2500 To see pictures and contact information go to http://www.3-cities.com/~msmith/vw.html UNIX IS user friendly, it's just very choosy about who it calls a friend! ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 11 21:40:13 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 2B3EF1585B for ; Tue, 11 May 1999 21:40:09 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id WAA32726; Tue, 11 May 1999 22:39:57 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905120439.WAA32726@panzer.plutotech.com> Subject: Re: NEC SCSI CD problems In-Reply-To: <199905120403.VAA14253@revolution.3-cities.com> from Mark D Smith at "May 11, 1999 9: 3:12 pm" To: msmith@revolution.3-cities.com (Mark D Smith) Date: Tue, 11 May 1999 22:39:57 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mark D Smith wrote... > Greetings, > > Below is some snippage from my messages file. I have an NEC 462, > firmware rev 1.15, CD ROM player that won't work with cdcontrol! The > system is an ASUS P55T2P4S with the Adaptec AIC7880 UW SCSI chip. > > 1. cdcdontrol and the music cd will play in the plextor. > 2. windoze 95 and NT and DOS will play the music disk in the NEC. > 3. the NEC will mount and read a data only CD just fine. > 4. the ONLY problem is when I try to use the NEC to play a music cd > and use cdcontrol to do it with, then I get the following: > > May 9 23:57:13 mark /kernel: (cd1:ahc0:0:2:0): PLAY AUDIO(12). CDB: a5 0 0 0 0 > 0 0 3 a5 9 0 0 > May 9 23:57:13 mark /kernel: (cd1:ahc0:0:2:0): ILLEGAL REQUEST asc:64,0 > May 9 23:57:13 mark /kernel: (cd1:ahc0:0:2:0): Illegal mode for this track > > This is how the boot probe shows [ ... ] > May 9 23:26:37 mark /kernel: cd1 at ahc0 bus 0 target 2 lun 0 > May 9 23:26:38 mark /kernel: cd1: Removable CD-ROM > SCSI-2 device > May 9 23:26:38 mark /kernel: cd1: 10.0MB/s transfers (10.0MHz, offset 15) > May 9 23:26:38 mark /kernel: cd1: cd present [238857 x 2048 byte records] The problem is that your NEC drive doesn't work with the standard 12 byte SCSI-2 audio play command. I think the problem is that it has a vendor unique play command. cdcontrol uses the ioctl interface to the CD driver to do all of its operations. The ioctl interface generally uses the standard SCSI-2 method to talk to CDROM drives. It's just that your NEC drive doesn't really conform to the standard for audio playback. Don't worry, you're not alone here: cd0 at ahc0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.300MB/s transfers cd0: Attempt to query device size failed: NOT READY, Medium not present (cd0:ahc0:0:4:0): PLAY AUDIO(12). CDB: a5 0 0 0 0 0 0 3 77 71 0 0 (cd0:ahc0:0:4:0): ILLEGAL REQUEST asc:20,0 (cd0:ahc0:0:4:0): Invalid command operation code And I wrote the driver! :) The reason NT, 95 and DOS all work okay is because they know about NEC's vendor-unique command and use it to play CDs on NEC CDROM drives. I remember back in the days when I ran OS/2 on the computer that has the NEC drive on it, I had to load a special driver for NEC CDROM drives. I'm sure that driver had the information on how to send NEC's vendor unique play commands. To solve your problem, I would recommend installing xmcd. (ports/audio/xmcd) xmcd is certainly my favorite cd player, and it'll talk to your NEC drive just fine. It's got code to generate vendor-unique commands for all sorts of drives. It also comes with a command line utility called "cda" that even supports cddb. xmcd uses the pass(4) driver to talk directly to your cdrom drive, so it won't run into the same problem with the ioctl interface. Long term, I probably need to put a quirk facility in the cd driver to handle drives that use vendor-unique commands. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 11 22:33:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from revolution.3-cities.com (revolution.3-cities.com [204.203.224.155]) by hub.freebsd.org (Postfix) with ESMTP id 9690A14ED2 for ; Tue, 11 May 1999 22:33:24 -0700 (PDT) (envelope-from msmith@revolution.3-cities.com) Received: (from msmith@localhost) by revolution.3-cities.com (8.9.3/8.9.3) id WAA27535; Tue, 11 May 1999 22:33:21 -0700 (PDT) From: Mark D Smith Message-Id: <199905120533.WAA27535@revolution.3-cities.com> Subject: Re: NEC SCSI CD problems To: ken@plutotech.com (Kenneth D. Merry) Date: Tue, 11 May 1999 22:33:20 -0700 (PDT) Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: <199905120439.WAA32726@panzer.plutotech.com> from "Kenneth D. Merry" at May 11, 99 10:39:57 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The problem is that your NEC drive doesn't work with the standard 12 byte > SCSI-2 audio play command. I think the problem is that it has a vendor > unique play command. OUUUUCH! Well, it only cost me $35, so no big deal. > Don't worry, you're not alone here: Misery loves company. > To solve your problem, I would recommend installing xmcd. Thanks! I'll do that and play with it. > Long term, I probably need to put a quirk facility in the cd driver to > handle drives that use vendor-unique commands. It would be apreciated! Many thanks! Mark -- ========================================================================= For sale: 1978 VW Van, Champaign Edition, 13,000 miles on new engine with fuel injection. $2500 To see pictures and contact information go to http://www.3-cities.com/~msmith/vw.html UNIX IS user friendly, it's just very choosy about who it calls a friend! ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 12 10: 8:48 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from sparcy.delanet.com (sparcy.delanet.com [208.9.136.54]) by hub.freebsd.org (Postfix) with SMTP id 29BF114CA3 for ; Wed, 12 May 1999 10:08:44 -0700 (PDT) (envelope-from stevec@delanet.com) Received: (qmail 2002 invoked from network); 12 May 1999 17:03:18 -0000 Received: from somnus.delanet.com (HELO delanet.com) (208.9.136.84) by sparcy.delanet.com with SMTP; 12 May 1999 17:03:18 -0000 Message-ID: <3739B608.F0D93CAD@delanet.com> Date: Wed, 12 May 1999 13:10:32 -0400 From: "Stephen C. Comoletti" Organization: DelaNET X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 3.0-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: transfer rate on qlogic 1040/seagate incorrect? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello. I posted this once to freebsd-questions with no reply..figured I'd try here as this is the more appropriate spot for it. I have a DEC 300i+ with a qlogic 1040 uw-scsi controller, and a seagate barracuda 9.1gig 68pin drive. Under 3.1r it was detected correctly. After cvsupping to 3.1s/3.2b and recompiling the kernel it now detects the transfer rate of the drive as 3.300mb/s instead of the previous 40mb/s. I did notice the cam drivers have been updated. No changes were made to the kernel other than removing a few unused devices to slim it down and increasing maxusers. I'm at a loss as to how to fix this..any help would be appreciated. Below is a copy of the boot probe both before and after the upgrade. If you could cc me on any replies I'd appreciate it as I'm not on this list. Regards, -- Stephen C. Comoletti Systems Administrator DELANET, Inc. http://www.delanet.com TEL: (302) 326-5800, FAX: (302) 326-5802 -- before -- May 11 09:53:24 somnus2 /kernel: Qlogic ISP Driver, FreeBSD CAM Version 0.98,Core Version 1.5 May 11 09:53:24 somnus2 /kernel: isp0: rev0x05 int a irq 9 on pci2.6.0 May 11 09:53:24 somnus2 /kernel: isp0: using Memory space register mapping May 11 09:53:24 somnus2 /kernel: isp0: Board Revision 1040B, loaded F/W Revision 7.55 May 11 09:53:24 somnus2 /kernel: isp0: Last F/W revision was 4.50 May 11 09:53:24 somnus2 /kernel: Waiting 15 seconds for SCSI devices to settle May 11 09:53:24 somnus2 /kernel: isp0: driver initiated bus reset May 11 09:53:24 somnus2 /kernel: de0: enabling 10baseT port May 11 09:53:24 somnus2 /kernel: changing root device to da0s1a May 11 09:53:24 somnus2 /kernel: da0 at isp0 bus 0 target 0 lun 0 May 11 09:53:24 somnus2 /kernel: da0: Fixed Direct Access SCSI-2 device May 11 09:53:24 somnus2 /kernel: da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled May 11 09:53:24 somnus2 /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) -- after -- May 11 18:30:41 somnus2 /kernel: Qlogic ISP Driver, FreeBSD CAM Version 0.991, Core Version 1.8 May 11 18:30:41 somnus2 /kernel: isp0: rev 0x05 int a irq 9 on pci2.6.0 May 11 18:30:41 somnus2 /kernel: isp0: using Memory space register mapping May 11 18:30:41 somnus2 /kernel: isp0: set PCI line size to 16 May 11 18:30:41 somnus2 /kernel: isp0: Ultra Mode Capable May 11 18:30:41 somnus2 /kernel: isp0: Board Revision 1040B, loaded F/W Revision 7.63.0 May 11 18:30:41 somnus2 /kernel: isp0: Last F/W revision was 4.50.0 May 11 18:30:41 somnus2 /kernel: Waiting 15 seconds for SCSI devices to settle May 11 18:30:41 somnus2 /kernel: isp0: driver initiated bus reset of bus 0 May 11 18:30:41 somnus2 /kernel: de0: enabling 10baseT port May 11 18:30:41 somnus2 /kernel: da0 at isp0 bus 0 target 0 lun 0 May 11 18:30:41 somnus2 /kernel: da0: Fixed Direct Access SCSI-2 device May 11 18:30:41 somnus2 /kernel: da0: 3.300MB/s transfers, Tagged Queueing Enabled May 11 18:30:41 somnus2 /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 12 10:28:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 51B5614F80 for ; Wed, 12 May 1999 10:28:15 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA23517; Wed, 12 May 1999 10:27:52 -0700 Date: Wed, 12 May 1999 10:27:52 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Stephen C. Comoletti" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: transfer rate on qlogic 1040/seagate incorrect? In-Reply-To: <3739B608.F0D93CAD@delanet.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'm a little confused as to which release you've moved up to. I'm the guilty party here, and I have to say I've stubbed my toes a couple of times on this one. Not only is this at ASYNC mode but it's also now narrow. Hang on for a second... I'll check my configuration...Arghh..... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 12 11: 4: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id BC25914C12 for ; Wed, 12 May 1999 11:03:57 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA23683; Wed, 12 May 1999 11:03:46 -0700 Date: Wed, 12 May 1999 11:03:46 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Stephen C. Comoletti" Cc: freebsd-scsi@freebsd.org Subject: Re: transfer rate on qlogic 1040/seagate incorrect? In-Reply-To: <3739BC54.B381D5C8@delanet.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 Okay, here's what's happening. You in fact probably are running at wide && Ultra mode: From my 3.2B machine: Intel Pentium detected, installing workaround for F00F bug Waiting 15 seconds for SCSI devices to settle isp0: driver initiated bus reset of bus 0 isp0: 0.4 get user period 0xc offset 0x8 flags 0xfd00 isp0: 0.4 get current period 0x0 offset 0x0 flags 0x0 isp0: 0.4 set current period 0xc offset 0x8 flags 0xfd00 isp0: bus 0 set tgt 4 flags 0xfd00 off 0x8 period 0xc changing root device to wd0s1a da0 at isp0 bus 0 target 4 lun 0 da0: Fixed Direct Access SCSI-2 device isp0: 0.4 get current period 0x0 offset 0x0 flags 0x800 da0: 3.300MB/s transfers, Tagged Queueing Enabled da0: 4148MB (8496884 512 byte sectors: 255H 63S/T 528C) Huh? 3.3MB/s? Huh? but.... semuta.feral.com > root lmdd if=/dev/rda0 bs=64k ^C44.00 MB in 4.87 seconds (9.0387 MB/sec) Well- That ain't ASYNC mode! -------------------- Here's the sequence... A) At startup the ISP driver deliberately negotiates narrow/async mode (iff the loaded f/w >= 7.55). B) Later on, the CAM midlayer asks "What are you capable of"- The ISP driver says "Ultra, offset 8, wide, ....". C) The CAM midlayer says "Make it so....". The ISP driver then instructs the ISP card to do so. However, it continues, when asked what the current state is, to say what it has been told by the ISP it is. D) The ISP chip is supposed to set, if it renegotiates a rate, a bit on a response packet that says a new rate was renegotiated. That's supposed to be the trigger to go off again and ask it what the current rates are. I've found that it doesn't always do so! Argh! What I used to do after asking it to set new rates was to ask it right away what the new rates are. This is wrong because it needs to run at least one command to do the negotiation. It's also wrong because the f/w actually started returning random values for what it has set. I told Qlogic, but they really had trouble reproducing/fixing it, so I decided to just live with it. --------------------- Like you *I* find such a message about 3.3MB/s alarming and disconcerting- I guess I'm saying that I haven't quite found a good way to get the chip to tell me truthfully what the heck it's set for at the times that the CAM subsystem queries me about the settings. I'm still fiddling with it. If I find something and it can get into 3.2, I'll ask Jordan to let me put it in. Otherwise, err, umm 'sorry'! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 12 16:26:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from atlrel1.hp.com (atlrel1.hp.com [156.153.255.210]) by hub.freebsd.org (Postfix) with ESMTP id 38DB615675 for ; Wed, 12 May 1999 16:25:54 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by atlrel1.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id TAA05444; Wed, 12 May 1999 19:25:16 -0400 (EDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA095531529; Wed, 12 May 1999 16:25:29 -0700 Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_14041)/8.7.3 TIS 5.0) id QAA14502; Wed, 12 May 1999 16:25:28 -0700 (PDT) Message-Id: <199905122325.QAA14502@mina.sr.hp.com> To: Karl Denninger Cc: mjacob@feral.com, freebsd-scsi@FreeBSD.ORG Subject: Re: Question - Onstream SCSI Streamer Reply-To: Darryl Okahata In-Reply-To: Your message of "Sat, 08 May 1999 00:19:36 CDT." <19990508001936.A597@Denninger.Net> Mime-Version: 1.0 (generated by tm-edit 1.1.1.1) Content-Type: text/plain; charset=US-ASCII Date: Wed, 12 May 1999 16:25:27 -0700 From: Darryl Okahata Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Karl Denninger wrote: > Well, I added a quirk entry for the OnStream (and support for "rewind > immediate" in general) to the SA driver. > > All that did for me is discover that the Onstream also refuses to respond to > an inquiry for block limits (!) > > I'm going to try a few other things here before giving up on this quest and > waiting for someone to get real documentation, but I'm not encouraged by > what I'm seeing so far. It also appears that the drive only supports 32KB sectors. ;-( See the appended message. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. =============================================================================== From: Kurt Godwin Subject: Re: More OnStream commentary (followup) Newsgroups: comp.sys.ibm.pc.hardware.storage Date: Tue, 11 May 1999 19:03:54 GMT Organization: Deja.com - Share what you know. Learn what you don't. In article <3735f1e6.17806602@basement>, please@see.sig (SteveR) wrote: > On Tue, 27 Apr 1999 16:26:51 GMT, Kurt Godwin > wrote: > >The REAL fix from Microsoft will be available soon (at > >http://support.microsoft.com/support/kb/articles/q224/0/73.asp) > >Keep checking this url, it should be up soon. > > Yup. It's there. Ya gotta love Microsoft. They admittedly screw up > then put all kinds of hoops out for users to jump through (call > Microsoft paid support line to get access to the fix...) when a simple > download would have done the job far more directly. Arrgh. Maybe > whoever gets to this first can post it in > alt.binaries.shareware.ibm.pc, or somewhere equally accessible. > > Hey Kurt, when are we going to get the other issues with Echo > addressed? You know, like large block sizes, multi-tape backups, and > optional installation of Echo "features"? > SteveR > m.a.i.l.t.o.: > s.r.r.2 a.t r.c.n d.o.t c.o.m > The next version of Echo software is scheduled for June (probably end of June). The OnStream drive supports only 32K sectors. We have added code to compress files within sectors (this changes the backup format), and allows better use of the tape. This fix will only work with backups, as copying files to the tape will not change. I should mention that this "limitation" is a physical limitation with the drive, and not clustering issue. Our backup product creates files on the tape (or other media) Multi-tape backups (or tape linking) will be in this version as well (end of june) As far as "optional" installation of features, I don't know what you mean. The only "optional" component of our system is the backup engine (pconfig.exe), and if you don't want to use it, just don't run it. The rest of the product is not divisible. If you don't want to use our backup product, the tape drive letter ( usually T: )is there for you to use however you wish. Microsoft Backup will work with it as well as any other program that creates files. What is it that you don't want to install? --== Sent via Deja.com http://www.deja.com/ ==-- ---Share what you know. Learn what you don't.--- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 12 16:31:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (Postfix) with ESMTP id 99F8915AF2 for ; Wed, 12 May 1999 16:31:27 -0700 (PDT) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id SAA20419; Wed, 12 May 1999 18:28:41 -0500 (CDT) Message-ID: <19990512182841.A20409@Denninger.Net> Date: Wed, 12 May 1999 18:28:41 -0500 From: Karl Denninger To: Darryl Okahata Cc: mjacob@feral.com, freebsd-scsi@FreeBSD.ORG Subject: Re: Question - Onstream SCSI Streamer References: <19990508001936.A597@Denninger.Net> <199905122325.QAA14502@mina.sr.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199905122325.QAA14502@mina.sr.hp.com>; from Darryl Okahata on Wed, May 12, 1999 at 04:25:27PM -0700 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, for the kinds of use to which we'd put the device (ie: streaming tape) a 32k block size isn't horrid. I can see where if you tried to use it as a random-access replacement (ie: to write "files" to) you'd be rather unhappy with the wastage that this would cause, but for streaming applications I doubt it hurts much. I'll try hardcoding THAT as a quirk and see if the drive decides it would like to at least get past the open and actually perform I/O :-) -- -- Karl Denninger (karl@denninger.net) Web: fathers.denninger.net I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. On Wed, May 12, 1999 at 04:25:27PM -0700, Darryl Okahata wrote: > Karl Denninger wrote: > > > Well, I added a quirk entry for the OnStream (and support for "rewind > > immediate" in general) to the SA driver. > > > > All that did for me is discover that the Onstream also refuses to respond to > > an inquiry for block limits (!) > > > > I'm going to try a few other things here before giving up on this quest and > > waiting for someone to get real documentation, but I'm not encouraged by > > what I'm seeing so far. > > It also appears that the drive only supports 32KB sectors. ;-( > See the appended message. > > -- > Darryl Okahata > darrylo@sr.hp.com > > DISCLAIMER: this message is the author's personal opinion and does not > constitute the support, opinion, or policy of Hewlett-Packard, or of the > little green men that have been following him all day. > > =============================================================================== > From: Kurt Godwin > Subject: Re: More OnStream commentary (followup) > Newsgroups: comp.sys.ibm.pc.hardware.storage > Date: Tue, 11 May 1999 19:03:54 GMT > Organization: Deja.com - Share what you know. Learn what you don't. > > In article <3735f1e6.17806602@basement>, > please@see.sig (SteveR) wrote: > > On Tue, 27 Apr 1999 16:26:51 GMT, Kurt Godwin > > wrote: > > >The REAL fix from Microsoft will be available soon (at > > >http://support.microsoft.com/support/kb/articles/q224/0/73.asp) > > >Keep checking this url, it should be up soon. > > > > Yup. It's there. Ya gotta love Microsoft. They admittedly screw up > > then put all kinds of hoops out for users to jump through (call > > Microsoft paid support line to get access to the fix...) when a simple > > download would have done the job far more directly. Arrgh. Maybe > > whoever gets to this first can post it in > > alt.binaries.shareware.ibm.pc, or somewhere equally accessible. > > > > Hey Kurt, when are we going to get the other issues with Echo > > addressed? You know, like large block sizes, multi-tape backups, and > > optional installation of Echo "features"? > > SteveR > > m.a.i.l.t.o.: > > s.r.r.2 a.t r.c.n d.o.t c.o.m > > > The next version of Echo software is scheduled for June (probably end > of June). > The OnStream drive supports only 32K sectors. We have added code to > compress files within sectors (this changes the backup format), and > allows better use of the tape. This fix will only work with backups, > as copying files to the tape will not change. I should mention that > this "limitation" is a physical limitation with the drive, and not > clustering issue. Our backup product creates files on the tape (or > other media) > > Multi-tape backups (or tape linking) will be in this version as well > (end of june) > > As far as "optional" installation of features, I don't know what you > mean. The only "optional" component of our system is the backup engine > (pconfig.exe), and if you don't want to use it, just don't run it. > The rest of the product is not divisible. If you don't want to use our > backup product, the tape drive letter ( usually T: )is there for you > to use however you wish. Microsoft Backup will work with it as well as > any other program that creates files. > > What is it that you don't want to install? > > > > --== Sent via Deja.com http://www.deja.com/ ==-- > ---Share what you know. Learn what you don't.--- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 12 16:38:52 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 8B9E815E04 for ; Wed, 12 May 1999 16:38:46 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by palrel3.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id QAA18963; Wed, 12 May 1999 16:38:24 -0700 (PDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA099012300; Wed, 12 May 1999 16:38:20 -0700 Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_14041)/8.7.3 TIS 5.0) id QAA14698; Wed, 12 May 1999 16:38:19 -0700 (PDT) Message-Id: <199905122338.QAA14698@mina.sr.hp.com> To: Karl Denninger Cc: mjacob@feral.com, freebsd-scsi@FreeBSD.ORG Subject: Re: Question - Onstream SCSI Streamer Reply-To: Darryl Okahata In-Reply-To: Your message of "Wed, 12 May 1999 18:28:41 CDT." <19990512182841.A20409@Denninger.Net> Mime-Version: 1.0 (generated by tm-edit 1.1.1.1) Content-Type: text/plain; charset=US-ASCII Date: Wed, 12 May 1999 16:38:19 -0700 From: Darryl Okahata Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Karl Denninger wrote: > Well, for the kinds of use to which we'd put the device (ie: streaming > tape) a 32k block size isn't horrid. I can see where if you tried to use > it as a random-access replacement (ie: to write "files" to) you'd be rather > unhappy with the wastage that this would cause, but for streaming > applications I doubt it hurts much. True. I was just mentioning that as an example of how "different" the OnStream drive is from traditional SCSI tape drives. > I'll try hardcoding THAT as a quirk and see if the drive decides it would > like to at least get past the open and actually perform I/O :-) Heh. I really, really hope it works, but I'll bet that there are enough other quirks that it won't. ;-( -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 12 18: 1:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (Postfix) with ESMTP id 4CC5714CFD for ; Wed, 12 May 1999 18:01:41 -0700 (PDT) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id TAA20684; Wed, 12 May 1999 19:59:07 -0500 (CDT) Message-ID: <19990512195907.A20680@Denninger.Net> Date: Wed, 12 May 1999 19:59:07 -0500 From: Karl Denninger To: Darryl Okahata Cc: mjacob@feral.com, freebsd-scsi@FreeBSD.ORG Subject: Re: Question - Onstream SCSI Streamer References: <19990512182841.A20409@Denninger.Net> <199905122338.QAA14698@mina.sr.hp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199905122338.QAA14698@mina.sr.hp.com>; from Darryl Okahata on Wed, May 12, 1999 at 04:38:19PM -0700 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 12, 1999 at 04:38:19PM -0700, Darryl Okahata wrote: > Karl Denninger wrote: > > > Well, for the kinds of use to which we'd put the device (ie: streaming > > tape) a 32k block size isn't horrid. I can see where if you tried to use > > it as a random-access replacement (ie: to write "files" to) you'd be rather > > unhappy with the wastage that this would cause, but for streaming > > applications I doubt it hurts much. > > True. I was just mentioning that as an example of how "different" > the OnStream drive is from traditional SCSI tape drives. > > > I'll try hardcoding THAT as a quirk and see if the drive decides it would > > like to at least get past the open and actually perform I/O :-) > > Heh. I really, really hope it works, but I'll bet that there are > enough other quirks that it won't. ;-( Well, this IS the fun of doing stuff like this without a low-level hardware MANUAL! :-) -- -- Karl Denninger (karl@denninger.net) Web: fathers.denninger.net I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 0:38:51 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from postoffice.aeonflux.net (postoffice.aeonflux.net [208.139.254.10]) by hub.freebsd.org (Postfix) with ESMTP id AD19E14D5B for ; Thu, 13 May 1999 00:38:49 -0700 (PDT) (envelope-from webmaster@aeonflux.net) Received: from interstel (interstel.aeonflux.net [208.139.254.31]) by postoffice.aeonflux.net (8.8.8/8.8.7/PCS9711a) with SMTP id DAA11177 for ; Thu, 13 May 1999 03:38:48 -0400 (EDT) Message-Id: <3.0.5.32.19990513033700.01c38a50@aeonflux.net> X-Sender: jfporter@aeonflux.net (Unverified) X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Thu, 13 May 1999 03:37:00 -0400 To: freebsd-scsi@FreeBSD.ORG From: James Porter Subject: Adaptec 2940UW PCI Controller BIOS rev 1.34.3 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 searched around the archives for a solution to a now critial problem for us here. We're a small ISP and use lowly Intel PC's with UW SCSI's. We have been running fine under a wide range of FreeBSD verions over the last 2 years from 1.2.1 through 3.1r. In the past we had encountered an apparently unreferenced problem when trying to use AHA 2940UW bios revisions higher than 1.26 which caused the controller to either never load our drives or spend forever doing SCSI BUS Resets on Channel A. Our solution was simply to keep location BIOS rev 1.26 controllers. Unfortunately this has now become impossible. We had hoped that 3.1R would correct this problem but we have found it hasn't. And the only card Adaptec is shipping or that anyone has on their shelves now is BIOS rev 1.34.3. And it generates the same problem with or without a drive attached. We even tried setting an EIDE boot drive and then adding the controller with or without drive and it still hangs. Is there a solution or fix out there because this is a critical problem now for us. James Porter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 11: 1:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id B983E14ED9 for ; Thu, 13 May 1999 11:01:24 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id NAA01509 for ; Thu, 13 May 1999 13:59:01 -0400 (EDT) Date: Thu, 13 May 1999 13:59:01 -0400 (EDT) From: Chuck Robey To: freebsd-scsi@freebsd.org Subject: IBM scsi drives 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 Anyone got experience with an IBM scsi drive, DDRS34560W-LVD? Their web page says the LVD stands for low voltage differential, and I've got bad memories of dealing with Quantum differentials ... the IBM data says it's fully compatible, on my existing bus, with single-ended scsi (at a lower transfer rate, only 40MB), but I'm wondering. At $175 for 4.5G, it seems like it would be a good deal if I knew it to work .... does anyone have any experience with it? BTW, this is for a hobby system, not a professional system, so anyone suggesting I spend triple the price for extra reliability is going to be politely ignored. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 11:11:25 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E754115166 for ; Thu, 13 May 1999 11:11:23 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA27985; Thu, 13 May 1999 11:11:10 -0700 Date: Thu, 13 May 1999 11:11:09 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Chuck Robey Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IBM scsi drives In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've had some reasonable good experiences in some contexts with the IBM drives- but they have a wierd property of not working if your host adapter negotiates sync speeds before negotiating wide. Make sure these drives work for you before you pay! On Thu, 13 May 1999, Chuck Robey wrote: > Anyone got experience with an IBM scsi drive, DDRS34560W-LVD? Their web > page says the LVD stands for low voltage differential, and I've got bad > memories of dealing with Quantum differentials ... the IBM data says > it's fully compatible, on my existing bus, with single-ended scsi (at a > lower transfer rate, only 40MB), but I'm wondering. > > At $175 for 4.5G, it seems like it would be a good deal if I knew it to > work .... does anyone have any experience with it? > > BTW, this is for a hobby system, not a professional system, so anyone > suggesting I spend triple the price for extra reliability is going to be > politely ignored. > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@picnic.mat.net | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run picnic (FreeBSD-current) > (301) 220-2114 | and jaunt (Solaris7). > ----------------------------+----------------------------------------------- > > > > > > > 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 May 13 11:17:16 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id AF567150FE for ; Thu, 13 May 1999 11:17:12 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id OAA01558; Thu, 13 May 1999 14:14:35 -0400 (EDT) Date: Thu, 13 May 1999 14:14:35 -0400 (EDT) From: Chuck Robey To: Matthew Jacob Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IBM scsi drives In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 13 May 1999, Matthew Jacob wrote: > > > I've had some reasonable good experiences in some contexts with the IBM > drives- but they have a wierd property of not working if your host adapter > negotiates sync speeds before negotiating wide. Make sure these drives > work for you before you pay! Tried that. Price I quoted is from TJT Intl, and they have a 30 day guarantee, except they charge a 15% restocking fee, so I was hunting more assurance. I want to stick it on a bus with 3 existing IBM 34330W drives, and the 34560 will be the only LVD drive. Those old Quantum differential drives burned a warning message into my soul. That was a 50 pin bus, this is 68 pin, but I'm still wary. The TJT guy says he *thinks* they work ok with ohter drives, excepting the 34560 will not provide a termination, so one of the 34330's will have to do that (no problem there). I just want to see if someone else has some direct experience with the DDRS34560W-LVD. Sure would make me feel better. > > > On Thu, 13 May 1999, Chuck Robey wrote: > > > Anyone got experience with an IBM scsi drive, DDRS34560W-LVD? Their web > > page says the LVD stands for low voltage differential, and I've got bad > > memories of dealing with Quantum differentials ... the IBM data says > > it's fully compatible, on my existing bus, with single-ended scsi (at a > > lower transfer rate, only 40MB), but I'm wondering. > > > > At $175 for 4.5G, it seems like it would be a good deal if I knew it to > > work .... does anyone have any experience with it? > > > > BTW, this is for a hobby system, not a professional system, so anyone > > suggesting I spend triple the price for extra reliability is going to be > > politely ignored. > > > > ----------------------------+----------------------------------------------- > > Chuck Robey | Interests include any kind of voice or data > > chuckr@picnic.mat.net | communications topic, C programming, and Unix. > > 213 Lakeside Drive Apt T-1 | > > Greenbelt, MD 20770 | I run picnic (FreeBSD-current) > > (301) 220-2114 | and jaunt (Solaris7). > > ----------------------------+----------------------------------------------- > > > > > > > > > > > > > > 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 > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 11:24:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id D34761528F for ; Thu, 13 May 1999 11:24:11 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by palrel3.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id LAA03100; Thu, 13 May 1999 11:21:50 -0700 (PDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA272899705; Thu, 13 May 1999 11:21:45 -0700 Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_14041)/8.7.3 TIS 5.0) id LAA06990; Thu, 13 May 1999 11:21:44 -0700 (PDT) Message-Id: <199905131821.LAA06990@mina.sr.hp.com> To: Chuck Robey Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IBM scsi drives Reply-To: Darryl Okahata In-Reply-To: Your message of "Thu, 13 May 1999 13:59:01 EDT." Mime-Version: 1.0 (generated by tm-edit 1.1.1.1) Content-Type: text/plain; charset=US-ASCII Date: Thu, 13 May 1999 11:21:44 -0700 From: Darryl Okahata Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Chuck Robey wrote: > Anyone got experience with an IBM scsi drive, DDRS34560W-LVD? Their web > page says the LVD stands for low voltage differential, and I've got bad > memories of dealing with Quantum differentials ... the IBM data says > it's fully compatible, on my existing bus, with single-ended scsi (at a > lower transfer rate, only 40MB), but I'm wondering. It works. I'm currently using both an IBM 34560 LVD (4.5GB) and an IBM 39130 LVD (9GB) in SE mode (I ordered "wide SCSI drives" and my vendor shipped me LVD ones ;-). They're very nice, and are attached to a Gigabyte 6BXDS (Adaptec 7895) motherboard. I also have another plain F/W (not LVD) IBM 39130 on the same SE bus, and I'm using vinum to stripe the LVD and plain F/W 93130 drives. They work well. The only thing to note about LVD drives is that they have *NO* provision for on-drive termination. All termination must be provided elsewhere. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 11:31:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 005551500A for ; Thu, 13 May 1999 11:31:23 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA28065; Thu, 13 May 1999 11:30:21 -0700 Date: Thu, 13 May 1999 11:30:21 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Chuck Robey Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IBM scsi drives In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > > > > I've had some reasonable good experiences in some contexts with the IBM > > drives- but they have a wierd property of not working if your host adapter > > negotiates sync speeds before negotiating wide. Make sure these drives > > work for you before you pay! > > Tried that. Price I quoted is from TJT Intl, and they have a 30 day > guarantee, except they charge a 15% restocking fee, so I was hunting > more assurance. I want to stick it on a bus with 3 existing IBM 34330W > drives, and the 34560 will be the only LVD drive. You can't mix ultra && LVD. They're one or the other (it's a voltage thingie). > > Those old Quantum differential drives burned a warning message into my > soul. That was a 50 pin bus, this is 68 pin, but I'm still wary. The > TJT guy says he *thinks* they work ok with ohter drives, excepting the > 34560 will not provide a termination, so one of the 34330's will have to > do that (no problem there). > > I just want to see if someone else has some direct experience with the > DDRS34560W-LVD. Sure would make me feel better. I've had experience with Quantum LVD drives and IBM LVD drives, but not particularly under FreeBSD for a variety of complex && uninteresting reasons. The drives I've had to play with are (they're now remote attached to a Sun): 2. c2t8d0 /pci@1f,0/pci@1/scsi@4/sd@8,0 3. c2t9d0 /pci@1f,0/pci@1/scsi@4/sd@9,0 4. c2t10d0 /pci@1f,0/pci@1/scsi@4/sd@a,0 5. c2t11d0 /pci@1f,0/pci@1/scsi@4/sd@b,0 6. c2t12d0 /pci@1f,0/pci@1/scsi@4/sd@c,0 7. c2t13d0 /pci@1f,0/pci@1/scsi@4/sd@d,0 8. c2t14d0 /pci@1f,0/pci@1/scsi@4/sd@e,0 9. c2t15d0 /pci@1f,0/pci@1/scsi@4/sd@f,0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 11:31:28 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from atlrel1.hp.com (atlrel1.hp.com [156.153.255.210]) by hub.freebsd.org (Postfix) with ESMTP id 0AC2C1536D for ; Thu, 13 May 1999 11:31:26 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by atlrel1.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id OAA07973; Thu, 13 May 1999 14:30:31 -0400 (EDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA274930247; Thu, 13 May 1999 11:30:47 -0700 Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_14041)/8.7.3 TIS 5.0) id LAA07103; Thu, 13 May 1999 11:30:46 -0700 (PDT) Message-Id: <199905131830.LAA07103@mina.sr.hp.com> To: Chuck Robey Cc: Matthew Jacob , freebsd-scsi@FreeBSD.ORG Subject: Re: IBM scsi drives Reply-To: Darryl Okahata In-Reply-To: Your message of "Thu, 13 May 1999 14:14:35 EDT." Mime-Version: 1.0 (generated by tm-edit 1.1.1.1) Content-Type: text/plain; charset=US-ASCII Date: Thu, 13 May 1999 11:30:46 -0700 From: Darryl Okahata Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Chuck Robey wrote: > I just want to see if someone else has some direct experience with the > DDRS34560W-LVD. Sure would make me feel better. Just FYI, my IBM LVD drives reports themselves as: da0: Fixed Direct Access SCSI-2 device da1: Fixed Direct Access SCSI-2 device The plain F/W (non-LVD) version reports as: da2: Fixed Direct Access SCSI-2 device Basically, the "W" suffix is used for the non-LVD drive, and the "D" suffix is used on LVD drives. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 11:32:55 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 8E2BD1500A for ; Thu, 13 May 1999 11:32:53 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA28099; Thu, 13 May 1999 11:32:40 -0700 Date: Thu, 13 May 1999 11:32:40 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Chuck Robey Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IBM scsi drives 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 > > > work for you before you pay! > > > > Tried that. Price I quoted is from TJT Intl, and they have a 30 day > > guarantee, except they charge a 15% restocking fee, so I was hunting > > more assurance. I want to stick it on a bus with 3 existing IBM 34330W > > drives, and the 34560 will be the only LVD drive. > > You can't mix ultra && LVD. They're one or the other (it's a voltage > thingie). Let me restate: you can mix the drives, but it'll only be in UltraSE mode. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 11:52:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 2205D1536D for ; Thu, 13 May 1999 11:52:27 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id OAA01700; Thu, 13 May 1999 14:47:30 -0400 (EDT) Date: Thu, 13 May 1999 14:47:29 -0400 (EDT) From: Chuck Robey To: Darryl Okahata Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IBM scsi drives In-Reply-To: <199905131821.LAA06990@mina.sr.hp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 13 May 1999, Darryl Okahata wrote: > Chuck Robey wrote: > > > Anyone got experience with an IBM scsi drive, DDRS34560W-LVD? Their web > > page says the LVD stands for low voltage differential, and I've got bad > > memories of dealing with Quantum differentials ... the IBM data says > > it's fully compatible, on my existing bus, with single-ended scsi (at a > > lower transfer rate, only 40MB), but I'm wondering. > > It works. I'm currently using both an IBM 34560 LVD (4.5GB) and an > IBM 39130 LVD (9GB) in SE mode (I ordered "wide SCSI drives" and my > vendor shipped me LVD ones ;-). They're very nice, and are attached to > a Gigabyte 6BXDS (Adaptec 7895) motherboard. I also have another plain > F/W (not LVD) IBM 39130 on the same SE bus, and I'm using vinum to > stripe the LVD and plain F/W 93130 drives. They work well. > > The only thing to note about LVD drives is that they have *NO* > provision for on-drive termination. All termination must be provided > elsewhere. Thanks Darryl, that's exactly what I wanted to hear! It's already ordered. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 12:10:15 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail-gw3adm.rcsntx.swbell.net (mail-gw3.rcsntx.swbell.net [151.164.30.53]) by hub.freebsd.org (Postfix) with ESMTP id E822A14F58 for ; Thu, 13 May 1999 12:10:10 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ppp-207-193-14-155.hstntx.swbell.net [207.193.14.155]) by mail-gw3adm.rcsntx.swbell.net (8.8.5/8.8.5) with ESMTP id OAA03358; Thu, 13 May 1999 14:09:51 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id OAA20222; Thu, 13 May 1999 14:11:20 -0500 (CDT) (envelope-from chris) Date: Thu, 13 May 1999 14:11:19 -0500 From: Chris Costello To: Chuck Robey Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IBM scsi drives Message-ID: <19990513141119.B19831@holly.dyndns.org> Reply-To: chris@calldei.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.2i In-Reply-To: ; from Chuck Robey on Thu, May 13, 1999 at 01:59:01PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, May 13, 1999, Chuck Robey wrote: > At $175 for 4.5G, it seems like it would be a good deal if I knew it to > work .... does anyone have any experience with it? I paid $179 for my IBM DDRS-34560D DC1B (4.5 GB Ultrastar) and it's been a good deal so far. What real advantages does the DDRS34560W-LVD have? > > BTW, this is for a hobby system, not a professional system, so anyone > suggesting I spend triple the price for extra reliability is going to be > politely ignored. > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@picnic.mat.net | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run picnic (FreeBSD-current) > (301) 220-2114 | and jaunt (Solaris7). > ----------------------------+----------------------------------------------- -- Chris Costello Artificial Intelligence: Making computers behave like they do in the movies. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 13: 5:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id ED82914D7F for ; Thu, 13 May 1999 13:05:44 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA28456; Thu, 13 May 1999 13:05:11 -0700 Date: Thu, 13 May 1999 13:05:11 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Gerard Roudier Cc: Chuck Robey , freebsd-scsi@FreeBSD.ORG Subject: Re: IBM scsi drives In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > On Thu, 13 May 1999, Matthew Jacob wrote: > > > I've had some reasonable good experiences in some contexts with the IBM > > drives- but they have a wierd property of not working if your host adapter > > negotiates sync speeds before negotiating wide. Make sure these drives > > work for you before you pay! > > If your driver/controller pair assume the SYNC agreement is still valid > after a WIDE negotiation that succeeds, then the IBM drives may well > be quite correct. > > A WIDE negotation that succeeds makes the SYNC agreement go back to > ASYNCHRONOUS. So, a driver that negotiates SYNC before WIDE must assume > WIDE-ASYNCHRONOUS if the target agrees with WIDE transfers. > > By the way, SDTR, then WDTR, then SDTR is correct, but indeed stupid since > both Wide and Sync capabilities are returned in the INQUIRY data. > > The right order for negotiations is, first WIDE (leads to ASYNC if > succeeds), then SYNC. Yes, I agree. But systems and f/w don't always do the right thing. Suns enable sync mode first, and then enable wide. IBM Drive accepts the wide and chokes. It's not that it goes back to Async. It just chokes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 14:35:13 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id E63F114FD1 for ; Thu, 13 May 1999 14:35:00 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id RAA02099; Thu, 13 May 1999 17:29:28 -0400 (EDT) Date: Thu, 13 May 1999 17:29:28 -0400 (EDT) From: Chuck Robey To: Darryl Okahata Cc: Matthew Jacob , freebsd-scsi@FreeBSD.ORG Subject: Re: IBM scsi drives In-Reply-To: <199905131830.LAA07103@mina.sr.hp.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 13 May 1999, Darryl Okahata wrote: > Chuck Robey wrote: > > > I just want to see if someone else has some direct experience with the > > DDRS34560W-LVD. Sure would make me feel better. > > Just FYI, my IBM LVD drives reports themselves as: > > da0: Fixed Direct Access SCSI-2 device > da1: Fixed Direct Access SCSI-2 device > > The plain F/W (non-LVD) version reports as: > > da2: Fixed Direct Access SCSI-2 device > > Basically, the "W" suffix is used for the non-LVD drive, and the "D" > suffix is used on LVD drives. Huh. According to the IBM web site, they are scsi-3. I don't know enough about scsi to tell the difference, tho. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 16:44:50 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 9BDC014EF3 for ; Thu, 13 May 1999 16:44:47 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id TAA02467; Thu, 13 May 1999 19:42:12 -0400 (EDT) Date: Thu, 13 May 1999 19:42:12 -0400 (EDT) From: Chuck Robey To: Matthew Jacob Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IBM scsi drives In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 13 May 1999, Matthew Jacob wrote: > You can't mix ultra && LVD. They're one or the other (it's a voltage > thingie). This is something new to me, I hadn't had to worry about the difference between wide and ultra wide. I have the IBM DCAS 34330W drive already, I think that's a wide drive. I'm looking at the web page now for the 34560W, and it doesn't say ultra either. It says that the interface has 2 modes, one with LVD and one without it. Doesn't seem to be too well defined as to what the non-LVD mode is. Guess I'm going to find out tho, I went ahead and ordered it. I really liked the 34330, and I understand the 34560 is as cool as the 34330W is. Being cool is important to me, 'cause I run SMP, and I don't need melting processors. Extra fans are extra loud. Thanks for all the help, everybody, the response has been remarkable, even for FreeBSD. I sure appreciate it. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 16:46:11 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 87A6D14EF3 for ; Thu, 13 May 1999 16:46:00 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id TAA02476; Thu, 13 May 1999 19:43:30 -0400 (EDT) Date: Thu, 13 May 1999 19:43:30 -0400 (EDT) From: Chuck Robey To: Chris Costello Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IBM scsi drives In-Reply-To: <19990513141119.B19831@holly.dyndns.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 13 May 1999, Chris Costello wrote: > On Thu, May 13, 1999, Chuck Robey wrote: > > At $175 for 4.5G, it seems like it would be a good deal if I knew it to > > work .... does anyone have any experience with it? > > I paid $179 for my IBM DDRS-34560D DC1B (4.5 GB Ultrastar) and > it's been a good deal so far. What real advantages does the > DDRS34560W-LVD have? I don't know, I didn't even see a "D" for sale, Chris. I don't know what it is. > > > > > BTW, this is for a hobby system, not a professional system, so anyone > > suggesting I spend triple the price for extra reliability is going to be > > politely ignored. > > > > ----------------------------+----------------------------------------------- > > Chuck Robey | Interests include any kind of voice or data > > chuckr@picnic.mat.net | communications topic, C programming, and Unix. > > 213 Lakeside Drive Apt T-1 | > > Greenbelt, MD 20770 | I run picnic (FreeBSD-current) > > (301) 220-2114 | and jaunt (Solaris7). > > ----------------------------+----------------------------------------------- > > -- > Chris Costello > Artificial Intelligence: Making computers behave like they do in the movies. > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 17: 7: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 5AC9514C48 for ; Thu, 13 May 1999 17:06:57 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id RAA29050; Thu, 13 May 1999 17:06:38 -0700 Date: Thu, 13 May 1999 17:06:38 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Gerard Roudier Cc: Chuck Robey , freebsd-scsi@FreeBSD.ORG Subject: Re: IBM scsi drives 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 > > > > Yes, I agree. But systems and f/w don't always do the right thing. > > > > Suns enable sync mode first, and then enable wide. IBM Drive accepts the > > wide and chokes. It's not that it goes back to Async. It just chokes. > > (Just guessing about the reasons of the correponding clause in the specs) > The reason of Wide forcing back to Async may be due to the fact that > doubling the BUS width just doubles the data speed and requires twice more > bytes for the offset. For these reasons, a device may elect to negotiate > different period/offset value for SDTR depending on the current agreement > on BUS width. > > On the other hand, SPI-2 says _explicitely_ that WIDE must be negotiated > prior to SYNC and SCSI-2 was also clear about WIDE forcing ASYNC. What you > report is properly unbeleivable, unless Sun guys that maintain Sun's SCSI > stuff are absolute morons. But, may-be, they just donnot want to fix their > stuff. Result of such important vendor not conforming to the specs may > encourage SCSI device manufacturers to sell non compliant devices that may > defeat compliant drivers and controllers. It is properly unacceptable. As a former Sun employee, I'll agree with some of this. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 17:51:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 5E9B814FD5 for ; Thu, 13 May 1999 17:51:24 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (813 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Thu, 13 May 1999 17:51:24 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Thu, 13 May 1999 17:51:24 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-scsi@freebsd.org Reply-To: randy@psg.com Subject: advice on new config Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org so, i am building yet another system. this one will be multi-user over the net. medium mail load. no news. a few compiles. headless. should i put root and swap on a separate spindle? my guess is not because of extra space, heat, etc. in the rack. so maybe just one largish, 6-9mb, drive. who's the controller of the month? the drive of the week? my criteria are reliability first, reliability second, and speed tied with cost for third. note that reply-to: has been set. if i get interesting answers, i will summarize. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 19: 1:36 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from tasam.com (tasam.com [206.161.83.22]) by hub.freebsd.org (Postfix) with ESMTP id 6BEEE154CD for ; Thu, 13 May 1999 18:59:56 -0700 (PDT) (envelope-from freebsd.list@bug.tasam.com) Received: from bug (bug.tasam.com [206.161.113.114]) by tasam.com (8.9.3/8.9.1) with SMTP id VAA28753; Thu, 13 May 1999 21:56:34 -0400 (EDT) Message-ID: <009b01be9dad$021ed270$7271a1ce@tasam.com> From: "Joe Gleason" To: "Chuck Robey" , "Darryl Okahata" Cc: "Matthew Jacob" , References: Subject: Re: IBM scsi drives Date: Thu, 13 May 1999 21:56:11 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My drive is reported as: da0 at ahc0 bus 0 target 5 lun 0 da0: Fixed Direct Access SCSI3 device da0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) And I am running. I don't know if this is useful or not, I haven't realy read the entire thread. Joe Gleason Tasam ----- Original Message ----- From: Chuck Robey To: Darryl Okahata Cc: Matthew Jacob ; Sent: Thursday, May 13, 1999 17:29 Subject: Re: IBM scsi drives > On Thu, 13 May 1999, Darryl Okahata wrote: > > > Chuck Robey wrote: > > > > > I just want to see if someone else has some direct experience with the > > > DDRS34560W-LVD. Sure would make me feel better. > > > > Just FYI, my IBM LVD drives reports themselves as: > > > > da0: Fixed Direct Access SCSI-2 device > > da1: Fixed Direct Access SCSI-2 device > > > > The plain F/W (non-LVD) version reports as: > > > > da2: Fixed Direct Access SCSI-2 device > > > > Basically, the "W" suffix is used for the non-LVD drive, and the "D" > > suffix is used on LVD drives. > > Huh. According to the IBM web site, they are scsi-3. I don't know > enough about scsi to tell the difference, tho. > > > ----------------------------+--------------------------------------- -------- > Chuck Robey | Interests include any kind of voice or data > chuckr@picnic.mat.net | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run picnic (FreeBSD-current) > (301) 220-2114 | and jaunt (Solaris7). > ----------------------------+--------------------------------------- -------- > > > > > > > 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 May 13 21: 7:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from tinker.com (troll.tinker.com [204.214.7.146]) by hub.freebsd.org (Postfix) with ESMTP id A334C151F1 for ; Thu, 13 May 1999 21:07:17 -0700 (PDT) (envelope-from kim@tinker.com) Received: by localhost (8.8.5/8.8.5) Received: by mail.tinker.com via smap (V2.0) id xma016939; Thu May 13 23:03:45 1999 Received: by localhost (8.8.8/8.8.8) id XAA20232 for ; Thu, 13 May 1999 23:04:17 -0500 (CDT) Message-ID: <373BA24E.1A447BCF@tinker.com> Date: Thu, 13 May 1999 23:10:54 -0500 From: Kim Shrier Organization: Shrier and Deihl X-Mailer: Mozilla 4.5 [en] (X11; U; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Is the 7895 supported on the Adaptec 3940uw in 2.2 STABLE Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Subject says it all. Please reply directly to me since I am not on this list. Thanks, Kim Shrier kim@tinker.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 21:36:10 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 723D215435 for ; Thu, 13 May 1999 21:36:09 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id WAA20888; Thu, 13 May 1999 22:26:21 -0600 (MDT) Date: Thu, 13 May 1999 22:26:21 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199905140426.WAA20888@narnia.plutotech.com> To: mjacob@feral.com Cc: scsi@FreeBSD.org Subject: Re: IBM scsi drives X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > > > I've had some reasonable good experiences in some contexts with the IBM > drives- but they have a wierd property of not working if your host adapter > negotiates sync speeds before negotiating wide. Make sure these drives > work for you before you pay! It doesn't make much sense to negotiate sync before wide since, according to the spec, a wide negotiation invalidates any sync setting. The aic7xxx driver always reverts to async after a wide negotiation and will renegotiate sync if appropriate. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 22: 1: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail-gw1adm.rcsntx.swbell.net (mail-gw1.rcsntx.swbell.net [151.164.30.51]) by hub.freebsd.org (Postfix) with ESMTP id A27F315425 for ; Thu, 13 May 1999 22:01:06 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ppp-207-193-16-161.hstntx.swbell.net [207.193.16.161]) by mail-gw1adm.rcsntx.swbell.net (8.8.5/8.8.5) with ESMTP id AAA19601; Fri, 14 May 1999 00:00:59 -0500 (CDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id AAA33625; Fri, 14 May 1999 00:02:26 -0500 (CDT) (envelope-from chris) Date: Fri, 14 May 1999 00:02:25 -0500 From: Chris Costello To: Chuck Robey Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: IBM scsi drives Message-ID: <19990514000224.A33582@holly.dyndns.org> Reply-To: chris@calldei.com References: <19990513141119.B19831@holly.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.2i In-Reply-To: ; from Chuck Robey on Thu, May 13, 1999 at 07:43:30PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, May 13, 1999, Chuck Robey wrote: > I don't know, I didn't even see a "D" for sale, Chris. I don't know > what it is. Strange -- it was there. There's one exactly the same except that it ends in 'W' and is an LVD drive. How odd. I bought mine from TJT, as well. -- Chris Costello Your e-mail has been returned due to insufficient voltage. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 22: 5:33 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 66BA315425 for ; Thu, 13 May 1999 22:05:31 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id WAA29809; Thu, 13 May 1999 22:05:21 -0700 Date: Thu, 13 May 1999 22:05:21 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: scsi@FreeBSD.ORG Subject: Re: IBM scsi drives In-Reply-To: <199905140426.WAA20888@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 > > > > > > I've had some reasonable good experiences in some contexts with the IBM > > drives- but they have a wierd property of not working if your host adapter > > negotiates sync speeds before negotiating wide. Make sure these drives > > work for you before you pay! > > It doesn't make much sense to negotiate sync before wide since, > according to the spec, a wide negotiation invalidates any sync > setting. The aic7xxx driver always reverts to async after a wide > negotiation and will renegotiate sync if appropriate. So Comte Roudier informed me... I knew that sorta (I really don't need to know this for the Qlogic cards- this is done in the f/w...)... I don't really remember all the details and can dig out the fax from an IBM engineer..but the basic gist of this was I had to (for a Solaris driver) break the Solaris order of 'first sync then wide'. It's possible I could have forced renegotiation but it seems to me that there was something that would make this not work. All of this is the dance between spec && shipping h/w. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 13 22: 6:31 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 4FDD615425 for ; Thu, 13 May 1999 22:06:29 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id XAA10870; Thu, 13 May 1999 23:06:04 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905140506.XAA10870@panzer.plutotech.com> Subject: Re: Is the 7895 supported on the Adaptec 3940uw in 2.2 STABLE In-Reply-To: <373BA24E.1A447BCF@tinker.com> from Kim Shrier at "May 13, 1999 11:10:54 pm" To: kim@tinker.com (Kim Shrier) Date: Thu, 13 May 1999 23:06:04 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kim Shrier wrote... > Subject says it all. Please reply directly to me since I am not on this > list. No. You need one of the 3.x releases. 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 May 13 23:49:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from cain.gsoft.com.au (genesi.lnk.telstra.net [139.130.136.161]) by hub.freebsd.org (Postfix) with ESMTP id 9856B14BF7 for ; Thu, 13 May 1999 23:49:14 -0700 (PDT) (envelope-from doconnor@gsoft.com.au) Received: from lot.gsoft.com.au (lot.gsoft.com.au [203.38.152.106]) by cain.gsoft.com.au (8.8.8/8.8.8) with ESMTP id QAA03274; Fri, 14 May 1999 16:18:29 +0930 (CST) (envelope-from doconnor@gsoft.com.au) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199905140506.XAA10870@panzer.plutotech.com> Date: Fri, 14 May 1999 16:18:29 +0930 (CST) From: "Daniel O'Connor" To: "Kenneth D. Merry" Subject: Re: Is the 7895 supported on the Adaptec 3940uw in 2.2 STABLE Cc: freebsd-scsi@FreeBSD.ORG, (Kim Shrier) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 14-May-99 Kenneth D. Merry wrote: > Kim Shrier wrote... > > Subject says it all. Please reply directly to me since I am not on this > > list. > No. You need one of the 3.x releases. Ahh, well there are patches for 2.2, I'm using them :) ie the CAM ones allow support for the 3940. Hmm.. given the place where I got the patches no longer exists I'll assume they're no longer available :-/ --- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 14 8:55:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 028E814C3D for ; Fri, 14 May 1999 08:55:27 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id JAA13005; Fri, 14 May 1999 09:55:10 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905141555.JAA13005@panzer.plutotech.com> Subject: Re: Is the 7895 supported on the Adaptec 3940uw in 2.2 STABLE In-Reply-To: from "Daniel O'Connor" at "May 14, 1999 4:18:29 pm" To: doconnor@gsoft.com.au (Daniel O'Connor) Date: Fri, 14 May 1999 09:55:10 -0600 (MDT) Cc: ken@plutotech.com, freebsd-scsi@FreeBSD.ORG, kim@tinker.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Daniel O'Connor wrote... > > On 14-May-99 Kenneth D. Merry wrote: > > Kim Shrier wrote... > > > Subject says it all. Please reply directly to me since I am not on this > > > list. > > No. You need one of the 3.x releases. > > Ahh, well there are patches for 2.2, I'm using them :) > ie the CAM ones allow support for the 3940. > > Hmm.. given the place where I got the patches no longer exists I'll assume > they're no longer available :-/ They're still there, the directory moved: ftp://ftp.FreeBSD.ORG/pub/FreeBSD/development/cam There's a release there as well. 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 May 15 12: 0:38 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 48B6714C9E for ; Sat, 15 May 1999 12:00:35 -0700 (PDT) (envelope-from dcs@newsguy.com) Received: from newsguy.com by peach.ocn.ne.jp (8.9.1a/OCN) id EAA08895; Sun, 16 May 1999 04:00:34 +0900 (JST) Message-ID: <373DC3A0.73F664A6@newsguy.com> Date: Sun, 16 May 1999 03:57:36 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.51 [en] (Win98; I) X-Accept-Language: pt-BR,ja MIME-Version: 1.0 To: scsi@freebsd.org Subject: AHA fix Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Did the AHA fix got in time for 3.2? If not, could the responsible please ask Jordan to slide the tag for that one? -- Daniel C. Sobral (8-DCS) dcs@newsguy.com dcs@freebsd.org "Proof of Trotsky's farsightedness is that _none_ of his predictions have come true yet." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 15 21:53:10 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 0F20F14EF1 for ; Sat, 15 May 1999 21:53:07 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id WAA52351; Sat, 15 May 1999 22:52:05 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id WAA63463; Sat, 15 May 1999 22:53:16 -0600 (MDT) Message-Id: <199905160453.WAA63463@harmony.village.org> To: "Daniel C. Sobral" Subject: Re: AHA fix Cc: scsi@FreeBSD.ORG In-reply-to: Your message of "Sun, 16 May 1999 03:57:36 +0900." <373DC3A0.73F664A6@newsguy.com> References: <373DC3A0.73F664A6@newsguy.com> Date: Sat, 15 May 1999 22:53:16 -0600 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <373DC3A0.73F664A6@newsguy.com> "Daniel C. Sobral" writes: : Did the AHA fix got in time for 3.2? If not, could the responsible : please ask Jordan to slide the tag for that one? I've asked Jordan to slide the tag, and he agreed. 1.19.2.3 has the fix and the tag. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 18 6:10:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (Postfix) with ESMTP id 8EF6D15170 for ; Tue, 18 May 1999 06:09:52 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from solist.partitur.se (solist.partitur.se [193.219.246.204]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id PAA01388 for ; Tue, 18 May 1999 15:09:50 +0200 (CEST) (envelope-from girgen@partitur.se) Received: from partitur.se (localhost [127.0.0.1]) by solist.partitur.se (8.9.1b+Sun/8.8.8) with ESMTP id PAA03406 for ; Tue, 18 May 1999 15:09:24 +0200 (MET DST) (envelope-from girgen@partitur.se) Message-ID: <37416684.64A54C87@partitur.se> Date: Tue, 18 May 1999 15:09:24 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.51 [en] (X11; I; SunOS 5.7 sun4u) X-Accept-Language: sv, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Will IDE disks impact SCSI or system performance? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! Our main internal server, FreeBSD 3.2b with five large SCSI disks, running vinum and softupdates etc... It fast, and we're happy. It runs both filesharing (mainly NFS) and applications. Now some guys here are interested in having a large archive with not-so-important data (read mp3 files...) and suggest a large IDE disk for almost no money at all. My question: will an IDE disk in a now SCSI-only system impact performance for the rest of the system? Thanks! Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 18 6:15:47 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (Postfix) with ESMTP id 1D610152EF for ; Tue, 18 May 1999 06:15:14 -0700 (PDT) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id IAA02906; Tue, 18 May 1999 08:14:50 -0500 (CDT) Message-ID: <19990518081450.A2902@Denninger.Net> Date: Tue, 18 May 1999 08:14:50 -0500 From: Karl Denninger To: Palle Girgensohn , freebsd-scsi@FreeBSD.ORG Subject: Re: Will IDE disks impact SCSI or system performance? References: <37416684.64A54C87@partitur.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <37416684.64A54C87@partitur.se>; from Palle Girgensohn on Tue, May 18, 1999 at 03:09:24PM +0200 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, May 18, 1999 at 03:09:24PM +0200, Palle Girgensohn wrote: > Hi! > > Our main internal server, FreeBSD 3.2b with five large SCSI disks, > running vinum and softupdates etc... It fast, and we're happy. It runs > both filesharing (mainly NFS) and applications. > > Now some guys here are interested in having a large archive with > not-so-important data (read mp3 files...) and suggest a large IDE disk > for almost no money at all. > > My question: will an IDE disk in a now SCSI-only system impact > performance for the rest of the system? > > Thanks! > Palle Why not just add another SCSI disk? They're almost as cheap as IDE these days. If you really want to do IDE, you can, but you might have fun with the system trying to boot from it - which would be a pain in the ass. -- -- Karl Denninger (karl@denninger.net) Web: fathers.denninger.net I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 18 6:45: 2 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (Postfix) with ESMTP id C132E14A2D for ; Tue, 18 May 1999 06:44:27 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from solist.partitur.se (solist.partitur.se [193.219.246.204]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id PAA01654; Tue, 18 May 1999 15:44:20 +0200 (CEST) (envelope-from girgen@partitur.se) Received: from partitur.se (localhost [127.0.0.1]) by solist.partitur.se (8.9.1b+Sun/8.8.8) with ESMTP id PAA03430; Tue, 18 May 1999 15:43:48 +0200 (MET DST) (envelope-from girgen@partitur.se) Message-ID: <37416E94.58C7FC76@partitur.se> Date: Tue, 18 May 1999 15:43:48 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.51 [en] (X11; I; SunOS 5.7 sun4u) X-Accept-Language: sv, en MIME-Version: 1.0 To: Karl Denninger Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Will IDE disks impact SCSI or system performance? References: <37416684.64A54C87@partitur.se> <19990518081450.A2902@Denninger.Net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Karl Denninger wrote: > > On Tue, May 18, 1999 at 03:09:24PM +0200, Palle Girgensohn wrote: > > Hi! > > > > Our main internal server, FreeBSD 3.2b with five large SCSI disks, > > running vinum and softupdates etc... It fast, and we're happy. It runs > > both filesharing (mainly NFS) and applications. > > > > Now some guys here are interested in having a large archive with > > not-so-important data (read mp3 files...) and suggest a large IDE disk > > for almost no money at all. > > > > My question: will an IDE disk in a now SCSI-only system impact > > performance for the rest of the system? > > > > Thanks! > > Palle > > Why not just add another SCSI disk? They're almost as cheap as IDE these > days. Well, in the price lists I have, I can get a 22 MB IDE (SLOW... 5krpm) for around 2000 SEK (around USD 250). Can't find any low performance SCSI disks at all, and 22 MB costs a fortune... :( Even for smaller disk, with same rpm SCSI is almost twice the price... I guess you get what you pay for; SCSI is better; but this time I just wan't it cheap... ;-) > > If you really want to do IDE, you can, but you might have fun with the > system trying to boot from it - which would be a pain in the ass. Yeah, I thought about that... Is there no way to get around that. BIOS? I have an alternative; put the disk on a IDE only workstation, as an IDE slave... But it would be better to have it on the SCSI machine if it will not impact performance. /Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 18 7:26:58 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id B3401156D5 for ; Tue, 18 May 1999 07:26:16 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id IAA34389; Tue, 18 May 1999 08:26:04 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905181426.IAA34389@panzer.plutotech.com> Subject: Re: Will IDE disks impact SCSI or system performance? In-Reply-To: <37416684.64A54C87@partitur.se> from Palle Girgensohn at "May 18, 1999 3: 9:24 pm" To: girgen@partitur.se (Palle Girgensohn) Date: Tue, 18 May 1999 08:26:04 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Palle Girgensohn wrote... > Hi! > > Our main internal server, FreeBSD 3.2b with five large SCSI disks, > running vinum and softupdates etc... It fast, and we're happy. It runs > both filesharing (mainly NFS) and applications. > > Now some guys here are interested in having a large archive with > not-so-important data (read mp3 files...) and suggest a large IDE disk > for almost no money at all. > > My question: will an IDE disk in a now SCSI-only system impact > performance for the rest of the system? It shouldn't have any effect on performance. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 18 10:36:37 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id B665414D1A for ; Tue, 18 May 1999 10:36:35 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id LAA35435 for scsi@FreeBSD.ORG; Tue, 18 May 1999 11:36:34 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905181736.LAA35435@panzer.plutotech.com> Subject: 7890 hang fixed To: scsi@FreeBSD.ORG Date: Tue, 18 May 1999 11:36:34 -0600 (MDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For those of you who don't watch the cvs-all list, Justin fixed the fabled "7890 hang" on Thursday (May 13th) in -current and Saturday (May 15th) in -stable. It looks like the -stable change was tagged for 3.2, so the hang fix should be in 3.2 as well. If you're still having problems, complain to the SCSI list or Justin, not me. :) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 18 11:33:15 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id ABA6B14CC8 for ; Tue, 18 May 1999 11:33:09 -0700 (PDT) (envelope-from sthaug@nethelp.no) Received: (qmail 27673 invoked by uid 1001); 18 May 1999 18:33:07 +0000 (GMT) To: ken@plutotech.com Cc: scsi@FreeBSD.ORG Subject: Re: 7890 hang fixed From: sthaug@nethelp.no In-Reply-To: Your message of "Tue, 18 May 1999 11:36:34 -0600 (MDT)" References: <199905181736.LAA35435@panzer.plutotech.com> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Tue, 18 May 1999 20:33:07 +0200 Message-ID: <27671.927052387@verdi.nethelp.no> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > For those of you who don't watch the cvs-all list, Justin fixed the fabled > "7890 hang" on Thursday (May 13th) in -current and Saturday (May 15th) in > -stable. I presume this corresponds to the following CVS log message? > Take advantage of the HS_MAILBOX register to avoid the > aic7890/91/96/97 pause race during sync/wide negotiation. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 18 11:45:11 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from dingo.cdrom.com (castles506.castles.com [208.214.165.70]) by hub.freebsd.org (Postfix) with ESMTP id CEBC115771 for ; Tue, 18 May 1999 11:45:06 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.3/8.8.8) with ESMTP id LAA04720; Tue, 18 May 1999 11:43:19 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199905181843.LAA04720@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" Cc: scsi@FreeBSD.ORG Subject: Re: 7890 hang fixed In-reply-to: Your message of "Tue, 18 May 1999 11:36:34 MDT." <199905181736.LAA35435@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 18 May 1999 11:43:19 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > For those of you who don't watch the cvs-all list, Justin fixed the fabled > "7890 hang" on Thursday (May 13th) in -current and Saturday (May 15th) in > -stable. > > It looks like the -stable change was tagged for 3.2, so the hang fix should > be in 3.2 as well. > > If you're still having problems, complain to the SCSI list or Justin, not > me. :) And even if you're not, please politely ask Justin to come up with these fixes at better times than "a few hours after a release tag". His reputation for causing the release engineer(s) to barf hairballs is legendary. We're happy to have the changes, less so to have them come in at such desperately short notice. Maybe a letter-writing campaign will prompt a change of heart? 8) -- \\ The mind's the standard \\ Mike Smith \\ of the man. \\ msmith@freebsd.org \\ -- Joseph Merrick \\ 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 May 18 11:55:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id A4BCF15399 for ; Tue, 18 May 1999 11:55:13 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id LAA26758; Tue, 18 May 1999 11:50:16 -0700 (PDT) Date: Tue, 18 May 1999 11:50:15 -0700 (PDT) From: Julian Elischer To: Palle Girgensohn Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Will IDE disks impact SCSI or system performance? In-Reply-To: <37416684.64A54C87@partitur.se> 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 you can get a motherboard that supports Ultra-DMA IDE then one or two large IDE UDMA drives will be very fast and not impact the SCSI system too much. Julian On Tue, 18 May 1999, Palle Girgensohn wrote: > Hi! > > Our main internal server, FreeBSD 3.2b with five large SCSI disks, > running vinum and softupdates etc... It fast, and we're happy. It runs > both filesharing (mainly NFS) and applications. > > Now some guys here are interested in having a large archive with > not-so-important data (read mp3 files...) and suggest a large IDE disk > for almost no money at all. > > My question: will an IDE disk in a now SCSI-only system impact > performance for the rest of the system? > > Thanks! > Palle > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 18 11:55:28 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (Postfix) with ESMTP id 399B51573E for ; Tue, 18 May 1999 11:55:25 -0700 (PDT) (envelope-from julian@whistle.com) Received: from current1.whistle.com (current1.whistle.com [207.76.205.22]) by alpo.whistle.com (8.9.1a/8.9.1) with SMTP id LAA26838; Tue, 18 May 1999 11:54:07 -0700 (PDT) Date: Tue, 18 May 1999 11:54:06 -0700 (PDT) From: Julian Elischer To: Palle Girgensohn Cc: Karl Denninger , freebsd-scsi@FreeBSD.ORG Subject: Re: Will IDE disks impact SCSI or system performance? In-Reply-To: <37416E94.58C7FC76@partitur.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 18 May 1999, Palle Girgensohn wrote: > Karl Denninger wrote: > > > > On Tue, May 18, 1999 at 03:09:24PM +0200, Palle Girgensohn wrote: > > > Hi! > > > > > > Our main internal server, FreeBSD 3.2b with five large SCSI disks, > > > running vinum and softupdates etc... It fast, and we're happy. It runs > > > both filesharing (mainly NFS) and applications. > > > > > > Now some guys here are interested in having a large archive with > > > not-so-important data (read mp3 files...) and suggest a large IDE disk > > > for almost no money at all. > > > > > > My question: will an IDE disk in a now SCSI-only system impact > > > performance for the rest of the system? > > > > > > Thanks! > > > Palle > > > > Why not just add another SCSI disk? They're almost as cheap as IDE these > > days. > > Well, in the price lists I have, I can get a 22 MB IDE (SLOW... 5krpm) > for around 2000 SEK (around USD 250). Can't find any low performance > SCSI disks at all, and 22 MB costs a fortune.... :( Even for smaller > disk, with same rpm SCSI is almost twice the price... I guess you get > what you pay for; SCSI is better; but this time I just wan't it cheap... > ;-) > > > > > If you really want to do IDE, you can, but you might have fun with the > > system trying to boot from it - which would be a pain in the ass. > > Yeah, I thought about that... Is there no way to get around that. BIOS? just tell the BIOS it is not there,.... > > I have an alternative; put the disk on a IDE only workstation, as an IDE > slave... But it would be better to have it on the SCSI machine if it > will not impact performance. > > /Palle > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 18 13:34: 1 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 9712814DCD for ; Tue, 18 May 1999 13:33:59 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id OAA36208; Tue, 18 May 1999 14:33:53 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905182033.OAA36208@panzer.plutotech.com> Subject: Re: 7890 hang fixed In-Reply-To: <27671.927052387@verdi.nethelp.no> from "sthaug@nethelp.no" at "May 18, 1999 8:33: 7 pm" To: sthaug@nethelp.no Date: Tue, 18 May 1999 14:33:53 -0600 (MDT) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org sthaug@nethelp.no wrote... > > For those of you who don't watch the cvs-all list, Justin fixed the fabled > > "7890 hang" on Thursday (May 13th) in -current and Saturday (May 15th) in > > -stable. > > I presume this corresponds to the following CVS log message? > > > Take advantage of the HS_MAILBOX register to avoid the > > aic7890/91/96/97 pause race during sync/wide negotiation. Yes, that's the one. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 18 13:56:36 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from bastuba.partitur.se (bastuba.partitur.se [193.219.246.194]) by hub.freebsd.org (Postfix) with ESMTP id 76FED14DD5 for ; Tue, 18 May 1999 13:56:28 -0700 (PDT) (envelope-from girgen@partitur.se) Received: from solist.partitur.se (solist.partitur.se [193.219.246.204]) by bastuba.partitur.se (8.8.8/8.8.8) with ESMTP id WAA04423; Tue, 18 May 1999 22:56:24 +0200 (CEST) (envelope-from girgen@partitur.se) Received: from partitur.se (localhost [127.0.0.1]) by solist.partitur.se (8.9.1b+Sun/8.8.8) with ESMTP id WAA03619; Tue, 18 May 1999 22:55:57 +0200 (MET DST) (envelope-from girgen@partitur.se) Message-ID: <3741D3DD.21278320@partitur.se> Date: Tue, 18 May 1999 22:55:57 +0200 From: Palle Girgensohn Organization: Partitur X-Mailer: Mozilla 4.51 [en] (X11; I; SunOS 5.7 sun4u) X-Accept-Language: sv, en MIME-Version: 1.0 To: Julian Elischer Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Will IDE disks impact SCSI or system performance? References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Julian Elischer wrote: > > > > > > > If you really want to do IDE, you can, but you might have fun with the > > > system trying to boot from it - which would be a pain in the ass. > > > > Yeah, I thought about that... Is there no way to get around that. BIOS? > > just tell the BIOS it is not there,.... > Yeah, sounds right. Thanks. /Palle To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 18 14:12:58 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id CEF62152B9 for ; Tue, 18 May 1999 14:12:50 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id RAA64039 for ; Tue, 18 May 1999 17:13:04 -0400 (EDT) Date: Tue, 18 May 1999 17:13:04 -0400 (EDT) From: Chuck Robey To: freebsd-scsi@FreeBSD.ORG Subject: ahc boot messages 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 recently got my new DK440LX motherboard cranking (it's great!) and I've not seen the ahc driver since back in 1.1.5.1 days. It went real smoothly getting it going (well, one f-u, but we won't talk about that :-) .... anyhow, I noticed the boot messages produced by the ahc driver, it seemed excessively verbose. The DK440LX has the 7895 controller which has 2 busses, and all targets on both buses get a line each to announce their status. I get a LOT of these lines: ahc0: Selection Timeout on A:1. 1 SCBs aborted ahc1: Selection Timeout on A:0. 1 SCBs aborted ahc0: Selection Timeout on A:2. 1 SCBs aborted ahc1: Selection Timeout on A:2. 1 SCBs aborted 32 lines of this. Isn't this really excessive? For anyone? Even if the messages are needed (and I like having the message) it wouldn't be all that difficult to come up with a format to squeeze all messages from each buss into 2 lines (one header, one data line) so all the info could still be displayed, but in a far more readable format. Am I off here? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 18 16:39:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 78AAE14F2D for ; Tue, 18 May 1999 16:39:30 -0700 (PDT) (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 JAA04018; Wed, 19 May 1999 09:09:23 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id JAA04940; Wed, 19 May 1999 09:09:22 +0930 (CST) Date: Wed, 19 May 1999 09:09:22 +0930 From: Greg Lehey To: Palle Girgensohn Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Will IDE disks impact SCSI or system performance? Message-ID: <19990519090922.D89091@freebie.lemis.com> References: <37416684.64A54C87@partitur.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <37416684.64A54C87@partitur.se>; from Palle Girgensohn on Tue, May 18, 1999 at 03:09:24PM +0200 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Tuesday, 18 May 1999 at 15:09:24 +0200, Palle Girgensohn wrote: > Hi! > > Our main internal server, FreeBSD 3.2b with five large SCSI disks, > running vinum and softupdates etc... It fast, and we're happy. It runs > both filesharing (mainly NFS) and applications. > > Now some guys here are interested in having a large archive with > not-so-important data (read mp3 files...) and suggest a large IDE disk > for almost no money at all. > > My question: will an IDE disk in a now SCSI-only system impact > performance for the rest of the system? Julian sort of answered this, but to be sure: if you run DMA, it shouldn't make any difference. If you run it in PIO mode, you can end up using up to 90% of the processor in interrupt code, which will make it seem like it's grinding to a halt. 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 Tue May 18 18: 1:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from granite.sentex.net (granite.sentex.ca [199.212.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 39E6514CB0 for ; Tue, 18 May 1999 18:01:32 -0700 (PDT) (envelope-from mike@sentex.net) Received: from ospf-wat.sentex.net (ospf-wat.sentex.net [209.167.248.81]) by granite.sentex.net (8.8.8/8.6.9) with SMTP id VAA25116; Tue, 18 May 1999 21:01:30 -0400 (EDT) From: mike@sentex.net (Mike Tancsa) To: freebsd-scsi@freebsd.org Cc: girgen@partitur.se Subject: Re: Will IDE disks impact SCSI or system performance? Date: Wed, 19 May 1999 01:11:35 GMT Message-ID: <37420f2c.77551222@mail.sentex.net> References: <37416684.64A54C87@partitur.se> In-Reply-To: X-Mailer: Forte Agent .99e/32.227 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 18 May 1999 19:40:10 -0400, in sentex.lists.freebsd.misc you wrote: >On Tuesday, 18 May 1999 at 15:09:24 +0200, Palle Girgensohn wrote: >> Hi! >> >> Our main internal server, FreeBSD 3.2b with five large SCSI disks, >> running vinum and softupdates etc... It fast, and we're happy. It runs >> both filesharing (mainly NFS) and applications. >> >> Now some guys here are interested in having a large archive with >> not-so-important data (read mp3 files...) and suggest a large IDE disk >> for almost no money at all. >> >> My question: will an IDE disk in a now SCSI-only system impact >> performance for the rest of the system? > >Julian sort of answered this, but to be sure: if you run DMA, it >shouldn't make any difference. If you run it in PIO mode, you can end >up using up to 90% of the processor in interrupt code, which will make >it seem like it's grinding to a halt. But only when the disk is being accessed no ? Also, regarding the boot issue someone else mentioned, you should be able to take the reference to the drive out of the BIOS, and it will boot from your SCSI device. ---Mike Mike Tancsa (mdtancsa@sentex.net) Sentex Communications Corp, Waterloo, Ontario, Canada To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 18 18:14:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id 30C0514D91 for ; Tue, 18 May 1999 18:14:40 -0700 (PDT) (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 KAA04466; Wed, 19 May 1999 10:44:25 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA05509; Wed, 19 May 1999 10:44:25 +0930 (CST) Date: Wed, 19 May 1999 10:44:25 +0930 From: Greg Lehey To: Mike Tancsa Cc: freebsd-scsi@FreeBSD.ORG, girgen@partitur.se Subject: Re: Will IDE disks impact SCSI or system performance? Message-ID: <19990519104425.S89091@freebie.lemis.com> References: <37416684.64A54C87@partitur.se> <37420f2c.77551222@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <37420f2c.77551222@mail.sentex.net>; from Mike Tancsa on Wed, May 19, 1999 at 01:11:35AM +0000 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wednesday, 19 May 1999 at 1:11:35 +0000, Mike Tancsa wrote: > On 18 May 1999 19:40:10 -0400, in sentex.lists.freebsd.misc you wrote: That must be me! >> On Tuesday, 18 May 1999 at 15:09:24 +0200, Palle Girgensohn wrote: >>> Hi! >>> >>> Our main internal server, FreeBSD 3.2b with five large SCSI disks, >>> running vinum and softupdates etc... It fast, and we're happy. It runs >>> both filesharing (mainly NFS) and applications. >>> >>> Now some guys here are interested in having a large archive with >>> not-so-important data (read mp3 files...) and suggest a large IDE disk >>> for almost no money at all. >>> >>> My question: will an IDE disk in a now SCSI-only system impact >>> performance for the rest of the system? >> >> Julian sort of answered this, but to be sure: if you run DMA, it >> shouldn't make any difference. If you run it in PIO mode, you can end >> up using up to 90% of the processor in interrupt code, which will make >> it seem like it's grinding to a halt. > > But only when the disk is being accessed no ? Right. Sorry, I suppose I should have mentioned that. > Also, regarding the boot issue someone else mentioned, you should be > able to take the reference to the drive out of the BIOS, and it will > boot from your SCSI device. Yes, somebody (I think it was Julian again) said that. Note that some BIOSes are sneaky and check anyway, and refuse to take "no" for an answer. 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 Wed May 19 8:43:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 806AE15354 for ; Wed, 19 May 1999 08:43:15 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id JAA08620; Wed, 19 May 1999 09:32:57 -0600 (MDT) Date: Wed, 19 May 1999 09:32:57 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199905191532.JAA08620@narnia.plutotech.com> To: Mike Smith Cc: scsi@FreeBSD.org Subject: Re: 7890 hang fixed X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <199905181843.LAA04720@dingo.cdrom.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > And even if you're not, please politely ask Justin to come up with > these fixes at better times than "a few hours after a release tag". > His reputation for causing the release engineer(s) to barf hairballs is > legendary. We're happy to have the changes, less so to have them come > in at such desperately short notice. Actually it's Justin that's been coughing up hair balls for over two weeks now which greatly contributed to the timing of these fixes. 8-) -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 19 8:48:47 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id DE0ED14E70 for ; Wed, 19 May 1999 08:48:45 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id JAA08634; Wed, 19 May 1999 09:38:40 -0600 (MDT) Date: Wed, 19 May 1999 09:38:40 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199905191538.JAA08634@narnia.plutotech.com> To: Chuck Robey Cc: scsi@FreeBSD.org Subject: Re: ahc boot messages X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > I recently got my new DK440LX motherboard cranking (it's great!) and > I've not seen the ahc driver since back in 1.1.5.1 days. It went real > smoothly getting it going (well, one f-u, but we won't talk about that > :-) .... anyhow, I noticed the boot messages produced by the ahc driver, > it seemed excessively verbose. The DK440LX has the 7895 controller > which has 2 busses, and all targets on both buses get a line each to > announce their status. I get a LOT of these lines: > > ahc0: Selection Timeout on A:1. 1 SCBs aborted If you don't like the messages, stop booting with the verbose flag. You asked for the system to be verbose, and so it is. > 32 lines of this. Isn't this really excessive? For anyone? Even if > the messages are needed (and I like having the message) it wouldn't be > all that difficult to come up with a format to squeeze all messages from > each buss into 2 lines (one header, one data line) so all the info could > still be displayed, but in a far more readable format. Each of those messages occurs ~250ms apart. How does the controller know in advance if a device will respond to selection? It doesn't. The main reason I added the message is so you can determine why a device was either not found at boot, or disappears after boot has completed. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 19 9: 4: 2 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from picnic.mat.net (picnic.mat.net [206.246.122.133]) by hub.freebsd.org (Postfix) with ESMTP id 49EFE14D2B for ; Wed, 19 May 1999 09:03:54 -0700 (PDT) (envelope-from chuckr@picnic.mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.3/8.8.5) with ESMTP id MAA69013; Wed, 19 May 1999 12:03:55 -0400 (EDT) Date: Wed, 19 May 1999 12:03:55 -0400 (EDT) From: Chuck Robey To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: ahc boot messages In-Reply-To: <199905191538.JAA08634@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 On Wed, 19 May 1999, Justin T. Gibbs wrote: > In article you wrote: > > I recently got my new DK440LX motherboard cranking (it's great!) and > > I've not seen the ahc driver since back in 1.1.5.1 days. It went real > > smoothly getting it going (well, one f-u, but we won't talk about that > > :-) .... anyhow, I noticed the boot messages produced by the ahc driver, > > it seemed excessively verbose. The DK440LX has the 7895 controller > > which has 2 busses, and all targets on both buses get a line each to > > announce their status. I get a LOT of these lines: > > > > ahc0: Selection Timeout on A:1. 1 SCBs aborted > > If you don't like the messages, stop booting with the verbose flag. > You asked for the system to be verbose, and so it is. Actually, I didn't, but you're telling me that I'm getting it anyway. OK, I can stop perstering the scsi list, at least. I specifically turned off verbose booting in /boot/loader.conf, darn it! > > > 32 lines of this. Isn't this really excessive? For anyone? Even if > > the messages are needed (and I like having the message) it wouldn't be > > all that difficult to come up with a format to squeeze all messages from > > each buss into 2 lines (one header, one data line) so all the info could > > still be displayed, but in a far more readable format. > > Each of those messages occurs ~250ms apart. How does the > controller know in advance if a device will respond to selection? > It doesn't. The main reason I added the message is so you can > determine why a device was either not found at boot, or disappears > after boot has completed. > > -- > Justin > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@picnic.mat.net | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run picnic (FreeBSD-current) (301) 220-2114 | and jaunt (Solaris7). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 21 12:33:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from quark.ChrisBowman.com (crbowman.erols.com [209.122.47.155]) by hub.freebsd.org (Postfix) with ESMTP id 2F31F1502C for ; Fri, 21 May 1999 12:33:15 -0700 (PDT) (envelope-from crb@ChrisBowman.com) Received: from fermion (crb@fermion.ChrisBowman.com [10.0.1.2]) by quark.ChrisBowman.com (8.9.2/8.8.8) with SMTP id PAA07285 for ; Fri, 21 May 1999 15:33:00 -0400 (EDT) (envelope-from crb@ChrisBowman.com) Message-Id: <199905211933.PAA07285@quark.ChrisBowman.com> X-Sender: crb@quark X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Fri, 21 May 1999 15:31:31 -0400 To: freebsd-scsi@freebsd.org From: "Christopher R. Bowman" Subject: Question about ncr.c Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org a small section of ncr.c is presented below. Shouldn't line 3851 read cam_sim_free(np->sim, /*free_simq*/TRUE); instead of just free? Not much practical difference, but it just seems more correct. 3829 /* 3830 ** Create the device queue. We only allow MAX_START-1 concurrent 3831 ** transactions so we can be sure to have one element free in our 3832 ** start queue to reset to the idle loop. 3833 */ 3834 devq = cam_simq_alloc(MAX_START - 1); 3835 if (devq == NULL) 3836 return; 3837 3838 /* 3839 ** Now tell the generic SCSI layer 3840 ** about our bus. 3841 */ 3842 np->sim = cam_sim_alloc(ncr_action, ncr_poll, "ncr", np, np->unit, 3843 1, MAX_TAGS, devq); 3844 if (np->sim == NULL) { 3845 cam_simq_free(devq); 3846 return; 3847 } 3848 3849 3850 if (xpt_bus_register(np->sim, 0) != CAM_SUCCESS) { 3851 free(np->sim, M_DEVBUF); 3852 return; 3853 } 3854 3855 #ifdef __alpha__ 3856 alpha_register_pci_scsi(config_id->bus, config_id->slot, np->sim); 3857 #endif 3858 3859 if (xpt_create_path(&np->path, /*periph*/NULL, 3860 cam_sim_path(np->sim), CAM_TARGET_WILDCARD, 3861 CAM_LUN_WILDCARD) != CAM_REQ_CMP) { 3862 xpt_bus_deregister(cam_sim_path(np->sim)); 3863 cam_sim_free(np->sim, /*free_simq*/TRUE); 3864 free(np->sim, M_DEVBUF); 3865 return; 3866 } -------- Christopher R. Bowman crb@ChrisBowman.com http://www.ChrisBowman.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 21 14: 3:12 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 227D914DCC for ; Fri, 21 May 1999 14:03:05 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id PAA72441; Fri, 21 May 1999 15:03:02 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905212103.PAA72441@panzer.plutotech.com> Subject: Re: Question about ncr.c In-Reply-To: <199905211933.PAA07285@quark.ChrisBowman.com> from "Christopher R. Bowman" at "May 21, 1999 03:31:31 pm" To: crb@ChrisBowman.com (Christopher R. Bowman) Date: Fri, 21 May 1999 15:03:01 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Christopher R. Bowman wrote... > a small section of ncr.c is presented below. Shouldn't line 3851 read > > cam_sim_free(np->sim, /*free_simq*/TRUE); > instead of just free? Not much practical difference, but it just seems more correct. [ ... ] > 3850 if (xpt_bus_register(np->sim, 0) != CAM_SUCCESS) { > 3851 free(np->sim, M_DEVBUF); > 3852 return; > 3853 } Yeah, looks like a bug. Your solution is correct. The current code will cause a memory leak since np->sim->devq won't get freed. 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 May 21 14:42: 8 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from quark.ChrisBowman.com (crbowman.erols.com [209.122.47.155]) by hub.freebsd.org (Postfix) with ESMTP id D212415286 for ; Fri, 21 May 1999 14:42:01 -0700 (PDT) (envelope-from crb@ChrisBowman.com) Received: from fermion (fermion.ChrisBowman.com [10.0.1.2]) by quark.ChrisBowman.com (8.9.2/8.8.8) with SMTP id RAA07519; Fri, 21 May 1999 17:41:41 -0400 (EDT) (envelope-from crb@ChrisBowman.com) Message-Id: <199905212141.RAA07519@quark.ChrisBowman.com> X-Sender: crb@quark X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Fri, 21 May 1999 17:40:12 -0400 To: "Kenneth D. Merry" From: "Christopher R. Bowman" Subject: Re: Question about ncr.c Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: <199905212103.PAA72441@panzer.plutotech.com> References: <199905211933.PAA07285@quark.ChrisBowman.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 03:03 PM 5/21/99 -0600, Kenneth D. Merry wrote: >Christopher R. Bowman wrote... >> a small section of ncr.c is presented below. Shouldn't line 3851 read >> >> cam_sim_free(np->sim, /*free_simq*/TRUE); >> instead of just free? Not much practical difference, but it just seems more correct. > >[ ... ] > >> 3850 if (xpt_bus_register(np->sim, 0) != CAM_SUCCESS) { >> 3851 free(np->sim, M_DEVBUF); >> 3852 return; >> 3853 } > >Yeah, looks like a bug. Your solution is correct. The current code will >cause a memory leak since np->sim->devq won't get freed. it's not like it's a serious bug, it only happens if memory is short at ncr attach time, and if that is the case, then you probably have other serious problems, but then again if we are going to have loadedable drivers in the future it is probably worth correcting. Do I need to send-pr this or will you take care of this (I don't have commit privs or I would do it myself). On another note, while I have you, I was looking through my old email archives and I found messages from when the cam work was being done saying that the ncr driver hadn't as yet been fully camified. Is there further work that needs to be done on the ncr driver under cam? -------- Christopher R. Bowman crb@ChrisBowman.com http://www.ChrisBowman.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 21 14:44:56 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from leap.innerx.net (leap.innerx.net [38.179.176.25]) by hub.freebsd.org (Postfix) with ESMTP id 8CBE314CC5 for ; Fri, 21 May 1999 14:44:53 -0700 (PDT) (envelope-from chris@holly.dyndns.org) Received: from holly.dyndns.org (ip90.houston2.tx.pub-ip.psi.net [38.11.201.90]) by leap.innerx.net (Postfix) with ESMTP id 581A137084; Fri, 21 May 1999 17:44:47 -0400 (EDT) Received: (from chris@localhost) by holly.dyndns.org (8.9.3/8.9.3) id QAA11250; Fri, 21 May 1999 16:46:25 -0500 (CDT) (envelope-from chris) Date: Fri, 21 May 1999 16:46:24 -0500 From: Chris Costello To: "Christopher R. Bowman" Cc: "Kenneth D. Merry" , freebsd-scsi@FreeBSD.ORG Subject: Re: Question about ncr.c Message-ID: <19990521164624.B10777@holly.dyndns.org> Reply-To: chris@calldei.com References: <199905211933.PAA07285@quark.ChrisBowman.com> <199905212103.PAA72441@panzer.plutotech.com> <199905212141.RAA07519@quark.ChrisBowman.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/0.96.2i In-Reply-To: <199905212141.RAA07519@quark.ChrisBowman.com>; from Christopher R. Bowman on Fri, May 21, 1999 at 05:40:12PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, May 21, 1999, Christopher R. Bowman wrote: > At 03:03 PM 5/21/99 -0600, Kenneth D. Merry wrote: > >Christopher R. Bowman wrote... > >> a small section of ncr.c is presented below. Shouldn't line 3851 read > >> > >> cam_sim_free(np->sim, /*free_simq*/TRUE); > >> instead of just free? Not much practical difference, but it just seems more > correct. > > > >[ ... ] > > > >> 3850 if (xpt_bus_register(np->sim, 0) != CAM_SUCCESS) { > >> 3851 free(np->sim, M_DEVBUF); > >> 3852 return; > >> 3853 } > > > >Yeah, looks like a bug. Your solution is correct. The current code will > >cause a memory leak since np->sim->devq won't get freed. > > it's not like it's a serious bug, it only happens if memory is short at ncr Serious or not, it's a bug, and bugs in drivers, especially fixable ones, are a no-no. -- Chris Costello Meets quality standards: It compiles without errors. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 21 14:51: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4AAE014D50 for ; Fri, 21 May 1999 14:50:59 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA10762; Fri, 21 May 1999 14:50:25 -0700 Date: Fri, 21 May 1999 14:49:23 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Chris Costello Cc: "Christopher R. Bowman" , "Kenneth D. Merry" , freebsd-scsi@FreeBSD.ORG Subject: Re: Question about ncr.c In-Reply-To: <19990521164624.B10777@holly.dyndns.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Serious or not, it's a bug, and bugs in drivers, especially > fixable ones, are a no-no. And: > Chris Costello > Meets quality standards: It compiles without errors. "cognitive dissonance" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 21 14:56:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 164C614D50 for ; Fri, 21 May 1999 14:56:41 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id PAA72831; Fri, 21 May 1999 15:56:39 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905212156.PAA72831@panzer.plutotech.com> Subject: Re: Question about ncr.c In-Reply-To: <199905212141.RAA07519@quark.ChrisBowman.com> from "Christopher R. Bowman" at "May 21, 1999 05:40:12 pm" To: crb@ChrisBowman.com (Christopher R. Bowman) Date: Fri, 21 May 1999 15:56:39 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Christopher R. Bowman wrote... > At 03:03 PM 5/21/99 -0600, Kenneth D. Merry wrote: > >Christopher R. Bowman wrote... > >> a small section of ncr.c is presented below. Shouldn't line 3851 read > >> > >> cam_sim_free(np->sim, /*free_simq*/TRUE); > >> instead of just free? Not much practical difference, but it just seems more > correct. > > > >[ ... ] > > > >> 3850 if (xpt_bus_register(np->sim, 0) != CAM_SUCCESS) { > >> 3851 free(np->sim, M_DEVBUF); > >> 3852 return; > >> 3853 } > > > >Yeah, looks like a bug. Your solution is correct. The current code will > >cause a memory leak since np->sim->devq won't get freed. > > it's not like it's a serious bug, it only happens if memory is short at ncr > attach time, and if that is the case, then you probably have other serious > problems, but then again if we are going to have loadedable drivers in the > future it is probably worth correcting. Do I need to send-pr this or will you > take care of this (I don't have commit privs or I would do it myself). I'll fix it. There's another bug just below that as well -- np->sim gets freed twice in once case. > On another note, while I have you, I was looking through my old email archives > and I found messages from when the cam work was being done saying that the ncr > driver hadn't as yet been fully camified. Is there further work that needs to > be done on the ncr driver under cam? Oh, I'm sure there's loads of work that needs to be done to that driver. I think the error recovery especially needs 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 Fri May 21 21:40:18 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from sasami.jurai.net (sasami.jurai.net [63.67.141.99]) by hub.freebsd.org (Postfix) with ESMTP id 8ED4114D39 for ; Fri, 21 May 1999 21:40:15 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with ESMTP id AAA03877 for ; Sat, 22 May 1999 00:40:15 -0400 (EDT) Date: Sat, 22 May 1999 00:40:15 -0400 (EDT) From: "Matthew N. Dodd" To: freebsd-scsi@freebsd.org Subject: Where to buy Symbios boards. 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'm looking for a Symbios SYM22802 board to drive the gaggle of differential drives I just scored. Anyone know of a good place to pick one of these up and about how much I should expect to pay for one? I'd go with an Adaptec 3944 but they're a tad pricy. Does QLOGIC make a dual channel board? Thanks. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 23 5:26:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id 50857152EB for ; Sun, 23 May 1999 05:26:39 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id WAA10648; Sun, 23 May 1999 22:25:16 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (4.1) id xma010645; Sun, 23 May 99 22:25:04 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id WAA29681 for ; Sun, 23 May 1999 22:25:04 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id WAA21108 for ; Sun, 23 May 1999 22:25:03 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id WAA05009; Sun, 23 May 1999 22:25:02 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199905231225.WAA05009@nymph.detir.qld.gov.au> To: freebsd-scsi@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: aha1542 brokenness, and CAM technique query Date: Sun, 23 May 1999 22:25:01 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The recent insertion of a 10ms delay in ahafetchtransinfo() does not help my -current box. The delay required is related to the number of devices on the chain, and my box needs 11ms. Big deal, you say? Well, the true answer is that aha_cmd() is broken, and there is no easy fix that I know of. Fiddling with splcam() is not sufficient. aha_cmd() should not be called if there are any other scsi commands in flight. Otherwise, AOP_START_MBOX might be issued in the *middle* of another command. This is impossible with the 1542 since there is just one shared command and parameter port, and the two colliding commands fail. Lucky that, since issuing random scsi commands is a file system scrambler. So, either I implement some sort of mutex in the bowels of the driver, or there is a simple way of telling CAM to single thread things for a while. Please, CAM experts, let me know if this is easy. Otherwise, I will do it the hard way. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 23 6:15:29 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from beach.silcom.com (beach.silcom.com [199.201.128.19]) by hub.freebsd.org (Postfix) with ESMTP id 9F8A21532D; Sun, 23 May 1999 06:15:20 -0700 (PDT) (envelope-from dburr@pobox.com) Received: from pm0-47.sba1.avtel.net (pm0-47.sba1.avtel.net [207.71.218.47]) by beach.silcom.com (Postfix) with ESMTP id B4B787F7; Sun, 23 May 1999 06:15:17 -0700 (PDT) Date: Sun, 23 May 1999 06:15:15 -0700 (PDT) From: Donald Burr X-Sender: dburr@control.colossus.dynip.com To: FreeBSD Questions Cc: FreeBSD SCSI Subject: Help! - "parity error during data-in phase" when using CD-R drv 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 have suddenly started getting the following types of error messages when trying to access a CD-ROM that's mounted in my SCSI CD-R (CD-recordiable, cd writer) device. May 23 03:01:51 control /kernel: (cd0:ahc0:0:4:0): parity error during Data-In phase. May 23 03:01:51 control /kernel: SEQADDR == 0x110 May 23 03:01:52 control /kernel: SCSIRATE == 0xf May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): SCB 0x31 - timed out in datain phase, SEQADDR == 0x153 May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): BDR message in message buffer May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): SCB 0x31 - timed out in datain phase, SEQADDR == 0x153 May 23 03:02:35 control /kernel: (cd0:ahc0:0:4:0): no longer in timeout, status = 34b May 23 03:02:35 control /kernel: ahc0: Issued Channel A Bus Reset. 120 SCBs aborted May 23 03:02:35 control /kernel: (cd0:ahc0:0:4:0): parity error during Data-In phase. May 23 03:02:35 control /kernel: SEQADDR == 0x110 May 23 03:02:35 control /kernel: SCSIRATE == 0xf [...] Please note that ALL OF MY OTHER SCSI PERIPHERALS ARE WORKING FINE. Before I continue, let me mention my system's configuration. EPoX EP-MVP3G Motherboard (VIA MVP3 chipset) AMD K6-2/300 CPU (100 bus * 3 multiplier) 128 MB PC100 SDRAM DIMM NO IDE HARD DRIVES IDE CD-ROM: Creative Labs PC-DVD Encore Dxr2 (Primary master) SCSI: Adaptec AHA-2940AU PCI SCSI controller SCSI disk 0: Quantum Viking 4.5 GB SCSI disk 1: Quantum Viking 4.5 GB SCSI disk 2: IBM 0662 S12 1.0 GB SCSI CD-ROM 4: Sony CDU-926S CD-Recordable (CD-R) drive SCSI Scanner 5: UMAX Astra 1200S SCSI DAT drive 6: Wangtek 6200-HS (Yes, the bus is properly terminated and all that, I checked.) OS: FreeBSD 3.1-RELEASE Anyway, as I said, my other SCSI devices (hard drives, scanner, etc.) are working fine. The ATAPI DVD-ROM drive is also working fine. It's only the SCSI CD-recorder that does not work. It fails when accessing mounted CD's (doing a 'du' of the CD will bring the error on really quickly), and also I cannot use tosha to grab audio tracks off of it (same error). I don't dare trying to write a CD on it... The drive does not work under Windows either. Here's something interesting: This same hardware configuration (except the motherboard) was, up until a few weeks ago, installed in an AT case with a Tyan Titan Turbo S1571 motherboard, and it worked fine (CD burner and all). However in mid-April I got myself a new ATX motherboard (the EPoX one) and case, and I moved all of my hardware into that. I don't really use the CD-burner that often, so it was only just yesterday (when I wanted to grab some audio tracks from a music CD to burn a "greatest hits" type cd), that I noticed the errors. It seems to me, then, that I somehow managed to damage the drive while moving it between cases. But I thought I had better post this anyway, in case someone else out there has any ideas as to what I'm doing wrong, or how I might go about fixing this. Thanks in advance for whatever help you may be able to provide. -- Donald Burr | PGP: Your *NEW* WWW HomePage: http://more.at/dburr/ ICQ #16997506 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 23 11:26:10 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 93BE214FB8 for ; Sun, 23 May 1999 11:26:08 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id MAA19947; Sun, 23 May 1999 12:16:07 -0600 (MDT) Date: Sun, 23 May 1999 12:16:07 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199905231816.MAA19947@narnia.plutotech.com> To: Donald Burr Cc: scsi@FreeBSD.org Subject: Re: Help! - "parity error during data-in phase" when using CD-R drv X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > I have suddenly started getting the following types of error messages when > trying to access a CD-ROM that's mounted in my SCSI CD-R (CD-recordiable, > cd writer) device. > > May 23 03:01:51 control /kernel: (cd0:ahc0:0:4:0): parity error during > Data-In phase. You have a bad connection to this device. Since your other devices seem to work okay, this is likely a bent pin on the CD-R's connector, or the one connector attached to this device is defective. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 23 20:44:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 3CF4914EC5 for ; Sun, 23 May 1999 20:44:35 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id VAA78530; Sun, 23 May 1999 21:43:20 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id VAA16346; Sun, 23 May 1999 21:43:35 -0600 (MDT) Message-Id: <199905240343.VAA16346@harmony.village.org> To: Stephen McKay Subject: Re: aha1542 brokenness, and CAM technique query Cc: freebsd-scsi@FreeBSD.ORG In-reply-to: Your message of "Sun, 23 May 1999 22:25:01 +1000." <199905231225.WAA05009@nymph.detir.qld.gov.au> References: <199905231225.WAA05009@nymph.detir.qld.gov.au> Date: Sun, 23 May 1999 21:43:35 -0600 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199905231225.WAA05009@nymph.detir.qld.gov.au> Stephen McKay writes: : Big deal, you say? Well, the true answer is that aha_cmd() is broken, : and there is no easy fix that I know of. Fiddling with splcam() is not : sufficient. aha_cmd() should not be called if there are any other scsi : commands in flight. Otherwise, AOP_START_MBOX might be issued in the : *middle* of another command. This is impossible with the 1542 since : there is just one shared command and parameter port, and the two colliding : commands fail. Lucky that, since issuing random scsi commands is a : file system scrambler. Yuck. I suspect that the buslogic will have same problem. Also, Justin keeps telling me that I need to merge his changes from bt_cmd. One of the things it does is to check the interrupt status while sending commands, but it doesn't seem to try any interlocking. I don't know if the buslogic boards have a similar limitation or not. : So, either I implement some sort of mutex in the bowels of the driver, : or there is a simple way of telling CAM to single thread things for : a while. Please, CAM experts, let me know if this is easy. Otherwise, : I will do it the hard way. I suspect that Justin will have something to say about that :-) Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 23 21: 8:25 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from quark.ChrisBowman.com (crbowman.erols.com [209.122.47.155]) by hub.freebsd.org (Postfix) with ESMTP id 446A6150D6; Sun, 23 May 1999 21:08:20 -0700 (PDT) (envelope-from crb@ChrisBowman.com) Received: from fermion (crb@fermion.ChrisBowman.com [10.0.1.2]) by quark.ChrisBowman.com (8.9.2/8.8.8) with SMTP id AAA02561; Mon, 24 May 1999 00:08:08 -0400 (EDT) (envelope-from crb@ChrisBowman.com) Message-Id: <199905240408.AAA02561@quark.ChrisBowman.com> X-Sender: crb@quark X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Mon, 24 May 1999 00:06:24 -0400 To: dg@root.com From: "Christopher R. Bowman" Subject: Re: Quad Processor System Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG In-Reply-To: <199905232235.PAA06073@implode.root.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 03:35 PM 5/23/99 -0700, David Greenman wrote: >>>>http://www.intel.com/design/servers/SC450NX/index.htm >>> >>> The onboard Symbios SCSI controller won't work, but you can work around >>>that by plugging in an Adaptec aha-2940u2w. I put together such a system for >>>a client who is quite happy with it. >>> >>>-DG >> >>Why doesn't the onboard Symbios SCSI controller work? > > It's a newer chip that isn't properly supported, at least when I last tried >it a few months ago. The Adaptec chips are generally better supported in >FreeBSD and I wouldn't consider anything else for systems that I build. I have a set of their data books here (Symbios '875 '876 '895 '896) and have been looking around in the ncr driver lately. Do you have any concrete ideas about what isn't working, or has no one ever bothered to teach the drivers about the '895 series chips? I find it very curious that the Adaptec controllers are such the rage considering how hard I tried to get data books from them and failed. Symbios is only to happy to send out their data books. I know Adaptec supports Justin very well, but contrary to Justin's mail[*] of 5/8/98 I wasn't able to get any documentation on the parts. * http://www.freebsd.org/cgi/getmsg.cgi?fetch=55133+58159+/usr/local/www/db/te xt/1998/freebsd-hardware/19980503.freebsd-hardware -------- Christopher R. Bowman crb@ChrisBowman.com http://www.ChrisBowman.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 23 21:59:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id D40E514CB9 for ; Sun, 23 May 1999 21:59:13 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id OAA01931; Mon, 24 May 1999 14:53:52 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (4.1) id xma001848; Mon, 24 May 99 14:53:26 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id OAA11681; Mon, 24 May 1999 14:53:25 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id OAA04600; Mon, 24 May 1999 14:53:25 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id OAA11833; Mon, 24 May 1999 14:53:23 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199905240453.OAA11833@nymph.detir.qld.gov.au> To: Warner Losh Cc: freebsd-scsi@FreeBSD.ORG, syssgm@detir.qld.gov.au Subject: Re: aha1542 brokenness, and CAM technique query References: <199905231225.WAA05009@nymph.detir.qld.gov.au> <199905240343.VAA16346@harmony.village.org> In-Reply-To: <199905240343.VAA16346@harmony.village.org> from Warner Losh at "Sun, 23 May 1999 21:43:35 -0600" Date: Mon, 24 May 1999 14:53:22 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sunday, 23rd May 1999, Warner Losh wrote: >In message <199905231225.WAA05009@nymph.detir.qld.gov.au> Stephen McKay writes >: >: Big deal, you say? Well, the true answer is that aha_cmd() is broken, >: and there is no easy fix that I know of. Fiddling with splcam() is not >: sufficient. aha_cmd() should not be called if there are any other scsi >: commands in flight. Otherwise, AOP_START_MBOX might be issued in the >: *middle* of another command. This is impossible with the 1542 since >: there is just one shared command and parameter port, and the two colliding >: commands fail. Lucky that, since issuing random scsi commands is a >: file system scrambler. > >Yuck. I suspect that the buslogic will have same problem. Also, >Justin keeps telling me that I need to merge his changes from bt_cmd. >One of the things it does is to check the interrupt status while >sending commands, but it doesn't seem to try any interlocking. I >don't know if the buslogic boards have a similar limitation or not. I expect that the buslogics will fail also, but haven't tried any of my cards yet. Justin has ported the bt_cmd changes to the aha driver, and I'll give that a go in case my analysis is not correct. But I don't expect it to help given that I already played with the same stuff attempting to fix it by myself. Copying from my mail to Justin: A mailbox command (ie real SCSI command) is in flight when aha_cmd() is called. After the command byte, but before all of the parameter bytes are written, it completes, calling aha_intr(), which calls ahadone(), which calls xpt_done() which (as far as I can tell) allows something else to run which queues another command which issues another mailbox command. Crunch! At least, that's what I think is happening. I have thought of a way to fix this using splcam(), but I'm not sure if everyone will accept the tradeoff. If priority is raised before the command byte is issued and lowered after all parameter bytes have been sent, then the problem cannot occur. I have not yet tested this, and will tonight, and then the wrangling over the ugliness can begin. A cleaner solution (assuming my analysis is correct) is to find some way to tell CAM to single thread the aha driver for a while. I don't know anything about CAM, so I'm asking. Is it easy? >: So, either I implement some sort of mutex in the bowels of the driver, >: or there is a simple way of telling CAM to single thread things for >: a while. Please, CAM experts, let me know if this is easy. Otherwise, >: I will do it the hard way. > >I suspect that Justin will have something to say about that :-) I'm sure he will, as soon as I've convinced him that there is a real problem. Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 24 0:28:10 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id CAE5A14C48 for ; Mon, 24 May 1999 00:28:07 -0700 (PDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id BAA78913; Mon, 24 May 1999 01:26:51 -0600 (MDT) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id BAA17292; Mon, 24 May 1999 01:27:14 -0600 (MDT) Message-Id: <199905240727.BAA17292@harmony.village.org> To: Stephen McKay Subject: Re: aha1542 brokenness, and CAM technique query Cc: freebsd-scsi@FreeBSD.ORG In-reply-to: Your message of "Mon, 24 May 1999 14:53:22 +1000." <199905240453.OAA11833@nymph.detir.qld.gov.au> References: <199905240453.OAA11833@nymph.detir.qld.gov.au> <199905231225.WAA05009@nymph.detir.qld.gov.au> <199905240343.VAA16346@harmony.village.org> Date: Mon, 24 May 1999 01:27:13 -0600 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <199905240453.OAA11833@nymph.detir.qld.gov.au> Stephen McKay writes: : A mailbox command (ie real SCSI command) is in flight when aha_cmd() : is called. After the command byte, but before all of the parameter : bytes are written, it completes, calling aha_intr(), which calls : ahadone(), which calls xpt_done() which (as far as I can tell) allows : something else to run which queues another command which issues another : mailbox command. Crunch! At least, that's what I think is happening. Ouch! I think that Justin's bt_cmd will also have this same problem, since it doesn't block CAM interrupts while the bt_cmd is processing. It does check to see if there is an interrupt pending, however. Maybe a "simple" solution would be to mask off the aha interrupts while processing and check for interrupts in the middle of processing. However, I don't have the aha databook here at home and I can't tell from the driver's header files if there is an easy way to do this. One could go to splcam around the aha_cmd stuff. From approx the aha_outb of the COMMAND_REG to the end of the function where any interrupts are cleared. IT may still require a port of Justin's changes, but it might get you going... However, it does seem a little extreme, since all that needs to be masked is the interrupts from this card.... Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 24 1:54: 2 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from relay1.mail.uk.psi.net (relay1.mail.uk.psi.net [154.32.105.6]) by hub.freebsd.org (Postfix) with ESMTP id 931BF14D26 for ; Mon, 24 May 1999 01:53:59 -0700 (PDT) (envelope-from amobbs@allstor-sw.co.uk) Received: from mail.plasmon.co.uk ([193.115.5.217]) by relay1.mail.uk.psi.net with smtp (Exim 2.02 #3) id 10lqUb-0003Vb-00 for freebsd-scsi@freebsd.org; Mon, 24 May 1999 09:53:53 +0100 Received: by mail.plasmon.co.uk(Lotus SMTP MTA v4.6.3 (778.2 1-4-1999)) id 8025677B.00309C00 ; Mon, 24 May 1999 09:50:56 +0100 X-Lotus-FromDomain: PLASNOTES From: amobbs@allstor-sw.co.uk To: freebsd-scsi@freebsd.org Message-ID: <8025677B.00309A45.00@mail.plasmon.co.uk> Date: Mon, 24 May 1999 09:50:51 +0100 Subject: Bug in cam_periph.c Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It looks to me that the tests for useracc read/write permission in cam_periph_mapmem are the wrong way around. Surely if the data direction is OUT, you want to be able to read the memory, and if it's IN you need to be able to write to the buffer. (He said, having tried to put a R/O mmap'd buffer through a passthrough driver write with little success.) (patch against -stable). --- cam_periph.c.orig Sun May 23 11:58:17 1999 +++ cam_periph.c Sun May 23 12:00:31 1999 @@ -558,7 +558,7 @@ return(E2BIG); } - if (dirs[i] & CAM_DIR_IN) { + if (dirs[i] & CAM_DIR_OUT) { flags[i] = B_READ; if (useracc(*data_ptrs[i], lengths[i], B_READ) == 0){ printf("cam_periph_mapmem: error, " @@ -574,7 +574,7 @@ * XXX this check is really bogus, since B_WRITE currently * is all 0's, and so it is "set" all the time. */ - if (dirs[i] & CAM_DIR_OUT) { + if (dirs[i] & CAM_DIR_IN) { flags[i] |= B_WRITE; if (useracc(*data_ptrs[i], lengths[i], B_WRITE) == 0){ printf("cam_periph_mapmem: error, " To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 24 2:40: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from hyperion.eclipse.net.uk (hyperion.eclipse.net.uk [195.188.32.122]) by hub.freebsd.org (Postfix) with ESMTP id 6A67B15231; Mon, 24 May 1999 02:39:59 -0700 (PDT) (envelope-from stuart@eclipse.net.uk) Received: from eclipse.net.uk (elara.eclipse.net.uk [195.188.32.31]) by hyperion.eclipse.net.uk (8.9.3/8.9.3) with ESMTP id KAA46703; Mon, 24 May 1999 10:39:43 +0100 (BST) Message-ID: <37491E5F.B4C83D57@eclipse.net.uk> Date: Mon, 24 May 1999 10:39:43 +0100 From: Stuart Henderson Organization: Eclipse Networking X-Mailer: Mozilla 4.6 [en] (WinNT; I) X-Accept-Language: en-GB MIME-Version: 1.0 To: "Christopher R. Bowman" Cc: dg@root.com, freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Quad Processor System References: <199905240408.AAA02561@quark.ChrisBowman.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have a set of their data books here (Symbios '875 '876 '895 '896) > and have been looking around in the ncr driver lately. Do you have > any concrete ideas about what isn't working, or has no one ever > bothered to teach the drivers about the '895 series chips? If you're talking about using 80MB/sec, I asked about this and someone suggested "options SCSI_NCR_DFLT_SYNC=10", which I have used on a squid box for a couple of months without problems, dmesg reports the higher speed and dd'ing da0 to /dev/null gives 13mb/sec rather than 8mb/sec so it seems to be working. Stuart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 24 7: 1:25 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 8E94414BF8 for ; Mon, 24 May 1999 07:01:22 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id HAA21077; Mon, 24 May 1999 07:51:21 -0600 (MDT) Date: Mon, 24 May 1999 07:51:21 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199905241351.HAA21077@narnia.plutotech.com> To: Warner Losh Cc: scsi@FreeBSD.org Subject: Re: aha1542 brokenness, and CAM technique query X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <199905240453.OAA11833@nymph.detir.qld.gov.au> <199905231225.WAA05009@nymph.detir.qld.gov.au> <199905240343.VAA16346@harmony.village.org> <199905240727.BAA17292@harmony.village.org> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199905240727.BAA17292@harmony.village.org> you wrote: > In message <199905240453.OAA11833@nymph.detir.qld.gov.au> Stephen McKay writes: > : A mailbox command (ie real SCSI command) is in flight when aha_cmd() > : is called. After the command byte, but before all of the parameter > : bytes are written, it completes, calling aha_intr(), which calls > : ahadone(), which calls xpt_done() which (as far as I can tell) allows > : something else to run which queues another command which issues another > : mailbox command. Crunch! At least, that's what I think is happening. > > Ouch! I think that Justin's bt_cmd will also have this same problem, > since it doesn't block CAM interrupts while the bt_cmd is processing. > It does check to see if there is an interrupt pending, however. You should be at splsoftcam() when this code is executed which will prevent the queuing of any additional commands to the card. If we aren't at splsoftcam() here, then there is a bug in the cam xpt. You do not need to block hardware interrupts in order to prevent additional commands from comming down the pipe due to the deferred processing technique used by CAM (similar to the networkig stack). -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 24 8:43:49 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id E93D414C8C for ; Mon, 24 May 1999 08:43:47 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id JAA24675; Mon, 24 May 1999 09:41:25 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905241541.JAA24675@panzer.plutotech.com> Subject: Re: Bug in cam_periph.c In-Reply-To: <8025677B.00309A45.00@mail.plasmon.co.uk> from "amobbs@allstor-sw.co.uk" at "May 24, 1999 09:50:51 am" To: amobbs@allstor-sw.co.uk Date: Mon, 24 May 1999 09:41:25 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 amobbs@allstor-sw.co.uk wrote... > > It looks to me that the tests for useracc read/write permission in > cam_periph_mapmem are the wrong way around. Surely if the data direction is OUT, > you want to be able to read the memory, and if it's IN you need to be able to > write to the buffer. (He said, having tried to put a R/O mmap'd buffer through a > passthrough driver write with little success.) > > (patch against -stable). > > --- cam_periph.c.orig Sun May 23 11:58:17 1999 > +++ cam_periph.c Sun May 23 12:00:31 1999 > @@ -558,7 +558,7 @@ > return(E2BIG); > } > > - if (dirs[i] & CAM_DIR_IN) { > + if (dirs[i] & CAM_DIR_OUT) { > flags[i] = B_READ; > if (useracc(*data_ptrs[i], lengths[i], B_READ) == 0){ > printf("cam_periph_mapmem: error, " [ ... ] Oops, looks like a bug all right. Thanks for finding 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 Tue May 25 11: 9:41 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id CA7F014CE5; Tue, 25 May 1999 11:09:33 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id LAA01025; Tue, 25 May 1999 11:03:16 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Tue, 25 May 1999 11:03:15 -0700 (PDT) From: Doug White To: Donald Burr Cc: FreeBSD Questions , FreeBSD SCSI Subject: Re: Help! - "parity error during data-in phase" when using CD-R drv In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, 23 May 1999, Donald Burr wrote: > I have suddenly started getting the following types of error messages when > trying to access a CD-ROM that's mounted in my SCSI CD-R (CD-recordiable, > cd writer) device. > > May 23 03:01:51 control /kernel: (cd0:ahc0:0:4:0): parity error during Data-In phase. > May 23 03:01:51 control /kernel: SEQADDR == 0x110 > May 23 03:01:52 control /kernel: SCSIRATE == 0xf > May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): SCB 0x31 - timed out in datain phase, SEQADDR == 0x153 > May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): BDR message in message buffer > May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): SCB 0x31 - timed out in datain phase, SEQADDR == 0x153 > May 23 03:02:35 control /kernel: (cd0:ahc0:0:4:0): no longer in timeout, status = 34b > May 23 03:02:35 control /kernel: ahc0: Issued Channel A Bus Reset. 120 SCBs aborted > May 23 03:02:35 control /kernel: (cd0:ahc0:0:4:0): parity error during Data-In phase. > May 23 03:02:35 control /kernel: SEQADDR == 0x110 > May 23 03:02:35 control /kernel: SCSIRATE == 0xf > [...] > > Please note that ALL OF MY OTHER SCSI PERIPHERALS ARE WORKING FINE. Hm, this implies that the CDR is busted. My guess is that it's the cable. > SCSI: Adaptec AHA-2940AU PCI SCSI controller > SCSI disk 0: Quantum Viking 4.5 GB > SCSI disk 1: Quantum Viking 4.5 GB > SCSI disk 2: IBM 0662 S12 1.0 GB > SCSI CD-ROM 4: Sony CDU-926S CD-Recordable (CD-R) drive > SCSI Scanner 5: UMAX Astra 1200S > SCSI DAT drive 6: Wangtek 6200-HS > (Yes, the bus is properly terminated and all that, I checked.) Did you check it again? > Anyway, as I said, my other SCSI devices (hard drives, scanner, etc.) are > working fine. The ATAPI DVD-ROM drive is also working fine. It's only > the SCSI CD-recorder that does not work. It fails when accessing mounted > CD's (doing a 'du' of the CD will bring the error on really quickly), and > also I cannot use tosha to grab audio tracks off of it (same error). I > don't dare trying to write a CD on it... It may not support those operations. How old is the CDR? > The drive does not work under Windows either. Hm, perhaps the entire drive is bad. > It seems to me, then, that I somehow managed to damage the drive while > moving it between cases. But I thought I had better post this anyway, in > case someone else out there has any ideas as to what I'm doing wrong, or > how I might go about fixing this. Cable on upside down? Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 25 11:44:23 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ginger.kf7nn.com (mti-r1-aptis-4-p1997.cybertrails.com [162.42.15.204]) by hub.freebsd.org (Postfix) with ESMTP id A007C15A10; Tue, 25 May 1999 11:44:06 -0700 (PDT) (envelope-from root@ginger.kf7nn.com) Received: (from root@localhost) by ginger.kf7nn.com (8.9.3/8.9.2) id LAA00369; Tue, 25 May 1999 11:43:42 -0700 (MST) (envelope-from root) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Tue, 25 May 1999 11:43:42 -0700 (MST) From: laszlo vagner To: Doug White Subject: Re: Help! - "parity error during data-in phase" when using CD-R Cc: FreeBSD SCSI , FreeBSD Questions , Donald Burr Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org You may have moved some dust onto the lense. try cleaning the laser with a q-tip and some alchohol. worked for me... On 25-May-99 Doug White wrote: > On Sun, 23 May 1999, Donald Burr wrote: > >> I have suddenly started getting the following types of error messages when >> trying to access a CD-ROM that's mounted in my SCSI CD-R (CD-recordiable, >> cd writer) device. >> >> May 23 03:01:51 control /kernel: (cd0:ahc0:0:4:0): parity error during >> Data-In phase. >> May 23 03:01:51 control /kernel: SEQADDR == 0x110 >> May 23 03:01:52 control /kernel: SCSIRATE == 0xf >> May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): SCB 0x31 - timed out in >> datain phase, SEQADDR == 0x153 >> May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): BDR message in message >> buffer >> May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): SCB 0x31 - timed out in >> datain phase, SEQADDR == 0x153 >> May 23 03:02:35 control /kernel: (cd0:ahc0:0:4:0): no longer in timeout, >> status = 34b >> May 23 03:02:35 control /kernel: ahc0: Issued Channel A Bus Reset. 120 SCBs >> aborted >> May 23 03:02:35 control /kernel: (cd0:ahc0:0:4:0): parity error during >> Data-In phase. >> May 23 03:02:35 control /kernel: SEQADDR == 0x110 >> May 23 03:02:35 control /kernel: SCSIRATE == 0xf >> [...] >> >> Please note that ALL OF MY OTHER SCSI PERIPHERALS ARE WORKING FINE. > > Hm, this implies that the CDR is busted. My guess is that it's the cable. > >> SCSI: Adaptec AHA-2940AU PCI SCSI controller >> SCSI disk 0: Quantum Viking 4.5 GB >> SCSI disk 1: Quantum Viking 4.5 GB >> SCSI disk 2: IBM 0662 S12 1.0 GB >> SCSI CD-ROM 4: Sony CDU-926S CD-Recordable (CD-R) drive >> SCSI Scanner 5: UMAX Astra 1200S >> SCSI DAT drive 6: Wangtek 6200-HS >> (Yes, the bus is properly terminated and all that, I checked.) > > Did you check it again? > >> Anyway, as I said, my other SCSI devices (hard drives, scanner, etc.) are >> working fine. The ATAPI DVD-ROM drive is also working fine. It's only >> the SCSI CD-recorder that does not work. It fails when accessing mounted >> CD's (doing a 'du' of the CD will bring the error on really quickly), and >> also I cannot use tosha to grab audio tracks off of it (same error). I >> don't dare trying to write a CD on it... > > It may not support those operations. How old is the CDR? > >> The drive does not work under Windows either. > > Hm, perhaps the entire drive is bad. > >> It seems to me, then, that I somehow managed to damage the drive while >> moving it between cases. But I thought I had better post this anyway, in >> case someone else out there has any ideas as to what I'm doing wrong, or >> how I might go about fixing this. > > Cable on upside down? > > Doug White > Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve > http://gladstone.uoregon.edu/~dwhite | www.freebsd.org > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message ---------------------------------- Vetex C/O L. Vagner 3600 W. Mountain Drive Flagstaff, AZ 86001 E-Mail: laszlo vagner Date: 25-May-99 Time: 11:42:24 Windows Exception Error: noun: Meaning- With the exception of a reboot anything you do will fail to recover the system. ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 25 12:22:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from revolution.3-cities.com (revolution.3-cities.com [204.203.224.155]) by hub.freebsd.org (Postfix) with ESMTP id 8D54A151AB; Tue, 25 May 1999 12:22:17 -0700 (PDT) (envelope-from kstewart@3-cities.com) Received: from 3-cities.com (kenn2190.bossig.com [208.26.242.190]) by revolution.3-cities.com (8.9.3/8.9.3) with ESMTP id MAA03578; Tue, 25 May 1999 12:15:56 -0700 (PDT) Message-ID: <374AF6E8.9CD7300C@3-cities.com> Date: Tue, 25 May 1999 12:15:52 -0700 From: Kent Stewart Organization: BOSSig X-Mailer: Mozilla 4.51 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: Doug White Cc: Donald Burr , FreeBSD Questions , FreeBSD SCSI Subject: Re: Help! - "parity error during data-in phase" when using CD-Rdrv References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Doug White wrote: > > On Sun, 23 May 1999, Donald Burr wrote: > > > I have suddenly started getting the following types of error messages when > > trying to access a CD-ROM that's mounted in my SCSI CD-R (CD-recordiable, > > cd writer) device. > > > > May 23 03:01:51 control /kernel: (cd0:ahc0:0:4:0): parity error during Data-In phase. > > May 23 03:01:51 control /kernel: SEQADDR == 0x110 > > May 23 03:01:52 control /kernel: SCSIRATE == 0xf > > May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): SCB 0x31 - timed out in datain phase, SEQADDR == 0x153 > > May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): BDR message in message buffer > > May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): SCB 0x31 - timed out in datain phase, SEQADDR == 0x153 > > May 23 03:02:35 control /kernel: (cd0:ahc0:0:4:0): no longer in timeout, status = 34b > > May 23 03:02:35 control /kernel: ahc0: Issued Channel A Bus Reset. 120 SCBs aborted > > May 23 03:02:35 control /kernel: (cd0:ahc0:0:4:0): parity error during Data-In phase. > > May 23 03:02:35 control /kernel: SEQADDR == 0x110 > > May 23 03:02:35 control /kernel: SCSIRATE == 0xf > > [...] > > > > Please note that ALL OF MY OTHER SCSI PERIPHERALS ARE WORKING FINE. > > Hm, this implies that the CDR is busted. My guess is that it's the cable. > > > SCSI: Adaptec AHA-2940AU PCI SCSI controller > > SCSI disk 0: Quantum Viking 4.5 GB > > SCSI disk 1: Quantum Viking 4.5 GB > > SCSI disk 2: IBM 0662 S12 1.0 GB > > SCSI CD-ROM 4: Sony CDU-926S CD-Recordable (CD-R) drive > > SCSI Scanner 5: UMAX Astra 1200S > > SCSI DAT drive 6: Wangtek 6200-HS > > (Yes, the bus is properly terminated and all that, I checked.) > > Did you check it again? There are a few people I know that have been having problems with Adaptec AHA-2940AU/UW controller's unless power is supplied to the terminator. Using bus power created problems for those systems. I have also had a bad power connector on an internal power supply. It is usually the one on the end of the daisy chain. If you have a free power connector you might replace the connector you are using to power the CDROM with a free one. If you don't, add a Y cable and then use the new connector for power. I have also hooked a scsi cable incorrectly. Nothing on the scsi controller worked when I did that. You can't hook a scsi cable up to a CDROM off one pin like you can some devices. Nothing worked when you do that either. It seems like you end up with a ground on a data line or power. Kent > > > Anyway, as I said, my other SCSI devices (hard drives, scanner, etc.) are > > working fine. The ATAPI DVD-ROM drive is also working fine. It's only > > the SCSI CD-recorder that does not work. It fails when accessing mounted > > CD's (doing a 'du' of the CD will bring the error on really quickly), and > > also I cannot use tosha to grab audio tracks off of it (same error). I > > don't dare trying to write a CD on it... > > It may not support those operations. How old is the CDR? > > > The drive does not work under Windows either. > > Hm, perhaps the entire drive is bad. > > > It seems to me, then, that I somehow managed to damage the drive while > > moving it between cases. But I thought I had better post this anyway, in > > case someone else out there has any ideas as to what I'm doing wrong, or > > how I might go about fixing this. > > Cable on upside down? > > Doug White > Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve > http://gladstone.uoregon.edu/~dwhite | www.freebsd.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Kent Stewart Richland, WA mailto:kstewart@3-cities.com http://www.3-cities.com/~kstewart/index.html SETI (Search for Extraterrestrial Intelligence) @ Home http://setiathome.ssl.berkeley.edu/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 25 13: 8: 1 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id A77FE15A2F; Tue, 25 May 1999 13:07:51 -0700 (PDT) (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 FAA08620; Wed, 26 May 1999 05:37:47 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id FAA99684; Wed, 26 May 1999 05:37:43 +0930 (CST) Date: Wed, 26 May 1999 05:37:43 +0930 From: Greg Lehey To: Doug White Cc: Donald Burr , FreeBSD Questions , FreeBSD SCSI Subject: Re: Help! - "parity error during data-in phase" when using CD-R drv Message-ID: <19990526053742.R95827@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Doug White on Tue, May 25, 1999 at 11:03:15AM -0700 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF 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 Tuesday, 25 May 1999 at 11:03:15 -0700, Doug White wrote: > On Sun, 23 May 1999, Donald Burr wrote: > >> I have suddenly started getting the following types of error messages when >> trying to access a CD-ROM that's mounted in my SCSI CD-R (CD-recordiable, >> cd writer) device. >> >> May 23 03:01:51 control /kernel: (cd0:ahc0:0:4:0): parity error during Data-In phase. >> May 23 03:01:51 control /kernel: SEQADDR == 0x110 >> May 23 03:01:52 control /kernel: SCSIRATE == 0xf >> May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): SCB 0x31 - timed out in datain phase, SEQADDR == 0x153 >> May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): BDR message in message buffer >> May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): SCB 0x31 - timed out in datain phase, SEQADDR == 0x153 >> May 23 03:02:35 control /kernel: (cd0:ahc0:0:4:0): no longer in timeout, status = 34b >> May 23 03:02:35 control /kernel: ahc0: Issued Channel A Bus Reset. 120 SCBs aborted >> May 23 03:02:35 control /kernel: (cd0:ahc0:0:4:0): parity error during Data-In phase. >> May 23 03:02:35 control /kernel: SEQADDR == 0x110 >> May 23 03:02:35 control /kernel: SCSIRATE == 0xf >> [...] >> >> Please note that ALL OF MY OTHER SCSI PERIPHERALS ARE WORKING FINE. > > Hm, this implies that the CDR is busted. My guess is that it's the > cable. If it were the cable, the other devices wouldn't work either. And it wouldn't explain why this happened suddenly. >> SCSI: Adaptec AHA-2940AU PCI SCSI controller >> SCSI disk 0: Quantum Viking 4.5 GB >> SCSI disk 1: Quantum Viking 4.5 GB >> SCSI disk 2: IBM 0662 S12 1.0 GB >> SCSI CD-ROM 4: Sony CDU-926S CD-Recordable (CD-R) drive >> SCSI Scanner 5: UMAX Astra 1200S >> SCSI DAT drive 6: Wangtek 6200-HS >> (Yes, the bus is properly terminated and all that, I checked.) > > Did you check it again? Again, if it was a simple termination problem, the others wouldn't work either. >> Anyway, as I said, my other SCSI devices (hard drives, scanner, etc.) are >> working fine. The ATAPI DVD-ROM drive is also working fine. It's only >> the SCSI CD-recorder that does not work. It fails when accessing mounted >> CD's (doing a 'du' of the CD will bring the error on really quickly), and >> also I cannot use tosha to grab audio tracks off of it (same error). I >> don't dare trying to write a CD on it... > > It may not support those operations. How old is the CDR? If it doesn't support the operation, it would say so. A parity error suggests that there's something wrong with the connection or the device. We've ruled out the connection. >> The drive does not work under Windows either. > > Hm, perhaps the entire drive is bad. Sounds like it. >> It seems to me, then, that I somehow managed to damage the drive while >> moving it between cases. But I thought I had better post this anyway, in >> case someone else out there has any ideas as to what I'm doing wrong, or >> how I might go about fixing this. > > Cable on upside down? That would stop everything from working. It's possible, though unlikely in this case, that the device is particularly sensitive to the bus load and termination. I've had a couple of drives like that, and you (Donald) have a lot of stuff on the chain. Could you try removing as much as possible (at least the DDS drive and the scanner, and any disks you can get by without for a test), and see if you can get it to work then. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html 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 Tue May 25 13:25: 7 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 93A0E15AE1; Tue, 25 May 1999 13:25:02 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id OAA04678; Tue, 25 May 1999 14:22:16 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905252022.OAA04678@panzer.plutotech.com> Subject: Re: Help! - "parity error during data-in phase" when using CD-R drv In-Reply-To: <19990526053742.R95827@freebie.lemis.com> from Greg Lehey at "May 26, 1999 05:37:43 am" To: grog@lemis.com (Greg Lehey) Date: Tue, 25 May 1999 14:22:16 -0600 (MDT) Cc: dwhite@resnet.uoregon.edu (Doug White), dburr@pobox.com (Donald Burr), freebsd-questions@FreeBSD.ORG (FreeBSD Questions), freebsd-scsi@FreeBSD.ORG (FreeBSD SCSI) X-Mailer: ELM [version 2.4ME+ PL54 (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 I think y'all must have all missed this thread on the -scsi list. Donald already posted this to -scsi, and Justin suggested that it may be a bent pin on the connector on the CD-R drive. That would explain why the other devices work fine, but the CD-R doesn't. Greg Lehey wrote... > On Tuesday, 25 May 1999 at 11:03:15 -0700, Doug White wrote: > > On Sun, 23 May 1999, Donald Burr wrote: > > > >> I have suddenly started getting the following types of error messages when > >> trying to access a CD-ROM that's mounted in my SCSI CD-R (CD-recordiable, > >> cd writer) device. > >> > >> May 23 03:01:51 control /kernel: (cd0:ahc0:0:4:0): parity error during Data-In phase. > >> May 23 03:01:51 control /kernel: SEQADDR == 0x110 > >> May 23 03:01:52 control /kernel: SCSIRATE == 0xf > >> May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): SCB 0x31 - timed out in datain phase, SEQADDR == 0x153 > >> May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): BDR message in message buffer > >> May 23 03:02:34 control /kernel: (cd0:ahc0:0:4:0): SCB 0x31 - timed out in datain phase, SEQADDR == 0x153 > >> May 23 03:02:35 control /kernel: (cd0:ahc0:0:4:0): no longer in timeout, status = 34b > >> May 23 03:02:35 control /kernel: ahc0: Issued Channel A Bus Reset. 120 SCBs aborted > >> May 23 03:02:35 control /kernel: (cd0:ahc0:0:4:0): parity error during Data-In phase. > >> May 23 03:02:35 control /kernel: SEQADDR == 0x110 > >> May 23 03:02:35 control /kernel: SCSIRATE == 0xf > >> [...] > >> > >> Please note that ALL OF MY OTHER SCSI PERIPHERALS ARE WORKING FINE. > > > > Hm, this implies that the CDR is busted. My guess is that it's the > > cable. > > If it were the cable, the other devices wouldn't work either. And it > wouldn't explain why this happened suddenly. It could be the connector on the CD-R, and not the cable. Unfortunately narrow SCSI devices have the pins on the device instead of the cable. It's much better, IMO, to have fragile things like pins on the cable, which is much cheaper to replace. > >> Anyway, as I said, my other SCSI devices (hard drives, scanner, etc.) are > >> working fine. The ATAPI DVD-ROM drive is also working fine. It's only > >> the SCSI CD-recorder that does not work. It fails when accessing mounted > >> CD's (doing a 'du' of the CD will bring the error on really quickly), and > >> also I cannot use tosha to grab audio tracks off of it (same error). I > >> don't dare trying to write a CD on it... > > > > It may not support those operations. How old is the CDR? > > If it doesn't support the operation, it would say so. A parity error > suggests that there's something wrong with the connection or the > device. We've ruled out the connection. It doesn't rule out the connection, since the cable can be good and the drive connector can be bad. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 25 14:10:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from des.follo.net (des.follo.net [195.204.143.216]) by hub.freebsd.org (Postfix) with ESMTP id 674BE158AB for ; Tue, 25 May 1999 14:10:18 -0700 (PDT) (envelope-from des@des.follo.net) Received: (from des@localhost) by des.follo.net (8.9.3/8.9.3) id XAA68841; Tue, 25 May 1999 23:10:05 +0200 (CEST) (envelope-from des) To: scsi@freebsd.org Subject: weird swapinfo(8) report Organization: Yes! Interactive Visit-Us-At: http://www.yes.no/ From: Dag-Erling Smorgrav Date: 25 May 1999 23:10:04 +0200 Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As shown below, one of my servers reports one of its swap partitions as od0b: root(yeshs-4)--# uname -a FreeBSD yeshs-4.yes.no 3.1-19990505-STABLE FreeBSD 3.1-19990505-STABLE #1: Wed May 19 05:11:30 CEST 1999 root@yeshs-4.yes.no:/usr/src/sys/compile/YESHS i386 root(yeshs-4)--# swapinfo Device 1K-blocks Used Avail Capacity Type /dev/od0b 524288 0 524160 0% Interleaved /dev/da1b 524288 0 524160 0% Interleaved /dev/da2b 524288 0 524160 0% Interleaved Total 1572480 0 1572480 0% DES -- Dag-Erling Smorgrav - des@yes.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 25 14:46:36 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 6E2B4158E6 for ; Tue, 25 May 1999 14:46:31 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id PAA05406; Tue, 25 May 1999 15:46:25 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905252146.PAA05406@panzer.plutotech.com> Subject: Re: weird swapinfo(8) report In-Reply-To: from Dag-Erling Smorgrav at "May 25, 1999 11:10:04 pm" To: des@yes.no (Dag-Erling Smorgrav) Date: Tue, 25 May 1999 15:46:25 -0600 (MDT) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Dag-Erling Smorgrav wrote... > As shown below, one of my servers reports one of its swap partitions > as od0b: > > root(yeshs-4)--# uname -a > FreeBSD yeshs-4.yes.no 3.1-19990505-STABLE FreeBSD 3.1-19990505-STABLE #1: Wed May 19 05:11:30 CEST 1999 root@yeshs-4.yes.no:/usr/src/sys/compile/YESHS i386 > root(yeshs-4)--# swapinfo > Device 1K-blocks Used Avail Capacity Type > /dev/od0b 524288 0 524160 0% Interleaved > /dev/da1b 524288 0 524160 0% Interleaved > /dev/da2b 524288 0 524160 0% Interleaved > Total 1572480 0 1572480 0% That probably isn't a SCSI or CAM problem, it's a problem somewhere else in the system I'd imagine. CAM has little idea about partitions, other than calling the slice code to read the disklabel. It certainly doesn't know anything about swap.. Here's what I get on a -current box: {thunderdome:/usr/home/ken:1:0} uname -a FreeBSD thunderdome.plutotech.com 4.0-CURRENT FreeBSD 4.0-CURRENT #0: Sat May 22 19:13:26 MDT 1999 ken@panzer.plutotech.com:/usr/home/ken/perforce/cam/sys/compile/thunderdome i386 {thunderdome:/usr/home/ken:2:0} pstat -s Device 1K-blocks Used Avail Capacity Type /dev/(null) 204672 0 204672 0% Interleaved Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 25 15:55:52 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 47E2A1598C; Tue, 25 May 1999 15:55:47 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA06455; Wed, 26 May 1999 00:13:19 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA05463; Tue, 25 May 1999 23:49:16 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905252149.XAA05463@yedi.iaf.nl> Subject: Re: Help! - "parity error during data-in phase" when using CD-Rdrv In-Reply-To: <374AF6E8.9CD7300C@3-cities.com> from Kent Stewart at "May 25, 1999 12:15:52 pm" To: kstewart@3-cities.com (Kent Stewart) Date: Tue, 25 May 1999 23:49:16 +0200 (CEST) Cc: dwhite@resnet.uoregon.edu, dburr@pobox.com, freebsd-questions@FreeBSD.ORG, 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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Kent Stewart wrote ... > > I have also hooked a scsi cable incorrectly. Nothing on the scsi > controller worked when I did that. You can't hook a scsi cable up to a > CDROM off one pin like you can some devices. Nothing worked when you > do that either. It seems like you end up with a ground on a data line > or power. Correct observation. Single ended SCSI has a 1:1 interleave of the signal lines with ground lines (ok, there are a few exceptions, but this is the ground rule). This is yet another indication why 25pin subD-connectors are a horrible idea on a SCSI bus. | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 25 16:10:50 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 88CBF15311; Tue, 25 May 1999 16:10:45 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA06444; Wed, 26 May 1999 00:13:10 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA05396; Tue, 25 May 1999 23:41:37 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905252141.XAA05396@yedi.iaf.nl> Subject: Re: Help! - "parity error during data-in phase" when using CD-R drv In-Reply-To: <19990526053742.R95827@freebie.lemis.com> from Greg Lehey at "May 26, 1999 5:37:43 am" To: grog@lemis.com (Greg Lehey) Date: Tue, 25 May 1999 23:41:37 +0200 (CEST) Cc: dwhite@resnet.uoregon.edu, dburr@pobox.com, freebsd-questions@FreeBSD.ORG, 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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Greg Lehey wrote ... > On Tuesday, 25 May 1999 at 11:03:15 -0700, Doug White wrote: > > On Sun, 23 May 1999, Donald Burr wrote: > > > >> Please note that ALL OF MY OTHER SCSI PERIPHERALS ARE WORKING FINE. > > > > Hm, this implies that the CDR is busted. My guess is that it's the > > cable. > > If it were the cable, the other devices wouldn't work either. And it > wouldn't explain why this happened suddenly. No true. I have cables to prove it wrong. > > Did you check it again? > > Again, if it was a simple termination problem, the others wouldn't > work either. This is not termination AFAI can see. > >> It seems to me, then, that I somehow managed to damage the drive while > >> moving it between cases. But I thought I had better post this anyway, in > >> case someone else out there has any ideas as to what I'm doing wrong, or > >> how I might go about fixing this. > > > > Cable on upside down? > > That would stop everything from working. Yes. > couple of drives like that, and you (Donald) have a lot of stuff on > the chain. Could you try removing as much as possible (at least the > DDS drive and the scanner, and any disks you can get by without for a > test), and see if you can get it to work then. Good idea. Loose all external devices (scanner). External and internal devices on the same bus are a Bad Idea(tm) anyway. Wilko | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 25 16:12:14 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 434AE14C12; Tue, 25 May 1999 16:10:45 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA06454; Wed, 26 May 1999 00:13:18 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA05348; Tue, 25 May 1999 23:38:54 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905252138.XAA05348@yedi.iaf.nl> Subject: Re: Help! - "parity error during data-in phase" when using CD-R drv In-Reply-To: <199905252022.OAA04678@panzer.plutotech.com> from "Kenneth D. Merry" at "May 25, 1999 2:22:16 pm" To: ken@plutotech.com (Kenneth D. Merry) Date: Tue, 25 May 1999 23:38:54 +0200 (CEST) Cc: grog@lemis.com, dwhite@resnet.uoregon.edu, dburr@pobox.com, freebsd-questions@FreeBSD.ORG, 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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Kenneth D. Merry wrote ... ... > > If it were the cable, the other devices wouldn't work either. And it > > wouldn't explain why this happened suddenly. > > It could be the connector on the CD-R, and not the cable. Unfortunately > narrow SCSI devices have the pins on the device instead of the cable. It's > much better, IMO, to have fragile things like pins on the cable, which is > much cheaper to replace. Narrow connectors have much more robust pins. But there is something worth checking: -does the connector on the drive have a SCSI connector that is surface mount soldered to the PCB? I hope you know what I mean. I once suffered the most mysterious problems using a DAT streamer. It proved that one of the pins had been 'lifted' out of the solder on the PCB. Sometimes it worked fine, sometimes not. You can try by 'wiggling' the cable to see if it works if you push it one way or the other. > > >> the SCSI CD-recorder that does not work. It fails when accessing mounted > > >> CD's (doing a 'du' of the CD will bring the error on really quickly), and > > >> also I cannot use tosha to grab audio tracks off of it (same error). I > > >> don't dare trying to write a CD on it... > > > > > > It may not support those operations. How old is the CDR? > > > > If it doesn't support the operation, it would say so. A parity error > > suggests that there's something wrong with the connection or the > > device. We've ruled out the connection. > > It doesn't rule out the connection, since the cable can be good and the > drive connector can be bad. I second Ken. This smells like a bad connection of some sorts. A connector punched to the flatcable that is slightly misaligned with respect to the cable wires is also something that makes you bang your head to the wall. I had that happen to me twice. The replacement cable had the same problem Argh :-(. All other devices on the same cable worked fine. Advice: take a *very* close look to your cable and CDR drive's connector. Wilko | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 25 20:40:58 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ren.detir.qld.gov.au (ns.detir.qld.gov.au [203.46.81.66]) by hub.freebsd.org (Postfix) with ESMTP id AB53214D65 for ; Tue, 25 May 1999 20:40:52 -0700 (PDT) (envelope-from syssgm@detir.qld.gov.au) Received: by ren.detir.qld.gov.au; id NAA08791; Wed, 26 May 1999 13:37:02 +1000 (EST) Received: from ogre.detir.qld.gov.au(167.123.8.3) by ren.detir.qld.gov.au via smap (4.1) id xma008740; Wed, 26 May 99 13:36:48 +1000 Received: from atlas.detir.qld.gov.au (atlas.detir.qld.gov.au [167.123.8.9]) by ogre.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id NAA05305 for ; Wed, 26 May 1999 13:36:48 +1000 (EST) Received: from nymph.detir.qld.gov.au (nymph.detir.qld.gov.au [167.123.10.10]) by atlas.detir.qld.gov.au (8.8.5/8.8.5) with ESMTP id NAA07058 for ; Wed, 26 May 1999 13:36:48 +1000 (EST) Received: from nymph.detir.qld.gov.au (localhost.detir.qld.gov.au [127.0.0.1]) by nymph.detir.qld.gov.au (8.8.8/8.8.7) with ESMTP id NAA19611; Wed, 26 May 1999 13:36:46 +1000 (EST) (envelope-from syssgm@nymph.detir.qld.gov.au) Message-Id: <199905260336.NAA19611@nymph.detir.qld.gov.au> To: freebsd-scsi@freebsd.org Cc: syssgm@detir.qld.gov.au Subject: Re: aha1542 brokenness, and CAM technique query References: <199905241351.HAA21077@narnia.plutotech.com> In-Reply-To: <199905241351.HAA21077@narnia.plutotech.com> from "Justin T. Gibbs" at "Mon, 24 May 1999 07:51:21 -0600" Date: Wed, 26 May 1999 13:36:46 +1000 From: Stephen McKay Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Monday, 24th May 1999, "Justin T. Gibbs" wrote: >In article <199905240727.BAA17292@harmony.village.org> you wrote: >> In message <199905240453.OAA11833@nymph.detir.qld.gov.au> Stephen McKay writes: >> : A mailbox command (ie real SCSI command) is in flight when aha_cmd() >> : is called. After the command byte, but before all of the parameter >> : bytes are written, it completes, calling aha_intr(), which calls >> : ahadone(), which calls xpt_done() which (as far as I can tell) allows >> : something else to run which queues another command which issues another >> : mailbox command. Crunch! At least, that's what I think is happening. >> >> Ouch! I think that Justin's bt_cmd will also have this same problem, >> since it doesn't block CAM interrupts while the bt_cmd is processing. >> It does check to see if there is an interrupt pending, however. > >You should be at splsoftcam() when this code is executed which will >prevent the queuing of any additional commands to the card. If we >aren't at splsoftcam() here, then there is a bug in the cam xpt. You >do not need to block hardware interrupts in order to prevent additional >commands from comming down the pipe due to the deferred processing >technique used by CAM (similar to the networkig stack). Well, everyone should be happy to know that the interleaved commands scenario that I described above is not happening. A much simpler case of colliding commands (without any chance of FS corruption) was causing the problem. Justin made a patch, it works fine on my box with dual 1542s and lots of disks, and it's already in the tree. Another happy ending! Stephen. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 25 23:11:51 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from control.colossus.dynip.com (pm5-15.sba1.avtel.net [207.71.222.15]) by hub.freebsd.org (Postfix) with ESMTP id ACF32151EB; Tue, 25 May 1999 23:11:42 -0700 (PDT) (envelope-from dburr@control.colossus.dynip.com) Received: (from dburr@localhost) by control.colossus.dynip.com (8.9.2/8.9.2) id XAA14280; Tue, 25 May 1999 23:11:41 -0700 (PDT) (envelope-from dburr) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199905252138.XAA05348@yedi.iaf.nl> Date: Tue, 25 May 1999 23:11:41 -0700 (PDT) Organization: Computer Help From: Donald Burr To: FreeBSD SCSI Subject: Re: Help! - "parity error during data-in phase" when using CD-R Cc: freebsd-questions@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks to all who responded to my SCSI CD-R problem. I have used this CD-R before under FreeBSD, and it works fine. Fully supported by cdrecord and all that -- I have a stack of self-made freeBSD release CD-ROMs to prove it. Someone suggested a bent pin on the connector. someone else suggested that the onnector itself might have been damaged somehow (broken solder connection). The pins are all fine, however I think the latter (bad sold er connections) is highly likely. Someone suggested that the SCSI connector on the cable is bad. Well, to test that I plugged that connector into one of my SCSI hard drives. No trouble at all. So the connector is crimped on to the ribbon cable properly and all. Someone suggested trying to remove all of my devices. Actually, t this is one of the first things I tried (I may have forgotten to mention it in my message) and that didn't help either. Someone else suggested a dirty lens. Again, one of the first things I tried -- I ran ye olde lens cleaning disc with no effect. Anyway, thank you all for your suggestions. I haven't given up yet, and I haven't thrown away the drive yet. I think it's a good bet that, by being too forceful when removing the cable, I may ahve broken one of the solder connections loose on the SCSI connector. It is out of warranty, but luckily I have an electronics technician friend who is real handy with a solder iron. --- Donald Burr | PGP: Your *NEW* WWW HomePage: http://more.at/dburr/ ICQ #16997506 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 26 3: 4: 5 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from shaft.noc.clara.net (shaft.noc.clara.net [195.8.70.216]) by hub.freebsd.org (Postfix) with ESMTP id 21033151F1 for ; Wed, 26 May 1999 03:04:02 -0700 (PDT) (envelope-from mivens@clara.net) Received: (from mark@localhost) by shaft.noc.clara.net (8.9.3/8.9.3) id LAA35364 for freebsd-scsi@freebsd.org; Wed, 26 May 1999 11:04:01 +0100 (BST) Date: Wed, 26 May 1999 11:04:01 +0100 From: Mark Ivens To: freebsd-scsi@freebsd.org Subject: Probing of multiple ahc devices in 3.2 Message-ID: <19990526110401.A35207@shaft.noc.clara.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I would be most grateful for your advice. One of our servers here has two Adaptec SCSI cards, a 2940 and a 2944 for the CCD array. After I cvsuped to 3.2-STABLE yesterday from a 3.1-19990422-STABLE snapshot, only the first card on the PCI bus (the 2940) was detected on boot up. I also observed this behaviour with 3.2-RELEASE boot floppies but not those from the last 3.1 snapshot on releng3.freebsd.org (3.1-19990505-STABLE) so I don't think it's some perculiarity of my kernel config. I have now performed a make world from the the last 3.1 snapshot source and the card is being detected again. I haven't managed to find anything in the release notes or errata for FreeBSD-3.2 about this and looking at LINT, the syntax hasn't changed as far as I can see; still a matter of specifying controller ahc0 for any number of installed devices. A problem with the new code commited in 3.2 or am I suffering from an acute case of pilot error? The device probes from /var/log/messages are below in case they are of help. TIA. -- Mark Ivens Junior Systems Administrator ClaraNET Ltd. First 3.1-19990505: ------------------- May 25 22:50:35 pandora /kernel: FreeBSD 3.1-19990505-STABLE #0: Tue May 25 22:47:53 BST 1999 [snip] May 25 22:50:35 pandora /kernel: Probing for devices on PCI bus 0: May 25 22:50:35 pandora /kernel: chip0: rev 0x03 on pci0.0.0 May 25 22:50:35 pandora /kernel: chip1: rev 0x03 on pci0.1.0 May 25 22:50:35 pandora /kernel: chip2: rev 0x01 on pci0.7.0 May 25 22:50:35 pandora /kernel: ide_pci0: rev 0x01 on May 25 22:50:35 pandora /kernel: pci0.7.1 May 25 22:50:35 pandora /kernel: chip3: rev 0x01 on pci0.7.3 May 25 22:50:35 pandora /kernel: tx0: rev 0x06 int a irq 10 on pci0.10.0 May 25 22:50:35 pandora /kernel: tx0: address 00:e0:29:22:71:4a, type SMC9432TX, Auto-Neg 100Mbps FD May 25 22:50:35 pandora /kernel: ahc0: rev 0x01 int a irq 12 on pci0.11.0 May 25 22:50:35 pandora /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs May 25 22:50:35 pandora /kernel: ahc1: rev 0x01 int a irq 11 on pci0.12.0 May 25 22:50:35 pandora /kernel: ahc1: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs May 25 22:50:35 pandora /kernel: Probing for devices on PCI bus 1: Now 3.2 stable, cvsuped May 25th: --------------------------------- May 25 16:10:03 pandora /kernel: FreeBSD 3.2-STABLE #0: Tue May 25 15:59:59 BST 1999 [snip] May 25 16:10:03 pandora /kernel: Probing for devices on PCI bus 0: May 25 16:10:03 pandora /kernel: chip0: rev 0x03 on pci0.0.0 May 25 16:10:03 pandora /kernel: chip1: rev 0x03 on pci0.1.0 May 25 16:10:03 pandora /kernel: chip2: rev 0x01 on pci0.7.0 May 25 16:10:03 pandora /kernel: ide_pci0: rev 0x01 on pci0.7.1 May 25 16:10:04 pandora /kernel: chip3: rev 0x01 on pci0.7.3 May 25 16:10:04 pandora /kernel: tx0: rev 0x06 int a irq 10 on pci0.10.0 May 25 16:10:04 pandora /kernel: tx0: address 00:e0:29:22:71:4a, type SMC9432TX, Auto-Neg 100Mbps FD May 25 16:10:04 pandora /kernel: ahc0: rev 0x01 int a irq 12 on pci0.11.0 May 25 16:10:04 pandora /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs May 25 16:10:04 pandora /kernel: Probing for devices on PCI bus 1: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 26 13:21:50 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from proteus.idirect.com (proteus.idirect.com [207.136.80.19]) by hub.freebsd.org (Postfix) with ESMTP id 9C37A15229; Wed, 26 May 1999 13:21:40 -0700 (PDT) (envelope-from fehr@idirect.com) Received: from localhost (fehr@localhost) by proteus.idirect.com (8.9.3/8.9.3) with ESMTP id QAA62986; Wed, 26 May 1999 16:21:40 -0400 (EDT) Date: Wed, 26 May 1999 16:21:40 -0400 (EDT) From: "Eric D. Fehr" To: freebsd-questions@freebsd.org Cc: freebsd-scsi@freebsd.org Subject: Errors w/Quantum drives (LVD), Ultra2SCSI, 3.1 & 3.2 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 Has anyone else experienced ongoing hardware read errors with this configuration? We're getting it with four different drives (same model), 3 different SCSI cables (running at 80MB/second), 3 different motherboards (Gigabyte and ASUS, Adaptec 7890 controller), 3 different terminators (active), and it is really starting to annoy me: (da1:ahc0:0:1:0): READ(10). CDB: 28 0 1 b8 11 f 0 0 80 0 (da1:ahc0:0:1:0): MEDIUM ERROR info:1b8117c csi:18,21,58,1d asc:11,0 (da1:ahc0:0:1:0): Unrecovered read error sks:80,98 The only common denominators would appear to be the 7890 controller chip and the Quantum QM318000TD-SW drives. The drives have 2 different firmware versions, and both appear to be equally effected. This is happening under high load only. Eric To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 26 13:24:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 1895D156CE; Wed, 26 May 1999 13:24:10 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id NAA23254; Wed, 26 May 1999 13:23:48 -0700 Date: Wed, 26 May 1999 13:22:55 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Eric D. Fehr" Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Errors w/Quantum drives (LVD), Ultra2SCSI, 3.1 & 3.2 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 This error is solely a property of the drive I would think. > Has anyone else experienced ongoing hardware read errors with this > configuration? > > We're getting it with four different drives (same model), 3 different SCSI > cables (running at 80MB/second), 3 different motherboards (Gigabyte and > ASUS, Adaptec 7890 controller), 3 different terminators (active), and it > is really starting to annoy me: > > (da1:ahc0:0:1:0): READ(10). CDB: 28 0 1 b8 11 f 0 0 80 0 > (da1:ahc0:0:1:0): MEDIUM ERROR info:1b8117c csi:18,21,58,1d asc:11,0 > (da1:ahc0:0:1:0): Unrecovered read error sks:80,98 > > The only common denominators would appear to be the 7890 controller chip > and the Quantum QM318000TD-SW drives. The drives have 2 different > firmware versions, and both appear to be equally effected. This is > happening under high load only. > > Eric > > > > > 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 Wed May 26 14:41: 4 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 6CE2A14F5F; Wed, 26 May 1999 14:40:54 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA03649; Wed, 26 May 1999 22:51:12 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id UAA31596; Wed, 26 May 1999 20:57:49 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905261857.UAA31596@yedi.iaf.nl> Subject: Re: Help! - "parity error during data-in phase" when using CD-R In-Reply-To: from Donald Burr at "May 25, 1999 11:11:41 pm" To: dburr@pobox.com (Donald Burr) Date: Wed, 26 May 1999 20:57:48 +0200 (CEST) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-questions@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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Donald Burr wrote ... > Thanks to all who responded to my SCSI CD-R problem. > > I have used this CD-R before under FreeBSD, and it works fine. Fully > supported by cdrecord and all that -- I have a stack of self-made freeBSD > release CD-ROMs to prove it. > > Someone suggested a bent pin on the connector. someone else suggested > that the onnector itself might have been damaged somehow (broken solder > connection). The pins are all fine, however I think the latter (bad sold > er connections) is highly likely. OK. Please note that this can be highly difficult to detect. I tend to just heat all the solder joints on the connector. Also look for cracks in the PCB tracks themselves. This procedure fixed my DAT drive. Good luck, Wilko | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 26 15:52:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 0BE5414CC5 for ; Wed, 26 May 1999 15:52:31 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id QAA03657; Wed, 26 May 1999 16:42:20 -0600 (MDT) Date: Wed, 26 May 1999 16:42:20 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199905262242.QAA03657@narnia.plutotech.com> To: "Eric D. Fehr" Cc: scsi@FreeBSD.org Subject: Re: Errors w/Quantum drives (LVD), Ultra2SCSI, 3.1 & 3.2 X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > Has anyone else experienced ongoing hardware read errors with this > configuration? > > We're getting it with four different drives (same model), 3 different SCSI > cables (running at 80MB/second), 3 different motherboards (Gigabyte and > ASUS, Adaptec 7890 controller), 3 different terminators (active), and it > is really starting to annoy me: > > (da1:ahc0:0:1:0): READ(10). CDB: 28 0 1 b8 11 f 0 0 80 0 > (da1:ahc0:0:1:0): MEDIUM ERROR info:1b8117c csi:18,21,58,1d asc:11,0 > (da1:ahc0:0:1:0): Unrecovered read error sks:80,98 CAM is only reporting what the drive has told us. This is not a cable or termination or problem, but I suppose it could be a drive firmware bug. There's very little anyone but the device can do about reading the physical media and that is what the complaint is about. Call Quantum tech support and give them the asc/ascq pair for the error (11, 0) that the drive is reporting. New devices should not be constanly reporting read errors unless you have a heat or other environment problem. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 26 16: 3: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from proteus.idirect.com (proteus.idirect.com [207.136.80.19]) by hub.freebsd.org (Postfix) with ESMTP id 09A0314DE8 for ; Wed, 26 May 1999 16:02:47 -0700 (PDT) (envelope-from fehr@idirect.com) Received: from localhost (fehr@localhost) by proteus.idirect.com (8.9.3/8.9.3) with ESMTP id TAA63340; Wed, 26 May 1999 19:02:41 -0400 (EDT) Date: Wed, 26 May 1999 19:02:41 -0400 (EDT) From: "Eric D. Fehr" To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: Errors w/Quantum drives (LVD), Ultra2SCSI, 3.1 & 3.2 In-Reply-To: <199905262242.QAA03657@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 After switching the drives from the Ultra2 channel to an Ultra channel (to force them to run at 40/20), they are giving errors related to dscheck. What exactly is a negative b_blkno? I've found the section of code in the kernel that this is generated by, but it isn't extremely obvious to me what exactly causes it. dsckeck: negative b_blkno -1873515648 I'll give Quantum a call and see what they have to say, as this has happened on at least 4 drives of the same model number, with two different firware versions. Thanks, Eric On Wed, 26 May 1999, Justin T. Gibbs wrote: > In article you wrote: > > Has anyone else experienced ongoing hardware read errors with this > > configuration? > > > > We're getting it with four different drives (same model), 3 different SCSI > > cables (running at 80MB/second), 3 different motherboards (Gigabyte and > > ASUS, Adaptec 7890 controller), 3 different terminators (active), and it > > is really starting to annoy me: > > > > (da1:ahc0:0:1:0): READ(10). CDB: 28 0 1 b8 11 f 0 0 80 0 > > (da1:ahc0:0:1:0): MEDIUM ERROR info:1b8117c csi:18,21,58,1d asc:11,0 > > (da1:ahc0:0:1:0): Unrecovered read error sks:80,98 > > CAM is only reporting what the drive has told us. This is not > a cable or termination or problem, but I suppose it could be a > drive firmware bug. There's very little anyone but the device > can do about reading the physical media and that is what the > complaint is about. > > Call Quantum tech support and give them the asc/ascq pair for the > error (11, 0) that the drive is reporting. New devices should not > be constanly reporting read errors unless you have a heat or other > environment problem. > > -- > Justin > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 26 16:24:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 1DABB14F0A for ; Wed, 26 May 1999 16:24:41 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id RAA33516; Wed, 26 May 1999 17:24:38 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <199905262324.RAA33516@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Eric D. Fehr" Cc: "Justin T. Gibbs" , scsi@FreeBSD.org Subject: Re: Errors w/Quantum drives (LVD), Ultra2SCSI, 3.1 & 3.2 In-reply-to: Your message of "Wed, 26 May 1999 19:02:41 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 May 1999 17:14:29 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >After switching the drives from the Ultra2 channel to an Ultra channel (to >force them to run at 40/20), they are giving errors related to dscheck. The kernel isn't getting valid disklabel information off the drive. The media is probably corrupted or dscheck is not handling disk errors correctly and we are returning EIO because of the hardware errors you reported earlier. This is a symptom of your drive problem, but not the problem. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 26 16:33:13 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 17B7A1515F for ; Wed, 26 May 1999 16:33:11 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id QAA04608; Wed, 26 May 1999 16:32:57 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id QAA25570; Wed, 26 May 1999 16:32:56 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id QAA09141; Wed, 26 May 1999 16:32:55 -0700 (PDT) From: Don Lewis Message-Id: <199905262332.QAA09141@salsa.gv.tsc.tdk.com> Date: Wed, 26 May 1999 16:32:55 -0700 In-Reply-To: "Justin T. Gibbs" "Re: Errors w/Quantum drives (LVD), Ultra2SCSI, 3.1 & 3.2" (May 26, 4:42pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: "Justin T. Gibbs" , "Eric D. Fehr" Subject: Re: Errors w/Quantum drives (LVD), Ultra2SCSI, 3.1 & 3.2 Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On May 26, 4:42pm, "Justin T. Gibbs" wrote: } Subject: Re: Errors w/Quantum drives (LVD), Ultra2SCSI, 3.1 & 3.2 } In article you wrote: } > Has anyone else experienced ongoing hardware read errors with this } > configuration? } > } > We're getting it with four different drives (same model), 3 different SCSI } > cables (running at 80MB/second), 3 different motherboards (Gigabyte and } > ASUS, Adaptec 7890 controller), 3 different terminators (active), and it } > is really starting to annoy me: } > } > (da1:ahc0:0:1:0): READ(10). CDB: 28 0 1 b8 11 f 0 0 80 0 } > (da1:ahc0:0:1:0): MEDIUM ERROR info:1b8117c csi:18,21,58,1d asc:11,0 } > (da1:ahc0:0:1:0): Unrecovered read error sks:80,98 } } CAM is only reporting what the drive has told us. This is not } a cable or termination or problem, but I suppose it could be a } drive firmware bug. There's very little anyone but the device } can do about reading the physical media and that is what the } complaint is about. } } Call Quantum tech support and give them the asc/ascq pair for the } error (11, 0) that the drive is reporting. New devices should not } be constanly reporting read errors unless you have a heat or other } environment problem. ... such as power quality or vibration. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 26 16:51:34 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D6DE15229; Wed, 26 May 1999 16:51:27 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id RAA15669; Wed, 26 May 1999 17:51:21 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905262351.RAA15669@panzer.plutotech.com> Subject: Re: Errors w/Quantum drives (LVD), Ultra2SCSI, 3.1 & 3.2 In-Reply-To: from "Eric D. Fehr" at "May 26, 1999 04:21:40 pm" To: fehr@idirect.com (Eric D. Fehr) Date: Wed, 26 May 1999 17:51:21 -0600 (MDT) Cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 Eric D. Fehr wrote... > Has anyone else experienced ongoing hardware read errors with this > configuration? > > We're getting it with four different drives (same model), 3 different SCSI > cables (running at 80MB/second), 3 different motherboards (Gigabyte and > ASUS, Adaptec 7890 controller), 3 different terminators (active), and it > is really starting to annoy me: > > (da1:ahc0:0:1:0): READ(10). CDB: 28 0 1 b8 11 f 0 0 80 0 > (da1:ahc0:0:1:0): MEDIUM ERROR info:1b8117c csi:18,21,58,1d asc:11,0 > (da1:ahc0:0:1:0): Unrecovered read error sks:80,98 > > The only common denominators would appear to be the 7890 controller chip > and the Quantum QM318000TD-SW drives. The drives have 2 different > firmware versions, and both appear to be equally effected. This is > happening under high load only. In addition to heat or power problems (as others have mentioned), this could just be bad blocks on the drives. I do think it's pretty suspicous that four different drives popped up with bad blocks at the same time, though. You'll want to make sure you've got read and write reallocation turned on. To check that, look at mode page 1: camcontrol modepage -v -n da -u 1 -m 1 To edit the AWRE and ARRE bits (set them to 1), you'd do: camcontrol modepage -v -n da -u 1 -m 1 -e -P 3 That'll tell the drive to remap any bad blocks it runs into. You may need to write to the blocks to get the drive to remap them. If you want to write to the block, you can use camcontrol to do it or you can just dd over the entire disk. You can look at the grown defects list using this command: camcontrol defects -n da -u 1 -v -G -f phys Most every drive I've seen supports the physical sector format, but Quantum drives often support the block defect format as well: camcontrol defects -n da -u 1 -v -G -f phys 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 May 26 18:17:10 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 4E6C115462 for ; Wed, 26 May 1999 18:17:06 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-14-138.dialup.HiWAAY.net [216.180.14.138]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id UAA08868 for ; Wed, 26 May 1999 20:17:02 -0500 (CDT) Received: from nospam.hiwaay.net (nospam.hiwaay.net [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id UAA48835 for ; Wed, 26 May 1999 20:17:01 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199905270117.UAA48835@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@freebsd.org Subject: proper mode page values? From: David Kelly Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 May 1999 20:17:01 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My formerly wonderful IBM DCAS 34330 narrow drive is acting up on my little FreeBSD system (a 486/133). Several months ago I had to use the Adaptec 2940 built in utility to scan the drive for bad blocks. It found several. Followed up with a clean installation of FreeBSD 3.1. Now I'm getting "indefinite wait" messages from swap_pager, much like Dag-Erling Smorgrav reported on 19 Feb 1999, something like this: swap_pager: indefinite wait buffer: device: 0x30401, blkno: 264, size: 4096 The problem blocks are always 264, 272, and 496. And to make things maximally fun, it only happens when reading variable block sized QIC-1000 tapes with an Archive Anaconda. Fixed block size on a QIC-150 runs nicely. The variable QIC-1000 starts and stops and starts and stops with every block. sa1 at ahc0 bus 0 target 6 lun 0 sa1: Removable Sequential Access SCSI-2 device sa1: 5.000MB/s transfers (5.000MHz, offset 15) Tried using camcontrol to view my bad block lists. Doesn't work on that IBM drive, nor the IBM drive on this machine: nospam: [1031] camcontrol defects -n da -u 0 -G camcontrol: no defect list format specified nospam: [1032] camcontrol defects -n da -u 0 -f block -G error reading defect list: Input/output error nospam: [1033] camcontrol defects -n da -u 0 -f bfi -G error reading defect list: Input/output error nospam: [1034] camcontrol defects -n da -u 0 -f phys -G error reading defect list: Input/output error nospam: [1035] camcontrol defects -n da -u 0 -f phys -P error reading defect list: Input/output error nospam: [1036] camcontrol defects -n da -u 0 -f bfi -P error reading defect list: Input/output error nospam: [1037] camcontrol defects -n da -u 0 -f block -P error reading defect list: Input/output error So then I go looking at mode pages to see what is set and to see if by any chance the drive was told not to substitute replacements for weakening blocks: nospam: [1038] camcontrol modepage -n da -u 0 -m 1 -P 2 AWRE (Auto Write Reallocation Enbld): 0 ARRE (Auto Read Reallocation Enbld): 0 TB (Transfer Block): 0 RC (Read Continuous): 0 EER (Enable Early Recovery): 0 PER (Post Error): 0 DTE (Disable Transfer on Error): 0 DCR (Disable Correction): 0 Read Retry Count: 1 Correction Span: 144 Head Offset Count: 0 Data Strobe Offset Count: 0 Write Retry Count: 1 Recovery Time Limit: 0 nospam: [1039] camcontrol modepage -n da -u 0 -m 1 -P 3 AWRE (Auto Write Reallocation Enbld): 1 ARRE (Auto Read Reallocation Enbld): 1 TB (Transfer Block): 0 RC (Read Continuous): 0 EER (Enable Early Recovery): 0 PER (Post Error): 0 DTE (Disable Transfer on Error): 0 DCR (Disable Correction): 0 Read Retry Count: 1 Correction Span: 144 Head Offset Count: 0 Data Strobe Offset Count: 0 Write Retry Count: 1 Recovery Time Limit: 0 The DCAS defaults are itentical to the stored values shown above on my: da0 at ncr0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) The DCAS is on a version 1.16 Adaptec 2940, but on a different computer: ahc0: rev 0x00 int a irq 15 on pci0.9.0 ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs So much for the background info. To the meat of the matter: How can I get bad block lists from IBM SCSI drives? Am I doing it wrong or does it simply not work yet? How to scan a SCSI drive and reallocate bad blocks? Are my modepage parameters sane? Was looking at page 0x01 because I was worried about error handling. But here's the popular 0x08 too: nospam: [1043] camcontrol modepage -n da -u 0 -m 8 -P 3 IC: 0 ABPF: 0 CAP: 0 DISC: 0 SIZE: 0 WCE: 0 MF: 0 RCD: 0 Demand Retention Priority: 1 Write Retention Priority: 1 Disable Pre-fetch Transfer Length: 65535 Minimum Pre-fetch: 0 Maximum Pre-fetch: 65535 Maximum Pre-fetch Ceiling: 65535 nospam: [1044] -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 26 18:44:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from midten.fast.no (midten.fast.no [195.139.251.11]) by hub.freebsd.org (Postfix) with ESMTP id 1E8DB15764 for ; Wed, 26 May 1999 18:44:31 -0700 (PDT) (envelope-from tegge@fast.no) Received: from fast.no (IDENT:tegge@midten.fast.no [195.139.251.11]) by midten.fast.no (8.9.3/8.9.3) with ESMTP id DAA83992; Thu, 27 May 1999 03:44:23 +0200 (CEST) Message-Id: <199905270144.DAA83992@midten.fast.no> To: fehr@idirect.com Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Errors w/Quantum drives (LVD), Ultra2SCSI, 3.1 & 3.2 From: Tor.Egge@fast.no In-Reply-To: Your message of "Wed, 26 May 1999 16:21:40 -0400 (EDT)" References: X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 27 May 1999 03:44:22 +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Has anyone else experienced ongoing hardware read errors with this > configuration? I've experienced the disk dropping the scsi bus and not responding to selection. 3.1-STABLE invalidated the disk pack, and the machine then hung (cf. PR#11697). I still get some errors when using 3.2-STABLE: ------------ ahc0: rev 0x00 int a irq 16 on pci2.4.0 ahc0: Reading SEEPROM...done. ahc0: BIOS eeprom not present ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 393 instructions downloaded [.... snip ....] da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Serial Number PCB=20-116002-05; HDA=321904650954 da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 17366MB (35566499 512 byte sectors: 255H 63S/T 2213C) [.... snip ....] Unexpected busfree. LASTPHASE == 0x80 SEQADDR == 0x15c ahc0: Selection Timeout on A:1. 5 SCBs aborted ahc0: Selection Timeout on A:1. 15 SCBs aborted Unexpected busfree. LASTPHASE == 0x80 SEQADDR == 0x15c ahc0: Selection Timeout on A:1. 23 SCBs aborted ahc0: Selection Timeout on A:1. 23 SCBs aborted (da1:ahc0:0:1:0): SCB 0xf - timed out while idle, LASTPHASE == 0x1, SEQADDR == 0xa (da1:ahc0:0:1:0): Queuing a BDR SCB (da1:ahc0:0:1:0): Bus Device Reset Message Sent (da1:ahc0:0:1:0): no longer in timeout, status = 34b ahc0: Bus Device Reset on A:1. 32 SCBs aborted (da1:ahc0:0:1:0): READ(10). CDB: 28 0 0 a8 a4 9f 0 0 20 0 (da1:ahc0:0:1:0): HARDWARE FAILURE info:a31c asc:40,82 (da1:ahc0:0:1:0): Diagnostic failure: ASCQ = Component ID --------------- According to "Quantum Atlas III SCSI Product Manual", available at , this error means Diagnostics Failure, Inconsistent Data or Bugcheck Error code in information field. The grown defect list is empty, AWRE and ARRE is 1 on mode page 1 and WCE is 0 on mode page 8. - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 26 19: 6:27 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id BC820157E3 for ; Wed, 26 May 1999 19:06:10 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id UAA16406; Wed, 26 May 1999 20:06:06 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905270206.UAA16406@panzer.plutotech.com> Subject: Re: proper mode page values? In-Reply-To: <199905270117.UAA48835@nospam.hiwaay.net> from David Kelly at "May 26, 1999 08:17:01 pm" To: dkelly@HiWAAY.net (David Kelly) Date: Wed, 26 May 1999 20:06:06 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 David Kelly wrote... > My formerly wonderful IBM DCAS 34330 narrow drive is acting up on my > little FreeBSD system (a 486/133). Several months ago I had to use the > Adaptec 2940 built in utility to scan the drive for bad blocks. It > found several. Followed up with a clean installation of FreeBSD 3.1. > > Now I'm getting "indefinite wait" messages from swap_pager, much like > Dag-Erling Smorgrav reported on 19 Feb 1999, something like this: > > swap_pager: indefinite wait buffer: device: 0x30401, blkno: 264, size: 4096 > > The problem blocks are always 264, 272, and 496. You should also be getting some SCSI error message printed on the console. > And to make things maximally fun, it only happens when reading variable > block sized QIC-1000 tapes with an Archive Anaconda. Fixed block size > on a QIC-150 runs nicely. The variable QIC-1000 starts and stops and > starts and stops with every block. > > sa1 at ahc0 bus 0 target 6 lun 0 > sa1: Removable Sequential Access SCSI-2 device > sa1: 5.000MB/s transfers (5.000MHz, offset 15) That's rather odd. It may be that the Anaconda is staying on the bus too long or something. I dunno. > Tried using camcontrol to view my bad block lists. Doesn't work on that > IBM drive, nor the IBM drive on this machine: > > nospam: [1031] camcontrol defects -n da -u 0 -G > camcontrol: no defect list format specified > nospam: [1032] camcontrol defects -n da -u 0 -f block -G > error reading defect list: Input/output error > nospam: [1033] camcontrol defects -n da -u 0 -f bfi -G > error reading defect list: Input/output error > nospam: [1034] camcontrol defects -n da -u 0 -f phys -G > error reading defect list: Input/output error > nospam: [1035] camcontrol defects -n da -u 0 -f phys -P > error reading defect list: Input/output error > nospam: [1036] camcontrol defects -n da -u 0 -f bfi -P > error reading defect list: Input/output error > nospam: [1037] camcontrol defects -n da -u 0 -f block -P > error reading defect list: Input/output error You need to use the -v switch on the command line to see why the command is failing. > So then I go looking at mode pages to see what is set and to see if by > any chance the drive was told not to substitute replacements for > weakening blocks: > > nospam: [1038] camcontrol modepage -n da -u 0 -m 1 -P 2 > AWRE (Auto Write Reallocation Enbld): 0 > ARRE (Auto Read Reallocation Enbld): 0 Those are the defaults. > nospam: [1039] camcontrol modepage -n da -u 0 -m 1 -P 3 > AWRE (Auto Write Reallocation Enbld): 1 > ARRE (Auto Read Reallocation Enbld): 1 And these are the saved parameters. > The DCAS defaults are itentical to the stored values shown above on my: > > da0 at ncr0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 20.000MB/s transfers (10.000MHz, offset 15, 16bit), Tagged Queueing Enabled > da0: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > > The DCAS is on a version 1.16 Adaptec 2940, but on a different computer: > > ahc0: rev 0x00 int a irq 15 on pci0.9.0 > ahc0: aic7870 Single Channel A, SCSI Id=7, 16/255 SCBs > > So much for the background info. To the meat of the matter: > > How can I get bad block lists from IBM SCSI drives? Am I doing it wrong > or does it simply not work yet? It should work, use the -v switch argument to camcontrol to figure out why it's failing. > How to scan a SCSI drive and reallocate bad blocks? There's no utility, other than perhaps your controller's builtin utility, to automatically do that. There are a couple of things you can do from FreeBSD, though, that will allow you to either remap bad blocks automatically or manually: 1. Enable read and write reallocation, and then do a dd to overwrite the entire disk. That will force any bad blocks to get remapped. 2. Enable read and write reallocation, and then do a dd to read the entire disk to /dev/null or something like that. Each time you get something in your dmesg about a bad block, note the block number (in the info: section of the sense printout) and then use camcontrol to write something out to that disk block. I used the latter method to recover a disk with a bad block a month or so ago. At some point I may put a bad block scanning and remapping utility into camcontrol, but there are some other things I want to do first. > Are my modepage parameters sane? Was looking at page 0x01 because I was > worried about error handling. But here's the popular 0x08 too: > > nospam: [1043] camcontrol modepage -n da -u 0 -m 8 -P 3 > IC: 0 > ABPF: 0 > CAP: 0 > DISC: 0 > SIZE: 0 > WCE: 0 > MF: 0 > RCD: 0 > Demand Retention Priority: 1 > Write Retention Priority: 1 > Disable Pre-fetch Transfer Length: 65535 > Minimum Pre-fetch: 0 > Maximum Pre-fetch: 65535 > Maximum Pre-fetch Ceiling: 65535 Looks okay to me. The only one you might want to play with is the WCE bit, which enables write caching. That won't have any effect 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 May 27 6:29:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from bsd.mbp.ee (bsd.mbp.ee [194.204.12.74]) by hub.freebsd.org (Postfix) with ESMTP id BE5CB14E86 for ; Thu, 27 May 1999 06:28:06 -0700 (PDT) (envelope-from mauri@aripaev.ee) Received: from lant.mbp.ee (lant.mbp.ee [194.204.12.41]) by bsd.mbp.ee (8.9.3/8.9.3) with ESMTP id QAA21019 for ; Thu, 27 May 1999 16:27:55 +0300 (EEST) (envelope-from mauri@aripaev.ee) Received: by lant.mbp.ee with Internet Mail Service (5.5.2232.9) id ; Thu, 27 May 1999 16:28:50 +0300 Message-ID: <554419C71610D211B3F808003636280213B090@lant.mbp.ee> From: Lauri Laupmaa To: "'freebsd-scsi@freebsd.org'" Subject: FW: -STABLE scsi problem (bug?) Date: Thu, 27 May 1999 16:28:50 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-4" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi > > I've lately added old but reliable Micropolis Raidion RAID 5 array and a > 3rd aic7870 adapter. Raidion is only device on this adapter, it has ID 0 > and LUNs 0 and 1. After some days I get some errors like: > > > (da8:ahc2:0:0:1): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, > SEQADDR > == 0xa > > (da8:ahc2:0:0:1): Queuing a BDR SCB > > (da8:ahc2:0:0:1): no longer in timeout, status = 34a > > (da8:ahc2:0:0:1): Invalidating pack > > (da8:ahc2:0:0:1): Invalidating pack > > (da8:ahc2:0:0:1): Invalidating pack > > and then when I try to unmount (even with -f) filesystems on RAID, I get > device not configured. ls shows no files there... > > Now for the BUG: If I do shutdown -r now it says syncing disks 2 2 2 2 2 2 > 2 ... giving up and after reboot starts fsck EVERY filesystem ! If it > can't sync one then it reboots without syncing others... > > _____________ > Lauri Laupmaa > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 7:28:55 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 95B9514D04 for ; Thu, 27 May 1999 07:28:50 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id IAA04664; Thu, 27 May 1999 08:18:21 -0600 (MDT) Date: Thu, 27 May 1999 08:18:21 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199905271418.IAA04664@narnia.plutotech.com> To: Lauri Laupmaa Cc: scsi@FreeBSD.org Subject: Re: FW: -STABLE scsi problem (bug?) X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <554419C71610D211B3F808003636280213B090@lant.mbp.ee> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <554419C71610D211B3F808003636280213B090@lant.mbp.ee> you wrote: >> Hi >> >> I've lately added old but reliable Micropolis Raidion RAID 5 array and a >> 3rd aic7870 adapter. Raidion is only device on this adapter, it has ID 0 >> and LUNs 0 and 1. After some days I get some errors like: >> >> > (da8:ahc2:0:0:1): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, >> SEQADDR >> == 0xa >> > (da8:ahc2:0:0:1): Queuing a BDR SCB >> > (da8:ahc2:0:0:1): no longer in timeout, status = 34a >> > (da8:ahc2:0:0:1): Invalidating pack >> > (da8:ahc2:0:0:1): Invalidating pack >> > (da8:ahc2:0:0:1): Invalidating pack What version of -stable are you using? The likely problem here is that the Raidion cannot handle the number of transactions we throw at it in parallel. Do you get any additional information if you boot -v? Without -v, I can't tell if the device is returing QUEUE FULL messages or not. >> and then when I try to unmount (even with -f) filesystems on RAID, I get >> device not configured. ls shows no files there... This is not a SCSI bug, but a problem with how the FS layers deal with devices that suddenly go away. >> Now for the BUG: If I do shutdown -r now it says syncing disks 2 2 2 2 2 2 >> 2 ... giving up and after reboot starts fsck EVERY filesystem ! If it >> can't sync one then it reboots without syncing others... That's also not a SCSI bug. I don't know why the clean bit is not set on any filesystem that is synched properly. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 7:52:18 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 1A87E1524B for ; Thu, 27 May 1999 07:52:09 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id AAA07687; Fri, 28 May 1999 00:45:12 +1000 Date: Fri, 28 May 1999 00:45:12 +1000 From: Bruce Evans Message-Id: <199905271445.AAA07687@godzilla.zeta.org.au> To: gibbs@narnia.plutotech.com, mauri@aripaev.ee Subject: Re: FW: -STABLE scsi problem (bug?) Cc: scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>> Now for the BUG: If I do shutdown -r now it says syncing disks 2 2 2 2 2 2 >>> 2 ... giving up and after reboot starts fsck EVERY filesystem ! If it >>> can't sync one then it reboots without syncing others... > >That's also not a SCSI bug. I don't know why the clean bit is not >set on any filesystem that is synched properly. vfs doesn't really know which filesystems have been synced properly, and doesn't call unmount() for any filesystem unless all buffers were synced. The clean bit is set by unmount() so it is left unset for all rw-mounted filesystems if the sync failed. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 7:56:52 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 3422B150DE for ; Thu, 27 May 1999 07:56:46 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id IAA49492; Thu, 27 May 1999 08:52:13 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <199905271452.IAA49492@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bruce Evans Cc: gibbs@plutotech.com, mauri@aripaev.ee, scsi@FreeBSD.ORG Subject: Re: FW: -STABLE scsi problem (bug?) In-reply-to: Your message of "Fri, 28 May 1999 00:45:12 +1000." <199905271445.AAA07687@godzilla.zeta.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 May 1999 08:42:05 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>> Now for the BUG: If I do shutdown -r now it says syncing disks 2 2 2 2 2 2 >>>> 2 ... giving up and after reboot starts fsck EVERY filesystem ! If it >>>> can't sync one then it reboots without syncing others... >> >>That's also not a SCSI bug. I don't know why the clean bit is not >>set on any filesystem that is synched properly. > >vfs doesn't really know which filesystems have been synced properly, >and doesn't call unmount() for any filesystem unless all buffers were >synced. The clean bit is set by unmount() so it is left unset for >all rw-mounted filesystems if the sync failed. > >Bruce Can't we just walk the buffer list, note the FSes the buffers reference, and unmount any FSes that aren't referenced? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 9:18:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 12AF71507D for ; Thu, 27 May 1999 09:18:51 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id CAA14114; Fri, 28 May 1999 02:17:50 +1000 Date: Fri, 28 May 1999 02:17:50 +1000 From: Bruce Evans Message-Id: <199905271617.CAA14114@godzilla.zeta.org.au> To: bde@zeta.org.au, gibbs@plutotech.com Subject: Re: FW: -STABLE scsi problem (bug?) Cc: mauri@aripaev.ee, scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>vfs doesn't really know which filesystems have been synced properly, >>and doesn't call unmount() for any filesystem unless all buffers were >>synced. The clean bit is set by unmount() so it is left unset for >>all rw-mounted filesystems if the sync failed. >Can't we just walk the buffer list, note the FSes the buffers reference, >and unmount any FSes that aren't referenced? We could, but syncing can only fail if there is an unexpected problem, so we should be conservative if we don't understand the problem. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 9:24:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from bsd.mbp.ee (bsd.mbp.ee [194.204.12.74]) by hub.freebsd.org (Postfix) with ESMTP id 7FE3F14FA8 for ; Thu, 27 May 1999 09:24:24 -0700 (PDT) (envelope-from mauri@aripaev.ee) Received: from lant.mbp.ee (lant.mbp.ee [194.204.12.41]) by bsd.mbp.ee (8.9.3/8.9.3) with ESMTP id TAA49700; Thu, 27 May 1999 19:23:58 +0300 (EEST) (envelope-from mauri@aripaev.ee) Received: by lant.mbp.ee with Internet Mail Service (5.5.2232.9) id ; Thu, 27 May 1999 19:24:53 +0300 Message-ID: <554419C71610D211B3F808003636280213B092@lant.mbp.ee> From: Lauri Laupmaa To: "'Bruce Evans'" Cc: scsi@FreeBSD.ORG Subject: RE: FW: -STABLE scsi problem (bug?) Date: Thu, 27 May 1999 19:24:52 +0300 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>all rw-mounted filesystems if the sync failed. >Can't we just walk the buffer list, note the FSes the buffers reference, >and unmount any FSes that aren't referenced? >We could, but syncing can only fail if there is an unexpected problem, so >we should be conservative if we don't understand the problem The problem is deinitely there, as when i unmount other filesystems by hand befoore shutdown then fsck checks only filesystems on Raidion. Below are filesystems: bash-2.03# mount /dev/da0s1a on / (local, soft-updates, writes: sync 5 async 57483) /dev/da0s1e on /tmp (local, soft-updates, writes: sync 24 async 233463) /dev/da0s1g on /usr (local, soft-updates, writes: sync 8 async 58498) /dev/da2s1e on /home (local, soft-updates, writes: sync 4 async 10976) /dev/da0s1f on /var (local, soft-updates, writes: sync 3729 async 274823) /dev/da3s1e on /usr/local (local, soft-updates, writes: sync 262 async 137647) /dev/da1s1e on /var/cache1 (local, noatime, soft-updates, writes: sync 6 async 117057) /dev/ccd0c on /usr/ftp (local, soft-updates, writes: sync 245 async 76466) <-------- Raidion /dev/da7s1e on /mnt (local, soft-updates, writes: sync 2 async 4) <--------------- Raidion /dev/da8s1e on /foto (local, soft-updates, writes: sync 107 async 3904) procfs on /proc (local) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 10:18:29 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 344791500E for ; Thu, 27 May 1999 10:18:26 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA26013; Thu, 27 May 1999 10:12:21 -0700 Date: Thu, 27 May 1999 10:11:18 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Dirk-Willem van Gulik , Darryl Okahata , Karl Denninger Cc: freebsd-scsi@freebsd.org Subject: OnStream SCSI drives In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I got the documentation for this device and got a drive unit, and took a quick look at this today (I have to be gone until next tuesday- my flight leaves in a couple of hours). The support for this is going to be quite complex. Not only is it the various modifications to commands (must have 'immediate' bit set, etc..), but it means that: + All records are 32KBytes user data *PLUS* a 512 byte AUX field that describes this tape frame. The AUX field has to not only describe what's in this record but also record the number of filemark frames preceeding this, etc... + Write errors due to defective media have to be handled in software- i.e., the data relocated to the next frame, with possibly updating the failed frame so that later read of that frame knows that it's bogus (and where to go for the 'good' frame). It will be possible to support variable mode or different blocksizes with this tape format- if we want to. Basically we have to do in software that which the Tandberg QIC tape devices do (and do in somwhat pixielike manner at that..). In any case, this is not a no-brainer trivial task. I'll start tackling it next week, but it'll probably take a couple of weeks at least. I'll ask Onstream if they mind the information going out so if others have more aggressive schedules they can try to implement this sooner if they lke, but you'd better coordinate with me on this. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 10:36:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from Genesis.Denninger.Net (kdhome-2.pr.mcs.net [205.164.6.10]) by hub.freebsd.org (Postfix) with ESMTP id 51FD414CE2 for ; Thu, 27 May 1999 10:36:40 -0700 (PDT) (envelope-from karl@Genesis.Denninger.Net) Received: (from karl@localhost) by Genesis.Denninger.Net (8.9.3/8.8.2) id MAA50905; Thu, 27 May 1999 12:33:50 -0500 (CDT) Message-ID: <19990527123349.B50895@Denninger.Net> Date: Thu, 27 May 1999 12:33:49 -0500 From: Karl Denninger To: mjacob@feral.com, Dirk-Willem van Gulik , Darryl Okahata Cc: freebsd-scsi@freebsd.org Subject: Re: OnStream SCSI drives 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 Thu, May 27, 1999 at 10:11:18AM -0700 Organization: Karl's Sushi and Packet Smashers X-Die-Spammers: Spammers will be LARTed and the remains fed to my cat Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks - I have decided to wait, as I found someone with two DLT 15/30s that they weren't using and got them REALLY cheap. I still want the Onstream support, but its no longer a fire. Now I know why the hacks I did (including the 32k fixed blocksize) didn't work. -- -- Karl Denninger (karl@denninger.net) Web: fathers.denninger.net I ain't even *authorized* to speak for anyone other than myself, so give up now on trying to associate my words with any particular organization. On Thu, May 27, 1999 at 10:11:18AM -0700, Matthew Jacob wrote: > > I got the documentation for this device and got a drive unit, and took a > quick look at this today (I have to be gone until next tuesday- my flight > leaves in a couple of hours). > > The support for this is going to be quite complex. Not only is it the > various modifications to commands (must have 'immediate' bit set, etc..), > but it means that: > > + All records are 32KBytes user data *PLUS* a 512 byte AUX field > that describes this tape frame. The AUX field has to not only > describe what's in this record but also record the number of > filemark frames preceeding this, etc... > > + Write errors due to defective media have to be handled in > software- i.e., the data relocated to the next frame, with > possibly updating the failed frame so that later read of that > frame knows that it's bogus (and where to go for the 'good' > frame). > > It will be possible to support variable mode or different blocksizes with > this tape format- if we want to. Basically we have to do in software that > which the Tandberg QIC tape devices do (and do in somwhat pixielike manner > at that..). In any case, this is not a no-brainer trivial task. I'll start > tackling it next week, but it'll probably take a couple of weeks at least. > > I'll ask Onstream if they mind the information going out so if others have > more aggressive schedules they can try to implement this sooner if they > lke, but you'd better coordinate with me on this. > > -matt > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 11: 9:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from atlrel1.hp.com (atlrel1.hp.com [156.153.255.210]) by hub.freebsd.org (Postfix) with ESMTP id 9F46814F99 for ; Thu, 27 May 1999 11:09:37 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by atlrel1.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id OAA10563; Thu, 27 May 1999 14:08:55 -0400 (EDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA184988554; Thu, 27 May 1999 11:09:14 -0700 Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_14041)/8.7.3 TIS 5.0) id LAA15473; Thu, 27 May 1999 11:09:14 -0700 (PDT) Message-Id: <199905271809.LAA15473@mina.sr.hp.com> To: mjacob@feral.com Cc: Dirk-Willem van Gulik , Karl Denninger , freebsd-scsi@freebsd.org Subject: Re: OnStream SCSI drives Reply-To: Darryl Okahata In-Reply-To: Your message of "Thu, 27 May 1999 10:11:18 PDT." Mime-Version: 1.0 (generated by tm-edit 1.1.1.1) Content-Type: text/plain; charset=US-ASCII Date: Thu, 27 May 1999 11:09:14 -0700 From: Darryl Okahata Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote: > I got the documentation for this device and got a drive unit, and took a > quick look at this today (I have to be gone until next tuesday- my flight > leaves in a couple of hours). Thanks for the update. I'm surprised (but glad!) that you obtained the documenatation so quickly. OnStream just contacted me yesterday, offering me a copy of their documentation; however, they told me that it wouldn't be available until June 7. > The support for this is going to be quite complex. Not only is it the > various modifications to commands (must have 'immediate' bit set, etc..), > but it means that: Yow. Ackptuii. How are you thinking of handling this? I was thinking of a userland driver program, but it sounds like you're considering kernel driver foo. If you can, great. > I'll ask Onstream if they mind the information going out so if others have > more aggressive schedules they can try to implement this sooner if they > lke, but you'd better coordinate with me on this. It sounds like you've got slightly more time than me. If you weren't going to do it, I'd give it a shot, but I'll let you do it. I can help with testing, though. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 11:18: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DD7AC15906 for ; Thu, 27 May 1999 11:17:56 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA26270; Thu, 27 May 1999 11:14:32 -0700 Date: Thu, 27 May 1999 11:13:29 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Darryl Okahata Cc: Dirk-Willem van Gulik , Karl Denninger , freebsd-scsi@freebsd.org Subject: Re: OnStream SCSI drives In-Reply-To: <199905271809.LAA15473@mina.sr.hp.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 > Matthew Jacob wrote: > > > I got the documentation for this device and got a drive unit, and took a > > quick look at this today (I have to be gone until next tuesday- my flight > > leaves in a couple of hours). > > Thanks for the update. I'm surprised (but glad!) that you > obtained the documenatation so quickly. OnStream just contacted me > yesterday, offering me a copy of their documentation; however, they told > me that it wouldn't be available until June 7. Heh.... > > > The support for this is going to be quite complex. Not only is it the > > various modifications to commands (must have 'immediate' bit set, etc..), > > but it means that: > > Yow. Ackptuii. > > How are you thinking of handling this? I was thinking of a > userland driver program, but it sounds like you're considering kernel > driver foo. If you can, great. I haven't quite decided. I'm inclined to just special case it. There's some utility to doing an emulation layer somewhere, but that's probably overkill. Look- we don't want to *encourage* manufacturers to produce this kind of stuff- we'll make an exception in this case 'coz this looks like a *really* nice drive, but let's not make this the rule. > > > I'll ask Onstream if they mind the information going out so if others have > > more aggressive schedules they can try to implement this sooner if they > > lke, but you'd better coordinate with me on this. > > It sounds like you've got slightly more time than me. If you > weren't going to do it, I'd give it a shot, but I'll let you do it. I > can help with testing, though. That would be helpful. What I'm also concerned about is media interchange with non-FreeBSD systems... Was it you who said you have a wad of NT workstations with these drives now? Making sure that the media can exchanged between systems is of crucial importance. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 11:27:42 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from palrel3.hp.com (palrel3.hp.com [156.153.255.226]) by hub.freebsd.org (Postfix) with ESMTP id 5E5C6155EF for ; Thu, 27 May 1999 11:27:40 -0700 (PDT) (envelope-from darrylo@sr.hp.com) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by palrel3.hp.com (8.8.6 (PHNE_17135)/8.8.5tis) with ESMTP id LAA18212; Thu, 27 May 1999 11:27:09 -0700 (PDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA197079628; Thu, 27 May 1999 11:27:08 -0700 Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_14041)/8.7.3 TIS 5.0) id LAA15872; Thu, 27 May 1999 11:27:07 -0700 (PDT) Message-Id: <199905271827.LAA15872@mina.sr.hp.com> To: mjacob@feral.com Cc: Dirk-Willem van Gulik , Karl Denninger , freebsd-scsi@freebsd.org Subject: Re: OnStream SCSI drives Reply-To: Darryl Okahata In-Reply-To: Your message of "Thu, 27 May 1999 11:13:29 PDT." Mime-Version: 1.0 (generated by tm-edit 1.1.1.1) Content-Type: text/plain; charset=US-ASCII Date: Thu, 27 May 1999 11:27:07 -0700 From: Darryl Okahata Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote: > > How are you thinking of handling this? I was thinking of a > > userland driver program, but it sounds like you're considering kernel > > driver foo. If you can, great. > > I haven't quite decided. I'm inclined to just special case it. There's > some utility to doing an emulation layer somewhere, but that's probably > overkill. Look- we don't want to *encourage* manufacturers to produce this > kind of stuff- we'll make an exception in this case 'coz this looks like a > *really* nice drive, but let's not make this the rule. True, but it sounds like we're talking about some pretty big driver additions. Would this be something (optional?) added to st0, or would it be a new driver like "os0"? We don't want to bloat the st0 driver for those people who don't have OnStream drives. If you can add support via a driver, great. That's certainly the best way to go. > That would be helpful. What I'm also concerned about is media interchange > with non-FreeBSD systems... Was it you who said you have a wad of NT > workstations with these drives now? Making sure that the media can > exchanged between systems is of crucial importance. Not me. While I do happen to have an NT box, it hasn't been turned on in months, and I've been meaning to wipe it clean and install FreeBSD on it. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 11:30:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D2E5F14BE4 for ; Thu, 27 May 1999 11:30:32 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA26306; Thu, 27 May 1999 11:20:22 -0700 Date: Thu, 27 May 1999 11:19:19 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Darryl Okahata Cc: Dirk-Willem van Gulik , Karl Denninger , freebsd-scsi@FreeBSD.ORG Subject: Re: OnStream SCSI drives 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 > > That would be helpful. What I'm also concerned about is media interchange > with non-FreeBSD systems... Was it you who said you have a wad of NT > workstations with these drives now? Making sure that the media can > exchanged between systems is of crucial importance. (answering myself, "No, it was Dirk-Willem....") To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 11:40:11 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6F3A8159B0 for ; Thu, 27 May 1999 11:40:07 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA26379; Thu, 27 May 1999 11:33:33 -0700 Date: Thu, 27 May 1999 11:32:30 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Darryl Okahata Cc: Dirk-Willem van Gulik , Karl Denninger , freebsd-scsi@freebsd.org Subject: Re: OnStream SCSI drives In-Reply-To: <199905271827.LAA15872@mina.sr.hp.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 > Matthew Jacob wrote: > > > > How are you thinking of handling this? I was thinking of a > > > userland driver program, but it sounds like you're considering kernel > > > driver foo. If you can, great. > > > > I haven't quite decided. I'm inclined to just special case it. There's > > some utility to doing an emulation layer somewhere, but that's probably > > overkill. Look- we don't want to *encourage* manufacturers to produce this > > kind of stuff- we'll make an exception in this case 'coz this looks like a > > *really* nice drive, but let's not make this the rule. > > True, but it sounds like we're talking about some pretty big driver > additions. Would this be something (optional?) added to st0, or would > it be a new driver like "os0"? We don't want to bloat the st0 driver > for those people who don't have OnStream drives. Added to st0. Maybe a config option. The amount of code probably isn't *that* big. > > If you can add support via a driver, great. That's certainly the > best way to go. > > > That would be helpful. What I'm also concerned about is media interchange > > with non-FreeBSD systems... Was it you who said you have a wad of NT > > workstations with these drives now? Making sure that the media can > > exchanged between systems is of crucial importance. > > Not me. While I do happen to have an NT box, it hasn't been turned > on in months, and I've been meaning to wipe it clean and install FreeBSD > on it. heh... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 11:48:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from quark.ChrisBowman.com (crbowman.erols.com [209.122.47.155]) by hub.freebsd.org (Postfix) with ESMTP id B8A13159B8; Thu, 27 May 1999 11:48:46 -0700 (PDT) (envelope-from crb@ChrisBowman.com) Received: from fermion (fermion.ChrisBowman.com [10.0.1.2]) by quark.ChrisBowman.com (8.9.2/8.8.8) with SMTP id OAA07996; Thu, 27 May 1999 14:47:46 -0400 (EDT) (envelope-from crb@ChrisBowman.com) Message-Id: <199905271847.OAA07996@quark.ChrisBowman.com> X-Sender: crb@quark X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Thu, 27 May 1999 14:46:06 -0400 To: "Justin T. Gibbs" From: "Christopher R. Bowman" Subject: Re: Support for Symbios vs. Adaptect SCSI Cc: freebsd-scsi@freebsd.org, hardware@freebsd.org In-Reply-To: <199905271517.JAA04842@narnia.plutotech.com> References: <199905270156.SAA11635@ryouko.nas.nasa.gov> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 09:17 AM 5/27/99 -0600, Justin T. Gibbs wrote: >In article <199905270156.SAA11635@ryouko.nas.nasa.gov> you wrote: >>> >Do you mean: >>> > >>> > 1) Has fewer bugs? >>> > 2) Makes better use of the hardware capabilities? >>> > 3) Has a maintainer who is willing/able to devote >>> > more time to the task? >> >> I can believe 1 & 3, but could you (Justin?) elaborate on 2? I've >> always been under the impression that everything after the old ISA >> Adaptec 1542CF has been basically riding on Adaptec's brand name to >> justify their cards costing 2-3x as much as the equivilent Symbios >> (NCR) based card. [You can pick up UW-SCSI 875 based Symbios cards >> for $75 bucks these days] > >In general, the PCI interface on the Adaptec chips is unsurpassed >in the industry. They have larger FIFOs and lower latency than their >competitors, and pretty much work if you follow the supplied schematics. >These were the reasons Pluto chose Adaptec over Symbios for our >motherboard applications where PCI bandwidth is a critical concern. >On the SCSI side of things, the built in RISC core has several features >that reduce DMA overhead and allow DMA prefetch to take advantage of >spare PCI bandwidth. You can setup background DMAs on the secondard DMA >channel to prefetch the next command to be serviced, the next block of >S/G list entries for the current command or other data well before you >need it so that even on a highly utilized PCI bus, you rarely keep SCSI >devices waiting. They really do know how to design hardware. I find this type of information most helpful in understanding why things are the way they are. Thank you. >Now for typical workstation and server workloads where you don't >have a fully populated PCI bus (Pluto boards can have up to 10 >devices per PCI bus), the Symbios parts should be able to provide >performance comensurate with those provided by Adaptec. The only >factor preventing that, in my opinion, is the structure of the NCR >driver's firmware. The format of the firmware, which is the >concatenation of several 'C' structures of different types, makes >it extremely difficult to modify unless you understand all of the >strange alignment restrictions and vagaries of this method. There >are known scalability problems in the data structures used to >represent SCSI transactions in this driver and I have not found >the time to completely understand how the firmware format to address >them. My plan is to write an assembler for the Symbios scripts >engine so that the firmware is easier to read, modify, and understand. >At that point, I would expect the Symbios parts to be as well >supported under FreeBSD as the Adaptec parts. I don't expect to >get around to this until late this summer. There already exists the SCRIPTS assembler that produces C code structures containing the data as preinitialized arrays. I thought I even saw the source to it floating around somewhere. Are you looking to write a better assembler or just oblivious of the existing one? I have, in the past, written an assembler for a custom CPU for which I did the mask layout and design, and I have been looking for a way to contribute to the project (I am a hardware guy with a lot of software under my belt, but I just can't seem to wrap my head around the kernel). Perhaps you could describe what exactly you are looking for in an assembler and I could work on it for you. When it comes to SCSI I am a neophyte but I have been reading the Symbios manuals and looking at the NCR driver lately because there is so much documentation readily available. When you do begin to work on the NCR driver, I would be very interested to hear your broad outline for how you intend to redesign the driver. -------- Christopher R. Bowman crb@ChrisBowman.com http://www.ChrisBowman.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 12:16:16 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 960D015055; Thu, 27 May 1999 12:16:10 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id NAA57184; Thu, 27 May 1999 13:16:07 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <199905271916.NAA57184@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Christopher R. Bowman" Cc: "Justin T. Gibbs" , freebsd-scsi@freebsd.org, hardware@freebsd.org Subject: Re: Support for Symbios vs. Adaptect SCSI In-reply-to: Your message of "Thu, 27 May 1999 14:46:06 EDT." <199905271847.OAA07996@quark.ChrisBowman.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 May 1999 13:05:58 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>My plan is to write an assembler for the Symbios scripts >>engine so that the firmware is easier to read, modify, and understand. >>At that point, I would expect the Symbios parts to be as well >>supported under FreeBSD as the Adaptec parts. I don't expect to >>get around to this until late this summer. > >There already exists the SCRIPTS assembler that produces C code structures >containing the data as preinitialized arrays. I thought I even saw the source >to it floating around somewhere. Are you looking to write a better assembler >or just oblivious of the existing one? It is the general policy of the project to provide all the tools required to modify a driver in the standard distribution. The aic7xxx driver, for instance, provides the assembler that I wrote for its RISC engine. If the source is available for NASM (I've only seen the DOS executables) and it allows for things like chip specific program patching at device attach time, then that would certainly work. >I have, in the past, written an assembler for a custom CPU for which I did the >mask layout and design, and I have been looking for a way to contribute to the >project (I am a hardware guy with a lot of software under my belt, but I just >can't seem to wrap my head around the kernel). Perhaps you could describe >what exactly you are looking for in an assembler and I could work on it for >you. The scripts syntax is somewhat obtuse, but I guess it would suffice. The main additional feature I'd want in the assembler is the ability to easily designate condition portions of the script that can be independently patched in. Take a look at the sys/dev/aic7xxx/aic7xxx.seq and the output from aicasm in sys/compile/KERNAME/aic7xxx_seq.h for an idea of the patching capability I'd want. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 18:47: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from web608.mail.yahoo.com (web608.mail.yahoo.com [128.11.68.172]) by hub.freebsd.org (Postfix) with SMTP id C16AB151A9 for ; Thu, 27 May 1999 18:47:00 -0700 (PDT) (envelope-from a426_400@yahoo.com) Message-ID: <19990528014816.25350.rocketmail@web608.mail.yahoo.com> Received: from [203.70.70.2] by web608.mail.yahoo.com; Thu, 27 May 1999 18:48:16 PDT Date: Thu, 27 May 1999 18:48:16 -0700 (PDT) From: card been Subject: auth c06bfb87 subscribe freebsd-scsi a426@sina.com.tw To: freebsd-scsi@FreeBSD.ORG MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org auth c06bfb87 subscribe freebsd-scsi a426@sina.com.tw _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 18:56:15 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (Postfix) with ESMTP id 51D1415247 for ; Thu, 27 May 1999 18:55:54 -0700 (PDT) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt8-216-180-14-252.dialup.HiWAAY.net [216.180.14.252]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id UAA17288; Thu, 27 May 1999 20:55:50 -0500 (CDT) Received: from nospam.hiwaay.net (nospam.hiwaay.net [127.0.0.1]) by nospam.hiwaay.net (8.9.3/8.9.3) with ESMTP id UAA53624; Thu, 27 May 1999 20:55:48 -0500 (CDT) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199905280155.UAA53624@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG From: David Kelly Subject: Re: proper mode page values? In-reply-to: Message from "Kenneth D. Merry" of "Wed, 26 May 1999 20:06:06 MDT." <199905270206.UAA16406@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 27 May 1999 20:55:48 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" writes: > > swap_pager: indefinite wait buffer: device: 0x30401, blkno: 264, size: 4096 > > > > The problem blocks are always 264, 272, and 496. > > You should also be getting some SCSI error message printed on the console. Actually that is what was being written to the console and /var/log/messages. I don't remember any other messages but the problem is easily repeatable (might take an hour, and the machine is at work while my email is at home). System spit out more than 10 or 15 of those messages before it locked up. Meanwile it was getting slower. X was not running. Could Alt-Fn between virtual consoles. Could control-alt-esc and get the "no kernel debugger" message. If I could read my whole tape then I could update the system and isntall the kernel debugger too. System doesn't have sources on it at the moment. :-( > That's rather odd. It may be that the Anaconda is staying on the bus too > long or something. I dunno. That's what I'm thinking. At home I have my tape drives on a narrow Adaptec 2940, the twin of the 2940 in the work machine. And a matching Anaconda in both places. But at home the HD is on a wide Symbios 875. > > Tried using camcontrol to view my bad block lists. Doesn't work on that > > IBM drive, nor the IBM drive on this machine: > > [...] > > nospam: [1037] camcontrol defects -n da -u 0 -f block -P > > error reading defect list: Input/output error > > You need to use the -v switch on the command line to see why the command is > failing. Fair enough. Doesn't look like -v adds much information: nospam: [1045] camcontrol defects -v -n da -u 0 -f block -G error reading defect list: Input/output error CAM status is 0 nospam: [1046] camcontrol defects -n da -u 0 -f block -G error reading defect list: Input/output error nospam: [1047] id uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff), 31(guest) nospam: [1048] Ah! Forgot to check /var/log/messages. This is the output for a single attempt at "camcontrol defects", the one listed above: May 27 19:12:22 nospam /kernel: (pass2:ncr0:0:0:0): extraneous data discarded. May 27 19:12:22 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 80) @0xc0abbe00. May 27 19:12:22 nospam /kernel: (pass2:ncr0:0:0:0): extraneous data discarded. May 27 19:12:22 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 80) @0xc0abbe00. > > So then I go looking at mode pages to see what is set and to see if by > > any chance the drive was told not to substitute replacements for > > weakening blocks: > > > > nospam: [1038] camcontrol modepage -n da -u 0 -m 1 -P 2 > > AWRE (Auto Write Reallocation Enbld): 0 > > ARRE (Auto Read Reallocation Enbld): 0 > > Those are the defaults. > > > nospam: [1039] camcontrol modepage -n da -u 0 -m 1 -P 3 > > AWRE (Auto Write Reallocation Enbld): 1 > > ARRE (Auto Read Reallocation Enbld): 1 > > And these are the saved parameters. Yes, I understood defaults and saved. The observation was the 9G drive was shipped with different saved (-P 3) values than the factory defaults (-P 2). The 9G saved values appear to be the same as the 4G defaults which were also the same as its saved values. So sifting thru everything, it would appear AWRE and ARRE are Good Things To Set? How about "TB (Transfer Block)"? That sounds like one that will attempt to copy (transfer) the contents of a sick but not dead block. But then AWRE and ARRE sound like they do that too. Or maybe "EER (Enable Early Recovery)" is one that will attempt to recover and repair before the damage is permanent? "DTE (Disable Transfer on Error)", now why would we enable something like TB then use a different parameter to disable it? This must mean something totally different. I'm confused. > 1. Enable read and write reallocation, and then do a dd to overwrite the > entire disk. That will force any bad blocks to get remapped. With AWRE and ARRE enabled in the first place I should never need to do the above? Right? The advantage of scanning the whole disk at once as above is to verify there are no problems and/or to observe the automatic bad block replacement doing its thing? > > Are my modepage parameters sane? Was looking at page 0x01 because I was > > worried about error handling. But here's the popular 0x08 too: [...] > > Looks okay to me. The only one you might want to play with is the WCE bit, > which enables write caching. That won't have any effect WCE is the only one I've played with. Had to use bonnie to tell the difference. So I put it back the way I found it. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 27 20:12:12 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id E0B4714E15 for ; Thu, 27 May 1999 20:12:06 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.3/8.8.5) id VAA23315; Thu, 27 May 1999 21:12:03 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199905280312.VAA23315@panzer.plutotech.com> Subject: Re: proper mode page values? In-Reply-To: <199905280155.UAA53624@nospam.hiwaay.net> from David Kelly at "May 27, 1999 08:55:48 pm" To: dkelly@hiwaay.net (David Kelly) Date: Thu, 27 May 1999 21:12:03 -0600 (MDT) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (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 David Kelly wrote... > "Kenneth D. Merry" writes: > > > swap_pager: indefinite wait buffer: device: 0x30401, blkno: 264, size: 4096 > > > > > > The problem blocks are always 264, 272, and 496. > > > > You should also be getting some SCSI error message printed on the console. > > Actually that is what was being written to the console and > /var/log/messages. I don't remember any other messages but the problem > is easily repeatable (might take an hour, and the machine is at work > while my email is at home). > > System spit out more than 10 or 15 of those messages before it locked > up. Meanwile it was getting slower. X was not running. Could Alt-Fn > between virtual consoles. Could control-alt-esc and get the "no kernel > debugger" message. If I could read my whole tape then I could update > the system and isntall the kernel debugger too. System doesn't have > sources on it at the moment. :-( > > > That's rather odd. It may be that the Anaconda is staying on the bus too > > long or something. I dunno. > > That's what I'm thinking. At home I have my tape drives on a narrow > Adaptec 2940, the twin of the 2940 in the work machine. And a matching > Anaconda in both places. But at home the HD is on a wide Symbios 875. > > > > Tried using camcontrol to view my bad block lists. Doesn't work on that > > > IBM drive, nor the IBM drive on this machine: > > > > [...] > > > nospam: [1037] camcontrol defects -n da -u 0 -f block -P > > > error reading defect list: Input/output error > > > > You need to use the -v switch on the command line to see why the command is > > failing. > > Fair enough. Doesn't look like -v adds much information: > > nospam: [1045] camcontrol defects -v -n da -u 0 -f block -G > error reading defect list: Input/output error > CAM status is 0 > nospam: [1046] camcontrol defects -n da -u 0 -f block -G > error reading defect list: Input/output error > nospam: [1047] id > uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff), 31(guest) > nospam: [1048] > > Ah! Forgot to check /var/log/messages. This is the output for a single > attempt at "camcontrol defects", the one listed above: > > May 27 19:12:22 nospam /kernel: (pass2:ncr0:0:0:0): extraneous data discarded. > May 27 19:12:22 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 80) @0xc0abbe00. > May 27 19:12:22 nospam /kernel: (pass2:ncr0:0:0:0): extraneous data discarded. > May 27 19:12:22 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 80) @0xc0abbe00. Hmm, that helps a little, but not much. I don't know how to decipher the NCR driver error messages. If someone knows what those NCR messages mean, it might shed some light on things. You could also try hooking the disks up to an Adaptec controller. (at least I generally understand the errors the Adaptec driver spits out, or can ask Justin what they mean) > > > So then I go looking at mode pages to see what is set and to see if by > > > any chance the drive was told not to substitute replacements for > > > weakening blocks: > > > > > > nospam: [1038] camcontrol modepage -n da -u 0 -m 1 -P 2 > > > AWRE (Auto Write Reallocation Enbld): 0 > > > ARRE (Auto Read Reallocation Enbld): 0 > > > > Those are the defaults. > > > > > nospam: [1039] camcontrol modepage -n da -u 0 -m 1 -P 3 > > > AWRE (Auto Write Reallocation Enbld): 1 > > > ARRE (Auto Read Reallocation Enbld): 1 > > > > And these are the saved parameters. > > Yes, I understood defaults and saved. The observation was the 9G drive > was shipped with different saved (-P 3) values than the factory defaults > (-P 2). The 9G saved values appear to be the same as the 4G defaults > which were also the same as its saved values. > > So sifting thru everything, it would appear AWRE and ARRE are Good > Things To Set? Yes, they generally are, unless you want to remap bad blocks on your own. (99.9% of people will want to have the drive do it automatically) > How about "TB (Transfer Block)"? That sounds like one that will attempt > to copy (transfer) the contents of a sick but not dead block. But then > AWRE and ARRE sound like they do that too. Actually, that means: =========================================================================== A transfer block (TB) bit of one indicates that a data block that is not recovered within the recovery limits specified shall be transferred to the initiator before CHECK CONDITION status is returned. A TB bit of zero indicates that such a data block shall not be transferred to the initiator. The TB bit does not affect the action taken for recovered data. =========================================================================== That's probably not what you're looking for. > Or maybe "EER (Enable Early Recovery)" is one that will attempt to > recover and repair before the damage is permanent? > > "DTE (Disable Transfer on Error)", now why would we enable something > like TB then use a different parameter to disable it? This must mean > something totally different. I'm confused. I'd suggest looking at the SCSI-2 or SCSI-3 spec. The SCSI-2 spec (i.e. the one I've got handy) has a reasonably long section describing mode page 1 and the various things you can set and what they do. > > 1. Enable read and write reallocation, and then do a dd to overwrite the > > entire disk. That will force any bad blocks to get remapped. > > With AWRE and ARRE enabled in the first place I should never need to do > the above? Right? The advantage of scanning the whole disk at once as > above is to verify there are no problems and/or to observe the > automatic bad block replacement doing its thing? Having read and write reallocation enabled doesn't necessarily mean you'll never run into bad blocks. The drive won't remap a block if it can't recover the data that was in it. That isn't so much a problem with write reallocation, since the data is being written, and therefore is valid. With read reallocation, though, the block can go bad and there may be no way for the drive to recover it. It's those blocks that you'll most likely get errors about, and it's those blocks that the above procedure will force to get remapped. Going over the whole drive at once is just a quick and dirty way to force any bad blocks on the disk to get remapped. You can also try to read every block on the disk, and then write to just the blocks that the disk complains about. I used that procedure recently to fix a bad block on a disk. > > > Are my modepage parameters sane? Was looking at page 0x01 because I was > > > worried about error handling. But here's the popular 0x08 too: > [...] > > > > Looks okay to me. The only one you might want to play with is the WCE bit, > > which enables write caching. That won't have any effect > > WCE is the only one I've played with. Had to use bonnie to tell the > difference. So I put it back the way I found it. Yeah, either way will generally work. It depends on what sort of performance you get and what you feel comfortable with. 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 May 28 0:32:43 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from vaio.on-the-road.webweaving.org (workstation1.swip.net [130.244.254.1]) by hub.freebsd.org (Postfix) with ESMTP id A623A14D86 for ; Fri, 28 May 1999 00:32:36 -0700 (PDT) (envelope-from dirkx@webweaving.org) Received: (from dirkx@localhost) by vaio.on-the-road.webweaving.org (8.8.8/8.8.8) id CAA00576; Fri, 28 May 1999 02:25:03 -0700 (PDT) (envelope-from dirkx) X-MX-Masquarade: Passed MX vaio.on-the-road.webweaving.org at Vaio / WebWeaving X-No-Spam: Neither the originator(s) address(es) nor the Receipient(s) addresses are to be used for unsolicited commercial email (spam) as a per message fee is incurred for both inbound and outbound traffic Date: Fri, 28 May 1999 02:25:03 -0700 (PDT) From: Dirk-Willem van Gulik X-Sender: dirkx@vaio.ispra.webweaving.org To: Matthew Jacob Cc: Darryl Okahata , Karl Denninger , freebsd-scsi@FreeBSD.ORG Subject: Re: OnStream SCSI drives In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 27 May 1999, Matthew Jacob wrote: > > That would be helpful. What I'm also concerned about is media interchange > > with non-FreeBSD systems... Was it you who said you have a wad of NT > > workstations with these drives now? Making sure that the media can > > exchanged between systems is of crucial importance. > > (answering myself, "No, it was Dirk-Willem....") The hospital people who contacted my have both NT and W95 machines. I have two tapes written on an NT machine for testing; of which I also have an exact copy (like a 'dd') on cdrom. Plus I have an NT machine here should the need arrise. But sofar I only got the first 30k bytes off.. and now I understand why. Dw. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 28 3:35:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from gatekeeper.tsc.tdk.com (gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (Postfix) with ESMTP id 04F4314C8B for ; Fri, 28 May 1999 03:35:17 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.8/8.8.8) with ESMTP id DAA26508; Fri, 28 May 1999 03:34:50 -0700 (PDT) (envelope-from gdonl@tsc.tdk.com) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id DAA04669; Fri, 28 May 1999 03:34:48 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id DAA13244; Fri, 28 May 1999 03:34:41 -0700 (PDT) From: Don Lewis Message-Id: <199905281034.DAA13244@salsa.gv.tsc.tdk.com> Date: Fri, 28 May 1999 03:34:40 -0700 In-Reply-To: Bruce Evans "Re: FW: -STABLE scsi problem (bug?)" (May 28, 2:17am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Bruce Evans , gibbs@plutotech.com Subject: Re: FW: -STABLE scsi problem (bug?) Cc: mauri@aripaev.ee, scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On May 28, 2:17am, Bruce Evans wrote: } Subject: Re: FW: -STABLE scsi problem (bug?) } >>vfs doesn't really know which filesystems have been synced properly, } >>and doesn't call unmount() for any filesystem unless all buffers were } >>synced. The clean bit is set by unmount() so it is left unset for } >>all rw-mounted filesystems if the sync failed. } } >Can't we just walk the buffer list, note the FSes the buffers reference, } >and unmount any FSes that aren't referenced? } } We could, but syncing can only fail if there is an unexpected problem, so } we should be conservative if we don't understand the problem. I think this is overly conservative. The unwritten buffers could be destined for a dead NFS server, and we could be rebooting to clear the stuck mount point. It could be a definite inconvenience if this forces a bunch of huge local filesystems to be fsck'ed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 28 3:57: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id B123E15AB6 for ; Fri, 28 May 1999 03:56:32 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id MAA10590; Fri, 28 May 1999 12:02:00 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id JAA09913; Fri, 28 May 1999 09:04:10 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199905280704.JAA09913@yedi.iaf.nl> Subject: Re: proper mode page values? In-Reply-To: <199905280312.VAA23315@panzer.plutotech.com> from "Kenneth D. Merry" at "May 27, 1999 9:12: 3 pm" To: ken@plutotech.com (Kenneth D. Merry) Date: Fri, 28 May 1999 09:04:10 +0200 (CEST) Cc: dkelly@hiwaay.net, 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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Kenneth D. Merry wrote ... > David Kelly wrote... > > "Kenneth D. Merry" writes: > > > > swap_pager: indefinite wait buffer: device: 0x30401, blkno: 264, size: 4096 > > > > > > > > The problem blocks are always 264, 272, and 496. > > > > > > You should also be getting some SCSI error message printed on the console. [...] > > > > nospam: [1037] camcontrol defects -n da -u 0 -f block -P > > > > error reading defect list: Input/output error > > > > > > You need to use the -v switch on the command line to see why the command is > > > failing. > > > > Fair enough. Doesn't look like -v adds much information: > > > > nospam: [1045] camcontrol defects -v -n da -u 0 -f block -G > > error reading defect list: Input/output error > > CAM status is 0 > > nospam: [1046] camcontrol defects -n da -u 0 -f block -G > > error reading defect list: Input/output error > > nospam: [1047] id > > uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff), 31(guest) > > nospam: [1048] > > > > Ah! Forgot to check /var/log/messages. This is the output for a single > > attempt at "camcontrol defects", the one listed above: > > > > May 27 19:12:22 nospam /kernel: (pass2:ncr0:0:0:0): extraneous data discarded. > > May 27 19:12:22 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 80) @0xc0abbe00. > > May 27 19:12:22 nospam /kernel: (pass2:ncr0:0:0:0): extraneous data discarded. > > May 27 19:12:22 nospam /kernel: (pass2:ncr0:0:0:0): COMMAND FAILED (9 80) @0xc0abbe00. > > Hmm, that helps a little, but not much. I don't know how to decipher the > NCR driver error messages. > > If someone knows what those NCR messages mean, it might shed some light on > things. You could also try hooking the disks up to an Adaptec controller. > (at least I generally understand the errors the Adaptec driver spits out, > or can ask Justin what they mean) FWIW I get errors close to the ones you see when trying to do a 'camcontrol defects': May 28 10:02:21 p100 /kernel: (pass2:ncr1:0:0:0): extraneous data discarded. May 28 10:02:21 p100 /kernel: (pass2:ncr1:0:0:0): extraneous data discarded. May 28 10:02:21 p100 /kernel: (pass2:ncr1:0:0:0): COMMAND FAILED (9 0) @0xc080fa00. May 28 10:02:21 p100 /kernel: (pass2:ncr1:0:0:0): COMMAND FAILED (9 0) @0xc080fa00. error reading defect list: Input/output error p100#May 28 10:02:23 p100 /kernel: (pass2:ncr1:0:0:0): extraneous data discarded. May 28 10:02:23 p100 /kernel: (pass2:ncr1:0:0:0): extraneous data discarded. May 28 10:02:23 p100 /kernel: (pass2:ncr1:0:0:0): COMMAND FAILED (9 0) @0xc080fa00. May 28 10:02:23 p100 /kernel: (pass2:ncr1:0:0:0): COMMAND FAILED (9 0) @0xc080fa00. p100#uname -a FreeBSD p100.iaf.nl 4.0-CURRENT FreeBSD 4.0-CURRENT #4: Wed May 26 23:14:09 CEST 1999 root@p100.iaf.nl:/usr/src/sys/compile/P100 i386 | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 28 4:36:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (Postfix) with ESMTP id 80ACF14BEF for ; Fri, 28 May 1999 04:36:15 -0700 (PDT) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id VAA29921; Fri, 28 May 1999 21:35:51 +1000 Date: Fri, 28 May 1999 21:35:51 +1000 From: Bruce Evans Message-Id: <199905281135.VAA29921@godzilla.zeta.org.au> To: bde@zeta.org.au, Don.Lewis@tsc.tdk.com, gibbs@plutotech.com Subject: Re: FW: -STABLE scsi problem (bug?) Cc: mauri@aripaev.ee, scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >} >Can't we just walk the buffer list, note the FSes the buffers reference, >} >and unmount any FSes that aren't referenced? >} >} We could, but syncing can only fail if there is an unexpected problem, so >} we should be conservative if we don't understand the problem. > >I think this is overly conservative. The unwritten buffers could be >destined for a dead NFS server, and we could be rebooting to clear the >stuck mount point. It could be a definite inconvenience if this forces >a bunch of huge local filesystems to be fsck'ed. The nfs case is understood. Special handling for it was added in rev.1.42 of kern_shutown.c. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat May 29 15: 4:17 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (Postfix) with ESMTP id 2C9C114C31 for ; Sat, 29 May 1999 15:04:15 -0700 (PDT) (envelope-from randy@psg.com) Received: from localhost (425 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Sat, 29 May 1999 15:04:15 -0700 (PDT) (Smail-3.2.0.101 1997-Dec-17 #1 built 1999-Apr-1) Message-Id: Date: Sat, 29 May 1999 15:04:15 -0700 (PDT) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-scsi@freebsd.org Subject: cd writer Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am quite happy with my teac 532S, using filesystems, tosha, xmcd, ... But now I need to write filesystems. Any particularly nice reader/writer SCSI drives I should consider? randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 31 16:16:17 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (Postfix) with ESMTP id CF2F114BF1 for ; Mon, 31 May 1999 16:16:15 -0700 (PDT) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id TAA21520; Mon, 31 May 1999 19:16:11 -0400 (EDT) Message-ID: <19990531191610.A21185@netmonger.net> Date: Mon, 31 May 1999 19:16:10 -0400 From: Christopher Masto To: mjacob@feral.com Cc: freebsd-scsi@freebsd.org Subject: Re: OnStream SCSI drives Mail-Followup-To: mjacob@feral.com, freebsd-scsi@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Matthew Jacob on Thu, May 27, 1999 at 10:11:18AM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, May 27, 1999 at 10:11:18AM -0700, Matthew Jacob wrote: > > I got the documentation for this device and got a drive unit, and took a > quick look at this today (I have to be gone until next tuesday- my flight > leaves in a couple of hours). [...] > I'll ask Onstream if they mind the information going out so if others have > more aggressive schedules they can try to implement this sooner if they > lke, but you'd better coordinate with me on this. I would be very interested in that. The IDE model has been sitting in my computer for a couple of months now. Since the ATAPI and SCSI tape commands are the same, I would think that they have the same quirks (probably identical firmware behind the bus-specific interface). Hopefully when you get back they'll have said yes. -- Christopher Masto Senior Network Monkey NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net Free yourself, free your machine, free the daemon -- http://www.freebsd.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 1 0:39:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns1.portal2.com (ns1.portal2.com [203.85.226.193]) by hub.freebsd.org (Postfix) with SMTP id 4C9DD1523E for ; Tue, 1 Jun 1999 00:39:22 -0700 (PDT) (envelope-from yusufg@outblaze.com) Received: (qmail 16655 invoked from network); 1 Jun 1999 07:58:35 -0000 Received: from yusufg.portal2.com (203.85.226.249) by ns1.portal2.com with SMTP; 1 Jun 1999 07:58:35 -0000 Received: (qmail 15515 invoked by uid 500); 1 Jun 1999 07:39:16 -0000 Date: 1 Jun 1999 07:39:16 -0000 Message-ID: <19990601073916.15514.qmail@yusufg.portal2.com> From: Yusuf Goolamabbas To: freebsd-scsi@freebsd.org Subject: Data parity error detected during address or write data phase Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am installing FreeBSD 3.2-RELEASE on a Tekram P6B40D-A5 440 BX Dual PIII/500/512MB server with an Adaptec 2940U2W card with two disks. One 9 GB ST 39102LW and one 18GB ST 318275LW. Whilst installing the OS, I get the following error shown on the console ahc0: Data parity error detected during address or write data phase I changed the controller card as well as the cable and I still get the same error. I also see the following error before the system locks-up completely (da0:ahc0:0:0:) SCB 0xc - timed out while idle, LASTPHASE === 0x1 , SEQADDR == 0xa (da0:ahc0:0:0:) SCB 12 - Immediate reset, Flags = 0x4040 (da0:ahc0:0:0:) no longer in timeout - status = 34b Thanks in advance for all those who may be able to help -- Yusuf Goolamabbas yusufg@outblaze.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 1 1:52:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from firewall1.lehman.com (firewall.Lehman.COM [192.147.65.66]) by hub.freebsd.org (Postfix) with ESMTP id E89A3150E1 for ; Tue, 1 Jun 1999 01:52:41 -0700 (PDT) (envelope-from nclayton@lehman.com) Received: from relay.messaging-svcs2.lehman.com by firewall1.lehman.com (8.8.6/8.8.6) id EAA02015; Tue, 1 Jun 1999 04:52:40 -0400 (EDT) Received: from lonmailhost.lehman.com by relay.messaging-svcs2.lehman.com (8.9.3/8.8.5) id EAA25779; Tue, 1 Jun 1999 04:52:09 -0400 (EDT) Received: by lonmailhost.lehman.com (SMI-8.6/Lehman Bros. V1.5) id JAA00556; Tue, 1 Jun 1999 09:52:08 +0100 Message-ID: <19990601095207.S22307@lehman.com> Date: Tue, 1 Jun 1999 09:52:07 +0100 From: nclayton@lehman.com To: scsi@freebsd.org Subject: Tapes written on 2.2.8 not readable on 3.2 (was Re: PR docs/6681) References: <19990531090735.Q22307@lehman.com> <199905312210.WAA04171@jhs.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199905312210.WAA04171@jhs.muc.de>; from Julian Stacey on Tue, Jun 01, 1999 at 12:10:22AM +0200 Organization: Lehman Brothers Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi folks, I'm not on the SCSI list myself, I'm forwarding this on behalf of Julian Stacey. I've been closing doc PRs, including docs/6681, and contacted Julian to see if his PR was still relevant. In what follows, "> >" is my message to Julian, ">" is his reply. If any of you SCSI gurus has the time could you take a look at this? Cheers, N On Tue, Jun 01, 1999 at 12:10:22AM +0200, Julian Stacey wrote: > > It's this (from the PR); > > > > I suggest you append some of this info: > > > > (ncr0:5:0): "DEC TLZ06 (C)DEC 0389" type 1 removable SCSI 2 > > st0(ncr0:5:0): Sequential-Access > > st0(ncr0:5:0): 5.0 MB/s (200 ns, offset 8) > > density code 0x0, drive empty > > > > DAT drive, does 2 Gig with 90M tape, or more with compression on. > > SIngle slot height. > > Works on 2.2.8 > > > (ncr0:6:0): "TANDBERG TDC 3800 =04Y" type 1 removable SCSI 2 > > st1(ncr0:6:0): Sequential-Access > > st1(ncr0:6:0): asynchronous. > > density code 0x0, drive empty > > > > A 525 M QIC drive, > > reads 45 & 60M & 150M & 525M, > > writes 150 & 525, > > does variable block sizing by default > > (mt blocksize 512 to suppress that). > > Single slot height. > > Works on 2.2.8 > 3.2-RELEASE Seems to move the drive, but couldn't read tapes written > on 2.2.8 > > > (aha0:3:0): " " type 1 removable SCSI 1 > > st0(aha0:3:0): Sequential-Access density code 0x5, drive empty > > > > A Cipher QIC-24 SCSI, does 60 Meg > > Has a twist lever like a 5" floppy, & a pull out drawer. > > Double height ie 2 slots. > > Works on 2.2.8 > > > I know that the switch to CAM broke some stuff, but I'm not sure how > > extensive the breakage is -- if these aren't affected, and work with > > -stable/-current then I'll update the Handbook. > > I have 2 TANDBERG TDC 3800 drives, one on > > 3.2-RELEASE > sa0: Removable Sequential Access SCSI-2 device > sa0: 4.032MB/s transfers (4.032MHz, offset 7) > > one on > > 2.2.8-RELEASE > (ncr0:6:0): "TANDBERG TDC 3800 =04Y" type 1 removable SCSI 2 > st1(ncr0:6:0): Sequential-Access > st1(ncr0:6:0): asynchronous. > density code 0x0, drive empty > > Seems to me on brief experiment, > 3.2 can write data that 2.2.8 can read, > but 2.2.8 tapes are not readable on 3.2 system > (a disaster for anyone relying on backup tapes (not me thankfully)). > > Anyway, that was just a quick check, > maybe it's to do with the blocksize 512 stuff, > but looks like this is a problem. > > As I have 2 drives, 1 on 2.2.8 & 1 on 3.2, I may be uniquely useful > for test purposes for scsi team, feel free to pass my name along. > I am not worried about installing current on the 3.2 Tandberg box, > except that can't spare too much time for it. > I am not prepared to destabilise my other main 2.2.8 Tandberg box though :-) > > In light of this nasty suprise I have cancelled plan to upgrade my 2.2.8 > main system (that has the DEC TLZ06 DAT) until this problem is solved. > Once it's solved for Tandberg, I can try. > > The system with the Cipher QIC-24 will be upgraded to 3.2 in about 2 weeks. > & I can let you know about that. > > What was intended as a docu. upgrade has become a warning of peril :-) > Thanks, I'm glad to know, let me know if I can help, > feel free to cut/paste forward to scsi@ (not on that list myself). -- --+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+-- --+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+-- --+==[ Year 2000 Testing: It's about time. . . ]==+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 1 10: 2: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id C9EC414DCC for ; Tue, 1 Jun 1999 10:01:47 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id KAA03091; Tue, 1 Jun 1999 10:51:23 -0600 (MDT) Date: Tue, 1 Jun 1999 10:51:23 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199906011651.KAA03091@narnia.plutotech.com> To: Yusuf Goolamabbas Cc: scsi@FreeBSD.org Subject: Re: Data parity error detected during address or write data phase X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <19990601073916.15514.qmail@yusufg.portal2.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <19990601073916.15514.qmail@yusufg.portal2.com> you wrote: > Hi, I am installing FreeBSD 3.2-RELEASE on a Tekram P6B40D-A5 440 BX > Dual PIII/500/512MB server with an Adaptec 2940U2W card with two > disks. One 9 GB ST 39102LW and one 18GB ST 318275LW. > > Whilst installing the OS, I get the following error > shown on the console > > ahc0: Data parity error detected during address or write data phase There is no such message in the driver. It must be one of the following: (da0:ahc0:0:0:) parity error during Data-Out phase. (da0:ahc0:0:0:) parity error during Data-In phase. (da0:ahc0:0:0:) parity error during Command phase. (da0:ahc0:0:0:) parity error during Message-Out phase. (da0:ahc0:0:0:) parity error during Status phase. (da0:ahc0:0:0:) parity error during Message-In phase. (da0:ahc0:0:0:) parity error during unknown phase. > I changed the controller card as well as the cable and I still get the > same error. > > I also see the following error before the system locks-up completely > > (da0:ahc0:0:0:) SCB 0xc - timed out while idle, LASTPHASE === 0x1 , > SEQADDR == 0xa > (da0:ahc0:0:0:) SCB 12 - Immediate reset, Flags = 0x4040 > (da0:ahc0:0:0:) no longer in timeout - status = 34b Perhaps you have a bent pin on the drive? I've never seent the aic7xxx chips lie about parity errors. It could also be something like a cold solder joint on the 2940U2W. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 1 11:15:50 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from zed.ludd.luth.se (zed.ludd.luth.se [130.240.16.33]) by hub.freebsd.org (Postfix) with ESMTP id 3222B15766 for ; Tue, 1 Jun 1999 11:15:46 -0700 (PDT) (envelope-from pantzer@speedy.ludd.luth.se) Received: from speedy.ludd.luth.se (pantzer@speedy.ludd.luth.se [130.240.16.164]) by zed.ludd.luth.se (8.8.5/8.8.5) with ESMTP id UAA17610; Tue, 1 Jun 1999 20:15:23 +0200 Message-Id: <199906011815.UAA17610@zed.ludd.luth.se> X-Mailer: exmh version 2.0.1 12/23/97 To: "Justin T. Gibbs" Cc: Yusuf Goolamabbas , scsi@FreeBSD.ORG Subject: Re: Data parity error detected during address or write data phase In-Reply-To: Message from "Justin T. Gibbs" of "Tue, 01 Jun 1999 10:51:23 MDT." <199906011651.KAA03091@narnia.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Jun 1999 20:15:22 +0200 From: Mattias Pantzare Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > In article <19990601073916.15514.qmail@yusufg.portal2.com> you wrote: > > Hi, I am installing FreeBSD 3.2-RELEASE on a Tekram P6B40D-A5 440 BX > > Dual PIII/500/512MB server with an Adaptec 2940U2W card with two > > disks. One 9 GB ST 39102LW and one 18GB ST 318275LW. > > > > Whilst installing the OS, I get the following error > > shown on the console > > > > ahc0: Data parity error detected during address or write data phase > > There is no such message in the driver. It must be one of the > following: If you look in ahc_pci_intr() in pci/ahc_pci.c you will find it. It's a two liner... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 1 11:22:37 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 13B5714CAA for ; Tue, 1 Jun 1999 11:22:24 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id MAA87571; Tue, 1 Jun 1999 12:22:16 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <199906011822.MAA87571@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mattias Pantzare Cc: "Justin T. Gibbs" , Yusuf Goolamabbas , scsi@FreeBSD.ORG Subject: Re: Data parity error detected during address or write data phase In-reply-to: Your message of "Tue, 01 Jun 1999 20:15:22 +0200." <199906011815.UAA17610@zed.ludd.luth.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 01 Jun 1999 12:12:02 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >If you look in ahc_pci_intr() in pci/ahc_pci.c you will find it. It's a two >liner... Oh. A PCI parity error. Try re-seating your card or cleaning the connector pins. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 1 22:32:45 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 00F4F14E49 for ; Tue, 1 Jun 1999 22:32:43 -0700 (PDT) (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 BAA17465; Wed, 2 Jun 1999 01:32:40 -0400 (EDT) Date: Wed, 2 Jun 1999 01:32:40 -0400 (EDT) From: spork X-Sender: spork@super-g.inch.com To: Randy Bush Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: cd writer In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I find the Panasonic 7502-B gives nice performance at a low cost. I found one on pricewatch for $180 and it works great. We have two at work that get regular use under FBSD and have yet to have a problem... Charles --- Charles Sprickman spork@super-g.com On Sat, 29 May 1999, Randy Bush wrote: > I am quite happy with my teac 532S, using filesystems, tosha, xmcd, ... But > now I need to write filesystems. Any particularly nice reader/writer SCSI > drives I should consider? > > randy > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Jun 1 23:21: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id B0D6115233 for ; Tue, 1 Jun 1999 23:20:55 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id IAA10455; Wed, 2 Jun 1999 08:20:50 +0200 (CEST) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.3/8.9.1) id IAA56145; Wed, 2 Jun 1999 08:05:07 +0200 (MET DST) (envelope-from j) Message-ID: <19990602080506.38306@uriah.heep.sax.de> Date: Wed, 2 Jun 1999 08:05:06 +0200 From: J Wunsch To: nclayton@lehman.com Cc: scsi@FreeBSD.ORG Subject: Re: Tapes written on 2.2.8 not readable on 3.2 (was Re: PR docs/6681) Reply-To: Joerg Wunsch References: <19990531090735.Q22307@lehman.com> <199905312210.WAA04171@jhs.muc.de> <19990601095207.S22307@lehman.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19990601095207.S22307@lehman.com>; from nclayton@lehman.com on Tue, Jun 01, 1999 at 09:52:07AM +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 nclayton@lehman.com wrote: > > Seems to me on brief experiment, > > 3.2 can write data that 2.2.8 can read, > > but 2.2.8 tapes are not readable on 3.2 system > > (a disaster for anyone relying on backup tapes (not me thankfully)). I think that's the well-known problem (*) that the defaults of 3.x and -current differ for some tape drives, for whatever reason. In particular, the current driver doesn't trust the user ;-) to default to variable mode for QIC > 150, as the pre-CAM tape driver did. Thus, tapes written in variable mode previously aren't readable by default. However, the world is not that bad, the old tapes are readable without problems if you use `mt blocksize variable' before reading them. At least, i haven't seen a tape so far i could not read that had been written with the old system. (*) Examining the archive of this list for the subject `tape' should reveal you a number of threads discussing it. -- 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 Wed Jun 2 15: 2:12 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from quark.ChrisBowman.com (crbowman.erols.com [209.122.47.155]) by hub.freebsd.org (Postfix) with ESMTP id D00B714BEF for ; Wed, 2 Jun 1999 15:01:49 -0700 (PDT) (envelope-from crb@ChrisBowman.com) Received: from fermion (crb@fermion.ChrisBowman.com [10.0.1.2]) by quark.ChrisBowman.com (8.9.2/8.8.8) with SMTP id SAA32326; Wed, 2 Jun 1999 18:00:49 -0400 (EDT) (envelope-from crb@ChrisBowman.com) Message-Id: <199906022200.SAA32326@quark.ChrisBowman.com> X-Sender: crb@quark X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Wed, 02 Jun 1999 17:59:25 -0400 To: "Justin T. Gibbs" From: "Christopher R. Bowman" Subject: Re: Support for Symbios vs. Adaptect SCSI Cc: freebsd-scsi@freebsd.org In-Reply-To: <199905271916.NAA57184@pluto.plutotech.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 01:05 PM 5/27/99 -0600, Justin T. Gibbs wrote: >>>My plan is to write an assembler for the Symbios scripts >>>engine so that the firmware is easier to read, modify, and understand. >>>At that point, I would expect the Symbios parts to be as well >>>supported under FreeBSD as the Adaptec parts. I don't expect to >>>get around to this until late this summer. >> >>There already exists the SCRIPTS assembler that produces C code structures >>containing the data as preinitialized arrays. I thought I even saw the source >>to it floating around somewhere. Are you looking to write a better assembler >>or just oblivious of the existing one? > >It is the general policy of the project to provide all the tools required >to modify a driver in the standard distribution. The aic7xxx driver, for >instance, provides the assembler that I wrote for its RISC engine. If >the source is available for NASM (I've only seen the DOS executables) >and it allows for things like chip specific program patching at device >attach time, then that would certainly work. > >>I have, in the past, written an assembler for a custom CPU for which I did the >>mask layout and design, and I have been looking for a way to contribute to the >>project (I am a hardware guy with a lot of software under my belt, but I just >>can't seem to wrap my head around the kernel). Perhaps you could describe >>what exactly you are looking for in an assembler and I could work on it for >>you. > >The scripts syntax is somewhat obtuse, but I guess it would suffice. The >main additional feature I'd want in the assembler is the ability to >easily designate condition portions of the script that can be independently >patched in. Take a look at the sys/dev/aic7xxx/aic7xxx.seq and the output >from aicasm in sys/compile/KERNAME/aic7xxx_seq.h for an idea of the >patching capability I'd want. Ok I read through some of it, but I don't get how the symbols are relocated. I mean I see how the sequencer script is assembled by your assembler, and I think I understand how you have implemented what amounts to a run time dropping of certain instruction from being downloaded to the chip using conditional statements executed at download time. What I don't understand is how are the assembly labels fixed up when instructions are dropped from being download to the chip due to this conditional situation. -------- Christopher R. Bowman crb@ChrisBowman.com http://www.ChrisBowman.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jun 2 15:10:41 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id 1571214CAA for ; Wed, 2 Jun 1999 15:10:35 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id QAA32101; Wed, 2 Jun 1999 16:10:32 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <199906022210.QAA32101@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Christopher R. Bowman" Cc: "Justin T. Gibbs" , freebsd-scsi@freebsd.org Subject: Re: Support for Symbios vs. Adaptect SCSI In-reply-to: Your message of "Wed, 02 Jun 1999 17:59:25 EDT." <199906022200.SAA32326@quark.ChrisBowman.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Jun 1999 16:00:19 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>The scripts syntax is somewhat obtuse, but I guess it would suffice. The >>main additional feature I'd want in the assembler is the ability to >>easily designate condition portions of the script that can be independently >>patched in. Take a look at the sys/dev/aic7xxx/aic7xxx.seq and the output >>from aicasm in sys/compile/KERNAME/aic7xxx_seq.h for an idea of the >>patching capability I'd want. > >Ok I read through some of it, but I don't get how the symbols are relocated. > >I mean I see how the sequencer script is assembled by your assembler, and I >think I understand how you have implemented what amounts to a run time >dropping of certain instruction from being downloaded to the chip using >conditional statements executed at download time. What I don't understand >is how are the assembly labels fixed up when instructions are dropped from >being download to the chip due to this conditional situation. Each instruction that references an address has that address re-calculated at download time to take into consideration the instructions that are not going to be included in the runtime load. So, a jump instruction starts out with an address relative to all instructions assembled. When the instruction is downloaded, we subtract the number of instructions discarded 'before it' from the original address. Take a look at ahc_download_instr() for details. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jun 2 15:40:38 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id A900214DBA for ; Wed, 2 Jun 1999 15:40:32 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA26677 for freebsd-scsi@freebsd.org; Wed, 2 Jun 1999 23:41:12 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA03811 for freebsd-scsi@freebsd.org; Wed, 2 Jun 1999 23:39:36 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199906022139.XAA03811@yedi.iaf.nl> Subject: Fibrechannel To: freebsd-scsi@freebsd.org (FreeBSD SCSI hackers) Date: Wed, 2 Jun 1999 23:39:36 +0200 (CEST) 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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there any work in progress around Fibrechannel? | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Jun 2 15:48: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 7775C14E5B for ; Wed, 2 Jun 1999 15:48:04 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id PAA11753; Wed, 2 Jun 1999 15:47:49 -0700 Date: Wed, 2 Jun 1999 15:45:38 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: FreeBSD SCSI hackers Subject: Re: Fibrechannel In-Reply-To: <199906022139.XAA03811@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What do you mean? There is a private loop fibre channel driver already integrated (Qlogic). I've been working on Fabric support ("any day now"). What were you looking for specifically? On Wed, 2 Jun 1999, Wilko Bulte wrote: > Is there any work in progress around Fibrechannel? > > | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - > |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org > > > 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 Jun 3 11:43: 5 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id DEA4C15571 for ; Thu, 3 Jun 1999 11:42:56 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id TAA20517; Thu, 3 Jun 1999 19:52:11 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id TAA00910; Thu, 3 Jun 1999 19:50:49 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199906031750.TAA00910@yedi.iaf.nl> Subject: Re: Fibrechannel In-Reply-To: from Matthew Jacob at "Jun 2, 1999 3:45:38 pm" To: mjacob@feral.com Date: Thu, 3 Jun 1999 19:50:49 +0200 (CEST) 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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Matthew Jacob wrote ... > What do you mean? Well, I borrowed an Emulex LP6000 from my employer. I hope to also borrow a couple of FC disks to hook up to it. I know there is no LP6000 driver around in FreeBSD so I'm sort of considering to try to write one. A FC-AL driver that is. > There is a private loop fibre channel driver already integrated (Qlogic). > I've been working on Fabric support ("any day now"). Well, fabrics are a bit on the expensive side. I could probably test it at work but that is quite awkward. I don't have any Qlogic FC cards so I can't really help you testing the fabric functionality. > What were you looking for specifically? For a start: does anyone have a (soft) copy of the Emulex programming interface manual for me? > On Wed, 2 Jun 1999, Wilko Bulte wrote: > > > Is there any work in progress around Fibrechannel? | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 3 11:57:46 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id E717E1544F for ; Thu, 3 Jun 1999 11:57:44 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id LAA14116; Thu, 3 Jun 1999 11:57:41 -0700 Date: Thu, 3 Jun 1999 11:55:20 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Fibrechannel In-Reply-To: <199906031750.TAA00910@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > As Matthew Jacob wrote ... > > > What do you mean? > > Well, I borrowed an Emulex LP6000 from my employer. I hope to also borrow a > couple of FC disks to hook up to it. I know there is no LP6000 driver > around in FreeBSD so I'm sort of considering to try to write one. A > FC-AL driver that is. Ah. Well, let's try and architect one so that IP && SCSI are just one of a set of ULPs on top of this. The Qlogic architecture is a bit more automatic transmission-like.... > > There is a private loop fibre channel driver already integrated (Qlogic). > > I've been working on Fabric support ("any day now"). > > Well, fabrics are a bit on the expensive side. I could probably test it > at work but that is quite awkward. I don't have any Qlogic FC cards so > I can't really help you testing the fabric functionality. Okay. > > > What were you looking for specifically? > > For a start: does anyone have a (soft) copy of the Emulex programming > interface manual for me? Not I. Sorry. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 3 14:42:48 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id D489E15A0F for ; Thu, 3 Jun 1999 14:42:45 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id WAA29451; Thu, 3 Jun 1999 22:42:06 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id VAA02758; Thu, 3 Jun 1999 21:30:32 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199906031930.VAA02758@yedi.iaf.nl> Subject: Re: Fibrechannel In-Reply-To: from Matthew Jacob at "Jun 3, 1999 11:55:20 am" To: mjacob@feral.com Date: Thu, 3 Jun 1999 21:30:32 +0200 (CEST) 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+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Matthew Jacob wrote ... > > As Matthew Jacob wrote ... > > > > > What do you mean? > > > > Well, I borrowed an Emulex LP6000 from my employer. I hope to also borrow a > > couple of FC disks to hook up to it. I know there is no LP6000 driver > > around in FreeBSD so I'm sort of considering to try to write one. A > > FC-AL driver that is. > > Ah. Well, let's try and architect one so that IP && SCSI are just one of a > set of ULPs on top of this. The Qlogic architecture is a bit more > automatic transmission-like.... The approach you mention is what the FC standards advocate, I think it is a good thing to layer it. Some other things that need thought, esp. on fabrics: how to 'wire down' a FC device. I think something like: disk da0 at fcloop 0 wwn=<64bitnumber> disk da1 at fabric 1 wwn=<64bitnumber> Maybe one could even omit the fcloop 0 stuff, as the wwn should be sufficient, being worldwide unique etc. These are currently some first random thoughts.. > > Well, fabrics are a bit on the expensive side. I could probably test it > > at work but that is quite awkward. I don't have any Qlogic FC cards so > > I can't really help you testing the fabric functionality. > > Okay. What is the part# for the Qlogic FC adapter anyway? One never knows... > > > What were you looking for specifically? > > > > For a start: does anyone have a (soft) copy of the Emulex programming > > interface manual for me? > > Not I. Sorry. I'll try to hunt it down. | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 3 14:57: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 96A6C158C6 for ; Thu, 3 Jun 1999 14:56:58 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA14734; Thu, 3 Jun 1999 14:56:55 -0700 Date: Thu, 3 Jun 1999 14:54:32 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Wilko Bulte Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Fibrechannel In-Reply-To: <199906031930.VAA02758@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Ah. Well, let's try and architect one so that IP && SCSI are just one of a (as Julian pointed out to me: "design" would have been a better verb) > > set of ULPs on top of this. The Qlogic architecture is a bit more > > automatic transmission-like.... > > The approach you mention is what the FC standards advocate, I think it is a > good thing to layer it. > > Some other things that need thought, esp. on fabrics: how to 'wire down' > a FC device. > > I think something like: > > disk da0 at fcloop 0 wwn=<64bitnumber> > disk da1 at fabric 1 wwn=<64bitnumber> > > Maybe one could even omit the fcloop 0 stuff, as the wwn should be > sufficient, being worldwide unique etc. > > These are currently some first random thoughts.. Yes- this indeed is a problem- if you believe wiring down is important. Distinguising between loop and fabric is not likely to be a good thing- but association with a WWN is a good thing- although I'd really like to see this done in DEVFS, where we could also assign unique numbers to non-WWN based devices (parallel SCSI disks with VPD info that gives serial number...). > > > > Well, fabrics are a bit on the expensive side. I could probably test it > > > at work but that is quite awkward. I don't have any Qlogic FC cards so > > > I can't really help you testing the fabric functionality. > > > > Okay. > > What is the part# for the Qlogic FC adapter anyway? One never knows... The Qlogic 2100. The 2200 is out, but I haven't gotten one or a firmware spec for it yet. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jun 3 17:26:18 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 2F70014E7A for ; Thu, 3 Jun 1999 17:26:14 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id RAA15103; Thu, 3 Jun 1999 17:26:07 -0700 Date: Thu, 3 Jun 1999 17:23:42 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: nclayton@lehman.com Cc: scsi@FreeBSD.ORG Subject: Re: Tapes written on 2.2.8 not readable on 3.2 (was Re: PR docs/6681) In-Reply-To: <19990601095207.S22307@lehman.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've editted the PR to note this is a tape driver problem (if any). I'll need more info from Julian, but I'll contact him directly. On Tue, 1 Jun 1999 nclayton@lehman.com wrote: > Hi folks, > > I'm not on the SCSI list myself, I'm forwarding this on behalf of Julian > Stacey. > > I've been closing doc PRs, including docs/6681, and contacted Julian to see > if his PR was still relevant. > > In what follows, "> >" is my message to Julian, ">" is his reply. If any > of you SCSI gurus has the time could you take a look at this? > > Cheers, > > N > > On Tue, Jun 01, 1999 at 12:10:22AM +0200, Julian Stacey wrote: > > > It's this (from the PR); > > > > > > I suggest you append some of this info: > > > > > > (ncr0:5:0): "DEC TLZ06 (C)DEC 0389" type 1 removable SCSI 2 > > > st0(ncr0:5:0): Sequential-Access > > > st0(ncr0:5:0): 5.0 MB/s (200 ns, offset 8) > > > density code 0x0, drive empty > > > > > > DAT drive, does 2 Gig with 90M tape, or more with compression on. > > > SIngle slot height. > > > > Works on 2.2.8 > > > > > (ncr0:6:0): "TANDBERG TDC 3800 =04Y" type 1 removable SCSI 2 > > > st1(ncr0:6:0): Sequential-Access > > > st1(ncr0:6:0): asynchronous. > > > density code 0x0, drive empty > > > > > > A 525 M QIC drive, > > > reads 45 & 60M & 150M & 525M, > > > writes 150 & 525, > > > does variable block sizing by default > > > (mt blocksize 512 to suppress that). > > > Single slot height. > > > > Works on 2.2.8 > > 3.2-RELEASE Seems to move the drive, but couldn't read tapes written > > on 2.2.8 > > > > > (aha0:3:0): " " type 1 removable SCSI 1 > > > st0(aha0:3:0): Sequential-Access density code 0x5, drive empty > > > > > > A Cipher QIC-24 SCSI, does 60 Meg > > > Has a twist lever like a 5" floppy, & a pull out drawer. > > > Double height ie 2 slots. > > > > Works on 2.2.8 > > > > > I know that the switch to CAM broke some stuff, but I'm not sure how > > > extensive the breakage is -- if these aren't affected, and work with > > > -stable/-current then I'll update the Handbook. > > > > I have 2 TANDBERG TDC 3800 drives, one on > > > > 3.2-RELEASE > > sa0: Removable Sequential Access SCSI-2 device > > sa0: 4.032MB/s transfers (4.032MHz, offset 7) > > > > one on > > > > 2.2.8-RELEASE > > (ncr0:6:0): "TANDBERG TDC 3800 =04Y" type 1 removable SCSI 2 > > st1(ncr0:6:0): Sequential-Access > > st1(ncr0:6:0): asynchronous. > > density code 0x0, drive empty > > > > Seems to me on brief experiment, > > 3.2 can write data that 2.2.8 can read, > > but 2.2.8 tapes are not readable on 3.2 system > > (a disaster for anyone relying on backup tapes (not me thankfully)). > > > > Anyway, that was just a quick check, > > maybe it's to do with the blocksize 512 stuff, > > but looks like this is a problem. > > > > As I have 2 drives, 1 on 2.2.8 & 1 on 3.2, I may be uniquely useful > > for test purposes for scsi team, feel free to pass my name along. > > I am not worried about installing current on the 3.2 Tandberg box, > > except that can't spare too much time for it. > > I am not prepared to destabilise my other main 2.2.8 Tandberg box though :-) > > > > In light of this nasty suprise I have cancelled plan to upgrade my 2.2.8 > > main system (that has the DEC TLZ06 DAT) until this problem is solved. > > Once it's solved for Tandberg, I can try. > > > > The system with the Cipher QIC-24 will be upgraded to 3.2 in about 2 weeks. > > & I can let you know about that. > > > > What was intended as a docu. upgrade has become a warning of peril :-) > > Thanks, I'm glad to know, let me know if I can help, > > feel free to cut/paste forward to scsi@ (not on that list myself). > > -- > --+==[ Systems Administrator, Year 2000 Test Lab, Lehman Brothers, Inc. ]==+-- > --+==[ 1 Broadgate, London, EC2M 7HA 0171-601-0011 x5514 ]==+-- > --+==[ Year 2000 Testing: It's about time. . . ]==+-- > > > 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 Jun 4 0:25:53 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mailgate.cadence.com (mailgate.Cadence.COM [158.140.2.1]) by hub.freebsd.org (Postfix) with ESMTP id E027E14D36 for ; Fri, 4 Jun 1999 00:25:51 -0700 (PDT) (envelope-from ngr@cotswold.demon.co.uk) Received: (from smap@localhost) by mailgate.cadence.com (8.8.5/8.6.8) id AAA13717 for ; Fri, 4 Jun 1999 00:25:51 -0700 (PDT) Received: from mailhub2.Cadence.COM(158.140.128.8) by mailgate.cadence.com via smap (mjr-v1.2) id xma928481149.013713; Fri, 4 Jun 99 00:25:49 -0700 Received: from symnt3.Cadence.COM (symnt3 [194.32.101.100]) by mailhub.Cadence.COM (8.8.8/8.8.5) with ESMTP id AAA23122 for ; Fri, 4 Jun 1999 00:24:14 -0700 (PDT) Message-Id: <199906040724.AAA23122@mailhub.Cadence.COM> Received: from pc364-cam.cadence.com ([194.32.96.180]) by symnt3.Cadence.COM with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2232.9) id LJVM2L42; Fri, 4 Jun 1999 08:19:57 +0100 From: "Nigel Roles" To: freebsd-scsi@freebsd.org Date: Fri, 4 Jun 1999 08:18:27 +0100 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Assertion in ncr.c Reply-To: ngr@cotswold.demon.co.uk X-mailer: Pegasus Mail for Win32 (v3.11) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kernel: RELENG_3 as of yesterday (and all previous versions) Controller: Symbios 22910 (53c896 dual channel Ultra2 wide) Problem: Assertion at line 5000 (first assertion in ncr_setsync()) This assertion fires (4 times) as soon as the kernel attempts to access the disks just after the "waiting 15 seconds for disks to settle" message. No meaningful progress is made, and lots of ccb timeouts are announced. This assertion implies that the target that has connected is not the expected one (i.e. target id in ccb is not that in the chip register) If I make a straight exchange for an Adaptec 2940UW, everything is fine. One factor that may be significant is that I am using a wide to narrow (stright through connected, non Hi-9 terminated) converter _on the card_, before using a narrow cable to all devices, and active termination. The fact that the Adaptec 2940UW is happy suggests that this is not the problem. Why do I have a dual channel wide controller and no wide devices? Because I haven't bought a IBM Ultrastar 9LZW yet. I am much more familiar with the Symbios chips than FreeBSD, so would welcome suggestions as to likey causes, and/or ways to proceed. it took most of yesterday evening to figure out how to update to 3.2, and recompile it, so I could check that the problem had not been fixed. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message