From owner-freebsd-scsi Sun Nov 8 23:21:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA21349 for freebsd-scsi-outgoing; Sun, 8 Nov 1998 23:21:43 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from iclub.nsu.ru (iclub.nsu.ru [193.124.222.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA21343 for ; Sun, 8 Nov 1998 23:21:29 -0800 (PST) (envelope-from semen@iclub.nsu.ru) Received: from localhost (semen@localhost) by iclub.nsu.ru (8.8.8/8.8.5) with SMTP id NAA00603; Mon, 9 Nov 1998 13:25:10 +0600 (NS) Date: Mon, 9 Nov 1998 13:25:10 +0600 (NS) From: Ustimenko Semen To: Nick Wilhelm-Olsen cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SDT-7000 density woes In-Reply-To: <199811052249.RAA09611@terra.milkyway.stdio.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 Hello! There is many klugdes with this device :-( To make modes manual settable, you need to switch jumpers on bottom of the device. You can find the description at Sony's site: http://www.sony-cp.com/_E/Support/Download/Compatibility/unix.pdf But this may not help you :-> It works rather stable in it standard mode (0x13 at boot time, 0 is reported by mt status, this also depends on those jumpers). In my case it works well for some time after power on. Especially for small dumps < 100MB per day. But if you erase the tape and soon dump on it 4Gb (with compression), it fails... It dumps very slow (100Kb/s instead of 1111Mb/s) and very little. IMHO it overheats. After the drive began to work in the wrong way, you can try to power off, wait several minuts, power on procedure to make it back alive. Good luck. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 9 02:38:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA12007 for freebsd-scsi-outgoing; Mon, 9 Nov 1998 02:38:15 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA12000; Mon, 9 Nov 1998 02:38:12 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.1a/8.9.1) with ESMTP id LAA20918; Mon, 9 Nov 1998 11:37:54 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id LAA10161; Mon, 9 Nov 1998 11:37:54 +0100 (MET) Message-ID: <19981109113753.00487@follo.net> Date: Mon, 9 Nov 1998 11:37:53 +0100 From: Eivind Eklund To: Bagnara Stefano , freebsd-scsi@FreeBSD.ORG Subject: Re: Allways RAIDing... References: <007f01be0bc8$e81f9060$0f63b1c2@lust.datasail.it> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89.1i In-Reply-To: <007f01be0bc8$e81f9060$0f63b1c2@lust.datasail.it>; from Bagnara Stefano on Mon, Nov 09, 1998 at 11:08:29AM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Please post any followups to FreeBSD-scsi only (ie, do not re-introduce FreeBSD-fs). Thanks! On Mon, Nov 09, 1998 at 11:08:29AM +0100, Bagnara Stefano wrote: > I cannot find a SCSI card for RAID3. AAA-131-SA from Adaptec does RAID0/1/5 > ... in RAID5 needs a minimum of 3 disks... but... with 3 disks and RAID5 if > a disk fail the whole system die? or RAID5 can handle redundancy with only 3 > disks? RAID5 can handle redundancy with only three disks. > Any idea if FreeBSD support AAA-131-SA? it's not on the HW compatibility > list... but no RAID controllers are on it.... I have no idea what the AAA-131-SA even is, from a programmers standpoint. I don't think we support it. I'm running with a DPT controller, and am fairly happy with it (due to this being a really old board, they don't have and won't produce a workaround for a bug in my BIOS, but apart from that I've had absolutely no problems). I also believe these are faster than the Adaptecs. The FreeBSD driver is stable and actively maintained (to the degree it need maintenance - this hasn't really been that much). Eivind. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 9 17:07:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18103 for freebsd-scsi-outgoing; Mon, 9 Nov 1998 17:07:33 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18093 for ; Mon, 9 Nov 1998 17:07:27 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA15751; Tue, 10 Nov 1998 11:36:53 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA17828; Tue, 10 Nov 1998 11:36:49 +1030 (CST) Message-ID: <19981110113649.Q499@freebie.lemis.com> Date: Tue, 10 Nov 1998 11:36:49 +1030 From: Greg Lehey To: John Fieber Cc: John Hay , freebsd-scsi@FreeBSD.ORG Subject: Re: cam panic... probably tag related References: <19981106182907.B2331@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from John Fieber on Fri, Nov 06, 1998 at 10:08:36AM -0500 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Friday, 6 November 1998 at 10:08:36 -0500, John Fieber wrote: > On Fri, 6 Nov 1998, Greg Lehey wrote: > >>>>>> da1: Fixed Direct Access SCSI2 device >>>>> Mine is , on an ASUS SC200 (ncr) >>>> da1: Fixed Direct Access SCSI2 device >> >> Well, quite the contrary. I've had this disk in my machine since new >> (when's that? 3 years?), and I never had any trouble. Yesterday, >> after I built a new kernel, it started giving me trouble. No panics, >> just hangs from which it wouldn't recover with a bus reset. I rebuilt >> the kernel with the quirk entry suggested (sorry, forget who did it), >> and since then I haven't had any trouble. > > The plot thickens.... > > Exactly what (when?) was your old kernel and the new one with > problems? The two kernels were made freshly supped (less than 4 hours in each case): FreeBSD 3.0-RELEASE #114: Sat Oct 17 17:49:53 CST 1998 FreeBSD 3.0-CURRENT #114: Sat Oct 31 15:57:42 CST 1998 Note that CST is +0930 (first kernel) and +1030 (second kernel). Don't ask me why the number is the same for both of them. > I've been running a 3.0-CURRENT kernel as of about a week ago and am > having problems with daemons (inetd, sendmail, apache mostly) dying > right and left. This hasn't happened to me, even though I did crazy things like running Emacs against a 160 MB file, which caused a couple of swap overflows (no more! I added another 500 MB swap). > Oh, and I got the drive in question just in the last week two (it is > temporary acquisition; it goes away in another week or so). Ah. I've had mine in the machine since the BSDI days. 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 Mon Nov 9 17:40:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21785 for freebsd-scsi-outgoing; Mon, 9 Nov 1998 17:40:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21779 for ; Mon, 9 Nov 1998 17:40:16 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.7/8.7.3) id RAA23827; Mon, 9 Nov 1998 17:40:01 -0800 (PST) Date: Mon, 9 Nov 1998 17:40:01 -0800 (PST) Message-Id: <199811100140.RAA23827@vader.cs.berkeley.edu> To: scsi@FreeBSD.ORG Subject: turning off tagged queuing with CAM? From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Justin and Ken (and others :), Is it possible to turn off tagged queuing with the current version of CAM? There used to be an AHC_TAGENABLE variable but it seems to have gone away. I looked at the mode pages but couldn't find anything suspicious. Here's one of the systems: === Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #2: Wed Nov 4 04:13:25 PST 1998 asami2@m8.cs.berkeley.edu:/disks/stampede/sandbox1/freebsd/allsrc/current/src/sys/compile/TD Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 199432708 Hz CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x616 Stepping=6 Features=0xf9ff real memory = 100663296 (98304K bytes) avail memory = 95531008 (93292K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x00 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 vga0: rev 0x03 on pci0.11.0 fxp0: rev 0x02 int a irq 11 on pci0.15.0 fxp0: Ethernet address 00:a0:c9:72:86:45 chip2: rev 0x02 on pci0.17.0 chip3: rev 0x02 on pci0.19.0 Probing for devices on PCI bus 1: ahc0: rev 0x00 int a irq 10 on pci1.4.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 11 on pci1.5.0 ahc1: aic7880 Wide Channel B, SCSI Id=7, 16/255 SCBs Probing for devices on PCI bus 2: ahc2: rev 0x00 int a irq 11 on pci2.4.0 ahc2: aic7880 Wide Channel A, SCSI Id=6, 16/255 SCBs ahc3: rev 0x00 int a irq 11 on pci2.5.0 ahc3: aic7880 Wide Channel B, SCSI Id=6, 16/255 SCBs Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: CGA <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2015MB (4127760 sectors), 4095 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface ahc1: Someone reset channel A ccd0-7: Concatenated disk drivers Waiting 2 seconds for SCSI devices to settle changing root device to wd0s1a da8 at ahc0 bus 0 target 8 lun 0 da8: Fixed Direct Access SCSI2 device da8: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da8: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) da41 at ahc2 bus 0 target 9 lun 0 da41: Fixed Direct Access SCSI2 device da41: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da41: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) da46 at ahc2 bus 0 target 14 lun 0 da46: Fixed Direct Access SCSI2 device da46: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da46: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) da47 at ahc2 bus 0 target 15 lun 0 da47: Fixed Direct Access SCSI2 device da47: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da47: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI2 device da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) da43 at ahc2 bus 0 target 11 lun 0 da43: Fixed Direct Access SCSI2 device da43: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da43: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) da4 at ahc0 bus 0 target 4 lun 0 da4: Fixed Direct Access SCSI2 device da4: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da4: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) da40 at ahc2 bus 0 target 8 lun 0 da40: Fixed Direct Access SCSI2 device da40: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da40: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) da42 at ahc2 bus 0 target 10 lun 0 da42: Fixed Direct Access SCSI2 device da42: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da42: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI2 device da3: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) da45 at ahc2 bus 0 target 13 lun 0 da45: Fixed Direct Access SCSI2 device da45: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da45: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) da9 at ahc0 bus 0 target 9 lun 0 da9: Fixed Direct Access SCSI2 device da9: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da9: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) da44 at ahc2 bus 0 target 12 lun 0 da44: Fixed Direct Access SCSI2 device da44: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da44: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) da5 at ahc0 bus 0 target 5 lun 0 da5: Fixed Direct Access SCSI2 device da5: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da5: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) === Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 9 19:22:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA02582 for freebsd-scsi-outgoing; Mon, 9 Nov 1998 19:22:42 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA02575 for ; Mon, 9 Nov 1998 19:22:38 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id UAA06848; Mon, 9 Nov 1998 20:22:17 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811100322.UAA06848@panzer.plutotech.com> Subject: Re: turning off tagged queuing with CAM? In-Reply-To: <199811100140.RAA23827@vader.cs.berkeley.edu> from Satoshi Asami at "Nov 9, 98 05:40:01 pm" To: asami@cs.berkeley.edu (Satoshi Asami) Date: Mon, 9 Nov 1998 20:22:17 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Satoshi Asami wrote... > Hi Justin and Ken (and others :), > > Is it possible to turn off tagged queuing with the current version of > CAM? There used to be an AHC_TAGENABLE variable but it seems to have > gone away. I looked at the mode pages but couldn't find anything > suspicious. > > Here's one of the systems: [ ... ] You can do a couple of things: - put a quirk entry in cam_xpt.c and set the minimum and maximum tag counts to 0. (there are a couple of examples for that) - edit mode page 10 (0x0a) and set the DQue bit to 1. Either one of those will do what you want. I guess you must have a firmware problem that makes you want to disable tagged queueing? Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 9 21:31:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA12742 for freebsd-scsi-outgoing; Mon, 9 Nov 1998 21:31:02 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA12737 for ; Mon, 9 Nov 1998 21:31:01 -0800 (PST) (envelope-from asami@vader.cs.berkeley.edu) Received: from silvia.hip.berkeley.edu (sji-ca6-19.ix.netcom.com [205.186.213.19]) by vader.cs.berkeley.edu (8.8.7/8.7.3) with ESMTP id VAA24266; Mon, 9 Nov 1998 21:30:45 -0800 (PST) Received: (from asami@localhost) by silvia.hip.berkeley.edu (8.8.8/8.6.9) id VAA08453; Mon, 9 Nov 1998 21:30:42 -0800 (PST) Date: Mon, 9 Nov 1998 21:30:42 -0800 (PST) Message-Id: <199811100530.VAA08453@silvia.hip.berkeley.edu> To: ken@plutotech.com CC: scsi@FreeBSD.ORG, nisha@cs.berkeley.edu In-reply-to: <199811100322.UAA06848@panzer.plutotech.com> (ken@plutotech.com) Subject: Re: turning off tagged queuing with CAM? From: asami@FreeBSD.ORG (Satoshi Asami) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * From: "Kenneth D. Merry" * Satoshi Asami wrote... * > Hi Justin and Ken (and others :), * > * > Is it possible to turn off tagged queuing with the current version of * > CAM? There used to be an AHC_TAGENABLE variable but it seems to have * > gone away. I looked at the mode pages but couldn't find anything * > suspicious. * > * > Here's one of the systems: * [ ... ] * * You can do a couple of things: * * - put a quirk entry in cam_xpt.c and set the minimum and maximum tag * counts to 0. (there are a couple of examples for that) I see. * - edit mode page 10 (0x0a) and set the DQue bit to 1. Mode page 10! Didn't know there were that many. I got an error at page 5 and 6 and thought that was it. ;) * Either one of those will do what you want. * * I guess you must have a firmware problem that makes you want to disable * tagged queueing? Actually no, we just want to see how much effect it has on performance. Being able to turning it off on a per-disk basis would be very nice. Thanks. * Ken * -- * Kenneth Merry * ken@plutotech.com Satoshi To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 08:08:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA09709 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 08:08:42 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nygate.undp.org (nygate.undp.org [192.124.42.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA09704; Tue, 10 Nov 1998 08:08:38 -0800 (PST) (envelope-from ugen@undp.org) Received: from inet01.hq.undp.org (inet01.hq.undp.org [192.124.42.9]) by nygate.undp.org (8.9.1/8.9.1/1.13) with ESMTP id LAA08477; Tue, 10 Nov 1998 11:08:14 -0500 (EST) Received: from undp.org ([165.65.2.224]) by inet01.hq.undp.org (Netscape Messaging Server 3.6) with ESMTP id AAAB7; Tue, 10 Nov 1998 11:04:32 -0500 Message-ID: <36486409.FB3BBC51@undp.org> Date: Tue, 10 Nov 1998 11:04:25 -0500 From: "Ugen Antsilevitch" X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: hardware@FreeBSD.ORG CC: scsi@FreeBSD.ORG Subject: AHA-2940 U/UW Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org All right..i have a PROBLEM.... We here at UNDP ordered a special custom machine to run our dynamic DNS and some other things using FreeBSD stable. Well..spec's seemed all fine, but now when it came - apparently there is a problem. The machine is a Dell OptiPlex or something, 400Mhz, with AHA 2940 U/UW dual SCSI. This card and the onboard Ethernet card (3COM 590) are both on PCI bus 1. For whatever reason when i boot from installation CDROM, the dmesg says that some devices (theese two) were found at such and such location on PCI bus 1. But "driver not attached" (or "assigned"?) to those devices and thats about it. On the same machine it finds correctly VGA pci device on PCI bus 1 and Intel EtherExpress PCI card on PCI bus 2. Well..so what do i do now? Any ideas? --Ugen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 08:48:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA15182 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 08:48:08 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA15084; Tue, 10 Nov 1998 08:47:57 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from gnipahellir.ifi.uio.no (2602@gnipahellir.ifi.uio.no [129.240.64.86]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id RAA17123; Tue, 10 Nov 1998 17:47:28 +0100 (MET) Received: (from dag-erli@localhost) by gnipahellir.ifi.uio.no ; Tue, 10 Nov 1998 17:47:27 +0100 (MET) Mime-Version: 1.0 To: "Ugen Antsilevitch" Cc: hardware@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: AHA-2940 U/UW References: <36486409.FB3BBC51@undp.org> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 10 Nov 1998 17:47:26 +0100 In-Reply-To: "Ugen Antsilevitch"'s message of "Tue, 10 Nov 1998 11:04:25 -0500" Message-ID: Lines: 27 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id IAA15177 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Ugen Antsilevitch" writes: > The machine is a Dell OptiPlex or something, 400Mhz, with AHA 2940 > U/UW dual SCSI. The AHA2940 is a single-channel card. You probably have a dual-channel AHA3940U/UW with an AIC7895 chip. > This card and the onboard Ethernet card (3COM 590) > are both on PCI bus 1. For whatever reason when i boot from > installation CDROM, the dmesg says that some devices (theese two) > were found at such and such location on PCI bus 1. But "driver not > attached" (or "assigned"?) to those devices and thats about it. On > the same machine it finds correctly VGA pci device on PCI bus 1 and > Intel EtherExpress PCI card on PCI bus 2. a) Stay away from Dell. Even if you get the above problems fixed, you'll find out the box has a broken keyboard controller. b) It sounds to me like you tried to install -stable, which supports neither the Etherlink XL nor the AIC7895. Get -current, or get another computer, with an Intel EtherExpress Pro/100 and a plain Adaptec 2940. I really doubt you need a dual-channel SCSI controller if all you're doing is DNS "and some other things". DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 09:11:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18532 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 09:11:30 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nygate.undp.org (nygate.undp.org [192.124.42.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18527; Tue, 10 Nov 1998 09:11:24 -0800 (PST) (envelope-from ugen@undp.org) Received: from inet01.hq.undp.org (inet01.hq.undp.org [192.124.42.9]) by nygate.undp.org (8.9.1/8.9.1/1.13) with ESMTP id MAA12396; Tue, 10 Nov 1998 12:11:04 -0500 (EST) Received: from undp.org ([165.65.2.224]) by inet01.hq.undp.org (Netscape Messaging Server 3.6) with ESMTP id AAA51E9; Tue, 10 Nov 1998 12:07:08 -0500 Message-ID: <364872B5.96C269C4@undp.org> Date: Tue, 10 Nov 1998 12:07:01 -0500 From: "Ugen Antsilevitch" X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" CC: hardware@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: AHA-2940 U/UW References: <36486409.FB3BBC51@undp.org> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Dag-Erling C. Smørgrav" wrote: > "Ugen Antsilevitch" writes: > > The machine is a Dell OptiPlex or something, 400Mhz, with AHA 2940 > > U/UW dual SCSI. > > The AHA2940 is a single-channel card. You probably have a dual-channel > AHA3940U/UW with an AIC7895 chip. > Thats what it says when you boot: AHA2940U/UW . I presumed it's dual channel since when you go into SCSI utility it shows two sets of SCSI devices/id's etc. Will this be unsupported also? Thanx! --Ugen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 09:15:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA19259 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 09:15:45 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from amalthea.salford.ac.uk (amalthea.salford.ac.uk [146.87.255.61]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id JAA18254 for ; Tue, 10 Nov 1998 09:09:54 -0800 (PST) (envelope-from M.S.Powell@ais.salford.ac.uk) Received: (qmail 3026 invoked by alias); 10 Nov 1998 17:09:07 -0000 Received: (qmail 3020 invoked from network); 10 Nov 1998 17:09:07 -0000 Received: from plato.salford.ac.uk (146.87.255.76) by amalthea.salford.ac.uk with SMTP; 10 Nov 1998 17:09:07 -0000 Received: (qmail 19757 invoked by alias); 10 Nov 1998 17:09:07 -0000 Delivered-To: catchall-freebsd-scsi@freebsd.org Received: (qmail 19748 invoked by uid 141); 10 Nov 1998 17:09:06 -0000 Date: Tue, 10 Nov 1998 17:09:06 +0000 (GMT) From: Mark Powell To: freebsd-scsi@FreeBSD.ORG Subject: 3.0 scsi parity and tagged openings problems 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 Just did a fresh install of 3.0-RELEASE on a machine that previously ran 2.2.7-STABLE. It's a Viglen XX server with two 7880 chips on the motherboard. It has three Fujitsu M2934 wide drives on each scsi bus, connected thus: 7880 -> (da0) 2934 : (da1) 2934 : (da2) 2934 : CDROM : TAPE 7880 -> (da3) 2934 : (da4) 2934 : (da5) 2934 I have the system on da0 and want to make a ccd of drives da1 and da3. However, when I try to newfs the newly created ccd... # newfs /dev/rccd0a Warning: 1280 sector(s) in last cylinder unallocated /dev/ccd0a: 17013504 sectors in 4154 cylinders of 1 tracks, 4096 sectors 8307.4MB in 260 cyl groups (16 c/g, 32.00MB/g, 7936 i/g) super-block backups (for fsck -b #) at: n1, n2, n3, n4 etc. Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 125 Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 125 Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 124 Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 124 Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 122 Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 122 Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 121 etc. etc. until Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 64 Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 63 Nov 10 15:48:58 titan /kernel: (da2:ahc0:0:1:0): tagged openings now 2 Nov 10 15:48:58 titan /kernel: (da2:ahc0:0:1:0): tagged openings now 2 Then the block numbers stop. First time it happened I thought the machine had hung, so I sshed in and rebooted it. Upon the console appeared: syncing disks x y x ... giving up ahc0: data parity error detected during address or write data phase Next time I tried it, I noticed that it hadn't actually hung, but was still printing a block number every couple of minutes or so. I killed it and after a few minutes got my prompt back. Then the same newfs command worked perfectly? Any ideas what caused that? Cheers. Mark Powell - System Administrator (UNIX) - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 Email: M.S.Powell@ais.salfrd.ac.uk www.pgp.com (for PGP key) NO SPAM please: Spell salford correctly to reply to me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 10:01:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24083 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 10:01:15 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from obiwan.TerraNova.net (obiwan.TerraNova.net [205.152.191.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24075 for ; Tue, 10 Nov 1998 10:01:13 -0800 (PST) (envelope-from bofh@terranova.net) Received: from terranova.net (tog@guenhwyvar.TerraNova.net [205.152.191.4]) by obiwan.TerraNova.net (8.9.1a/TNN/3.1) with ESMTP id NAA06500 for ; Tue, 10 Nov 1998 13:00:53 -0500 (EST) Message-ID: <36487EE6.81B29D0D@terranova.net> Date: Tue, 10 Nov 1998 12:59:02 -0500 From: Travis Mikalson Organization: TerraNovaNet X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: scsi@FreeBSD.ORG Subject: Revision E 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 Ok so it's been a while since this has come up but how're the Revision E Adaptec AHA-2940(UW)s working now with -STABLE's SCSI layer and with CAM? Rev. E 2940s is all that Adaptec is shipping now unfortunately. Thanks, -T -- TerraNovaNet Internet Services - Key Largo, FL Voice: (305)453-4011 Fax: (305)451-5991 http://www.terranova.net/ ---------------------------------------------- "By the time they had diminished from 50 to 8, the other dwarves began to suspect 'Hungry'..." -- Gary Larson, "The Far Side" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 10:07:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24845 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 10:07:35 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24837; Tue, 10 Nov 1998 10:07:32 -0800 (PST) (envelope-from kyle@stdio.com) Received: from localhost (kyle@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id NAA28787; Tue, 10 Nov 1998 13:09:56 -0500 (EST) (envelope-from kyle@heathers.stdio.com) Date: Tue, 10 Nov 1998 13:09:56 -0500 (EST) From: Kyle McPeek To: Ugen Antsilevitch cc: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" , hardware@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: AHA-2940 U/UW In-Reply-To: <364872B5.96C269C4@undp.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id KAA24841 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have some of these machines. They work fine with 3.0, 2.2 will not work at all with the 2940/Dual. It is a 2940 with a 7895 chip. There are two scsi buses on it, an internal wide,and an external SCSI-2 (Mini 50Pin). It looks just like a regular 2940, except that the external connector is a separate bus and has a Mini 50 connector instead of a 68 Pin. kyle. On Tue, 10 Nov 1998, Ugen Antsilevitch wrote: > > > "Dag-Erling C. Smørgrav" wrote: > > > "Ugen Antsilevitch" writes: > > > The machine is a Dell OptiPlex or something, 400Mhz, with AHA 2940 > > > U/UW dual SCSI. > > > > The AHA2940 is a single-channel card. You probably have a dual-channel > > AHA3940U/UW with an AIC7895 chip. > > > > Thats what it says when you boot: AHA2940U/UW . I presumed it's dual > channel > since when you go into SCSI utility it shows two sets of SCSI devices/id's > etc. > Will this be unsupported also? > > Thanx! > --Ugen > > > 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 Nov 10 10:31:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA27706 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 10:31:26 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nygate.undp.org (nygate.undp.org [192.124.42.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27698 for ; Tue, 10 Nov 1998 10:31:22 -0800 (PST) (envelope-from ugen@undp.org) Received: from inet01.hq.undp.org (inet01.hq.undp.org [192.124.42.9]) by nygate.undp.org (8.9.1/8.9.1/1.13) with ESMTP id NAA17478 for ; Tue, 10 Nov 1998 13:31:05 -0500 (EST) Received: from undp.org ([165.65.2.224]) by inet01.hq.undp.org (Netscape Messaging Server 3.6) with ESMTP id AAA6DF5; Tue, 10 Nov 1998 13:28:29 -0500 Message-ID: <364885C5.A809D885@undp.org> Date: Tue, 10 Nov 1998 13:28:21 -0500 From: "Ugen Antsilevitch" X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: Travis Mikalson CC: scsi@FreeBSD.ORG Subject: Re: Revision E References: <36487EE6.81B29D0D@terranova.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Heh...i asked this question in here this morning actually:) I think this is probably what i have - it's dell and it has AHA-2940UW. I tried to use with with 2.2.7-stable and it didn't work:) Let's see if you get any better answers:) --Ugen Travis Mikalson wrote: > Ok so it's been a while since this has come up but how're the Revision E > Adaptec AHA-2940(UW)s working now with -STABLE's SCSI layer and with > CAM? > > Rev. E 2940s is all that Adaptec is shipping now unfortunately. > > Thanks, > -T > -- > TerraNovaNet Internet Services - Key Largo, FL > Voice: (305)453-4011 Fax: (305)451-5991 > http://www.terranova.net/ > ---------------------------------------------- > "By the time they had diminished from 50 to 8, > the other dwarves began to suspect 'Hungry'..." > -- Gary Larson, "The Far Side" > > 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 Nov 10 11:37:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA04844 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 11:37:52 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from obiwan.TerraNova.net (obiwan.TerraNova.net [205.152.191.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA04836 for ; Tue, 10 Nov 1998 11:37:50 -0800 (PST) (envelope-from bofh@terranova.net) Received: from terranova.net (tog@guenhwyvar.TerraNova.net [205.152.191.4]) by obiwan.TerraNova.net (8.9.1a/TNN/3.1) with ESMTP id OAA09238; Tue, 10 Nov 1998 14:37:36 -0500 (EST) Message-ID: <3648958F.9C5C03CE@terranova.net> Date: Tue, 10 Nov 1998 14:35:43 -0500 From: Travis Mikalson Organization: TerraNovaNet X-Mailer: Mozilla 4.5 [en] (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: Ugen Antsilevitch CC: scsi@FreeBSD.ORG Subject: Re: Revision E References: <36487EE6.81B29D0D@terranova.net> <364885C5.A809D885@undp.org> 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 Ugen Antsilevitch wrote: > > Heh...i asked this question in here this morning actually:) I think this is > probably what i have - > it's dell and it has AHA-2940UW. I tried to use with with 2.2.7-stable and > it didn't work:) > Let's see if you get any better answers:) > --Ugen Oh as far as I know they work just fine until you put load on them.. then they spew timeout errors. At least that's been my experience with the Rev. E chipset 2940s with either 2.2 or 3.0 as of about 6 months ago (pre-CAM) A dual channel AHA-2940 would be a 3940 which uses a different and unsupported chipset (the 7895 I believe) unless you either patch CAM into 2.2 or use 3.0 which now uses CAM. Although I wouldn't put 3.0 into immediate production without testing it out thoroughly it would be easier for you to install than trying to get a CAM-patched 2.2 working. -T -- TerraNovaNet Internet Services - Key Largo, FL Voice: (305)453-4011 Fax: (305)451-5991 http://www.terranova.net/ ---------------------------------------------- "By the time they had diminished from 50 to 8, the other dwarves began to suspect 'Hungry'..." -- Gary Larson, "The Far Side" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 11:45:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA05679 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 11:45:17 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA05674 for ; Tue, 10 Nov 1998 11:45:15 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id OAA11656 for ; Tue, 10 Nov 1998 14:41:02 -0500 (EST) Date: Tue, 10 Nov 1998 14:41:02 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: freebsd-scsi@FreeBSD.ORG Subject: CMD raid and multiple luns Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm running a CMD CRD-5440 and an Adaptec 2940UW on a stable snap from 980825. Since this is a production machine, I'm not yet ready to jump to 3.0 and CAM. The problem I'm having is that I have an array set up with two partitions. Each partition is mapped to a LUN. In other words partition 1 is at controller 0, ID 0, LUN 0, and partition 2 is at controller 0, ID 0, LUN 1. The Adaptec BIOS screen shows the two LUNS, but on boot, the OS only detects the first one. I've tried just letting it probe for the second LUN and wiring sd0 to LUN0 and sd1 to LUN1 with no luck. Any ideas? I found this in the archives, might it apply to my situation? http://www.freebsd.org/cgi/getmsg.cgi?fetch=42792+44758+/usr/local/www/db/text/1998/freebsd-scsi/19980802.freebsd-scsi Thanks, Charles --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 12:03:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA07219 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 12:03:10 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA07210; Tue, 10 Nov 1998 12:03:07 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id VAA14021; Tue, 10 Nov 1998 21:02:46 +0100 (MET) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Tue, 10 Nov 1998 21:02:44 +0100 (MET) Mime-Version: 1.0 To: Kyle McPeek Cc: Ugen Antsilevitch , "Dag-Erling C. Smørgrav" , hardware@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: AHA-2940 U/UW References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 10 Nov 1998 21:02:41 +0100 In-Reply-To: Kyle McPeek's message of "Tue, 10 Nov 1998 13:09:56 -0500 (EST)" Message-ID: Lines: 15 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id MAA07214 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kyle McPeek writes: > I have some of these machines. They work fine with 3.0, 2.2 will not work > at all with the 2940/Dual. It is a 2940 with a 7895 chip. There are two > scsi buses on it, an internal wide,and an external SCSI-2 (Mini 50Pin). > It looks just like a regular 2940, except that the external connector is a > separate bus and has a Mini 50 connector instead of a 68 Pin. Uh-huh. The AHA2940 and AHA2940UW are single-channel adapters based on the AIC7880 and AIC7890 chips, respectively. The only multichannel SCSI adapters Adaptec make are the AHA3940/W and the AHA3940U/UW, unless there are Adaptec cards even Adaptec doesn't know about. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 12:49:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12911 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 12:49:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from heathers.stdio.com (heathers.stdio.com [199.89.192.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12906; Tue, 10 Nov 1998 12:49:52 -0800 (PST) (envelope-from kyle@stdio.com) Received: from localhost (kyle@localhost) by heathers.stdio.com (8.8.8/8.8.8) with SMTP id PAA05019; Tue, 10 Nov 1998 15:52:36 -0500 (EST) (envelope-from kyle@heathers.stdio.com) Date: Tue, 10 Nov 1998 15:52:35 -0500 (EST) From: Kyle McPeek To: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" cc: hardware@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: AHA-2940 U/UW In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id MAA12907 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The card I have is clearly labeled "AHA-2940UW Dual / NE adaptec". The sticker over the AIC 7895P chip bears the following text "AHA-2940UW DUAL / DELL". When in a machine running 3.0-RELEASE it probes with the following: ahc0: rev 0x03 int a irq 5 on pci0.13.0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x03 int b irq 11 on pci0.13.1 ahc1: aic7895 Single Channel B, SCSI Id=7, 16/255 SCBs I think it just might be an Adaptec that you don't know about. kyle. On 10 Nov 1998, Dag-Erling C. [iso-8859-1] Smørgrav wrote: > Kyle McPeek writes: > > I have some of these machines. They work fine with 3.0, 2.2 will not work > > at all with the 2940/Dual. It is a 2940 with a 7895 chip. There are two > > scsi buses on it, an internal wide,and an external SCSI-2 (Mini 50Pin). > > It looks just like a regular 2940, except that the external connector is a > > separate bus and has a Mini 50 connector instead of a 68 Pin. > > Uh-huh. The AHA2940 and AHA2940UW are single-channel adapters based on > the AIC7880 and AIC7890 chips, respectively. The only multichannel > SCSI adapters Adaptec make are the AHA3940/W and the AHA3940U/UW, > unless there are Adaptec cards even Adaptec doesn't know about. > > DES > -- > Dag-Erling Smørgrav - dag-erli@ifi.uio.no > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 12:57:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13932 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 12:57:41 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13923 for ; Tue, 10 Nov 1998 12:57:39 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id MAA18098; Tue, 10 Nov 1998 12:56:26 -0800 Date: Tue, 10 Nov 1998 12:56:26 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Satoshi Asami cc: scsi@FreeBSD.ORG Subject: Re: turning off tagged queuing with CAM? In-Reply-To: <199811100140.RAA23827@vader.cs.berkeley.edu> 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 is a function missing from camcontrol, I believe, right now. Why do you want tagging off? On Mon, 9 Nov 1998, Satoshi Asami wrote: > Hi Justin and Ken (and others :), > > Is it possible to turn off tagged queuing with the current version of > CAM? There used to be an AHC_TAGENABLE variable but it seems to have > gone away. I looked at the mode pages but couldn't find anything > suspicious. > > Here's one of the systems: > > === > Copyright (c) 1992-1998 FreeBSD Inc. > Copyright (c) 1982, 1986, 1989, 1991, 1993 > The Regents of the University of California. All rights reserved. > FreeBSD 3.0-CURRENT #2: Wed Nov 4 04:13:25 PST 1998 > asami2@m8.cs.berkeley.edu:/disks/stampede/sandbox1/freebsd/allsrc/current/src/sys/compile/TD > Timecounter "i8254" frequency 1193182 Hz > Timecounter "TSC" frequency 199432708 Hz > CPU: Pentium Pro (199.43-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0x616 Stepping=6 > Features=0xf9ff > real memory = 100663296 (98304K bytes) > avail memory = 95531008 (93292K bytes) > Probing for devices on PCI bus 0: > chip0: rev 0x02 on pci0.0.0 > chip1: rev 0x00 on pci0.7.0 > ide_pci0: rev 0x00 on pci0.7.1 > vga0: rev 0x03 on pci0.11.0 > fxp0: rev 0x02 int a irq 11 on pci0.15.0 > fxp0: Ethernet address 00:a0:c9:72:86:45 > chip2: rev 0x02 on pci0.17.0 > chip3: rev 0x02 on pci0.19.0 > Probing for devices on PCI bus 1: > ahc0: rev 0x00 int a irq 10 on pci1.4.0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > ahc1: rev 0x00 int a irq 11 on pci1.5.0 > ahc1: aic7880 Wide Channel B, SCSI Id=7, 16/255 SCBs > Probing for devices on PCI bus 2: > ahc2: rev 0x00 int a irq 11 on pci2.4.0 > ahc2: aic7880 Wide Channel A, SCSI Id=6, 16/255 SCBs > ahc3: rev 0x00 int a irq 11 on pci2.5.0 > ahc3: aic7880 Wide Channel B, SCSI Id=6, 16/255 SCBs > Probing for devices on the ISA bus: > sc0 at 0x60-0x6f irq 1 on motherboard > sc0: CGA <16 virtual consoles, flags=0x0> > sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa > sio0: type 16550A, console > sio1 at 0x2f8-0x2ff irq 3 on isa > sio1: type 16550A > fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa > fdc0: FIFO enabled, 8 bytes threshold > fd0: 1.44MB 3.5in > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0): > wd0: 2015MB (4127760 sectors), 4095 cyls, 16 heads, 63 S/T, 512 B/S > npx0 on motherboard > npx0: INT 16 interface > ahc1: Someone reset channel A > ccd0-7: Concatenated disk drivers > Waiting 2 seconds for SCSI devices to settle > changing root device to wd0s1a > da8 at ahc0 bus 0 target 8 lun 0 > da8: Fixed Direct Access SCSI2 device > da8: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da8: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > da41 at ahc2 bus 0 target 9 lun 0 > da41: Fixed Direct Access SCSI2 device > da41: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da41: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > da46 at ahc2 bus 0 target 14 lun 0 > da46: Fixed Direct Access SCSI2 device > da46: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da46: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > da1 at ahc0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI2 device > da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da1: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > da47 at ahc2 bus 0 target 15 lun 0 > da47: Fixed Direct Access SCSI2 device > da47: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da47: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > da2 at ahc0 bus 0 target 2 lun 0 > da2: Fixed Direct Access SCSI2 device > da2: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da2: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > da43 at ahc2 bus 0 target 11 lun 0 > da43: Fixed Direct Access SCSI2 device > da43: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da43: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > da4 at ahc0 bus 0 target 4 lun 0 > da4: Fixed Direct Access SCSI2 device > da4: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da4: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > da40 at ahc2 bus 0 target 8 lun 0 > da40: Fixed Direct Access SCSI2 device > da40: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da40: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > da42 at ahc2 bus 0 target 10 lun 0 > da42: Fixed Direct Access SCSI2 device > da42: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da42: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI2 device > da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > da3 at ahc0 bus 0 target 3 lun 0 > da3: Fixed Direct Access SCSI2 device > da3: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da3: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > da45 at ahc2 bus 0 target 13 lun 0 > da45: Fixed Direct Access SCSI2 device > da45: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da45: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > da9 at ahc0 bus 0 target 9 lun 0 > da9: Fixed Direct Access SCSI2 device > da9: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da9: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > da44 at ahc2 bus 0 target 12 lun 0 > da44: Fixed Direct Access SCSI2 device > da44: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da44: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > da5 at ahc0 bus 0 target 5 lun 0 > da5: Fixed Direct Access SCSI2 device > da5: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da5: 8689MB (17796077 512 byte sectors: 255H 63S/T 1107C) > === > > Satoshi > > 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 Nov 10 13:17:48 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA16304 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 13:17:48 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA16292; Tue, 10 Nov 1998 13:17:45 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id OAA11523; Tue, 10 Nov 1998 14:16:54 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811102116.OAA11523@panzer.plutotech.com> Subject: Re: AHA-2940 U/UW In-Reply-To: from =?ISO-8859-1?Q?Dag=2DErling_C=2E_Sm=F8rgrav?= at "Nov 10, 98 09:02:41 pm" To: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=) Date: Tue, 10 Nov 1998 14:16:54 -0700 (MST) Cc: kyle@stdio.com, ugen@undp.org, dag-erli@ifi.uio.no, hardware@FreeBSD.ORG, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dag-Erling C. Smørgrav wrote... > Kyle McPeek writes: > > I have some of these machines. They work fine with 3.0, 2.2 will not work > > at all with the 2940/Dual. It is a 2940 with a 7895 chip. There are two > > scsi buses on it, an internal wide,and an external SCSI-2 (Mini 50Pin). > > It looks just like a regular 2940, except that the external connector is a > > separate bus and has a Mini 50 connector instead of a 68 Pin. > > Uh-huh. The AHA2940 and AHA2940UW are single-channel adapters based on > the AIC7880 and AIC7890 chips, respectively. Uh, no. The 2940UW is based on the 7880. The 2940U2W is based on the 7890. > The only multichannel > SCSI adapters Adaptec make are the AHA3940/W and the AHA3940U/UW, > unless there are Adaptec cards even Adaptec doesn't know about. They'll probably be coming out with cards based on the 7896/7897 at some point. (those are 32-bit and 64-bit dual-channel Ultra-2 controller chips) 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 Nov 10 13:36:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19167 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 13:36:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19160 for ; Tue, 10 Nov 1998 13:36:12 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id OAA11748; Tue, 10 Nov 1998 14:35:47 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811102135.OAA11748@panzer.plutotech.com> Subject: Re: turning off tagged queuing with CAM? In-Reply-To: from Matthew Jacob at "Nov 10, 98 12:56:26 pm" To: mjacob@feral.com Date: Tue, 10 Nov 1998 14:35:47 -0700 (MST) Cc: asami@cs.berkeley.edu, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote... > > This is a function missing from camcontrol, I believe, right now. No it isn't. As I told him yesterday, if you edit mode page 10 and set the DQue bit to 1, it will turn tagged queueing off. Or you can put a quirk entry in the transport layer to do 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 Nov 10 13:39:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19670 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 13:39:37 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19654 for ; Tue, 10 Nov 1998 13:39:35 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id NAA18246; Tue, 10 Nov 1998 13:38:43 -0800 Date: Tue, 10 Nov 1998 13:38:43 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Kenneth D. Merry" cc: asami@cs.berkeley.edu, scsi@FreeBSD.ORG Subject: Re: turning off tagged queuing with CAM? In-Reply-To: <199811102135.OAA11748@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This needs to be better documented. It's also not clear that this in fact is the right approach. Disabling something in a target device may or may not be the right approach to take when you want to disable something for the benefit of the initiator (e.g.). On Tue, 10 Nov 1998, Kenneth D. Merry wrote: > Matthew Jacob wrote... > > > > This is a function missing from camcontrol, I believe, right now. > > No it isn't. As I told him yesterday, if you edit mode page 10 and set the > DQue bit to 1, it will turn tagged queueing off. Or you can put a quirk > entry in the transport layer to do 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 Nov 10 13:40:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19817 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 13:40:02 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19736; Tue, 10 Nov 1998 13:39:46 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id QAA26100; Tue, 10 Nov 1998 16:34:02 -0500 (EST) Date: Tue, 10 Nov 1998 16:34:02 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: Kyle McPeek cc: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" , hardware@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: AHA-2940 U/UW In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id NAA19788 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I had three in hand last week. They do exist. Mine weren't labelled "Dell", but were OEM boards. Also included a manual that had (2940UW DUAL) on the cover. Adaptec is aware of the boards, just a little curious about where the general public gets them... Since we don't run 3.0, we had to return them. Charles --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." On Tue, 10 Nov 1998, Kyle McPeek wrote: > The card I have is clearly labeled "AHA-2940UW Dual / NE adaptec". The > sticker over the AIC 7895P chip bears the following text "AHA-2940UW > DUAL / DELL". > > When in a machine running 3.0-RELEASE it probes with the following: > > ahc0: rev 0x03 int a irq 5 on > pci0.13.0 > ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs > ahc1: rev 0x03 int b irq 11 on > pci0.13.1 > ahc1: aic7895 Single Channel B, SCSI Id=7, 16/255 SCBs > > I think it just might be an Adaptec that you don't know about. > > kyle. > > On 10 Nov 1998, Dag-Erling C. [iso-8859-1] Smørgrav wrote: > > > Kyle McPeek writes: > > > I have some of these machines. They work fine with 3.0, 2.2 will not work > > > at all with the 2940/Dual. It is a 2940 with a 7895 chip. There are two > > > scsi buses on it, an internal wide,and an external SCSI-2 (Mini 50Pin). > > > It looks just like a regular 2940, except that the external connector is a > > > separate bus and has a Mini 50 connector instead of a 68 Pin. > > > > Uh-huh. The AHA2940 and AHA2940UW are single-channel adapters based on > > the AIC7880 and AIC7890 chips, respectively. The only multichannel > > SCSI adapters Adaptec make are the AHA3940/W and the AHA3940U/UW, > > unless there are Adaptec cards even Adaptec doesn't know about. > > > > DES > > -- > > Dag-Erling Smørgrav - dag-erli@ifi.uio.no > > > > > 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 Nov 10 13:46:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20710 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 13:46:36 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20702 for ; Tue, 10 Nov 1998 13:46:34 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id OAA11882; Tue, 10 Nov 1998 14:46:12 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811102146.OAA11882@panzer.plutotech.com> Subject: Re: turning off tagged queuing with CAM? In-Reply-To: from Matthew Jacob at "Nov 10, 98 01:38:43 pm" To: mjacob@feral.com Date: Tue, 10 Nov 1998 14:46:12 -0700 (MST) Cc: asami@cs.berkeley.edu, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote... > On Tue, 10 Nov 1998, Kenneth D. Merry wrote: > > > Matthew Jacob wrote... > > > > > > This is a function missing from camcontrol, I believe, right now. > > > > No it isn't. As I told him yesterday, if you edit mode page 10 and set the > > DQue bit to 1, it will turn tagged queueing off. Or you can put a quirk > > entry in the transport layer to do it. > This needs to be better documented. Well, it's documented in the SCSI specs. :) I guess I could put something in the camcontrol man page about it. > It's also not clear that this in fact > is the right approach. Disabling something in a target device may or may > not be the right approach to take when you want to disable something for > the benefit of the initiator (e.g.). I'm not sure I understand what you're getting at... You mean you want a switch to disable tagged queueing for everything on a particular initiator? 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 Nov 10 13:52:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA21677 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 13:52:38 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA21659 for ; Tue, 10 Nov 1998 13:52:32 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id NAA18277; Tue, 10 Nov 1998 13:51:38 -0800 Date: Tue, 10 Nov 1998 13:51:38 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Kenneth D. Merry" cc: asami@cs.berkeley.edu, scsi@FreeBSD.ORG Subject: Re: turning off tagged queuing with CAM? In-Reply-To: <199811102146.OAA11882@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 10 Nov 1998, Kenneth D. Merry wrote: > Matthew Jacob wrote... > > On Tue, 10 Nov 1998, Kenneth D. Merry wrote: > > > > > Matthew Jacob wrote... > > > > > > > > This is a function missing from camcontrol, I believe, right now. > > > > > > No it isn't. As I told him yesterday, if you edit mode page 10 and set the > > > DQue bit to 1, it will turn tagged queueing off. Or you can put a quirk > > > entry in the transport layer to do it. > > > This needs to be better documented. > > Well, it's documented in the SCSI specs. :) I guess I could put something > in the camcontrol man page about it. Wrong. camcontrol is for users to use. A low level approach may work, but a useful tool won't force everyone to use that approach. > > > It's also not clear that this in fact > > is the right approach. Disabling something in a target device may or may > > not be the right approach to take when you want to disable something for > > the benefit of the initiator (e.g.). > > I'm not sure I understand what you're getting at... You mean you want a > switch to disable tagged queueing for everything on a particular initiator? Yes. You also need to disable it at the initiator level. For whatever reason. Don't depend upon your telephone to work to call somebody and tell them that your telephone isn't working. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 14:15:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24638 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 14:15:07 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24625; Tue, 10 Nov 1998 14:15:04 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id XAA00867; Tue, 10 Nov 1998 23:14:46 +0100 (MET) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Tue, 10 Nov 1998 23:14:45 +0100 (MET) Mime-Version: 1.0 To: Kyle McPeek Cc: "=?iso-8859-1?Q?=22Dag?= -Erling C. =?iso-8859-1?Q?Sm=F8rgrav=22?=" , hardware@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: AHA-2940 U/UW References: Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 10 Nov 1998 23:14:42 +0100 In-Reply-To: Kyle McPeek's message of "Tue, 10 Nov 1998 15:52:35 -0500 (EST)" Message-ID: Lines: 9 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id OAA24631 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kyle McPeek writes: > I think it just might be an Adaptec that you don't know about. Make that "an Adaptec Adaptec doesn't know about". According to their web pages, it simply doesn't exist. The AHA3940 is 7895-based AFAIK. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 14:17:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA24914 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 14:17:01 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ifi.uio.no (ifi.uio.no [129.240.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA24896; Tue, 10 Nov 1998 14:16:55 -0800 (PST) (envelope-from dag-erli@ifi.uio.no) Received: from hrotti.ifi.uio.no (2602@hrotti.ifi.uio.no [129.240.64.15]) by ifi.uio.no (8.8.8/8.8.7/ifi0.2) with ESMTP id XAA01252; Tue, 10 Nov 1998 23:16:33 +0100 (MET) Received: (from dag-erli@localhost) by hrotti.ifi.uio.no ; Tue, 10 Nov 1998 23:16:32 +0100 (MET) Mime-Version: 1.0 To: "Kenneth D. Merry" Cc: kyle@stdio.com, ugen@undp.org, hardware@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: AHA-2940 U/UW References: <199811102116.OAA11523@panzer.plutotech.com> Organization: University of Oslo, Department of Informatics X-url: http://www.stud.ifi.uio.no/~dag-erli/ X-other-addresses: 'finger dag-erli@ifi.uio.no' for a list X-disclaimer-1: The views expressed in this article are mine alone, and do X-disclaimer-2: not necessarily coincide with those of any organisation or X-disclaimer-3: company with which I am or have been affiliated. X-Stop-Spam: http://www.cauce.org/ From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) Date: 10 Nov 1998 23:16:29 +0100 In-Reply-To: "Kenneth D. Merry"'s message of "Tue, 10 Nov 1998 14:16:54 -0700 (MST)" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/Emacs 19.34 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id OAA24906 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" writes: > Dag-Erling C. Smørgrav wrote... > > Uh-huh. The AHA2940 and AHA2940UW are single-channel adapters based on > > the AIC7880 and AIC7890 chips, respectively. > Uh, no. The 2940UW is based on the 7880. The 2940U2W is based on the > 7890. Typo. I'm starting to believe that one or more of Adaptec, the world and me is going nuts. Or has been for a long time. Or something. Time to hit the haysack. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 14:56:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00475 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 14:56:16 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00470 for ; Tue, 10 Nov 1998 14:56:14 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id PAA12482; Tue, 10 Nov 1998 15:52:42 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811102252.PAA12482@panzer.plutotech.com> Subject: Re: Revision E In-Reply-To: <3648958F.9C5C03CE@terranova.net> from Travis Mikalson at "Nov 10, 98 02:35:43 pm" To: bofh@terranova.net (Travis Mikalson) Date: Tue, 10 Nov 1998 15:52:42 -0700 (MST) Cc: ugen@undp.org, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Travis Mikalson wrote... > Ugen Antsilevitch wrote: > > > > Heh...i asked this question in here this morning actually:) I think this is > > probably what i have - > > it's dell and it has AHA-2940UW. I tried to use with with 2.2.7-stable and > > it didn't work:) > > Let's see if you get any better answers:) > > --Ugen > > Oh as far as I know they work just fine until you put load on them.. > then they spew timeout errors. > At least that's been my experience with the Rev. E chipset 2940s with > either 2.2 or 3.0 as of about 6 months ago (pre-CAM) I believe the Rev. E 2940's (with Rev B 7880's) work fine now, in both -stable (non-CAM) and current. Justin fixed the problem months ago. (June, I think) > A dual channel AHA-2940 would be a 3940 which uses a different and > unsupported chipset (the 7895 I believe) unless you either patch CAM > into 2.2 or use 3.0 which now uses CAM. > Although I wouldn't put 3.0 into immediate production without testing it > out thoroughly it would be easier for you to install than trying to get > a CAM-patched 2.2 working. There is a 2.2-CAM release available. It's about the same vintage as 2.2.7. It's here: ftp://ftp.FreeBSD.ORG/pub/FreeBSD/development/cam/2.2CAM-19980716-SNAP/ 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 Nov 10 14:58:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA00776 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 14:58:28 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA00765; Tue, 10 Nov 1998 14:58:24 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id RAA04236; Tue, 10 Nov 1998 17:53:08 -0500 (EST) Date: Tue, 10 Nov 1998 17:53:08 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: "Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?=" cc: Kyle McPeek , hardware@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: AHA-2940 U/UW In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from QUOTED-PRINTABLE to 8bit by hub.freebsd.org id OAA00772 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It exists. I swear. --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." On 10 Nov 1998, Dag-Erling C. [iso-8859-1] Smørgrav wrote: > Kyle McPeek writes: > > I think it just might be an Adaptec that you don't know about. > > Make that "an Adaptec Adaptec doesn't know about". According to their > web pages, it simply doesn't exist. The AHA3940 is 7895-based AFAIK. > > DES > -- > Dag-Erling Smørgrav - dag-erli@ifi.uio.no > > 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 Nov 10 15:05:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA01617 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 15:05:41 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from n4hhe.ampr.org (tnt1-183.HiWAAY.net [208.147.147.183]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA01589 for ; Tue, 10 Nov 1998 15:05:11 -0800 (PST) (envelope-from dkelly@n4hhe.ampr.org) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by n4hhe.ampr.org (8.9.1/8.9.1) with ESMTP id RAA12327 for ; Tue, 10 Nov 1998 17:03:51 -0600 (CST) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199811102303.RAA12327@n4hhe.ampr.org> X-Mailer: exmh version 2.0.2 2/24/98 To: scsi@FreeBSD.ORG From: David Kelly Subject: Re: turning off tagged queuing with CAM? In-reply-to: Message from "Kenneth D. Merry" of "Tue, 10 Nov 1998 14:46:12 MST." <199811102146.OAA11882@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 10 Nov 1998 17:03:51 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" writes: > Matthew Jacob wrote... > > This needs to be better documented. > > Well, it's documented in the SCSI specs. :) I guess I could put something > in the camcontrol man page about it. It would be nice if there was more documentation or reference on SCSI mode pages for mere mortals. Without asking on a list such as this few would have figured out what DQue does. The closest we could come would be in /usr/share/misc/scsi_modes. But there only the name and location of the flags, and not what they do. -- 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 Tue Nov 10 17:34:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18662 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 17:34:45 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18657; Tue, 10 Nov 1998 17:34:42 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (gjp@localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id UAA05178; Tue, 10 Nov 1998 20:34:15 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) cc: Kyle McPeek , hardware@FreeBSD.ORG, scsi@FreeBSD.ORG From: "Gary Palmer" Subject: Re: AHA-2940 U/UW In-reply-to: Your message of "10 Nov 1998 23:14:42 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Date: Tue, 10 Nov 1998 20:34:15 -0500 Message-ID: <5174.910748055@gjp.erols.com> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id RAA18658 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= wrote in message ID : > Kyle McPeek writes: > > I think it just might be an Adaptec that you don't know about. > > Make that "an Adaptec Adaptec doesn't know about". According to their > web pages, it simply doesn't exist. The AHA3940 is 7895-based AFAIK. The newer 3940's are, yes. Older ones are 2 7880's behind a DEC PCI<->PCI bridge. Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 19:21:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29058 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 19:21:29 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29049 for ; Tue, 10 Nov 1998 19:21:28 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id UAA28974; Tue, 10 Nov 1998 20:14:22 -0700 (MST) Date: Tue, 10 Nov 1998 20:14:22 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199811110314.UAA28974@narnia.plutotech.com> To: spork cc: scsi@FreeBSD.ORG Subject: Re: AHA-2940 U/UW X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > It exists. I swear. Of course it exists. I've had a 2940UW-DUAL here for quite some time. It was the first aic7895 card that I received from Adaptec. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 19:24:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA29279 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 19:24:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA29270 for ; Tue, 10 Nov 1998 19:24:03 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id UAA28987; Tue, 10 Nov 1998 20:16:58 -0700 (MST) Date: Tue, 10 Nov 1998 20:16:58 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199811110316.UAA28987@narnia.plutotech.com> To: spork cc: scsi@FreeBSD.ORG Subject: Re: CMD raid and multiple luns X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-BETA (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > Hi, > > I'm running a CMD CRD-5440 and an Adaptec 2940UW on a stable snap from > 980825. Since this is a production machine, I'm not yet ready to jump to > 3.0 and CAM. If you want the machine to be stable under load, you should be running CAM. CAM is available for -stable, although the last snapshot is quite old. I'm still trying to dig out enough time from work to update it. 8-{ > The problem I'm having is that I have an array set up with two partitions. > Each partition is mapped to a LUN. In other words partition 1 is at > controller 0, ID 0, LUN 0, and partition 2 is at controller 0, ID 0, LUN > 1. The Adaptec BIOS screen shows the two LUNS, but on boot, the OS only > detects the first one. I've tried just letting it probe for the second > LUN and wiring sd0 to LUN0 and sd1 to LUN1 with no luck. Multiple LUN support in the 2.2-stable driver is somewhat problematic. I wouldn't trust it. If you really want to try it, you must add a quirk entry into sys/scsi/scsiconf.c telling it to probe multiple luns for this device. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 20:16:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA03027 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 20:16:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thelab.hub.org (nat0574.mpoweredpc.net [142.177.190.66]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA03021; Tue, 10 Nov 1998 20:16:12 -0800 (PST) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.9.1/8.9.1) with ESMTP id AAA21290; Wed, 11 Nov 1998 00:15:51 -0400 (AST) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Wed, 11 Nov 1998 00:15:51 -0400 (AST) From: The Hermit Hacker To: freebsd-current@FreeBSD.ORG cc: freebsd-scsi@FreeBSD.ORG Subject: SCSI Bus errors spewing on console... 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 Can someone tell me *what* this means? I have someone rushing to the office right now to reboot the machine, as there is nothing that I can do from here...is it a mis-configuration in my kernel (ie. I have to raise a limit somewhere?) or a driving going back (which one?) or something altogether different? I'm running a 3.0 system, still aout, but based on the cvs tree of ~3.0-RELEASE...I'd provide dmesg output, except I can't get into the machine to get it ;( It started all of a sudden...server was working fine all evening, then all of a sudden, loadavg went through the roof...figured I might have more response through the serial console, so switched to that, and saw this.. thanks in advance for *any* help on this... ahc2: Bus Device Reset on A:1. 4 SCBs aborted ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40 ahc2: Bus Device Reset on A:1. 4 SCBs aborted ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40 ahc2: Bus Device Reset on A:1. 4 SCBs aborted ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40 ahc2: Bus Device Reset on A:1. 4 SCBs aborted ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40 ahc2: Bus Device Reset on A:1. 4 SCBs aborted ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40 Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Nov 10 22:45:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA08203 for freebsd-scsi-outgoing; Tue, 10 Nov 1998 22:45:27 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA08191 for ; Tue, 10 Nov 1998 22:45:24 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id VAA14192; Tue, 10 Nov 1998 21:23:35 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811110423.VAA14192@panzer.plutotech.com> Subject: Re: 3.0 scsi parity and tagged openings problems In-Reply-To: from Mark Powell at "Nov 10, 98 05:09:06 pm" To: M.S.Powell@ais.salford.ac.uk (Mark Powell) Date: Tue, 10 Nov 1998 21:23:35 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mark Powell wrote... > > Just did a fresh install of 3.0-RELEASE on a machine that previously ran > 2.2.7-STABLE. It's a Viglen XX server with two 7880 chips on the > motherboard. It has three Fujitsu M2934 wide drives on each scsi bus, > connected thus: > > 7880 -> (da0) 2934 : (da1) 2934 : (da2) 2934 : CDROM : TAPE > 7880 -> (da3) 2934 : (da4) 2934 : (da5) 2934 > > I have the system on da0 and want to make a ccd of drives da1 and da3. > However, when I try to newfs the newly created ccd... > > # newfs /dev/rccd0a > Warning: 1280 sector(s) in last cylinder unallocated > /dev/ccd0a: 17013504 sectors in 4154 cylinders of 1 tracks, 4096 > sectors > 8307.4MB in 260 cyl groups (16 c/g, 32.00MB/g, 7936 i/g) > super-block backups (for fsck -b #) at: > n1, n2, n3, n4 etc. > Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 125 > Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 125 > Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 124 > Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 124 > Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 122 > Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 122 > Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 121 > etc. etc. until > Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 64 > Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 63 > Nov 10 15:48:58 titan /kernel: (da2:ahc0:0:1:0): tagged openings now 2 > Nov 10 15:48:58 titan /kernel: (da2:ahc0:0:1:0): tagged openings now 2 It looks like one of your disks at least doesn't like tagged queueing. The interesting thing is that it's one of the drives that is *not* in your CCD array. (you said that only da1 and da3 are in the array) Were you doing I/O to da2 at the time? What's on that disk? I would suggest that you: - disable tagged queueing for that disk or - get new, non-broken firmware for that disk Since you've got Fujitsu drives, it's questionable whether or not you'll be able to get non-broken firmware for them. You can disable tagged queueing one of two ways: - put a quirk entry in cam_xpt.c. There are examples of how to do this in there. (Just look for the Western Digital entries..) - use camcontrol to edit mode page 10 (0x0a) for the drive(s) in question, and set the DQue bit to 1. > Then the block numbers stop. First time it happened I thought the machine > had hung, so I sshed in and rebooted it. Upon the console appeared: > > syncing disks x y x ... > giving up > ahc0: data parity error detected during address or write data phase That's a PCI parity error. (I don't know what caused it, or why it appeared, etc..) > Next time I tried it, I noticed that it hadn't actually hung, but was > still printing a block number every couple of minutes or so. I killed it > and after a few minutes got my prompt back. Then the same newfs command > worked perfectly? > Any ideas what caused that? Bad firmware, most likely. Try disabling tagged queueing for the disk or disks in question and see if it helps any. The reason you probably didn't see this on 2.2.7-stable is because the old SCSI layer only allowed 4 tags at a time to go to a drive. It may be that your drive has trouble whenever its transaction queue gets full and it has to return queue full status. The old SCSI code probably wouldn't have filled the transaction queue, but CAM will send as many transactions as it can to the disk. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 11 01:05:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA22974 for freebsd-scsi-outgoing; Wed, 11 Nov 1998 01:05:13 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from server.noc.demon.net (server.noc.demon.net [193.195.224.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA22969; Wed, 11 Nov 1998 01:05:09 -0800 (PST) (envelope-from geoffb@gti.noc.demon.net) Received: by server.noc.demon.net; id JAA07613; Wed, 11 Nov 1998 09:04:21 GMT Received: from gti.noc.demon.net(195.11.55.101) by inside.noc.demon.net via smap (3.2) id xma007607; Wed, 11 Nov 98 09:04:16 GMT Received: (from geoffb@localhost) by gti.noc.demon.net (8.8.8/8.8.8) id JAA10682; Wed, 11 Nov 1998 09:04:07 GMT From: Geoff Buckingham Message-Id: <199811110904.JAA10682@gti.noc.demon.net> Subject: Re: SCSI Bus errors spewing on console... In-Reply-To: from The Hermit Hacker at "Nov 11, 98 00:15:51 am" To: scrappy@hub.org (The Hermit Hacker) Date: Wed, 11 Nov 1998 09:04:07 +0000 (GMT) Cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Reply-To: geoffb@demon.net X-Mailer: ELM [version 2.4ME+ PL32 (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 > > Can someone tell me *what* this means? I have someone rushing to the > office right now to reboot the machine, as there is nothing that I can do > from here...is it a mis-configuration in my kernel (ie. I have to raise a > limit somewhere?) or a driving going back (which one?) or something > altogether different? > > I'm running a 3.0 system, still aout, but based on the cvs tree of > ~3.0-RELEASE...I'd provide dmesg output, except I can't get into the > machine to get it ;( > > It started all of a sudden...server was working fine all evening, then all > of a sudden, loadavg went through the roof...figured I might have more > response through the serial console, so switched to that, and saw this.. > > thanks in advance for *any* help on this... > > > ahc2: Bus Device Reset on A:1. 4 SCBs aborted > ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40 > ahc2: Bus Device Reset on A:1. 4 SCBs aborted > ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40 > ahc2: Bus Device Reset on A:1. 4 SCBs aborted > ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40 > ahc2: Bus Device Reset on A:1. 4 SCBs aborted > ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40 > ahc2: Bus Device Reset on A:1. 4 SCBs aborted > ahc2:A:1: no active SCB for reconnecting target - issuing BUS DEVICE RESET > SAVED_TCL == 0x10, ARG_1 == 0xff, SEQ_FLAGS == 0x40 > > This looks an awful lot like a problemm we had with an adaptec 3940UW, our problem went away when we switched to a 2940UW with a more recent revision of the adaptec firmware. -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 11 07:44:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA27758 for freebsd-scsi-outgoing; Wed, 11 Nov 1998 07:44:17 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from smtp-gw.BayNetworks.COM (ns3.BayNetworks.COM [192.32.253.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA27749 for ; Wed, 11 Nov 1998 07:44:13 -0800 (PST) (envelope-from George_Morgan@BayNetworks.COM) Received: from mailhost.BayNetworks.COM ([132.245.135.84]) by smtp-gw.BayNetworks.COM (8.9.1/BNET-98/10/01-E) with ESMTP id JAA23703 for ; Wed, 11 Nov 1998 09:55:05 -0500 (EST) Received: from mailhost.corpeast.BayNetworks.COM (ns4.corpeast.baynetworks.com [132.245.135.76]) by mailhost.BayNetworks.COM (8.8.8/8.8.8) with ESMTP id JAA19545 for ; Wed, 11 Nov 1998 09:53:27 -0500 (EST) Received: from sc-mail2.corpwest.BayNetworks.com (sc-mail2-hme0.corpwest.baynetworks.com [134.177.1.56]) by mailhost.corpeast.BayNetworks.COM (SMI-8.6/BNET-97/05/05-S) with SMTP id JAA27041; Wed, 11 Nov 1998 09:56:51 -0500 for Received: from gmorgan-pc (gmorgan-pc.corpwest.baynetworks.com [134.177.69.176]) by sc-mail2.corpwest.BayNetworks.com (Post.Office MTA v3.5.1 release 219 ID# 0-51848U14000L14000S0V35) with SMTP id com for ; Wed, 11 Nov 1998 06:53:16 -0800 From: George_Morgan@BayNetworks.COM (George Morgan) To: freebsd-scsi@FreeBSD.ORG Date: Wed, 11 Nov 1998 06:53:17 -0800 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Good Hard Drives.... X-mailer: Pegasus Mail for Win32 (v3.01b) Message-ID: <19981111145316.AAA19669@sc-mail2.corpwest.BayNetworks.com@gmorgan-pc.corpwest.baynetworks.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org So, with all this talk about having problems with the tagged command queue... Who makes SCSI hard drives with the best firmware??? I have an IBM Ultrastar 2XP in a system that I hope to migrate to 3.0 and I'd like to know what kind of problems to expect :) George Morgan Bay Networks gmorgan@baynetworks.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 11 08:48:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA06406 for freebsd-scsi-outgoing; Wed, 11 Nov 1998 08:48:51 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA06400 for ; Wed, 11 Nov 1998 08:48:49 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id JAA17379; Wed, 11 Nov 1998 09:47:54 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199811111647.JAA17379@panzer.plutotech.com> Subject: Re: Good Hard Drives.... In-Reply-To: <19981111145316.AAA19669@sc-mail2.corpwest.BayNetworks.com@gmorgan-pc.corpwest.baynetworks.com> from George Morgan at "Nov 11, 98 06:53:17 am" To: George_Morgan@BayNetworks.COM (George Morgan) Date: Wed, 11 Nov 1998 09:47:54 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org George Morgan wrote... > So, with all this talk about having problems with the tagged > command queue... > > Who makes SCSI hard drives with the best firmware??? I have an > IBM Ultrastar 2XP in a system that I hope to migrate to 3.0 and I'd > like to know what kind of problems to expect :) I would say get IBM or Seagate disks. I doubt you'll have any trouble with your Ultrastar 2XP. And yes, by not mentioning various other drive vendors, I mean that it is probably a good idea to stay away from them. 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 Nov 12 07:25:26 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17346 for freebsd-scsi-outgoing; Thu, 12 Nov 1998 07:25:26 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from amalthea.salford.ac.uk (amalthea.salford.ac.uk [146.87.255.61]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA17300 for ; Thu, 12 Nov 1998 07:24:30 -0800 (PST) (envelope-from M.S.Powell@ais.salford.ac.uk) Received: (qmail 9379 invoked by alias); 12 Nov 1998 15:22:58 -0000 Received: (qmail 9358 invoked from network); 12 Nov 1998 15:22:57 -0000 Received: from plato.salford.ac.uk (146.87.255.76) by amalthea.salford.ac.uk with SMTP; 12 Nov 1998 15:22:57 -0000 Received: (qmail 13724 invoked by alias); 12 Nov 1998 15:22:57 -0000 Delivered-To: catchall-freebsd-scsi@FreeBSD.ORG Received: (qmail 13698 invoked by uid 141); 12 Nov 1998 15:22:56 -0000 Date: Thu, 12 Nov 1998 15:22:56 +0000 (GMT) From: Mark Powell To: "Kenneth D. Merry" cc: Mark Powell , freebsd-scsi@FreeBSD.ORG Subject: Re: 3.0 scsi parity and tagged openings problems In-Reply-To: <199811110423.VAA14192@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <72bbsi$p22$1@ananke.salford.ac.uk>, Kenneth D. Merry wrote: >Mark Powell wrote... >> Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 64 >> Nov 10 15:48:55 titan /kernel: (da3:ahc1:0:4:0): tagged openings now 63 >> Nov 10 15:48:58 titan /kernel: (da2:ahc0:0:1:0): tagged openings now 2 >> Nov 10 15:48:58 titan /kernel: (da2:ahc0:0:1:0): tagged openings now 2 > >It looks like one of your disks at least doesn't like tagged queueing. The >interesting thing is that it's one of the drives that is *not* in your CCD >array. (you said that only da1 and da3 are in the array) Were you doing >I/O to da2 at the time? What's on that disk? I would suggest that you: OOps, that was me recreating the output that had scrolled off the screen. Sorry :) That last drive should have been da1, of course. >The reason you probably didn't see this on 2.2.7-stable is because the old >SCSI layer only allowed 4 tags at a time to go to a drive. It may be that >your drive has trouble whenever its transaction queue gets full and it has >to return queue full status. The old SCSI code probably wouldn't have >filled the transaction queue, but CAM will send as many transactions as it >can to the disk. Okay, Kenneth, looks like I need Seagate or IBM drives in future. Many thanks for your advice. >Kenneth Merry >ken@plutotech.com Mark Powell - System Administrator (UNIX) - Clifford Whitworth Building A.I.S., University of Salford, Salford, Manchester, UK. Tel: +44 161 295 5936 Fax: +44 161 295 5888 Email: M.S.Powell@ais.salfrd.ac.uk www.pgp.com (for PGP key) NO SPAM please: Spell salford correctly to reply to me. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 12 09:42:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA01344 for freebsd-scsi-outgoing; Thu, 12 Nov 1998 09:42:01 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA01310 for ; Thu, 12 Nov 1998 09:41:56 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id JAA25468; Thu, 12 Nov 1998 09:36:05 -0800 Date: Thu, 12 Nov 1998 09:36:05 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Johan Granlund cc: dmlb@ragnet.demon.co.uk, freebsd-scsi@FreeBSD.ORG Subject: Where I'm at for the tape driver for the 8200 changes... In-Reply-To: <199811082132.WAA03498@phoenix.granlund.nu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The smoke test change I made for tape seemed to work fine for 8200's. Justin had a lot of suggestions about what to change about tape and I had a lot of opinions and I'll be getting to all of this very soon. The problem that has hung me up over the last couple of days (interleaving this all with a number of other tasks) is that dump sometimes either mysteriously hangs while writing to my DLT and I'm trying to trace what's occurred there, or the system has panic'd while doing a dump. There is some speculation and evidence that for the latter case I/O errors from a filesystem's disk can cause this panic, but that hasn't been definitively tested out. Have patience. I really am working on this- it's just each test run takes an hour or more and if we're dealing with a 'flakey' several runs have to occur for me to trap a particular error. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 12 23:05:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA02319 for freebsd-scsi-outgoing; Thu, 12 Nov 1998 23:05:40 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA02312 for ; Thu, 12 Nov 1998 23:05:34 -0800 (PST) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.9.1/8.9.1) id BAA19891; Fri, 13 Nov 1998 01:05:13 -0600 (CST) Date: Fri, 13 Nov 1998 01:05:13 -0600 From: Dan Nelson To: David Kelly , scsi@FreeBSD.ORG Subject: Re: turning off tagged queuing with CAM? Message-ID: <19981113010513.A19694@emsphone.com> References: <199811102303.RAA12327@n4hhe.ampr.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.94.3i In-Reply-To: <199811102303.RAA12327@n4hhe.ampr.org>; from "David Kelly" on Tue Nov 10 17:03:51 GMT 1998 X-OS: FreeBSD 2.2.7-STABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In the last episode (Nov 10), David Kelly said: > "Kenneth D. Merry" writes: > > Matthew Jacob wrote... > > > This needs to be better documented. > > > > Well, it's documented in the SCSI specs. :) I guess I could put > > something in the camcontrol man page about it. > > It would be nice if there was more documentation or reference on SCSI > mode pages for mere mortals. Without asking on a list such as this > few would have figured out what DQue does. The closest we could come > would be in /usr/share/misc/scsi_modes. But there only the name and > location of the flags, and not what they do. Scitex Digital Video (scitexdv.com) used to have a copy of the SCSI-2 Specification (Draft X3T9.2 Rev 10L) online, but it seems to have gone down. Altavista says there is a mirror at http://www.uni-mainz.de/~tacke/scsi/SCSI2.html , and I also made a mirror, available at http://dan.emsphone.com/scsi/ . It details all the mode pages, and all the SCSI commands for each device type. For example, mode page 0x0A is explained in section 8.3.3.1. It's accurate enough for me to have written an ANSI tape reading/writing program in DOS (with code to toggle compression), using this and Ralf Brown's Interrupt list for the ASPI calls :) -Dan Nelson dnelson@emsphone.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 13 00:30:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08796 for freebsd-scsi-outgoing; Fri, 13 Nov 1998 00:30:59 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08791 for ; Fri, 13 Nov 1998 00:30:57 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id AAA28173; Fri, 13 Nov 1998 00:29:33 -0800 Date: Fri, 13 Nov 1998 00:29:32 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Dan Nelson cc: David Kelly , scsi@FreeBSD.ORG Subject: Re: turning off tagged queuing with CAM? In-Reply-To: <19981113010513.A19694@emsphone.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 The documentation for SCSI is very easy to obtain. Check out www.symbios.com. On Fri, 13 Nov 1998, Dan Nelson wrote: > In the last episode (Nov 10), David Kelly said: > > "Kenneth D. Merry" writes: > > > Matthew Jacob wrote... > > > > This needs to be better documented. > > > > > > Well, it's documented in the SCSI specs. :) I guess I could put > > > something in the camcontrol man page about it. > > > > It would be nice if there was more documentation or reference on SCSI > > mode pages for mere mortals. Without asking on a list such as this > > few would have figured out what DQue does. The closest we could come > > would be in /usr/share/misc/scsi_modes. But there only the name and > > location of the flags, and not what they do. > > Scitex Digital Video (scitexdv.com) used to have a copy of the SCSI-2 > Specification (Draft X3T9.2 Rev 10L) online, but it seems to have gone > down. Altavista says there is a mirror at > http://www.uni-mainz.de/~tacke/scsi/SCSI2.html , and I also made a > mirror, available at http://dan.emsphone.com/scsi/ . > > It details all the mode pages, and all the SCSI commands for each > device type. For example, mode page 0x0A is explained in section > 8.3.3.1. > > It's accurate enough for me to have written an ANSI tape > reading/writing program in DOS (with code to toggle compression), using > this and Ralf Brown's Interrupt list for the ASPI calls :) > > -Dan Nelson > dnelson@emsphone.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 13 08:47:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01116 for freebsd-scsi-outgoing; Fri, 13 Nov 1998 08:47:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from laker.net (jet.laker.net [205.245.74.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01110 for ; Fri, 13 Nov 1998 08:47:12 -0800 (PST) (envelope-from sfriedri@laker.net) Received: from nt (digital-pbi-130.laker.net [208.0.233.30]) by laker.net (8.9.0/8.9.LAKERNET.NO-SPAM.SPAMMERS.AND.RELAYS.WILL.BE.TRACKED.AND.PROSECUTED.) with SMTP id LAA05775; Fri, 13 Nov 1998 11:46:33 -0500 Message-Id: <199811131646.LAA05775@laker.net> From: "Steve Friedrich" To: "Dan Nelson" , "mjacob@feral.com" Cc: "David Kelly" , "scsi@FreeBSD.ORG" Date: Fri, 13 Nov 1998 10:25:55 -0500 Reply-To: "Steve Friedrich" X-Mailer: PMMail 98 Professional (2.01.1600) For Windows NT (4.0.1381;3) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: turning off tagged queuing with CAM? Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 13 Nov 1998 00:29:32 -0800 (PST), Matthew Jacob wrote: >The documentation for SCSI is very easy to obtain. Check out >www.symbios.com. When I went to that site, I found: See Symbios SCSI Information at the LSI Logic Web Site As part of the integration of the former Symbios, Inc. into LSI Logic, Symbios SCSI product information is now available on the LSI Logic web site. Soon, when you visit this page, you will automatically be directed to this same information on the LSI Logic site. And on the LSI Logic web site, they aren't currently accepting new registrations for the tech library... Unix systems measure "uptime" in years, Winblows measures it in minutes. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 13 08:52:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA01517 for freebsd-scsi-outgoing; Fri, 13 Nov 1998 08:52:18 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA01509 for ; Fri, 13 Nov 1998 08:52:13 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with SMTP id IAA29155; Fri, 13 Nov 1998 08:50:49 -0800 Date: Fri, 13 Nov 1998 08:50:47 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Steve Friedrich cc: Dan Nelson , David Kelly , "scsi@FreeBSD.ORG" Subject: Re: turning off tagged queuing with CAM? In-Reply-To: <199811131646.LAA05775@laker.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry- I should have been more precise. Try: http://www.symbios.com/x3t10 I've been wondering whether or not that LSI will pull the plug on this site. This site exists on an informal basis. Don't abuse it. On Fri, 13 Nov 1998, Steve Friedrich wrote: > On Fri, 13 Nov 1998 00:29:32 -0800 (PST), Matthew Jacob wrote: > > >The documentation for SCSI is very easy to obtain. Check out > >www.symbios.com. > > When I went to that site, I found: > See Symbios SCSI Information at the LSI Logic Web Site > As part of the integration of the former Symbios, Inc. > into LSI Logic, Symbios SCSI > product information is now available on the LSI Logic > web site. Soon, when you visit this > page, you will automatically be directed to this same > information on the LSI Logic site. > > And on the LSI Logic web site, they aren't currently accepting new > registrations for the tech library... > > > Unix systems measure "uptime" in years, Winblows measures it in minutes. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 14 13:43:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18065 for freebsd-scsi-outgoing; Sat, 14 Nov 1998 13:43:24 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from cenotaph.snafu.de (gw-deadnet.snafu.de [195.21.6.33]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id NAA18060 for ; Sat, 14 Nov 1998 13:43:16 -0800 (PST) (envelope-from root@deadline.snafu.de) Received: by cenotaph.snafu.de from deadline.snafu.de using smtp id m0zenSG-000RhxC; Sat, 14 Nov 1998 22:42:04 +0100 (CET) (Smail-3.2.0.101 1997-Dec-17 #1) Received: by deadline.snafu.de id m0zenRt-000cJUC; Sat, 14 Nov 1998 22:41:41 +0100 (CET) (Smail-3.2.0.101 1997-Dec-17 #1) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Sat, 14 Nov 1998 22:41:41 +0100 (CET) From: "Andreas S. Wetzel" To: scsi@FreeBSD.ORG Subject: Support for Mylex Flashpoint Adapters? Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! --- Recently I was wondering if the bt driver in FreeBSD 3.0-RELEASE supports the Mylex (aka Buslogic) BT-930/BT-950 (Flashpoint) series of host adapters. The heading of all relevant files do only list the BT-956/BT-958 (MultiMaster) hostadapters, but the file /sys/pci/bt_pci.c defines a PCI_DEVICE_ID_BUSLOGIC_FLASHPOINT macro which seems otherwise unused? Are there concrete plans for supporting the flashpoint adapters? Are they downward compatible to the MultiMaster Adapters? Also I would be interested in the technical details and differences between the MultiMaster and Flashpoint adapters. Does anyone have experiences with these controllers using FreeBSD? Thanks in advance. Mickey -- (__) (@@) Andreas S. Wetzel Mail: mickey@deadline.snafu.de /-------\/ Utrechter Strasse 41 Web: http://cenotaph.snafu.de/ / | || 13347 Berlin Fon: <+4930> 456 066 90 * ||----|| Germany Fax: <+4930> 456 066 91/92 ~~ ~~ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 14 16:45:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03641 for freebsd-scsi-outgoing; Sat, 14 Nov 1998 16:45:02 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from jli.com (jli.com [199.2.111.1]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA03636 for ; Sat, 14 Nov 1998 16:45:00 -0800 (PST) (envelope-from trost@cloud.rain.com) Received: (qmail 26750 invoked by uid 4); 15 Nov 1998 00:44:38 -0000 Received: (qmail 469 invoked from network); 15 Nov 1998 00:43:55 -0000 Received: from softdnserror (HELO cloud.rain.com) (127.0.0.1) by softdnserror with SMTP; 15 Nov 1998 00:43:55 -0000 To: scsi@FreeBSD.ORG Subject: tape hang problem MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <465.911090634.1@cloud.rain.com> Date: Sat, 14 Nov 1998 16:43:54 -0800 Message-ID: <466.911090634@cloud.rain.com> From: Bill Trost Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have one single (irreplaceable backup )-: ) tape that is causing my system to hang (i.e., nothing is running, although the console tty driver still responds) when it reaches block 24342 of the file on the tape. It is doing this with an Adaptec 2940 and a -current kernel from 12 Novemeber at 10:00 PST. It was also doing it with an aic-based SCSI card and a kernel that just predated CAM (as well as some earlier predecessors). The tape drive is an ARCHIVE Python. Attached to the end of this message is the complete dmesg output. When the system hangs, it prints several messages like the following on the console: (da0:ahc0:0:0:...) SCB 0x11 - timed out in datain phase, SCSISIGI == 0x44 SEQADDR == 0x110, SSTATI == 0x2 It does this for several different SCB's, then starts saying swap_pager: indefinite wait buffer: device 0x30401, blkno 296, size 4096 which is presamably an indication that the entire SCSI bus (at least) has collapsed (there is swap on da0). Also I had to make the following change at the top of /sys/pci/ahc_pci.c:ahc_pci_attach to make my particular SCSI card and motherboard work together (this code is from Justin Gibbs, more or less): u_int32_t csize_lattime = pci_conf_read(config_id, CSIZE_LATTIME); printf("csize_lattime = %lx\n", csize_lattime); csize_lattime &= ~CACHESIZE; pci_conf_write(config_id, CSIZE_LATTIME, csize_lattime); I poked around with ddb after the hang occured, but what little I saw did not suggest to me any particular problem (how do you find out the interrupt mask under ddb, anyhow?). In any case -- any ideas as to what is causing this problem, and better yet, what to do about it? FreeBSD 3.0-BETA #2: Tue Oct 13 10:21:06 PDT 1998 x@grey.cloud.rain.com:/usr/src/sys/compile/GREY Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 89814501 Hz CPU: AMD-K5(tm) Processor (89.81-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x514 Stepping=4 Features=0x21bf real memory = 33554432 (32768K bytes) config> quit avail memory = 30236672 (29528K bytes) Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 ahc0: rev 0x01 int a irq 7 on pci0.17.0 csize_lattime = 4004 ahc0: aic7880 Single Channel A, SCSI Id=7, 16/255 SCBs vga0: rev 0xd3 int a irq 10 on pci0.20.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 ed1 at 0x300-0x31f irq 5 on isa ed1: address 00:40:05:11:50:43, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 1033MB (2116800 sectors), 2100 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2): wd2: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface ccd0-1: Concatenated disk drivers Waiting 3 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 4 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 5.0MB/s transfers (5.0MHz, offset 15) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 10.0MB/s transfers (10.0MHz, offset 15), Tagged Queueing Enabled da0: 1682MB (3445129 512 byte sectors: 255H 63S/T 214C) changing root device to da0s2a cd0 at ahc0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 5.681MB/s transfers (5.681MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present WARNING: / was not properly dismounted (da1:ahc0:0:1:0): SCB 0x4 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x0 SEQADDR == 0xb SSTAT1 == 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. 1 SCBs aborted da1 at ahc0 bus 0 target 1 lun 0 da1: Removable Direct Access SCSI2 device da1: 10.0MB/s transfers (10.0MHz, offset 15) da1: 1021MB (2091050 512 byte sectors: 64H 32S/T 1021C) ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 14 17:49:24 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA08147 for freebsd-scsi-outgoing; Sat, 14 Nov 1998 17:49:24 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from n4hhe.ampr.org (tnt1-224.HiWAAY.net [208.147.147.224]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA08142 for ; Sat, 14 Nov 1998 17:49:22 -0800 (PST) (envelope-from dkelly@n4hhe.ampr.org) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by n4hhe.ampr.org (8.9.1/8.9.1) with ESMTP id TAA28467; Sat, 14 Nov 1998 19:48:47 -0600 (CST) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199811150148.TAA28467@n4hhe.ampr.org> X-Mailer: exmh version 2.0.2 2/24/98 To: Bill Trost cc: scsi@FreeBSD.ORG From: David Kelly Subject: Re: tape hang problem In-reply-to: Message from Bill Trost of "Sat, 14 Nov 1998 16:43:54 PST." <466.911090634@cloud.rain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Nov 1998 19:48:46 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill Trost writes: > sa0 at ahc0 bus 0 target 4 lun 0 > sa0: Removable Sequential Access SCSI2 > device > sa0: 5.0MB/s transfers (5.0MHz, offset 15) I have slightly different firmware in mine. Wonder what the difference is? Haven't given it a good workout under 3.0 yet. My 2940 is the first generation, and has nothing but these two tape drives attached. sa0 at ahc0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI2 device sa0: 5.0MB/s transfers (5.0MHz, offset 15) sa1 at ahc0 bus 0 target 6 lun 0 sa1: Removable Sequential Access SCSI2 device sa1: 5.0MB/s transfers (5.0MHz, offset 15) -- 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 Sat Nov 14 23:51:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA01872 for freebsd-scsi-outgoing; Sat, 14 Nov 1998 23:51:25 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA01867 for ; Sat, 14 Nov 1998 23:51:23 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id IAA16354; Sun, 15 Nov 1998 08:50:40 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id IAA07942; Sun, 15 Nov 1998 08:31:48 +0100 (MET) (envelope-from j) Message-ID: <19981115083147.59967@uriah.heep.sax.de> Date: Sun, 15 Nov 1998 08:31:47 +0100 From: J Wunsch To: Bill Trost Cc: scsi@FreeBSD.ORG Subject: Re: tape hang problem Reply-To: Joerg Wunsch References: <466.911090634@cloud.rain.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <466.911090634@cloud.rain.com>; from Bill Trost on Sat, Nov 14, 1998 at 04:43:54PM -0800 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Bill Trost wrote: > When the system hangs, it prints several messages like the following on > the console: > > (da0:ahc0:0:0:...) SCB 0x11 - timed out in datain phase, SCSISIGI == 0x44 > SEQADDR == 0x110, > SSTATI == 0x2 > > It does this for several different SCB's, then starts saying I've seen such behaviour (incidentally also on an Archive Python) for a tape where i ultimately found that the drive that recorded the tape has too much adjustment tolerance to my own tape drive. Apparently, the drive then can't read the requested block immediately, and starts retensioning the tape (as i would guess from the sound). This operation takes too much time for the timeout in the driver, so it eventually aborts the operation before the drive completed. The drive would most likely only have told me that the requested block is unreadable anyway, and i'm afraid the same's true for you. (However, in case your tape is a dump(8) tape, restore(8) should at least have a way to continue without this block iff the driver wouldn't abort.) -- 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