From owner-freebsd-scsi Sun Apr 15 10:49:28 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from Mail6.nc.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id DF12C37B43E for ; Sun, 15 Apr 2001 10:49:14 -0700 (PDT) (envelope-from thomas@stromberg.org) Received: from localhost ([66.26.231.27]) by Mail6.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 15 Apr 2001 12:44:58 -0400 Date: Sun, 15 Apr 2001 12:45:32 -0400 Content-Type: text/plain; format=flowed; charset=us-ascii Mime-Version: 1.0 (Apple Message framework v387) From: Thomas Stromberg To: freebsd-scsi@freebsd.org X-Mailer: Apple Mail (2.387) Content-Transfer-Encoding: 7bit Subject: da0: invalid sector size 520 Message-ID: <01c345844160f41FE6@Mail6.nc.rr.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to add the following Seagate Barracuda to my FreeBSD box: da0: Fixed Direct Access SCSI-2 device da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled da0: 4087MB (8242659 520 byte sectors: 255H 63S/T 513C) notice the 520 byte sectors? This occurs whenever I try to do any operations (sysinstall, dd, disklabel) with da0: da0: invalid sector size 520 The machine is 5.0-CURRENT as of Wednesday, but I dont think that will matter much. Is there something I'm missing? Please CC any replies to me, I'm not on this particular list. / Thomas Stromberg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 15 10:57:55 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 83BB537B42C for ; Sun, 15 Apr 2001 10:57:53 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.22 #1) id 14oqmV-000Aa2-00; Sun, 15 Apr 2001 17:57:51 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.3/8.11.2) id f3FI1PS78073; Sun, 15 Apr 2001 20:01:25 +0200 (CEST) (envelope-from wkb) Date: Sun, 15 Apr 2001 20:01:25 +0200 From: Wilko Bulte To: Thomas Stromberg Cc: freebsd-scsi@freebsd.org Subject: Re: da0: invalid sector size 520 Message-ID: <20010415200125.C77682@freebie.demon.nl> References: <01c345844160f41FE6@Mail6.nc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <01c345844160f41FE6@Mail6.nc.rr.com>; from thomas@stromberg.org on Sun, Apr 15, 2001 at 12:45:32PM -0400 X-OS: FreeBSD 4.3-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Apr 15, 2001 at 12:45:32PM -0400, Thomas Stromberg wrote: > I'm trying to add the following Seagate Barracuda to my FreeBSD box: > > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da0: 4087MB (8242659 520 byte sectors: 255H 63S/T 513C) > > notice the 520 byte sectors? This occurs whenever I try to do any > operations (sysinstall, dd, disklabel) with da0: > > da0: invalid sector size 520 Guessing: Could be a disk from a machine that uses hardware RAID or extra checksumming in the 8 bytes beyond 512 bytes/sector. You can try to reformat the drive while first selecting 512 bytes/sector. W/ -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte FreeBSD/alpha Powered http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 15 11:15:16 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail5.nc.rr.com (fe5.southeast.rr.com [24.93.67.52]) by hub.freebsd.org (Postfix) with ESMTP id 51F0B37B422 for ; Sun, 15 Apr 2001 11:15:14 -0700 (PDT) (envelope-from thomas@stromberg.org) Received: from localhost ([66.26.231.27]) by mail5.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 15 Apr 2001 14:15:11 -0400 Date: Sun, 15 Apr 2001 14:15:45 -0400 From: Thomas Stromberg Content-Type: text/plain; format=flowed; charset=us-ascii Subject: Re: da0: invalid sector size 520 Cc: freebsd-scsi@freebsd.org To: Wilko Bulte X-Mailer: Apple Mail (2.387) In-Reply-To: <20010415200125.C77682@freebie.demon.nl> Mime-Version: 1.0 (Apple Message framework v387) Content-Transfer-Encoding: 7bit Message-ID: <0653a1115180f41FE5@mail5.nc.rr.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sunday, April 15, 2001, at 02:01 PM, Wilko Bulte wrote: > On Sun, Apr 15, 2001 at 12:45:32PM -0400, Thomas Stromberg wrote: >> I'm trying to add the following Seagate Barracuda to my FreeBSD box: >> >> da0: Fixed Direct Access SCSI-2 device >> da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing >> Enabled >> da0: 4087MB (8242659 520 byte sectors: 255H 63S/T 513C) >> >> notice the 520 byte sectors? This occurs whenever I try to do any >> operations (sysinstall, dd, disklabel) with da0: >> >> da0: invalid sector size 520 > > Guessing: > > Could be a disk from a machine that uses hardware RAID or extra > checksumming > in the 8 bytes beyond 512 bytes/sector. You can try to reformat the > drive > while first selecting 512 bytes/sector. > > W/ Not sure where this disk came from, got it from Ebay. The problem I have is I'm getting this error while trying to reformat it.. from sysinstall, disklabel, newfs, and dd.. Any advice on how to re-format this disk that I'm missing? I'm not very experieced with SCSI stuff. BTW, I'm not on the SCSI mailing list, so any replies should be CC'd to me / Thomas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 15 11:26:23 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id DCEA137B43F for ; Sun, 15 Apr 2001 11:26:20 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA18297; Sun, 15 Apr 2001 11:26:10 -0700 Date: Sun, 15 Apr 2001 11:26:09 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Thomas Stromberg Cc: Wilko Bulte , freebsd-scsi@FreeBSD.ORG Subject: Re: da0: invalid sector size 520 In-Reply-To: <0653a1115180f41FE5@mail5.nc.rr.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 is a drive that was in a raid unit. Reformat to to 512 byte sectors. There's some camcontrol magic for doing this, but, frankly, I just use Solaris. On Sun, 15 Apr 2001, Thomas Stromberg wrote: > > On Sunday, April 15, 2001, at 02:01 PM, Wilko Bulte wrote: > > > On Sun, Apr 15, 2001 at 12:45:32PM -0400, Thomas Stromberg wrote: > >> I'm trying to add the following Seagate Barracuda to my FreeBSD box: > >> > >> da0: Fixed Direct Access SCSI-2 device > >> da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing > >> Enabled > >> da0: 4087MB (8242659 520 byte sectors: 255H 63S/T 513C) > >> > >> notice the 520 byte sectors? This occurs whenever I try to do any > >> operations (sysinstall, dd, disklabel) with da0: > >> > >> da0: invalid sector size 520 > > > > Guessing: > > > > Could be a disk from a machine that uses hardware RAID or extra > > checksumming > > in the 8 bytes beyond 512 bytes/sector. You can try to reformat the > > drive > > while first selecting 512 bytes/sector. > > > > W/ > > Not sure where this disk came from, got it from Ebay. The problem I have > is I'm getting this error while trying to reformat it.. from sysinstall, > disklabel, newfs, and dd.. Any advice on how to re-format this disk that > I'm missing? I'm not very experieced with SCSI stuff. > > BTW, I'm not on the SCSI mailing list, so any replies should be CC'd to > me > > / Thomas > > 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 Sun Apr 15 11:48:41 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 447BF37B449 for ; Sun, 15 Apr 2001 11:48:38 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 14orVh-0002uE-00; Sun, 15 Apr 2001 11:44:33 -0700 Date: Sun, 15 Apr 2001 11:44:10 -0700 (PDT) From: Tom Samplonius To: Thomas Stromberg Cc: Wilko Bulte , freebsd-scsi@freebsd.org Subject: Re: da0: invalid sector size 520 In-Reply-To: <0653a1115180f41FE5@mail5.nc.rr.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 Sun, 15 Apr 2001, Thomas Stromberg wrote: > Not sure where this disk came from, got it from Ebay. The problem I have > is I'm getting this error while trying to reformat it.. from sysinstall, > disklabel, newfs, and dd.. Any advice on how to re-format this disk that > I'm missing? I'm not very experieced with SCSI stuff. disklabel, newsfs and dd don't format the disk though. You will need to do a low-level SCSI re-format in order to change the sector size to 512 bytes. If you read the manpage for "camcontrol", the section on the format option specifically mentions changing the sector size. If looks like you should change the sector size in the modepage, then issue the format command. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 15 12:11: 8 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from post.mail.nl.demon.net (post-11.mail.nl.demon.net [194.159.73.21]) by hub.freebsd.org (Postfix) with ESMTP id 63B9837B423 for ; Sun, 15 Apr 2001 12:11:05 -0700 (PDT) (envelope-from wkb@freebie.demon.nl) Received: from [212.238.54.101] (helo=freebie.demon.nl) by post.mail.nl.demon.net with smtp (Exim 3.22 #1) id 14orvL-000EcY-00; Sun, 15 Apr 2001 19:11:04 +0000 Received: (from wkb@localhost) by freebie.demon.nl (8.11.3/8.11.2) id f3FJEbg78668; Sun, 15 Apr 2001 21:14:37 +0200 (CEST) (envelope-from wkb) Date: Sun, 15 Apr 2001 21:14:37 +0200 From: Wilko Bulte To: Thomas Stromberg Cc: freebsd-scsi@freebsd.org Subject: Re: da0: invalid sector size 520 Message-ID: <20010415211437.A78654@freebie.demon.nl> References: <20010415200125.C77682@freebie.demon.nl> <0653a1115180f41FE5@mail5.nc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <0653a1115180f41FE5@mail5.nc.rr.com>; from thomas@stromberg.org on Sun, Apr 15, 2001 at 02:15:45PM -0400 X-OS: FreeBSD 4.3-RC X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Apr 15, 2001 at 02:15:45PM -0400, Thomas Stromberg wrote: > > On Sunday, April 15, 2001, at 02:01 PM, Wilko Bulte wrote: > > > On Sun, Apr 15, 2001 at 12:45:32PM -0400, Thomas Stromberg wrote: > >> I'm trying to add the following Seagate Barracuda to my FreeBSD box: > >> > >> da0: Fixed Direct Access SCSI-2 device > >> da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing > >> Enabled > >> da0: 4087MB (8242659 520 byte sectors: 255H 63S/T 513C) > >> > >> notice the 520 byte sectors? This occurs whenever I try to do any > >> operations (sysinstall, dd, disklabel) with da0: > >> > >> da0: invalid sector size 520 > > > > Guessing: > > > > Could be a disk from a machine that uses hardware RAID or extra > > checksumming > > in the 8 bytes beyond 512 bytes/sector. You can try to reformat the > > drive > > while first selecting 512 bytes/sector. > > > > W/ > > Not sure where this disk came from, got it from Ebay. The problem I have > is I'm getting this error while trying to reformat it.. from sysinstall, > disklabel, newfs, and dd.. Any advice on how to re-format this disk that > I'm missing? I'm not very experieced with SCSI stuff. See the man page for 'camcontrol'. You need to give it a low-level SCSI format. Things like 'dd' etc don't do that for you.. W/ -- | / o / / _ Arnhem, The Netherlands email: wilko@freebsd.org |/|/ / / /( (_) Bulte FreeBSD/alpha Powered http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 15 12:40:51 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail8.nc.rr.com (fe8.southeast.rr.com [24.93.67.55]) by hub.freebsd.org (Postfix) with ESMTP id 6FD7A37B424 for ; Sun, 15 Apr 2001 12:40:47 -0700 (PDT) (envelope-from thomas@stromberg.org) Received: from localhost ([66.26.231.27]) by mail8.nc.rr.com with Microsoft SMTPSVC(5.5.1877.537.53); Sun, 15 Apr 2001 15:37:33 -0400 Date: Sun, 15 Apr 2001 15:41:18 -0400 From: Thomas Stromberg Content-Type: text/plain; format=flowed; charset=us-ascii Subject: Changing b/s via camcontrol (was invalid sector size 520) Cc: Wilko Bulte , freebsd-scsi@freebsd.org To: Tom Samplonius X-Mailer: Apple Mail (2.387) In-Reply-To: Mime-Version: 1.0 (Apple Message framework v387) Content-Transfer-Encoding: 7bit Message-ID: <0c9113337190f41FE8@mail8.nc.rr.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > If you read the manpage for "camcontrol", the section on the format > option specifically mentions changing the sector size. If looks like > you > should change the sector size in the modepage, then issue the format > command. Thanks for the heads up on camcontrol. It looks exactly like what I need. I went through /usr/share/misc/scsi_modes to see what modepage needs to be edited for bytes/sector. It looked like 0x05 is what I needed. So, I tried: # camcontrol modepage da0 -m 5 -e camcontrol: error sending mode sense command I then check the list of valid mode pages camcontrol finds: # camcontrol modepage da0 -l 0x01 Read-Write Error Recovery Page 0x02 Disconnect-Reconnect Page 0x03 Format Device Page 0x04 Rigid Disk Drive Geometry Page 0x07 Verify Error Recovery Page 0x08 Caching Page 0x0a Control Mode Page 0x0c Notch and Partition Page 0x00 Vendor-Specific 0x00 Vendor-Specific I noticed that codepage 0x03 contains sector/bytes data (and no others): root@subedei (/home/helix)# camcontrol modepage da0 -m3 Tracks per Zone: 21 Alternate Sectors per Zone: 9 Alternate Tracks per Zone: 0 Alternate Tracks per Logical Unit: 21 Sectors per Track: 106 Data Bytes per Physical Sector: 520 ... So I try to use -e to edit it, but I only see Tracks per Zone, Alternate Sectors per Zone, and Alternate Tracks per Logical Unit in my editor. I just tried this with another Seagate drive on a production server of ours and camcontrol returned "no editable entries". Am I in the right direction? Thanks for your help btw. Once this gets settled, I'll be sure to add it to the bsdwiki for the next person. Unfortunatly, my Sun U10 is scsi-less. I've got an HP9000 and an Indigo^2 with SCSI, but no OS (two of these drives, which also have this problem, are so I can get them up and running again). SGI's fx.ARCS doesn't seem to be too friendly to the sector size either. / Thomas Stromberg To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Apr 15 16:49:49 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from wantadilla.lemis.com (wantadilla.lemis.com [192.109.197.80]) by hub.freebsd.org (Postfix) with ESMTP id 93A4237B424 for ; Sun, 15 Apr 2001 16:49:45 -0700 (PDT) (envelope-from grog@lemis.com) Received: by wantadilla.lemis.com (Postfix, from userid 1004) id D2D156ACB7; Mon, 16 Apr 2001 09:19:43 +0930 (CST) Date: Mon, 16 Apr 2001 09:19:43 +0930 From: Greg Lehey To: Thomas Stromberg Cc: freebsd-scsi@freebsd.org Subject: Re: da0: invalid sector size 520 Message-ID: <20010416091943.A9649@wantadilla.lemis.com> References: <01c345844160f41FE6@Mail6.nc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <01c345844160f41FE6@Mail6.nc.rr.com>; from thomas@stromberg.org on Sun, Apr 15, 2001 at 12:45:32PM -0400 Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-418-838-708 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sunday, 15 April 2001 at 12:45:32 -0400, Thomas Stromberg wrote: > I'm trying to add the following Seagate Barracuda to my FreeBSD box: > > da0: Fixed Direct Access SCSI-2 device > da0: 10.000MB/s transfers (10.000MHz, offset 15), Tagged Queueing Enabled > da0: 4087MB (8242659 520 byte sectors: 255H 63S/T 513C) > > notice the 520 byte sectors? This occurs whenever I try to do any > operations (sysinstall, dd, disklabel) with da0: > > da0: invalid sector size 520 > > The machine is 5.0-CURRENT as of Wednesday, but I dont think that will > matter much. Is there something I'm missing? Please CC any replies to > me, I'm not on this particular list. Try this: ======================================================================== Yup, there's some other way to change it. Set the current values, then immediately issue a format command: # camcontrol cmd da1 -v -c "15 10 0 0 v:i1 0" 12 -o 12 "0 0 0 8 0 0:i3 0 v:i3" 512 # camcontrol cmd -n da -u 1 -v -t 7200 -c "4 0 0 0 0 0" # camcontrol modepage da1 -m 3 Tracks per Zone: 19 Alternate Sectors per Zone: 12 Alternate Tracks per Zone: 0 Alternate Tracks per Logical Unit: 38 Sectors per Track: 84 Data Bytes per Physical Sector: 512 Interleave: 1 Track Skew Factor: 13 Cylinder Skew Factor: 22 SSEC: 0 HSEC: 1 RMB: 0 SURF: 0 ======================================================================== Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 16 1:50:25 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 241B937B43F for ; Mon, 16 Apr 2001 01:50:21 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id KAA08565 for freebsd-scsi@freebsd.org; Mon, 16 Apr 2001 10:50:20 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3G8kjU13869; Mon, 16 Apr 2001 10:46:45 +0200 (MET DST) (envelope-from j) Date: Mon, 16 Apr 2001 10:46:45 +0200 (MET DST) Message-Id: <200104160846.f3G8kjU13869@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden 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 References: <0c9113337190f41FE8@mail8.nc.rr.com> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Changing b/s via camcontrol (was invalid sector size 520) X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thomas Stromberg wrote: > I noticed that codepage 0x03 contains sector/bytes data (and no others): > > root@subedei (/home/helix)# camcontrol modepage da0 -m3 > Tracks per Zone: 21 > Alternate Sectors per Zone: 9 > Alternate Tracks per Zone: 0 > Alternate Tracks per Logical Unit: 21 > Sectors per Track: 106 > Data Bytes per Physical Sector: 520 > ... > > So I try to use -e to edit it, but I only see Tracks per Zone, Alternate > Sectors per Zone, and Alternate Tracks per Logical Unit in my editor. That means you cannot edit that value on this mode page. Use the cook recipe Greg Lehey posted. Unfortunately, the vendors never agreed about the procedure to reformat with another sector size (if possible at all, not all support it). Some use modepage 3, some use the blocksize value in the modepage header. Your drive is most likely of this type, and Greg's posting contains the solution. I'm not sure whether it would be possible to replace the second camcontrol in Greg's posting by a simple "camcontrol format da0" instead, or whether camcontrol format does some modepage fiddling of its own. It's vital for the success that both SCSI commands, the one setting the blocksize and the FORMAT UNIT command, are issued without intervening commands. > Unfortunatly, my Sun U10 is > scsi-less. Any 53c875-based card should work in it. I've seen cheap Tekram DC390 controllers work in it. Note that it (IMHO) doesn't work with any other Symbios Logic chip, only the '875. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 16 5:29:26 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from vision.vc3.com (vision.vc3.com [64.28.197.2]) by hub.freebsd.org (Postfix) with ESMTP id A27D137B42C for ; Mon, 16 Apr 2001 05:29:24 -0700 (PDT) (envelope-from tatemj@vision.vc3.com) Received: from localhost (tatemj@localhost) by vision.vc3.com (8.9.3/8.9.1) with ESMTP id IAA31948 for ; Mon, 16 Apr 2001 08:29:24 -0400 Date: Mon, 16 Apr 2001 08:29:24 -0400 (EDT) From: Jason Tatem To: freebsd-scsi@freebsd.org Subject: Compaq Proliant 4000/NCR 53c710 scsi Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I recently began playing with a Compaq Proliant 4000 server that I got a while back. It has an integrated NCR 53c710 EISA scsi controller...was wondering if there's any plans to support this controller in FreeBSD (HW compatibility list mentions several NCR chips, but not this particular one). Any help would be greatly appreciated. Thanks, Jason Tatem -- -------------------------------------------------------------------- Jason Tatem "When I was a kid, my mother told me VC3, Inc. not to stare at the sun. So once, tatemj@vc3.com when I was 6, I did." --Max, "Pi" -------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 16 9:41:49 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id A381937B423; Mon, 16 Apr 2001 09:41:39 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f3GGeis11580; Mon, 16 Apr 2001 10:41:25 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200104161641.f3GGeis11580@aslan.scsiguy.com> To: Alessandro de Manzano Cc: scsi@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: memory mapped I/O on adaptec ? In-Reply-To: Your message of "Sat, 14 Apr 2001 22:47:07 +0200." <20010414224707.C42900@libero.sunshine.ale> Date: Mon, 16 Apr 2001 10:40:44 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Hi! > >I've just noticed in LINT the "AHC_ALLOW_MEMIO" option, and I wonder >how much this setting would speed the Adaptec controllers. It depends on how saturated your PCI bus. The MEMIO option avoids some processor stalling when the PCI bus is not very idle. You would likely see a decrease in system time, not an increase in performance. >LINT says also that it's not default because does not work on some >motherboards. There is maybe a list of these of something ? Trying is >the only option I've to know if it will work on my motherboards ? :-) You will know almost instantly if it doesn't work. The controller will freeze up. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 16 12:43:43 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (Postfix) with ESMTP id 1380937B424 for ; Mon, 16 Apr 2001 12:43:33 -0700 (PDT) (envelope-from mreimer@vpop.net) Received: from vpop.net ([209.102.16.48]) by boromir.vpop.net (8.11.2/8.11.2) with ESMTP id f3GJhIn86076 for ; Mon, 16 Apr 2001 12:43:18 -0700 (PDT) (envelope-from mreimer@vpop.net) Message-ID: <3ADB4B77.B0F21EA0@vpop.net> Date: Mon, 16 Apr 2001 12:43:51 -0700 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: scsi@freebsd.org Subject: Errors: no active SCB for reconnecting target Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org What do these errors mean? Apr 15 07:33:00 ring /kernel: ahc0:A:13: no active SCB for reconnecting target - issuing BUS DEVICE RESET Apr 15 07:33:00 ring /kernel: SAVED_SCSIID == 0xd7, SAVED_LUN == 0x0, ARG_1 == 0x2a ACCUM = 0x17 Apr 15 07:33:00 ring /kernel: SEQ_FLAGS == 0x0, SCBPTR == 0x1, BTT == 0xff, SINDEX == 0x31 Apr 15 07:33:00 ring /kernel: SCSIID == 0x0, SCB_SCSIID == 0x17, SCB_LUN == 0x0, SCB_TAG == 0x2a, SCB_CONTROL == 0x64 Apr 15 07:33:00 ring /kernel: SCSIBUSL == 0x2a, SCSISIGI == 0xe6 Apr 15 07:33:00 ring /kernel: SXFRCTL0 == 0x88 Apr 15 07:33:00 ring /kernel: SEQCTL == 0x10 Apr 15 07:33:00 ring /kernel: ahc0: Dumping Card State at SEQADDR 0x1a7 Apr 15 07:33:00 ring /kernel: SCSISEQ = 0x12, SBLKCTL = 0xa, SSTAT0 0x2 Apr 15 07:33:00 ring /kernel: SCB count = 130 Apr 15 07:33:00 ring /kernel: Kernel NEXTQSCB = 35 Apr 15 07:33:00 ring /kernel: Card NEXTQSCB = 35 Apr 15 07:33:00 ring /kernel: QINFIFO entries: Apr 15 07:33:00 ring /kernel: Waiting Queue entries: Apr 15 07:33:00 ring /kernel: Disconnected Queue entries: 1:42 10:98 2:97 28:4 30:37 Apr 15 07:33:00 ring /kernel: QOUTFIFO entries: Apr 15 07:33:00 ring /kernel: Sequencer Free SCB List: 22 25 19 20 12 21 27 8 15 4 23 5 14 18 17 0 16 7 31 26 24 29 11 6 3 9 13 Apr 15 07:33:00 ring /kernel: Pending list: 98 97 4 37 42 Apr 15 07:33:00 ring /kernel: Kernel Free SCB list: 49 70 39 1 31 92 54 111 18 55 47 2 116 112 106 82 61 46 34 24 26 52 76 32 118 123 95 58 84 62 41 115 117 60 110 8 23 103 43 89 13 86 100 119 30 20 27 68 57 128 74 5 81 94 83 44 45 22 102 16 50 19 48 114 80 69 38 21 126 12 7 101 78 113 17 28 56 75 53 109 10 87 107 59 99 125 72 129 127 25 64 63 66 15 108 67 88 11 90 29 65 36 40 14 9 73 104 77 85 3 79 91 33 96 124 93 6 71 51 0 105 122 121 120 Apr 15 07:33:00 ring /kernel: ahc0: Bus Device Reset on A:13. 0 SCBs aborted Apr 15 07:34:00 ring /kernel: (da1:ahc0:0:1:0): SCB 0x2a - timed out while idle, SEQADDR == 0x8 Apr 15 07:34:00 ring /kernel: STACK == 0x3, 0x110, 0x166, 0xef Apr 15 07:34:00 ring /kernel: SXFRCTL0 == 0x80 Apr 15 07:34:00 ring /kernel: ahc0: Dumping Card State at SEQADDR 0x8 Apr 15 07:34:01 ring /kernel: SCSISEQ = 0x12, SBLKCTL = 0xa, SSTAT0 0x0 Apr 15 07:34:01 ring /kernel: SCB count = 130 Apr 15 07:34:01 ring /kernel: Kernel NEXTQSCB = 54 Apr 15 07:34:01 ring /kernel: Card NEXTQSCB = 54 Apr 15 07:34:01 ring /kernel: QINFIFO entries: Apr 15 07:34:01 ring /kernel: Waiting Queue entries: Apr 15 07:34:01 ring /kernel: Disconnected Queue entries: 1:42 10:98 2:97 Apr 15 07:34:01 ring /kernel: QOUTFIFO entries: Apr 15 07:34:01 ring /kernel: Sequencer Free SCB List: 8 30 6 14 4 17 12 7 31 15 21 3 26 13 0 29 22 18 11 23 9 19 24 20 16 27 28 25 5 Apr 15 07:34:01 ring /kernel: Pending list: 98 97 42 Apr 15 07:34:01 ring /kernel: Kernel Free SCB list: 26 61 112 92 39 58 76 31 123 46 70 35 32 115 84 34 110 41 62 8 82 23 95 60 52 116 117 47 55 118 37 24 106 49 1 4 2 111 18 103 43 89 13 86 100 119 30 20 27 68 57 128 74 5 81 94 83 44 45 22 102 16 50 19 48 114 80 69 38 21 126 12 7 101 78 113 17 28 56 75 53 109 10 87 107 59 99 125 72 129 127 25 64 63 66 15 108 67 88 11 90 29 65 36 40 14 9 73 104 77 85 3 79 91 33 96 124 93 6 71 51 0 105 122 121 120 Apr 15 07:34:01 ring /kernel: sg[0] - Addr 0xd637000 : Length 4096 Apr 15 07:34:01 ring /kernel: sg[1] - Addr 0x878000 : Length 4096 Apr 15 07:34:01 ring /kernel: (da1:ahc0:0:1:0): Queuing a BDR SCB Apr 15 07:34:01 ring /kernel: (da1:ahc0:0:1:0): Bus Device Reset Message Sent Apr 15 07:34:01 ring /kernel: (da1:ahc0:0:1:0): no longer in timeout, status = 34b Apr 15 07:34:01 ring /kernel: ahc0: Bus Device Reset on A:1. 3 SCBs aborted Apr 15 10:15:22 ring /kernel: ahc0:A:12: no active SCB for reconnecting target - issuing BUS DEVICE RESET Apr 15 10:15:22 ring /kernel: SAVED_SCSIID == 0xc7, SAVED_LUN == 0x0, ARG_1 == 0x46 ACCUM = 0x7 Apr 15 10:15:22 ring /kernel: SEQ_FLAGS == 0x0, SCBPTR == 0x1e, BTT == 0xff, SINDEX == 0x31 Apr 15 10:15:22 ring /kernel: SCSIID == 0x0, SCB_SCSIID == 0x7, SCB_LUN == 0x0, SCB_TAG == 0x46, SCB_CONTROL == 0x64 Apr 15 10:15:22 ring /kernel: SCSIBUSL == 0x46, SCSISIGI == 0xe6 Apr 15 10:15:22 ring /kernel: SXFRCTL0 == 0x88 Apr 15 10:15:22 ring /kernel: SEQCTL == 0x10 Apr 15 10:15:22 ring /kernel: ahc0: Dumping Card State at SEQADDR 0x1a7 Apr 15 10:15:22 ring /kernel: SCSISEQ = 0x12, SBLKCTL = 0xa, SSTAT0 0x2 Apr 15 10:15:22 ring /kernel: SCB count = 130 Apr 15 10:15:22 ring /kernel: Kernel NEXTQSCB = 48 Apr 15 10:15:22 ring /kernel: Card NEXTQSCB = 48 Apr 15 10:15:22 ring /kernel: QINFIFO entries: Apr 15 10:15:22 ring /kernel: Waiting Queue entries: Apr 15 10:15:22 ring /kernel: Disconnected Queue entries: 30:70 12:11 14:15 13:107 23:20 0:23 25:16 9:27 28:31 5:5 4:4 Apr 15 10:15:22 ring /kernel: QOUTFIFO entries: Apr 15 10:15:22 ring /kernel: Sequencer Free SCB List: 6 18 16 21 26 17 3 29 1 19 20 22 24 8 27 7 2 31 15 10 11 Apr 15 10:15:22 ring /kernel: Pending list: 15 11 107 20 23 16 27 31 5 70 4 Apr 15 10:15:22 ring /kernel: Kernel Free SCB list: 46 10 102 45 36 38 66 65 118 54 39 64 104 99 87 41 119 30 49 69 116 129 88 76 62 83 40 127 123 128 61 35 115 25 47 18 111 126 14 53 17 68 19 110 98 50 94 37 22 82 63 109 117 57 24 52 114 100 92 75 32 29 42 60 90 103 78 84 89 112 55 9 26 74 34 125 97 43 56 8 73 106 1 21 12 108 101 58 2 67 13 81 95 86 80 113 72 7 44 59 28 77 85 3 79 91 33 96 124 93 6 71 51 0 105 122 121 120 Apr 15 10:15:22 ring /kernel: ahc0: Bus Device Reset on A:12. 0 SCBs aborted Apr 15 10:16:23 ring /kernel: (da0:ahc0:0:0:0): SCB 0x4 - timed out while idle, SEQADDR == 0x8 Apr 15 10:16:23 ring /kernel: STACK == 0x3, 0x17c, 0x166, 0xef Apr 15 10:16:23 ring /kernel: SXFRCTL0 == 0x80 Apr 15 10:16:23 ring /kernel: ahc0: Dumping Card State at SEQADDR 0x8 Apr 15 10:16:24 ring /kernel: SCSISEQ = 0x12, SBLKCTL = 0xa, SSTAT0 0x20 Apr 15 10:16:24 ring /kernel: SCB count = 130 Apr 15 10:16:24 ring /kernel: Kernel NEXTQSCB = 82 Apr 15 10:16:24 ring /kernel: Card NEXTQSCB = 82 Apr 15 10:16:24 ring /kernel: QINFIFO entries: Apr 15 10:16:24 ring /kernel: Waiting Queue entries: Apr 15 10:16:24 ring /kernel: Disconnected Queue entries: 26:88 30:70 5:5 4:4 Apr 15 10:16:24 ring /kernel: QOUTFIFO entries: Apr 15 10:16:24 ring /kernel: Sequencer Free SCB List: 10 7 13 25 15 31 23 9 12 18 1 24 17 3 14 20 8 16 6 28 0 2 19 22 21 29 27 11 Apr 15 10:16:24 ring /kernel: Pending list: 88 5 70 4 Apr 15 10:16:24 ring /kernel: Kernel Free SCB list: 62 111 16 126 46 83 57 27 49 94 30 25 87 127 118 110 50 41 40 37 17 69 47 53 76 52 22 117 98 11 63 107 39 23 104 18 119 61 116 64 45 129 38 99 20 36 68 48 10 102 15 109 128 54 123 14 115 31 35 65 66 114 24 19 100 92 75 32 29 42 60 90 103 78 84 89 112 55 9 26 74 34 125 97 43 56 8 73 106 1 21 12 108 101 58 2 67 13 81 95 86 80 113 72 7 44 59 28 77 85 3 79 91 33 96 124 93 6 71 51 0 105 122 121 120 Apr 15 10:16:24 ring /kernel: sg[0] - Addr 0xc7e4000 : Length 4096 Apr 15 10:16:24 ring /kernel: sg[1] - Addr 0x3725000 : Length 4096 Apr 15 10:16:25 ring /kernel: sg[2] - Addr 0xa0c6000 : Length 4096 Apr 15 10:16:25 ring /kernel: sg[3] - Addr 0xe4a7000 : Length 4096 Apr 15 10:16:25 ring /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Apr 15 10:16:25 ring /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Apr 15 10:16:25 ring /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 34b Apr 15 10:16:25 ring /kernel: ahc0: Bus Device Reset on A:0. 3 SCBs aborted This machine has an L440GX motherboard with onboard Ultra2 adapter, plus another PCI 2940: ahc0: port 0x1400-0x14ff mem 0xf4100000-0xf4100fff irq 11 at device 12.0 on pci0 aic7896/97: Wide Channel A, SCSI Id=7, 32/255 SCBs ahc1: port 0x1800-0x18ff mem 0xf4101000-0xf4101fff irq 11 at device 12.1 on pci0 aic7896/97: Wide Channel B, SCSI Id=7, 32/255 SCBs ahc2: port 0x2000-0x20ff mem 0xf4103000-0xf4103fff irq 5 at device 16.0 on pci0 aic7870: Wide Channel A, SCSI Id=7, 16/255 SCBs SCSI devices: sa0 at ahc2 bus 0 target 0 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 15) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) ch0 at ahc2 bus 0 target 1 lun 0 ch0: Removable Changer SCSI-2 device ch0: 3.300MB/s transfers ch0: 8 slots, 1 drive, 1 picker, 0 portals da2 at ahc1 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 40.000MB/s transfers (20.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) The disks are all connected with Adaptec LVD cables. The machine hasn't hung since these errors were reported, but we were having problems earlier in the month. Thanks in advance for your help. Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 16 19:34:32 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id C4B9C37B43C for ; Mon, 16 Apr 2001 19:34:29 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f3H2Xos19986; Mon, 16 Apr 2001 20:34:21 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200104170234.f3H2Xos19986@aslan.scsiguy.com> To: Matthew Reimer Cc: scsi@FreeBSD.ORG Subject: Re: Errors: no active SCB for reconnecting target In-Reply-To: Your message of "Mon, 16 Apr 2001 12:43:51 PDT." <3ADB4B77.B0F21EA0@vpop.net> Date: Mon, 16 Apr 2001 20:33:50 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >What do these errors mean? It probably indicates a driver bug. What version of FreeBSD are you running? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Apr 17 11:36:47 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (Postfix) with ESMTP id 7987937B42C for ; Tue, 17 Apr 2001 11:36:31 -0700 (PDT) (envelope-from mreimer@vpop.net) Received: from vpop.net ([209.102.16.48]) by boromir.vpop.net (8.11.2/8.11.2) with ESMTP id f3HIZun69563; Tue, 17 Apr 2001 11:35:56 -0700 (PDT) (envelope-from mreimer@vpop.net) Message-ID: <3ADC8D2D.99125878@vpop.net> Date: Tue, 17 Apr 2001 11:36:29 -0700 From: Matthew Reimer Organization: VPOP Technologies, Inc. X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Justin T. Gibbs" Cc: scsi@FreeBSD.ORG Subject: Re: Errors: no active SCB for reconnecting target References: <200104170234.f3H2Xos19986@aslan.scsiguy.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Justin T. Gibbs" wrote: > > >What do these errors mean? > > It probably indicates a driver bug. What version of FreeBSD > are you running? Whoops, sorry about that. This machine is running 4.2-stable built April 5. Version numbers follow. Matt ahc_eisa.c: $FreeBSD: src/sys/dev/aic7xxx/ahc_eisa.c,v 1.15.2.4 2001/03/12 14:57:40 gibbs Exp $ ahc_pci.c: $FreeBSD: src/sys/dev/aic7xxx/ahc_pci.c,v 1.29.2.6 2001/03/12 14:57:40 gibbs Exp $ aic7770.c: $Id: //depot/src/aic7xxx/aic7770.c#8 $ $FreeBSD: src/sys/dev/aic7xxx/aic7770.c,v 1.1.2.3 2001/03/12 14:57:40 gibbs Exp $ aic7xxx.c: $Id: //depot/src/aic7xxx/aic7xxx.c#34 $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx.c,v 1.41.2.18 2001/03/19 15:09:24 gibbs Exp $ aic7xxx.h: $Id: //depot/src/aic7xxx/aic7xxx.h#22 $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx.h,v 1.16.2.11 2001/03/12 18:46:33 gibbs Exp $ aic7xxx.reg: $Id: //depot/src/aic7xxx/aic7xxx.reg#14 $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx.reg,v 1.20.2.9 2001/03/19 15:09:26 gibbs Exp $ aic7xxx.seq: $Id: //depot/src/aic7xxx/aic7xxx.seq#24 $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx.seq,v 1.94.2.13 2001/03/21 05:00:00 gibbs Exp $ aic7xxx_93cx6.c: $Id: //depot/src/aic7xxx/aic7xxx_93cx6.c#7 $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx_93cx6.c,v 1.8.2.3 2001/03/12 14:57:44 gibbs Exp $ aic7xxx_93cx6.h: $Id: //depot/src/aic7xxx/aic7xxx_93cx6.h#5 $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx_93cx6.h,v 1.7.2.2 2001/01/07 22:50:47 gibbs Exp $ aic7xxx_freebsd.c: $FreeBSD: src/sys/dev/aic7xxx/aic7xxx_freebsd.c,v 1.3.2.17 2001/03/12 14:57:44 gibbs Exp $ aic7xxx_freebsd.h: $FreeBSD: src/sys/dev/aic7xxx/aic7xxx_freebsd.h,v 1.2.2.5 2001/03/12 14:57:44 gibbs Exp $ aic7xxx_inline.h: $Id: //depot/src/aic7xxx/aic7xxx_inline.h#17 $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx_inline.h,v 1.2.2.9 2001/03/12 14:57:44 gibbs Exp $ aic7xxx_pci.c: $Id: //depot/src/aic7xxx/aic7xxx_pci.c#19 $ $FreeBSD: src/sys/dev/aic7xxx/aic7xxx_pci.c,v 1.2.2.10 2001/03/12 18:46:33 gibbs Exp $ aicasm.c: $Id: //depot/src/aic7xxx/aicasm/aicasm.c#6 $ $FreeBSD: src/sys/dev/aic7xxx/aicasm/aicasm.c,v 1.28.2.3 2001/01/07 22:52:35 gibbs Exp $ aicasm.h: $Id: //depot/src/aic7xxx/aicasm/aicasm.h#4 $ $FreeBSD: src/sys/dev/aic7xxx/aicasm/aicasm.h,v 1.11.2.2 2001/01/07 22:52:35 gibbs Exp $ aicasm_gram.y: $Id: //depot/src/aic7xxx/aicasm/aicasm_gram.y#6 $ $FreeBSD: src/sys/dev/aic7xxx/aicasm/aicasm_gram.y,v 1.11.2.3 2001/01/07 22:52:35 gibbs Exp $ aicasm_insformat.h: $Id: //depot/src/aic7xxx/aicasm/aicasm_insformat.h#4 $ $FreeBSD: src/sys/dev/aic7xxx/aicasm/aicasm_insformat.h,v 1.3.2.2 2001/01/07 22:52:36 gibbs Exp $ aicasm_scan.l: $Id: //depot/src/aic7xxx/aicasm/aicasm_scan.l#4 $ $FreeBSD: src/sys/dev/aic7xxx/aicasm/aicasm_scan.l,v 1.13.2.2 2001/01/07 22:52:36 gibbs Exp $ aicasm_symbol.c: $Id: //depot/src/aic7xxx/aicasm/aicasm_symbol.c#4 $ $FreeBSD: src/sys/dev/aic7xxx/aicasm/aicasm_symbol.c,v 1.11.2.2 2001/01/07 22:52:36 gibbs Exp $ aicasm_symbol.h: $Id: //depot/src/aic7xxx/aicasm/aicasm_symbol.h#4 $ $FreeBSD: src/sys/dev/aic7xxx/aicasm/aicasm_symbol.h,v 1.11.2.2 2001/01/07 22:52:36 gibbs Exp $ scsi_all.c: $FreeBSD: src/sys/cam/scsi/scsi_all.c,v 1.14.2.5 2001/02/24 19:25:30 gibbs Exp $ scsi_all.h: $FreeBSD: src/sys/cam/scsi/scsi_all.h,v 1.14.2.3 2000/08/14 05:42:33 kbyanc Exp $ scsi_cd.c: $FreeBSD: src/sys/cam/scsi/scsi_cd.c,v 1.31.2.7 2001/01/29 01:53:55 ken Exp $ scsi_cd.h: $FreeBSD: src/sys/cam/scsi/scsi_cd.h,v 1.2.6.1 2000/05/31 03:14:32 ken Exp $ scsi_ch.c: $FreeBSD: src/sys/cam/scsi/scsi_ch.c,v 1.20.2.2 2000/10/31 08:09:49 dwmalone Exp $ $NetBSD: ch.c,v 1.32 1998/01/12 09:49:12 thorpej Exp $ scsi_ch.h: $FreeBSD: src/sys/cam/scsi/scsi_ch.h,v 1.2.6.1 2000/08/03 00:50:59 peter Exp $ $NetBSD: scsi_changer.h,v 1.11 1998/02/13 08:28:32 enami Exp $ scsi_da.c: $FreeBSD: src/sys/cam/scsi/scsi_da.c,v 1.42.2.9 2001/01/18 00:28:47 n_hibma Exp $ scsi_da.h: $FreeBSD: src/sys/cam/scsi/scsi_da.h,v 1.3.2.2 2000/07/01 23:35:49 ken Exp $ scsi_dvcfg.h: $FreeBSD: src/sys/cam/scsi/scsi_dvcfg.h,v 1.1.2.1 2000/10/29 11:05:44 non Exp $ $NecBSD: scsi_dvcfg.h,v 1.4 1998/03/14 07:05:06 kmatsuda Exp $ scsi_low.c: $FreeBSD: src/sys/cam/scsi/scsi_low.c,v 1.1.2.2 2001/03/03 14:45:00 non Exp $ $NecBSD: scsi_low.c,v 1.24 1999/07/26 06:27:01 honda Exp $ scsi_low.h: $FreeBSD: src/sys/cam/scsi/scsi_low.h,v 1.1.2.3 2001/03/03 14:45:02 non Exp $ $NecBSD: scsi_low.h,v 1.24 1999/07/23 21:00:05 honda Exp $ scsi_low_pisa.c: $FreeBSD: src/sys/cam/scsi/scsi_low_pisa.c,v 1.2.2.2 2001/02/25 06:17:33 non Exp $ $NecBSD: scsi_low_pisa.c,v 1.13 1998/11/26 14:26:11 honda Exp $ scsi_low_pisa.h: $FreeBSD: src/sys/cam/scsi/scsi_low_pisa.h,v 1.2.2.1 2000/10/29 11:05:45 non Exp $ $NecBSD: scsi_low_pisa.h,v 1.3 1999/04/15 01:35:57 kmatsuda Exp $ scsi_message.h: $FreeBSD: src/sys/cam/scsi/scsi_message.h,v 1.1.6.3 2000/10/31 18:54:02 gibbs Exp $ scsi_pass.c: $FreeBSD: src/sys/cam/scsi/scsi_pass.c,v 1.19 2000/01/17 06:27:37 mjacob Exp $ scsi_pass.h: $FreeBSD: src/sys/cam/scsi/scsi_pass.h,v 1.3 1999/08/28 00:40:48 peter Exp $ scsi_pt.c: $FreeBSD: src/sys/cam/scsi/scsi_pt.c,v 1.17 2000/01/17 06:27:37 mjacob Exp $ scsi_pt.h: $FreeBSD: src/sys/cam/scsi/scsi_pt.h,v 1.2.2.1 2001/01/12 02:50:39 steve Exp $ scsi_sa.c: $FreeBSD: src/sys/cam/scsi/scsi_sa.c,v 1.45.2.7 2001/01/22 18:06:51 mjacob Exp $ scsi_sa.h: $FreeBSD: src/sys/cam/scsi/scsi_sa.h,v 1.6.2.2 2001/01/12 02:50:39 steve Exp $ scsi_ses.c: $FreeBSD: src/sys/cam/scsi/scsi_ses.c,v 1.8.2.2 2000/08/08 23:19:21 mjacob Exp $ scsi_ses.h: $FreeBSD: src/sys/cam/scsi/scsi_ses.h,v 1.2 2000/01/15 22:40:04 mjacob Exp $ scsi_targ_bh.c: $FreeBSD: src/sys/cam/scsi/scsi_targ_bh.c,v 1.4.2.4 2001/03/05 13:08:50 obrien Exp $ scsi_target.c: $FreeBSD: src/sys/cam/scsi/scsi_target.c,v 1.22.2.6 2001/03/05 13:08:50 obrien Exp $ scsi_targetio.h: $FreeBSD: src/sys/cam/scsi/scsi_targetio.h,v 1.5.2.2 2000/07/14 20:17:18 mjacob Exp $ ----- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Apr 17 12:50:19 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from crufty.research.bell-labs.com (crufty.research.bell-labs.com [204.178.16.49]) by hub.freebsd.org (Postfix) with SMTP id 9A84537B424 for ; Tue, 17 Apr 2001 12:50:16 -0700 (PDT) (envelope-from dharani@lucent.com) Received: from bronx.dnrc.bell-labs.com ([135.180.160.8]) by crufty; Tue Apr 17 15:47:08 EDT 2001 Received: from acme (acme [135.180.135.56]) by bronx.dnrc.bell-labs.com (8.9.3/8.9.3) with SMTP id PAA23018 for ; Tue, 17 Apr 2001 15:49:32 -0400 (EDT) Message-ID: <00db01c0c779$1cb702e0$3887b487@dnrc.belllabs.com> Reply-To: "Dharani Vilwanathan" From: "Dharani Vilwanathan" To: References: <200104170234.f3H2Xos19986@aslan.scsiguy.com> <3ADC8D2D.99125878@vpop.net> Subject: Tagged queuing Date: Tue, 17 Apr 2001 16:00:54 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have a couple of SCSI disks and Adaptec SCSI controller. I tried to access data blocks from the raw device in parallel using multiple threads and processes. I did succeed to some extent. So I was convinced that the tagged I/O works. Now, is there any way I can access the data blocks in parallel in a single thread/process? I am looking for a way to issue read requests in asynchronous/non-blocked fashion. Does aio_read(), aio_write(), etc. calls work? Is there any other way to do this? Any help is appreciated. Thanks dharani To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 18 4:38:33 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mailrelay2.alcatel.de (mailrelay2.alcatel.de [194.113.59.71]) by hub.freebsd.org (Postfix) with ESMTP id 4D1D837B424 for ; Wed, 18 Apr 2001 04:38:31 -0700 (PDT) (envelope-from A.Muellers@alcatel.de) Received: from ks.sel.alcatel.de (slsv0d.stgl.sel.alcatel.de [149.204.14.10]) by mailrelay2.alcatel.de (8.9.3/8.9.3) with ESMTP id NAA13636 for ; Wed, 18 Apr 2001 13:38:24 +0200 (MET DST) Received: from slsufn ([149.204.218.26] helo=slsufnt.stgl.sel.alcatel.de) by ks.sel.alcatel.de with esmtp (Exim 3.16) id 14pqI1-0001vn-00; Wed, 18 Apr 2001 13:38:29 +0200 Received: from sls6az ([149.204.253.201] helo=sls6az.stgl.sel.alcatel.de) by slsufnt.stgl.sel.alcatel.de with esmtp (Exim 2.12) id 14pqHy-0005Cy-00; Wed, 18 Apr 2001 13:38:26 +0200 Received: from localhost by sls6az.stgl.sel.alcatel.de (8.8.8+Sun/SMI-SVR4) id NAA09641; Wed, 18 Apr 2001 13:38:26 +0200 (MET DST) Date: Wed, 18 Apr 2001 13:38:26 +0200 (MET DST) From: Andreas Muellers Reply-To: A.Muellers@gmx.de To: freebsd-scsi@freebsd.org Subject: Adaptec slim scsi 1480 supported in current? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Alcanet-MTA-scanned-and-authorized: yes Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can anybody tell me whether this controller is or will be supported by FreeBSD or should I buy the old 1460 controller? thanx in advance A. M"ullers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 18 5:15: 3 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 39C2937B423 for ; Wed, 18 Apr 2001 05:14:59 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f3ICEts42441; Wed, 18 Apr 2001 06:14:55 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200104181214.f3ICEts42441@aslan.scsiguy.com> To: A.Muellers@gmx.de Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec slim scsi 1480 supported in current? In-Reply-To: Your message of "Wed, 18 Apr 2001 13:38:26 +0200." Date: Wed, 18 Apr 2001 06:14:55 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Can anybody tell me whether this controller is or will be supported >by FreeBSD or should I buy the old 1460 controller? It works for me. I do have some rather extensive cardbus modificiations on my system, but others have reported suceess as well. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 18 13:54:32 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id B6C6737B422 for ; Wed, 18 Apr 2001 13:54:28 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id WAA02215 for freebsd-scsi@FreeBSD.ORG; Wed, 18 Apr 2001 22:54:27 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3IKrta47169 for freebsd-scsi@FreeBSD.ORG; Wed, 18 Apr 2001 22:53:55 +0200 (MET DST) (envelope-from j) Date: Wed, 18 Apr 2001 22:53:55 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Subject: Re: Problem with current sa(4) driver Message-ID: <20010418225355.U688@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <20010414203925.A63281@uriah.heep.sax.de> <200104150504.f3F544s00932@aslan.scsiguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200104150504.f3F544s00932@aslan.scsiguy.com>; from gibbs@scsiguy.com on Sat, Apr 14, 2001 at 11:04:04PM -0600 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Justin T. Gibbs wrote: > While it is true that the sa driver should be filtering out this > particular case because there is no error, returning ERESTART for > NO_SENSE is also wrong. You should be able to fix that by changing > the table entry for that sense code in cam_periph.c. You mean, like this? Index: cam_periph.c =================================================================== RCS file: /home/ncvs/src/sys/cam/cam_periph.c,v retrieving revision 1.34 diff -c -r1.34 cam_periph.c *** cam_periph.c 2001/04/04 18:24:35 1.34 --- cam_periph.c 2001/04/17 17:46:11 *************** *** 1369,1374 **** --- 1369,1376 ---- switch (err_action & SS_MASK) { case SS_NOP: + error = 0; + break; case SS_RETRY: action_string = "Retrying Command"; error = ERESTART; Tried this, it fixes the problem with ILI's, sa(4) now properly returns a short read. However, it uncovers a new bug that was just waiting around... % dd if=/dev/sa0 of=/dev/null bs=10k dd: /dev/sa0: Input/output error ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 1+0 records in 1+0 records out 10240 bytes transferred in 70.992489 secs (144 bytes/sec) /var/log/messages says: (sa0:sym0:0:1:0): READ(06). CDB: 8 0 0 28 0 0 (sa0:sym0:0:1:0): CAM Status: SCSI Status Error (sa0:sym0:0:1:0): SCSI Status: Check Condition (sa0:sym0:0:1:0): NO SENSE info:2800 asc:0,1 (sa0:sym0:0:1:0): Filemark detected (sa0:sym0:0:1:0): Retries Exhausted So now, when hitting the EOM filemark, we get an EIO. Again, this looks like something where sa(4) should IMHO special-case the error decision, instead of relying on cam_periph_error() to DTRT (which it cannot). I tried to manually patch the return value of cam_periph_error() to 0 in kgdb, but this just gets me back at the second problem: % ps axl UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND ... 107 373 1 0 -8 0 244 33 cbwait DWE p0- 0:00.00 dd if=/dev/sa0 of=/dev/null bs=10 It sits there, and waits indefinately. I'm at a loss here to see why this happens. :-( > ERESTART means the error recovery code has already re-queued the > CCB to retry the operation. By ignoring this code, you are telling > the caller of saerror() to complete the command normally resulting in > an eventual release of this particular ccb back to the free pool. OK, understood, thanks for the explanation! -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 19 5:25:17 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from relay.ioffe.rssi.ru (relay.ioffe.rssi.ru [194.85.224.33]) by hub.freebsd.org (Postfix) with ESMTP id AC14037B424; Thu, 19 Apr 2001 05:25:06 -0700 (PDT) (envelope-from kopts@astro.ioffe.rssi.ru) Received: from astro.ioffe.rssi.ru (astro.ioffe.rssi.ru [194.85.229.130]) by relay.ioffe.rssi.ru (8.9.1/8.9.1) with ESMTP id QAA29263; Thu, 19 Apr 2001 16:24:57 +0400 (MSD) Received: by astro.ioffe.rssi.ru (8.9.3/Clnt-2.14-AS-eef) id QAA75606; Thu, 19 Apr 2001 16:24:24 +0400 (MSD) Date: Thu, 19 Apr 2001 16:24:24 +0400 (MSD) From: Alexey Koptsevich To: Mike Smith Cc: scsi@freebsd.org Subject: Re: IDE RAID In-Reply-To: <200103312051.f2VKp2300842@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Mike, Sorry for delay in reply :) > > Are ATA RAID controllers other than 3ware going to be supported by > > FreeBSD? I have not found any on your web-page. Unfortunately, 3ware > > products are not sold in Russia... > > Which products in particular were you interested in? > > I am waiting for a sample of the Promise RAID-5 controller before starting > work on it, but aside from that the other Promise and HPT controllers are > not actually RAID controllers at all (they are just ATA controllers with > some RAID software in the BIOS). Sure, only raid5 is interesting for me. Promise SuperTrak (raid5) controllers are available here. BWT, is 3ware supported by FreeBSD in raid5 mode? 'man twe' tells only about 0 and 1 somewhy. Thanks a lot, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 19 8:15:34 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from atlas.rccn.net (atlas.rccn.net [193.136.7.1]) by hub.freebsd.org (Postfix) with SMTP id 296CB37B423 for ; Thu, 19 Apr 2001 08:15:27 -0700 (PDT) (envelope-from jpsp@fccn.pt) Received: (qmail 90689 invoked from network); 19 Apr 2001 15:15:24 -0000 Received: from dhcp20.fccn.pt (HELO jpsp) (193.136.7.220) by atlas.rccn.net with SMTP; 19 Apr 2001 15:15:24 -0000 Message-ID: <027501c0c8e3$b0597d00$dc0788c1@jpsp> From: =?iso-8859-1?Q?Jo=E3o_Pagaime?= To: Cc: "Joao Pagaime" Subject: Mylex 170 - boot takes several minutes Date: Thu, 19 Apr 2001 16:16:20 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, I've installed a server with a Mylex 170 (doing RAID1) that seems to work fine, except for the boot of the OS, that pauses for about 5 minutes when "waiting for devices to settle". I've established that this pause is Mylex related, since booting with other controller has a normal boot time. Any help in fixing this glitch would be appreciated. Thanks, jp --Additional information: The OS is a FreeBSD 4.2-RELEASE the driver has this to say about the RAID sub-system, when booting: mly0: mem 0xfc000000-0xfc001fff \ irq 14 at device 2.1 on pci0 mly0: AcceleRAID 170 , 1 channel, firmware 6.00-1-00 \ (20000426), 32MB RAM da0 at mly0 bus 1 target 0 lun 0 and the driver“s version seems to be $FreeBSD: src/sys/dev/mly/mly.c,v 1.3.2.1 2000/10/27 \ 10:06:56 msmith Exp$ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 19 8:59:11 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id 9813D37B424 for ; Thu, 19 Apr 2001 08:59:03 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 14qGlf-0002ex-00; Thu, 19 Apr 2001 08:54:51 -0700 Date: Thu, 19 Apr 2001 08:54:49 -0700 (PDT) From: Tom Samplonius To: =?iso-8859-1?Q?Jo=E3o_Pagaime?= Cc: freebsd-scsi@freebsd.org Subject: Re: Mylex 170 - boot takes several minutes In-Reply-To: <027501c0c8e3$b0597d00$dc0788c1@jpsp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 19 Apr 2001, [iso-8859-1] Jo=E3o Pagaime wrote: > The OS is a >=20 > FreeBSD 4.2-RELEASE The mly driver in 4.3-RC is much better. It might fix this problem. Besides that, It is definitely much faster. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 19 9: 8:18 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail2.uniserve.com (mail2.uniserve.com [204.244.156.10]) by hub.freebsd.org (Postfix) with ESMTP id 2EC9737B505; Thu, 19 Apr 2001 09:08:10 -0700 (PDT) (envelope-from tom@uniserve.com) Received: from mail2.uniserve.com ([204.244.156.10]) by mail2.uniserve.com with esmtp (Exim 3.13 #1) id 14qGxz-00093k-00; Thu, 19 Apr 2001 09:07:35 -0700 Date: Thu, 19 Apr 2001 09:07:35 -0700 (PDT) From: Tom X-Sender: tom@athena.uniserve.ca To: Domas Mituzas Cc: freebsd-stable@freebsd.org, msmith@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: mly driver does not work with SCA in up-to-date 4.3 In-Reply-To: <20010419102313.P66974-100000@axis.tdd.lt> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 19 Apr 2001, Domas Mituzas wrote: > We've got Intel ISP2150 chasis with two quantum atlass 36g drives, > connected via SCA to mylex acceleraid 170 (firmware 6.x). > > Mylex logical volume was inicialized using automatic setup, cause it fully > satisfied our needs (fault-tolerant mirror). > > It always (during successful starts and not successful ones) showed us > > (probe15:mly0:1:0:0): MODE SENSE(06). CDB: 1a 0 a 0 14 0 > (probe15:mly0:1:0:0): ILLEGAL REQUEST asc:21,0 > (probe15:mly0:1:0:0): Logical block address out of range > > Unsuccessful starts included: > > (probe6:mly0:0:6:0): INQUIRY. CDB 12 1 80 0 ff 0 > (probe6:mly0:0:6:0): ILLEGAL REQUEST asc:24,0 > (probe6:mly0:0:6:0): Invalid field in CDB > > As far as I understand, 0:6:0 is SCA processor, identified by mylex bios > as: > > 0:06 Processor ESG-SHV SCA HBPM10 0.04 Good to know the ISP2150 has an intelligent SCSI backplane. Not every SCA system does. > So it seams, that mylex doesn't know how to work with it. Well, I've used FreeBSD with Mylex AccelRAID 352s on a number of IBM x340s with intelligent SCSI backplanes. It reports the physical device gone message: > mly0 physical device 0:6 gone > that is repeated several times. But it does not panic. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 19 9:41:45 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from axis.tdd.lt (axis.tdd.lt [193.219.211.5]) by hub.freebsd.org (Postfix) with ESMTP id EE82537B42C; Thu, 19 Apr 2001 09:41:38 -0700 (PDT) (envelope-from domas.mituzas@delfi.lt) Received: from localhost (midom@localhost) by axis.tdd.lt (8.11.1/8.11.1) with ESMTP id f3JGfFE49512; Thu, 19 Apr 2001 18:41:20 +0200 (EET) Date: Thu, 19 Apr 2001 18:41:15 +0200 (EET) From: Domas Mituzas X-X-Sender: To: Tom Cc: , , Subject: Re: mly driver does not work with SCA in up-to-date 4.3 In-Reply-To: Message-ID: <20010419183958.Q48822-100000@axis.tdd.lt> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, > But it does not panic. it did not panic. first time I saw was yesterday. there was a commit to cam subsystem two days ago. I didn't check if reversing the source solve the problem, but I'll try to do it asap (don't have access to those systems right now). Regards, Domas Mituzas To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 19 10:41:49 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 2255037B422 for ; Thu, 19 Apr 2001 10:41:46 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id MAA64479; Thu, 19 Apr 2001 12:41:28 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Thu, 19 Apr 2001 12:41:28 -0500 (CDT) From: Chris Dillon To: Tom Samplonius Cc: =?iso-8859-1?Q?Jo=E3o_Pagaime?= , Subject: Re: Mylex 170 - boot takes several minutes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 19 Apr 2001, Tom Samplonius wrote: > > > On Thu, 19 Apr 2001, [iso-8859-1] Joćo Pagaime wrote: > > > The OS is a > > > > FreeBSD 4.2-RELEASE > > > The mly driver in 4.3-RC is much better. It might fix this problem. > Besides that, It is definitely much faster. It doesn't fix that particular problem, at least not for me. The controller/driver was also causing a system panic for me shortly before root was mounted. I had some earlier kernels where everything worked just fine except for the long delay, and then a few days ago I attempted to update to the latest 4.3-RC and it still paniced on me. After attempting to go back to the known-working kernel I had copied off, it still caused panics. Weird. Maybe there is something stored in the controller configuration that is tickling the panic. Luckily I was doing RAID1 as well, so I crossed my fingers and attached the drives to the plain onboard Adaptec controller and they worked (just no RAID1 anymore). I'd get a coredump for Mike Smith, but it doesn't want to dump the core onto the RAID array at that point. Some day I'll stick another drive in there just for that purpose on the on-board controller. Its a production system and I have to stick around really late to take it down, thats the only reason it hasn't been done already. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 19 12:47:22 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id C5EBA37B423 for ; Thu, 19 Apr 2001 12:47:18 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f3JJnge01789; Thu, 19 Apr 2001 12:49:43 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104191949.f3JJnge01789@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Alexey Koptsevich Cc: scsi@freebsd.org Subject: Re: IDE RAID In-reply-to: Your message of "Thu, 19 Apr 2001 16:24:24 +0400." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Apr 2001 12:49:42 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > Are ATA RAID controllers other than 3ware going to be supported by > > > FreeBSD? I have not found any on your web-page. Unfortunately, 3ware > > > products are not sold in Russia... > > > > Which products in particular were you interested in? > > > > I am waiting for a sample of the Promise RAID-5 controller before starting > > work on it, but aside from that the other Promise and HPT controllers are > > not actually RAID controllers at all (they are just ATA controllers with > > some RAID software in the BIOS). > > Sure, only raid5 is interesting for me. Promise SuperTrak (raid5) > controllers are available here. Hmm. RAID5 isn't really all that wonderful; you pay a high price in both cost and performance to do all those XOR calculations. > BWT, is 3ware supported by FreeBSD in raid5 mode? > 'man twe' tells only about 0 and 1 somewhy. Yes, it is. I haven't had any time lately to test it, but it's known to work. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 19 14:12: 3 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from dirty.research.bell-labs.com (dirty.research.bell-labs.com [204.178.16.6]) by hub.freebsd.org (Postfix) with SMTP id 61B6E37B43C for ; Thu, 19 Apr 2001 14:11:58 -0700 (PDT) (envelope-from dharani@lucent.com) Received: from bronx.dnrc.bell-labs.com ([135.180.160.8]) by dirty; Thu Apr 19 17:10:53 EDT 2001 Received: from acme (acme [135.180.135.56]) by bronx.dnrc.bell-labs.com (8.9.3/8.9.3) with SMTP id RAA27180; Thu, 19 Apr 2001 17:10:49 -0400 (EDT) Message-ID: <004c01c0c916$d5ac8290$3887b487@dnrc.belllabs.com> Reply-To: "Dharani Vilwanathan" From: "Dharani Vilwanathan" To: "Dharani Vilwanathan" , Subject: Resend: Tagged queuing Date: Thu, 19 Apr 2001 17:22:27 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Since I didnt get any response to this request, I am resending it. Can someone give some pointers at least? Or can someone tell me which mailing list would be appropriate for this question? Thanks dharani > I have a couple of SCSI disks and Adaptec SCSI controller. I tried to access > data blocks from the raw device in parallel using multiple threads and > processes. I did succeed to some extent. So I was convinced that the tagged > I/O works. Now, is there any way I can access the data blocks in parallel in > a single thread/process? I am looking for a way to issue read requests in > asynchronous/non-blocked fashion. Does aio_read(), aio_write(), etc. calls > work? Is there any other way to do this? > > Any help is appreciated. > > Thanks > dharani > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 19 14:13:54 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 93A1837B446 for ; Thu, 19 Apr 2001 14:13:50 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id OAA11337; Thu, 19 Apr 2001 14:13:48 -0700 Date: Thu, 19 Apr 2001 14:13:48 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Dharani Vilwanathan Cc: scsi@FreeBSD.ORG Subject: Re: Resend: Tagged queuing In-Reply-To: <004c01c0c916$d5ac8290$3887b487@dnrc.belllabs.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 > > a single thread/process? I am looking for a way to issue read requests in > > asynchronous/non-blocked fashion. Does aio_read(), aio_write(), etc. calls > > work? Is there any other way to do this? Wrong list. Try questions@FreeBSD.org. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 19 15:35:12 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from cage.tse-online.de (cage.tse-online.de [194.97.69.170]) by hub.freebsd.org (Postfix) with SMTP id 9BEC737B422 for ; Thu, 19 Apr 2001 15:35:08 -0700 (PDT) (envelope-from braukmann@tse-online.de) Received: (qmail 43259 invoked by uid 1000); 19 Apr 2001 22:35:05 -0000 Date: Fri, 20 Apr 2001 00:35:05 +0200 From: Andreas Braukmann To: scsi@freebsd.org Subject: Re: IDE RAID Message-ID: <20010420003505.G33303@cage.tse-online.de> References: <200104191949.f3JJnge01789@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104191949.f3JJnge01789@mass.dis.org>; from msmith@freebsd.org on Thu, Apr 19, 2001 at 12:49:42PM -0700 Organization: TSE GmbH - Neue Medien Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, On Thu, Apr 19, 2001 at 12:49:42PM -0700, Mike Smith wrote: > > BWT, is 3ware supported by FreeBSD in raid5 mode? > > 'man twe' tells only about 0 and 1 somewhy. > > Yes, it is. I haven't had any time lately to test it, but it's known to > work. Yes, it just works. But the 3ware's current implementation seems to be not that efficient (compared to lowend SCSI-RAID-controllers like the Mylex 160/170 e.g.). My observation so far: RAID 0+1 => the 3ware (with 4 IBM drives) clearly outperforms the Mylex. The Mylex seems not be able to keep up with the speed of 4 modern SCSI harddrives (IBM DTYS or even with the older DNES). RAID 5 => the Mylex 170 clearly outperforms the 3ware. Sorry, I didn't archived my bonnie and rawio results :(. The conclusion (regarding cost/performance ratio) was pretty clear: Our new webserver machine got an 3Ware Escalade 6400 driving a RAID 0+1 Array. -Andreas -- : Anti-Spam Petition: http://www.politik-digital.de/spam/ : : PGP-Key: http://www.tse-online.de/~ab/public-key : : Key fingerprint: 12 13 EF BC 22 DD F4 B6 3C 25 C9 06 DC D3 45 9B : To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 19 21:27:59 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id E3C2B37B43C for ; Thu, 19 Apr 2001 21:27:51 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f3K2Edu18850; Thu, 19 Apr 2001 19:14:40 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104200214.f3K2Edu18850@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: =?iso-8859-1?Q?Jo=E3o_Pagaime?= Cc: freebsd-scsi@freebsd.org Subject: Re: Mylex 170 - boot takes several minutes In-reply-to: Your message of "Thu, 19 Apr 2001 16:16:20 BST." <027501c0c8e3$b0597d00$dc0788c1@jpsp> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Thu, 19 Apr 2001 19:14:39 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > = > I've installed a server with a Mylex 170 (doing RAID1) that > seems to work fine, except for the boot of the OS, that pauses > for about 5 minutes when "waiting for devices to settle". You need to boot with -v to see what's going on at this point; CAM is = probably having minor conniptions with some peripheral. -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 19 21:28: 2 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 1C5F637B423 for ; Thu, 19 Apr 2001 21:27:56 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f3K1llu17658; Thu, 19 Apr 2001 18:47:50 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104200147.f3K1llu17658@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Chris Dillon Cc: Tom Samplonius , =?iso-8859-1?Q?Jo=E3o_Pagaime?= , freebsd-scsi@freebsd.org Subject: Re: Mylex 170 - boot takes several minutes In-reply-to: Your message of "Thu, 19 Apr 2001 12:41:28 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Thu, 19 Apr 2001 18:47:46 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > The mly driver in 4.3-RC is much better. It might fix this problem= =2E > > Besides that, It is definitely much faster. > = > It doesn't fix that particular problem, at least not for me. The > controller/driver was also causing a system panic for me shortly > before root was mounted. I had some earlier kernels where everything > worked just fine except for the long delay, and then a few days ago I > attempted to update to the latest 4.3-RC and it still paniced on me. I've had another report of this, involving a smart/managed backplane. = Does this feature in your configuration as well? Regards, Mike -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 19 21:28: 3 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 1A59137B43F for ; Thu, 19 Apr 2001 21:27:57 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f3K0URu00650; Thu, 19 Apr 2001 17:30:30 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104200030.f3K0URu00650@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andreas Braukmann Cc: scsi@freebsd.org Subject: Re: IDE RAID In-reply-to: Your message of "Fri, 20 Apr 2001 00:35:05 +0200." <20010420003505.G33303@cage.tse-online.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Apr 2001 17:30:26 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Thu, Apr 19, 2001 at 12:49:42PM -0700, Mike Smith wrote: > > > BWT, is 3ware supported by FreeBSD in raid5 mode? > > > 'man twe' tells only about 0 and 1 somewhy. > > > > Yes, it is. I haven't had any time lately to test it, but it's known to > > work. > > Yes, it just works. But the 3ware's current implementation seems > to be not that efficient (compared to lowend SCSI-RAID-controllers > like the Mylex 160/170 e.g.). This is unsurprising. Most of the SCSI RAID controllers have 66MHz or faster i960 processors with dedicated XOR acceleration hardware, wheras the 3ware controller uses a 25Mhz 16-bit processor. 3ware's RAID5 support is there primarily as a checklist item; RAID5 just doesn't make cost-effective sense for their market. You're better off using a RAID10 setup. > The conclusion (regarding cost/performance ratio) was pretty clear: > Our new webserver machine got an 3Ware Escalade 6400 driving a > RAID 0+1 Array. This is the smartest approach, IMO. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 19 21:28: 9 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id C747F37B43E for ; Thu, 19 Apr 2001 21:27:56 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f3K1bUu17530; Thu, 19 Apr 2001 18:37:55 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104200137.f3K1bUu17530@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Domas Mituzas Cc: scsi@freebsd.org Subject: Re: mly driver does not work with SCA in up-to-date 4.3 In-reply-to: Your message of "Thu, 19 Apr 2001 11:17:40 +0200." <20010419102313.P66974-100000@axis.tdd.lt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 19 Apr 2001 18:37:25 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Mylex logical volume was inicialized using automatic setup, cause it fully > satisfied our needs (fault-tolerant mirror). > > It always (during successful starts and not successful ones) showed us > > (probe15:mly0:1:0:0): MODE SENSE(06). CDB: 1a 0 a 0 14 0 > (probe15:mly0:1:0:0): ILLEGAL REQUEST asc:21,0 > (probe15:mly0:1:0:0): Logical block address out of range I think you're booting verbose; this shouldn't actually show up normally AFAIR. > Unsuccessful starts included: > > (probe6:mly0:0:6:0): INQUIRY. CDB 12 1 80 0 ff 0 > (probe6:mly0:0:6:0): ILLEGAL REQUEST asc:24,0 > (probe6:mly0:0:6:0): Invalid field in CDB > > As far as I understand, 0:6:0 is SCA processor, identified by mylex bios > as: > > 0:06 Processor ESG-SHV SCA HBPM10 0.04 > > So it seams, that mylex doesn't know how to work with it. Actually, the Mylex controller does know how to deal with it, the problem is that it doesn't tell the driver to leave it alone, so the driver exposes it to the generic SCSI interface. That's really a bug in the driver (not detecting this and hiding it). > Stopped at mly_cam_action+0x25d: idivl 0x8c(%esi,%ebx,1),%eax ... > any details may be given upon request. This happens both with GENERIC and > tailored version of kernel. Hardware is new, stable and works with > 4.2-release. I'm sorry I'm a bit slow responding to this. I think that this is probably this line: /* convert speed (MHz) to usec */ cts->sync_period = 1000000 / sc->mly_btl[bus][target].mb_speed; and the problem is that the device isn't considered a "physical" device by the Mylex controller. You might try something like if (sc->mly_btl[bus][target].mb_speed == 0) { cts->sync_period = 1000000 / 5; } else { cts->sync_period = 1000000 / sc->mly_btl[bus][target].mb_speed; } and see if this works properly (yes, I know you'll have to build a replacement kernel to try this out). It's not accurate, but I'm not sure how else to go about dealing with this. I *knew* that interfacing this driver to CAM was a bad idea, and I was right. 8( -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 20 1: 2:51 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from axis.tdd.lt (axis.tdd.lt [193.219.211.5]) by hub.freebsd.org (Postfix) with ESMTP id 113F337B424; Fri, 20 Apr 2001 01:02:46 -0700 (PDT) (envelope-from domas.mituzas@delfi.lt) Received: from localhost (midom@localhost) by axis.tdd.lt (8.11.1/8.11.1) with ESMTP id f3K82hn35267; Fri, 20 Apr 2001 10:02:43 +0200 (EET) Date: Fri, 20 Apr 2001 10:02:42 +0200 (EET) From: Domas Mituzas X-X-Sender: To: Mike Smith Cc: , , Subject: Re: mly driver does not work with SCA in up-to-date 4.3 In-Reply-To: <200104200137.f3K1bUu17530@mass.dis.org> Message-ID: <20010420100053.I34482-100000@axis.tdd.lt> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I think you're booting verbose; this shouldn't actually show up normally > AFAIR. booting in normal mode gave just mly gone messages. of course I did verbose boot. > /* convert speed (MHz) to usec */ > cts->sync_period = 1000000 / sc->mly_btl[bus][target].mb_speed; > > and the problem is that the device isn't considered a "physical" device > by the Mylex controller. You might try something like > > if (sc->mly_btl[bus][target].mb_speed == 0) { > cts->sync_period = 1000000 / 5; > } else { > cts->sync_period = 1000000 / sc->mly_btl[bus][target].mb_speed; > } > Yes, it solved that division by zero problem. Thanks! It would be really nice to see this patch in 4.3-rel. Regards, Domas Mituzas --- src/sys/dev/mly/mly_cam.c.old Fri Apr 20 09:59:04 2001 +++ src/sys/dev/mly/mly_cam.c Fri Apr 20 09:59:14 2001 @@ -363,7 +363,11 @@ cts->valid |= CCB_TRANS_TQ_VALID; /* convert speed (MHz) to usec */ - cts->sync_period = 1000000 / sc->mly_btl[bus][target].mb_speed; + if (sc->mly_btl[bus][target].mb_speed == 0) { + cts->sync_period = 1000000 / 5; + } else { + cts->sync_period = 1000000 / sc->mly_btl[bus][target].mb_speed; + } /* convert bus width to CAM internal encoding */ switch (sc->mly_btl[bus][target].mb_width) { To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 20 4:24:14 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from relay.ioffe.rssi.ru (relay.ioffe.rssi.ru [194.85.224.33]) by hub.freebsd.org (Postfix) with ESMTP id 40E8937B424; Fri, 20 Apr 2001 04:24:10 -0700 (PDT) (envelope-from kopts@astro.ioffe.rssi.ru) Received: from astro.ioffe.rssi.ru (astro.ioffe.rssi.ru [194.85.229.130]) by relay.ioffe.rssi.ru (8.9.1/8.9.1) with ESMTP id PAA28254; Fri, 20 Apr 2001 15:24:08 +0400 (MSD) Received: by astro.ioffe.rssi.ru (8.9.3/Clnt-2.14-AS-eef) id PAA86602; Fri, 20 Apr 2001 15:23:33 +0400 (MSD) Date: Fri, 20 Apr 2001 15:23:33 +0400 (MSD) From: Alexey Koptsevich To: Mike Smith Cc: scsi@freebsd.org Subject: Re: IDE RAID In-Reply-To: <200104191949.f3JJnge01789@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike, > > Sure, only raid5 is interesting for me. Promise SuperTrak (raid5) > > controllers are available here. > > Hmm. RAID5 isn't really all that wonderful; you pay a high price in both > cost and performance to do all those XOR calculations. OK, for the moment we use software mirror via vinum, SCSI RAID controller and especially discs are a bit expensive :) > Yes, it is. I haven't had any time lately to test it, but it's known to > work. BTW, where can I read about configuration of the 'twe' array? E.g., how the discs are seen by the OS? How can I partition them? Can I have different types of RAID on the same array, e.g., half for RAD5 and half for mirror? Thanks a lot, Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 20 8:26: 8 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 4D9DC37B440; Fri, 20 Apr 2001 08:25:56 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id KAA82077; Fri, 20 Apr 2001 10:25:53 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 20 Apr 2001 10:25:52 -0500 (CDT) From: Chris Dillon To: Mike Smith Cc: Tom Samplonius , =?iso-8859-1?Q?Jo=E3o_Pagaime?= , Subject: Re: Mylex 170 - boot takes several minutes In-Reply-To: <200104200147.f3K1llu17658@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 19 Apr 2001, Mike Smith wrote: > > > The mly driver in 4.3-RC is much better. It might fix this problem. > > > Besides that, It is definitely much faster. > > > > It doesn't fix that particular problem, at least not for me. The > > controller/driver was also causing a system panic for me shortly > > before root was mounted. I had some earlier kernels where everything > > worked just fine except for the long delay, and then a few days ago I > > attempted to update to the latest 4.3-RC and it still paniced on me. > > I've had another report of this, involving a smart/managed > backplane. Does this feature in your configuration as well? Yes, the system is a SuperMicro SuperServer 6040, which I believe includes the CSE-031 SCA backplane that you can buy separately from them. It uses a "" on made by QLogic on ID 6. This is what I would get, wether the system booted successfully or paniced (obviously successful on this run, since it made it into the log): Mar 27 17:43:41 duey /kernel: mly0: mem 0xfc5fe000-0xfc5fffff irq 10 at device 1.1 on pci2 Mar 27 17:43:41 duey /kernel: mly0: AcceleRAID 170 , 1 channel, firmware 6.00-3-00 (20000919), 32MB RAM Mar 27 17:43:41 duey /kernel: Waiting 15 seconds for SCSI devices to settle [...here is where the long wait begins... the bus seems to be reset and devices probed between each message, judging just by the activity lights on the drives during the whole process] Mar 27 17:43:41 duey /kernel: mly0: physical device 0:6 sense data received Mar 27 17:43:41 duey /kernel: mly0: sense key 5 asc 00 ascq 00 Mar 27 17:43:41 duey /kernel: mly0: info 00000000 csi 00000000 Mar 27 17:43:41 duey /kernel: mly0: physical device 0:6 sense data received Mar 27 17:43:41 duey /kernel: mly0: sense key 5 asc 00 ascq 00 Mar 27 17:43:41 duey /kernel: mly0: info 00000000 csi 00000000 Mar 27 17:43:41 duey /kernel: mly0: physical device 0:6 sense data received Mar 27 17:43:41 duey /kernel: mly0: sense key 5 asc 00 ascq 00 Mar 27 17:43:41 duey /kernel: mly0: info 00000000 csi 00000000 Mar 27 17:43:41 duey /kernel: mly0: physical device 0:6 sense data received Mar 27 17:43:41 duey /kernel: mly0: sense key 5 asc 00 ascq 00 Mar 27 17:43:41 duey /kernel: mly0: info 00000000 csi 00000000 Mar 27 17:43:41 duey /kernel: mly0: physical device 0:6 sense data received Mar 27 17:43:41 duey /kernel: mly0: sense key 5 asc 00 ascq 00 Mar 27 17:43:41 duey /kernel: mly0: info 00000000 csi 00000000 Mar 27 17:43:41 duey /kernel: mly0: physical device 0:6 sense data received Mar 27 17:43:41 duey /kernel: mly0: sense key 5 asc 00 ascq 00 Mar 27 17:43:41 duey /kernel: mly0: info 00000000 csi 00000000 Mar 27 17:43:41 duey /kernel: mly0: physical device 0:6 sense data received Mar 27 17:43:41 duey /kernel: mly0: sense key 5 asc 00 ascq 00 Mar 27 17:43:41 duey /kernel: mly0: info 00000000 csi 00000000 [...and where the long wait ends...] Mar 27 17:43:41 duey /kernel: da0 at mly0 bus 1 target 0 lun 0 Mar 27 17:43:41 duey /kernel: da0: Fixed Direct Access SCSI-3 device I know a crashdump and backtrace would be best... I'll get that (the crashdump, at least, since I don't think I'll know how to backtrace it) at the next available opportunity. :-) One intersting thing is that one time I saw an error pop up during probing for the spare drive I had sitting in the chassis, which was not configured in the controller as anything. It was there just to be a warm spare that I would pull out and move over to the slot of a dead drive when the time came. The system suddenly started panicing every time on boot until I pulled that spare unconfigured drive out. Now it panics every time regardless, even with the same kernels. Does this sound like there is something weird going on with the on-controller configuration that could be causing the panic? Thats the only thing I can think of that would cause inconsistent boot failures and failures with previously known-good kernels. Is there any configuration information stored on the disk by the controller? -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 20 9:25:18 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id EA42437B42C; Fri, 20 Apr 2001 09:25:15 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id LAA83344; Fri, 20 Apr 2001 11:25:14 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 20 Apr 2001 11:25:13 -0500 (CDT) From: Chris Dillon To: Mike Smith Cc: Domas Mituzas , Subject: Re: mly driver does not work with SCA in up-to-date 4.3 In-Reply-To: <200104200137.f3K1bUu17530@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 19 Apr 2001, Mike Smith wrote: > I *knew* that interfacing this driver to CAM was a bad idea, and I > was right. 8( I'm kinda glad you did, since when I had to pull the Mylex controller when I could no longer get the system to boot, I just hooked one of the disks from the RAID1 array onto a regular SCSI controller and never had to edit fstab since the device name never changed. Its only a minor advantage, I know. What is it about CAM that doesn't fit well with what you're doing? -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 20 10:44:49 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp-1.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id C8FFC37B423; Fri, 20 Apr 2001 10:44:45 -0700 (PDT) (envelope-from presence@churchofinformationwarfare.org) Received: from shell-3.enteract.com (shell-3.enteract.com [207.229.143.42]) by smtp-1.enteract.com (Postfix) with ESMTP id 46D646774; Fri, 20 Apr 2001 12:40:18 -0500 (CDT) Date: Fri, 20 Apr 2001 12:40:17 -0500 (CDT) From: Reverend K Kanno X-Sender: presence@shell-3.enteract.com To: stable@FreeBSD.ORG, scsi@freebsd.org Subject: boot spinner In-Reply-To: <20010420184533.A60728@dcse.fee.vutbr.cz> 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 Greetings. I've got a 4.3-RC box that rebooted for some unknown reason. At this point it will boot only as far as the third bar in the boot spinner: - \ | (hangs here) Is there a meaning behind each position as in each letter of LILO displayed in lilo? Hardware is a dell 2450 with an Adaptec 2100s RAID card. ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== The Exploding Fruit Challenge! Rev. K. Kanno www.energybeam.com blowup-fruit@energybeam.com ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== ==== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 20 12:37:19 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id DC52637B43C for ; Fri, 20 Apr 2001 12:37:16 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f3KJcbf01621; Fri, 20 Apr 2001 12:38:38 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104201938.f3KJcbf01621@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Chris Dillon Cc: Domas Mituzas , scsi@FreeBSD.ORG Subject: Re: mly driver does not work with SCA in up-to-date 4.3 In-reply-to: Your message of "Fri, 20 Apr 2001 11:25:13 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Apr 2001 12:38:37 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Thu, 19 Apr 2001, Mike Smith wrote: > > > I *knew* that interfacing this driver to CAM was a bad idea, and I > > was right. 8( > > I'm kinda glad you did, since when I had to pull the Mylex controller > when I could no longer get the system to boot, I just hooked one of > the disks from the RAID1 array onto a regular SCSI controller and > never had to edit fstab since the device name never changed. Its only > a minor advantage, I know. What is it about CAM that doesn't fit well > with what you're doing? This, just for starters. 8) Basically, CAM insists that things behave exactly like SCSI disks, etc. And RAID arrays just don't; the driver has to fake up all sorts of rubbish like whether the array supports disconnect, tagged queueing, its transfer rate, etc. I thought initially that because the array uses a subset of SCSI-like commands, it'd make sense. Unfortunately, it doesn't support enough of them to be useful. A wiser compromise would be to have an optional CAM interface that can talk to non-disk devices on the SCSI bus and just interface the disks directly to the bio layer, as I used to do with other drivers. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 20 13: 7:53 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id 26E0F37B422; Fri, 20 Apr 2001 13:07:50 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id PAA87410; Fri, 20 Apr 2001 15:07:48 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 20 Apr 2001 15:07:47 -0500 (CDT) From: Chris Dillon To: Mike Smith Cc: Domas Mituzas , Subject: Re: mly driver does not work with SCA in up-to-date 4.3 In-Reply-To: <200104201938.f3KJcbf01621@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 20 Apr 2001, Mike Smith wrote: > > On Thu, 19 Apr 2001, Mike Smith wrote: > > > > > I *knew* that interfacing this driver to CAM was a bad idea, and I > > > was right. 8( > > > > I'm kinda glad you did, since when I had to pull the Mylex controller > > when I could no longer get the system to boot, I just hooked one of > > the disks from the RAID1 array onto a regular SCSI controller and > > never had to edit fstab since the device name never changed. Its only > > a minor advantage, I know. What is it about CAM that doesn't fit well > > with what you're doing? > > This, just for starters. 8) > > Basically, CAM insists that things behave exactly like SCSI disks, > etc. And RAID arrays just don't; the driver has to fake up all > sorts of rubbish like whether the array supports disconnect, > tagged queueing, its transfer rate, etc. I gather this would also cause problems for putting the ATA stuff under the CAM umbrella? I thought the idea behind CAM was to be somewhat generic in nature, not SCSI-specific. > I thought initially that because the array uses a subset of > SCSI-like commands, it'd make sense. Unfortunately, it doesn't > support enough of them to be useful. A wiser compromise would be > to have an optional CAM interface that can talk to non-disk > devices on the SCSI bus and just interface the disks directly to > the bio layer, as I used to do with other drivers. Would this help out the aforementioned ATA-under-CAM problems? -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 20 13:31:45 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 77FB737B42C for ; Fri, 20 Apr 2001 13:31:41 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f3KKX1f02169; Fri, 20 Apr 2001 13:33:01 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104202033.f3KKX1f02169@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Chris Dillon Cc: Domas Mituzas , scsi@FreeBSD.ORG Subject: Re: mly driver does not work with SCA in up-to-date 4.3 In-reply-to: Your message of "Fri, 20 Apr 2001 15:07:47 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Apr 2001 13:33:01 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Basically, CAM insists that things behave exactly like SCSI disks, > > etc. And RAID arrays just don't; the driver has to fake up all > > sorts of rubbish like whether the array supports disconnect, > > tagged queueing, its transfer rate, etc. > > I gather this would also cause problems for putting the ATA stuff > under the CAM umbrella? I thought the idea behind CAM was to be > somewhat generic in nature, not SCSI-specific. It may well have been, and in some ways at least the transport layer probably is fairly protocol-agnostic. However, the current implementation is hopelessly SCSI-specific, and the peripheral drivers are not good at dealing with odd situations. > > I thought initially that because the array uses a subset of > > SCSI-like commands, it'd make sense. Unfortunately, it doesn't > > support enough of them to be useful. A wiser compromise would be > > to have an optional CAM interface that can talk to non-disk > > devices on the SCSI bus and just interface the disks directly to > > the bio layer, as I used to do with other drivers. > > Would this help out the aforementioned ATA-under-CAM problems? I used to think that shimming ATA under CAM would make sense; I don't anymore. Even shimming ATAPI devices under CAM would be a bad idea. Whilst meaning no offense to Justin and the other CAM folks, I consider CAM to basically be baggage best avoided unless one has to deal with real SCSI peripherals. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 20 14: 8:14 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 8F84437B424; Fri, 20 Apr 2001 14:08:10 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f3KLAdf02644; Fri, 20 Apr 2001 14:10:39 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104202110.f3KLAdf02644@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Reverend K Kanno Cc: stable@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: Re: boot spinner In-reply-to: Your message of "Fri, 20 Apr 2001 12:40:17 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Apr 2001 14:10:37 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've got a 4.3-RC box that rebooted for some unknown reason. At this point it > will boot only as far as the third bar in the boot spinner: > > - \ | (hangs here) > > Is there a meaning behind each position as in each letter of LILO displayed > in lilo? No, there isn't a special meaning. It sounds like your disk BIOS is really upset about something. > Hardware is a dell 2450 with an Adaptec 2100s RAID card. What does the Adaptec RAID BIOS think about the current state of the array? -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 20 14:23: 8 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 2137837B43F; Fri, 20 Apr 2001 14:23:06 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f3KLPhf04507; Fri, 20 Apr 2001 14:25:43 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104202125.f3KLPhf04507@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Domas Mituzas Cc: scsi@freebsd.org, jkh@freebsd.org, vd@sampo.lt Subject: Re: mly driver does not work with SCA in up-to-date 4.3 In-reply-to: Your message of "Fri, 20 Apr 2001 10:02:42 +0200." <20010420100053.I34482-100000@axis.tdd.lt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Apr 2001 14:25:43 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > and the problem is that the device isn't considered a "physical" device > > by the Mylex controller. You might try something like > > > > if (sc->mly_btl[bus][target].mb_speed == 0) { > > cts->sync_period = 1000000 / 5; > > } else { > > cts->sync_period = 1000000 / sc->mly_btl[bus][target].mb_speed; > > } > > > > Yes, it solved that division by zero problem. Thanks! It would be really > nice to see this patch in 4.3-rel. I think, unfortunately, that we're just a couple of days too late. 8( -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 20 14:23:11 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp-1.enteract.com (mail.enteract.com [207.229.143.33]) by hub.freebsd.org (Postfix) with ESMTP id DAE9537B43E; Fri, 20 Apr 2001 14:23:09 -0700 (PDT) (envelope-from presence@churchofinformationwarfare.org) Received: from shell-3.enteract.com (shell-3.enteract.com [207.229.143.42]) by smtp-1.enteract.com (Postfix) with ESMTP id 519146D1A; Fri, 20 Apr 2001 16:23:09 -0500 (CDT) Date: Fri, 20 Apr 2001 16:23:09 -0500 (CDT) From: Reverend K Kanno X-Sender: presence@shell-3.enteract.com To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: boot spinner In-Reply-To: <200104202110.f3KLAdf02644@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 20 Apr 2001, Mike Smith wrote: > > I've got a 4.3-RC box that rebooted for some unknown reason. At this point it > > will boot only as far as the third bar in the boot spinner: > > > > - \ | (hangs here) > > > > Is there a meaning behind each position as in each letter of LILO displayed > > in lilo? > > No, there isn't a special meaning. It sounds like your disk BIOS is > really upset about something. > > > Hardware is a dell 2450 with an Adaptec 2100s RAID card. > > What does the Adaptec RAID BIOS think about the current state of the > array? It thinks it's fine. I setup another mirror set with a fresh install, then remounted the first mirror set. There is much file corruption on the failed set. I'm going to guess this is a hardware issue as the machine was ok for a week then went down with nothing in the logs. KEN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 20 14:33:20 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 17FE737B423 for ; Fri, 20 Apr 2001 14:33:19 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.2/8.11.2) with ESMTP id f3KLZnf05857; Fri, 20 Apr 2001 14:35:49 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104202135.f3KLZnf05857@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Reverend K Kanno Cc: scsi@FreeBSD.ORG Subject: Re: boot spinner In-reply-to: Your message of "Fri, 20 Apr 2001 16:23:09 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 20 Apr 2001 14:35:49 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > Hardware is a dell 2450 with an Adaptec 2100s RAID card. > > > > What does the Adaptec RAID BIOS think about the current state of the > > array? > > It thinks it's fine. I setup another mirror set with a fresh install, then > remounted the first mirror set. There is much file corruption on the failed > set. I'm going to guess this is a hardware issue as the machine was ok for a > week then went down with nothing in the logs. That's pretty ugly. You might want to be very certain that you are up to date with firmware, etc. on the controller as well, but it really does sound like hardware, yes. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 20 22:30:11 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 4EB2537B422; Fri, 20 Apr 2001 22:30:08 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA70254; Fri, 20 Apr 2001 23:29:57 -0600 (MDT) (envelope-from ken) Date: Fri, 20 Apr 2001 23:29:57 -0600 From: "Kenneth D. Merry" To: Chris Dillon Cc: Mike Smith , Domas Mituzas , scsi@FreeBSD.ORG Subject: Re: mly driver does not work with SCA in up-to-date 4.3 Message-ID: <20010420232957.A69868@panzer.kdm.org> References: <200104201938.f3KJcbf01621@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from cdillon@wolves.k12.mo.us on Fri, Apr 20, 2001 at 03:07:47PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Apr 20, 2001 at 15:07:47 -0500, Chris Dillon wrote: > On Fri, 20 Apr 2001, Mike Smith wrote: > > > On Thu, 19 Apr 2001, Mike Smith wrote: > > > > > > > I *knew* that interfacing this driver to CAM was a bad idea, and I > > > > was right. 8( > > > > > > I'm kinda glad you did, since when I had to pull the Mylex controller > > > when I could no longer get the system to boot, I just hooked one of > > > the disks from the RAID1 array onto a regular SCSI controller and > > > never had to edit fstab since the device name never changed. Its only > > > a minor advantage, I know. What is it about CAM that doesn't fit well > > > with what you're doing? > > > > This, just for starters. 8) > > > > Basically, CAM insists that things behave exactly like SCSI disks, > > etc. And RAID arrays just don't; the driver has to fake up all > > sorts of rubbish like whether the array supports disconnect, > > tagged queueing, its transfer rate, etc. > > I gather this would also cause problems for putting the ATA stuff > under the CAM umbrella? I thought the idea behind CAM was to be > somewhat generic in nature, not SCSI-specific. Not really. The ATA model is generic enough that we would probably do something like write a specific ad-type peripheral driver to talk to ATAPI disks. ATAPI CDROM drives may be enough like SCSI CDROM drives that they could use the current cd(4) driver with some modifications to that driver. The problem with RAID devices is that each RAID card has a different interface, so it really wouldn't make sense to hack CAM to work with each new RAID card. Mike's idea of doing a block driver for normal array access and then passthrough for other devices is likely the right way to go. > > I thought initially that because the array uses a subset of > > SCSI-like commands, it'd make sense. Unfortunately, it doesn't > > support enough of them to be useful. A wiser compromise would be > > to have an optional CAM interface that can talk to non-disk > > devices on the SCSI bus and just interface the disks directly to > > the bio layer, as I used to do with other drivers. > > Would this help out the aforementioned ATA-under-CAM problems? I don't think so. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 20 22:34:57 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 2B76337B423; Fri, 20 Apr 2001 22:34:54 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA70276; Fri, 20 Apr 2001 23:34:53 -0600 (MDT) (envelope-from ken) Date: Fri, 20 Apr 2001 23:34:53 -0600 From: "Kenneth D. Merry" To: Mike Smith Cc: Chris Dillon , Domas Mituzas , scsi@FreeBSD.ORG Subject: Re: mly driver does not work with SCA in up-to-date 4.3 Message-ID: <20010420233453.B69868@panzer.kdm.org> References: <200104202033.f3KKX1f02169@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200104202033.f3KKX1f02169@mass.dis.org>; from msmith@FreeBSD.ORG on Fri, Apr 20, 2001 at 01:33:01PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Apr 20, 2001 at 13:33:01 -0700, Mike Smith wrote: > > > Basically, CAM insists that things behave exactly like SCSI disks, > > > etc. And RAID arrays just don't; the driver has to fake up all > > > sorts of rubbish like whether the array supports disconnect, > > > tagged queueing, its transfer rate, etc. > > > > I gather this would also cause problems for putting the ATA stuff > > under the CAM umbrella? I thought the idea behind CAM was to be > > somewhat generic in nature, not SCSI-specific. > > It may well have been, and in some ways at least the transport layer > probably is fairly protocol-agnostic. However, the current > implementation is hopelessly SCSI-specific, and the peripheral drivers > are not good at dealing with odd situations. I wouldn't call it hopeless, but yes, the current implementation is definitely SCSI-specific. > > > I thought initially that because the array uses a subset of > > > SCSI-like commands, it'd make sense. Unfortunately, it doesn't > > > support enough of them to be useful. A wiser compromise would be > > > to have an optional CAM interface that can talk to non-disk > > > devices on the SCSI bus and just interface the disks directly to > > > the bio layer, as I used to do with other drivers. > > > > Would this help out the aforementioned ATA-under-CAM problems? > > I used to think that shimming ATA under CAM would make sense; I don't > anymore. Even shimming ATAPI devices under CAM would be a bad idea. > Whilst meaning no offense to Justin and the other CAM folks, I consider > CAM to basically be baggage best avoided unless one has to deal with real > SCSI peripherals. It should come as no surprise that I disagree. :) I think the queueing, resource allocation and probe code in the transport layer, as well as the passthrough facility, would work well for ATA. That was one of the design goals for the CAM spec in the first place. My guess is that if we did put ATA support into CAM, it probably wouldn't come as a translation layer under the transport layer to translate SCSI into ATA. Rather we would probably have a separate ad driver, and perhaps a merged cd(4) driver, since ATAPI and SCSI CDROM drives are fairly similar. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 21 14:29: 9 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id DC3B337B423 for ; Sat, 21 Apr 2001 14:29:03 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id XAA23300; Sat, 21 Apr 2001 23:29:01 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3LLRwf02467; Sat, 21 Apr 2001 23:27:58 +0200 (MET DST) (envelope-from j) Date: Sat, 21 Apr 2001 23:27:58 +0200 (MET DST) Message-Id: <200104212127.f3LLRwf02467@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden 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 References: <20010414203925.A63281@uriah.heep.sax.de> <200104150504.f3F544s00932@aslan.scsiguy.com> <20010418225355.U688@uriah.heep.sax.de> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Problem with current sa(4) driver X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Cc: j@uriah.heep.sax.de, mjacob@feral.com Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org J Wunsch wrote: >> While it is true that the sa driver should be filtering out this >> particular case because there is no error, returning ERESTART for >> NO_SENSE is also wrong. You should be able to fix that by changing >> the table entry for that sense code in cam_periph.c. > > You mean, like this? Hmm, no comments? > I tried to manually patch the return value of cam_periph_error() to 0 > in kgdb, but this just gets me back at the second problem: > > % ps axl > UID PID PPID CPU PRI NI VSZ RSS WCHAN STAT TT TIME COMMAND > ... > 107 373 1 0 -8 0 244 33 cbwait DWE p0- 0:00.00 dd if=/dev/sa0 of=/dev/null bs=10 > > It sits there, and waits indefinately. OK, i found this one. Obviously, the device queue is still frozen at this point. The following patch fixes the problem for me, by now only tested against that ARCHIVE Python DDS drive, but will also test shortly against my Tandberg TDC4222 drive. What the fix does is filtering out `no errors', i. e. illegal length indications with a shorter tape block than requested, and hitting a filemark during read, and then instead of calling cam_periph_error(), simply making sure that the device queue is really becoming unfrozen at exit (in case of an actual error, cam_periph_error() performs the unfreeze). I'd like to commit the fix to scsi_sa.c (or have Matt commit it, i don't care). Also repeated the patch for cam_periph.c that makes a NO_SENSE return no error, which should IMHO be what Justin was referring to in the quote above. Any feedback highly appreciated, since i feel a little far out on thin ice here in CAM-land. Index: cam_periph.c =================================================================== RCS file: /home/ncvs/src/sys/cam/cam_periph.c,v retrieving revision 1.34 diff -u -r1.34 cam_periph.c --- cam_periph.c 2001/04/04 18:24:35 1.34 +++ cam_periph.c 2001/04/17 17:46:11 @@ -1369,6 +1369,8 @@ switch (err_action & SS_MASK) { case SS_NOP: + error = 0; + break; case SS_RETRY: action_string = "Retrying Command"; error = ERESTART; Index: scsi/scsi_sa.c =================================================================== RCS file: /home/ncvs/src/sys/cam/scsi/scsi_sa.c,v retrieving revision 1.67 diff -u -r1.67 scsi_sa.c --- scsi/scsi_sa.c 2001/03/27 05:45:12 1.67 +++ scsi/scsi_sa.c 2001/04/21 21:05:53 @@ -2286,7 +2286,7 @@ u_int32_t resid = 0; int32_t info = 0; int error_code, sense_key, asc, ascq; - int error, defer_action; + int error, defer_action, no_actual_error = FALSE; periph = xpt_path_periph(ccb->ccb_h.path); softc = (struct sa_softc *)periph->softc; @@ -2396,6 +2396,8 @@ if (defer_action) { error = -1; softc->flags |= SA_FLAG_EOF_PENDING; + } else { + no_actual_error = TRUE; } /* * Unconditionally, if we detected a filemark on a read, @@ -2424,6 +2426,8 @@ softc->flags |= SA_FLAG_EIO_PENDING; else error = EIO; + } else { + no_actual_error = TRUE; } /* * Bump the block number if we hadn't seen a filemark. @@ -2438,8 +2442,17 @@ } } } - if (error == 0) + if (error == 0 && !no_actual_error) return (cam_periph_error(ccb, cflgs, sflgs, &softc->saved_ccb)); + if (no_actual_error) { + if ((ccb->ccb_h.status & CAM_DEV_QFRZN) != 0) + cam_release_devq(ccb->ccb_h.path, + /* relsim_flags */0, + /* openings */0, + /* timeout */0, + /* getcount_only */ FALSE); + return (0); + } if (error == -1) return (0); -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL 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