From owner-freebsd-scsi Sun Oct 31 11:51:18 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ba2.so-net.ne.jp (c230240.ap.plala.or.jp [210.150.230.240]) by hub.freebsd.org (Postfix) with ESMTP id 1248514E5E for ; Sun, 31 Oct 1999 11:51:14 -0800 (PST) (envelope-from saeki@ba2.so-net.ne.jp) Received: from localhost (localhost [127.0.0.1]) by ba2.so-net.ne.jp (8.8.8/3.5Wpl7) with ESMTP id EAA28541; Mon, 1 Nov 1999 04:51:20 +0900 (JST) To: freebsd-scsi@FreeBSD.ORG Cc: saeki@ba2.so-net.ne.jp Subject: Re: initio scsi controller In-Reply-To: Your message of "Sat, 30 Oct 1999 13:20:53 -0600 (MDT)" <199910301920.NAA17716@panzer.kdm.org> References: <199910301920.NAA17716@panzer.kdm.org> X-Mailer: Mew version 1.93 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19991101045120U.saeki@ba2.so-net.ne.jp> Date: Mon, 01 Nov 1999 04:51:20 +0900 From: Saeki Takashi X-Dispatcher: imput version 980905(IM100) Lines: 23 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Ken, Thank you for your reply. I am very glad to hear the drivers will be merged into FreeBSD. From: "Kenneth D. Merry" Subject: Re: initio scsi controller Date: Sat, 30 Oct 1999 13:20:53 -0600 (MDT) Message-ID: <199910301920.NAA17716@panzer.kdm.org> > I'm glad to know it works. You're the first person (at least that I can > remember) who I've heard from that has one of these cards. > Yes. I got the card about a week ago. I have searched FreeBSD archive, but I found negative responces. So, I thought there is no driver for the board yet, at first time. And I checked www.initio.com if I could port linux drivers. > The first two problems will hopefully be solved by Thomas. As for the last > one, I think he is going to try to contact Initio about it. > I see. I am waiting for good news, Thank you. -- saeki To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Oct 31 12:32:36 1999 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 73BC414CAC for ; Sun, 31 Oct 1999 12:32:33 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA26377; Sun, 31 Oct 1999 13:32:14 -0700 (MST) (envelope-from ken) Message-Id: <199910312032.NAA26377@panzer.kdm.org> Subject: Re: initio scsi controller In-Reply-To: <19991101045120U.saeki@ba2.so-net.ne.jp> from Saeki Takashi at "Nov 1, 1999 04:51:20 am" To: saeki@ba2.so-net.ne.jp (Saeki Takashi) Date: Sun, 31 Oct 1999 13:32:14 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Saeki Takashi wrote... > Hi Ken, Thank you for your reply. > I am very glad to hear the drivers will be merged into FreeBSD. > > From: "Kenneth D. Merry" > Subject: Re: initio scsi controller > Date: Sat, 30 Oct 1999 13:20:53 -0600 (MDT) > Message-ID: <199910301920.NAA17716@panzer.kdm.org> > > > I'm glad to know it works. You're the first person (at least that I can > > remember) who I've heard from that has one of these cards. > > > Yes. I got the card about a week ago. > I have searched FreeBSD archive, but I found negative responces. > So, I thought there is no driver for the board yet, at first time. > And I checked www.initio.com if I could port linux drivers. For what it's worth, the driver page here has more information/drivers than the Initio home page: http://www.ioiscsi.com/ 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 Sun Oct 31 12:35:28 1999 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 7E82614E63 for ; Sun, 31 Oct 1999 12:35:24 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA26377; Sun, 31 Oct 1999 13:32:14 -0700 (MST) (envelope-from ken) Message-Id: <199910312032.NAA26377@panzer.kdm.org> Subject: Re: initio scsi controller In-Reply-To: <19991101045120U.saeki@ba2.so-net.ne.jp> from Saeki Takashi at "Nov 1, 1999 04:51:20 am" To: saeki@ba2.so-net.ne.jp (Saeki Takashi) Date: Sun, 31 Oct 1999 13:32:14 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Saeki Takashi wrote... > Hi Ken, Thank you for your reply. > I am very glad to hear the drivers will be merged into FreeBSD. > > From: "Kenneth D. Merry" > Subject: Re: initio scsi controller > Date: Sat, 30 Oct 1999 13:20:53 -0600 (MDT) > Message-ID: <199910301920.NAA17716@panzer.kdm.org> > > > I'm glad to know it works. You're the first person (at least that I can > > remember) who I've heard from that has one of these cards. > > > Yes. I got the card about a week ago. > I have searched FreeBSD archive, but I found negative responces. > So, I thought there is no driver for the board yet, at first time. > And I checked www.initio.com if I could port linux drivers. For what it's worth, the driver page here has more information/drivers than the Initio home page: http://www.ioiscsi.com/ 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 Sun Oct 31 18:29: 7 1999 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 33243156D1; Sun, 31 Oct 1999 18:28:58 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 11i5iW-00046j-00; Sun, 31 Oct 1999 16:53:00 -0800 Date: Sun, 31 Oct 1999 16:52:59 -0800 (PST) From: Tom To: Mike Cc: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: DPT SmartRAID IV (da0:dpt0:0:0:0) : CCB 0xc550807c - timeout. In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 30 Oct 1999, Mike wrote: > Hi all! > > It seems once awhile the FreeBSD-3.3-Release system hangs with the > following message: > > /kernel: (da0:dpt0:0:0:0) : CCB 0xc550807c - timeout. > /kernel: (da0:dpt0:0:0:0) : CCB 0xc5508744 - timeout. You probably want to put the "DPT_VERIFY_HINTR" and "DPT_LOST_IRQ" options into your kernel config file. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 1 10:39:10 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front5m.grolier.fr (front5m.grolier.fr [195.36.216.55]) by hub.freebsd.org (Postfix) with ESMTP id 2C48014D60 for ; Mon, 1 Nov 1999 10:39:05 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-224-49.villette.club-internet.fr [195.36.224.49]) by front5m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id TAA23946 for ; Mon, 1 Nov 1999 19:39:02 +0100 (MET) Date: Mon, 1 Nov 1999 21:02:10 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: scsi@FreeBSD.org Subject: SYM-0.9.0 ok for 3.3 and -current (was SYM driver available for -stable) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I had updated my local repository last week-end and have had time this=20 week-end for checking that SYM-0.9.0 compiles ok for 3.3 and -current as=20 expected, and btw works fine for me under these O/S versions. G=E9rard. PS: If I am the only user of this driver, may-be I should switch its status to production quality immediately. ;-) On Sun, 24 Oct 1999, Gerard Roudier wrote: > I just made available SYM driver 0.9.0 as a tar file that contains full= =20 > driver files. This avoids applying 8 nasty patches successively. >=20 > ftp://ftp.tux.org/roudier/drivers/freebsd/experimental/SYM-0.9.0-19991024= =2Etar.gz > ftp://ftp.tux.org/roudier/drivers/freebsd/experimental/README.sym > (modulo spelling errors :-) ) >=20 > Status: (switched back to EXPERIMENTAL due to some heavy changes) > EXPERIMENTAL > This driver is currently developped under the following O/S: > FreeBSD 4.0 SNAPSHOT July 5th 1999 > Starting with version 0.9.0, the driver contains conditionnal code=20 > for using pre-4.0 BUS stuff for PCI. I have successfully tested driver= =20 > version 0.9.0 under: > FreeBSD 3.2 RELEASE > Given that the old bus stuff is still supported under FreeBSD, the dri= ver=20 > should also compile and work just fine under FreeBSD 3.3 RELEASE. >=20 > Latest revision: > sym-0.9.0-19991024 >=20 > * SYM-0.8.0-19991016 (diff file PATCH-SYM-0.8.0-19991016) > Heavy rewrite/rewamping of the error handling code in order to conform= =20 > to FreeBSD-CAM expectation of commands having to be requeued and device= =20 > queue to be frozen on any kind of error. Driver status switched back=20 > to EXPERIMENTAL due to these changes. > Warn user about targets that are not flagged for SCAN AT BOOT in the=20 > NVRAM, since the driver will not allow the corresponding devices to be= =20 > discovered by XPT. > And numerous minor changes. >=20 > * SYM-0.9.0-19991024 (Tar file SYM-0.9.0-19991024.tar.gz) > Add support for previous PCI BUS stuff, for the driver to be useable=20 > under FreeBSD 3.X RELEASES. The source is #ifdefed for using the old=20 > PCI BUS code under __FreeBSD_version < 400000 and the new one otherwise= =2E > Tested under RELENG_3_2_0_RELEASE, but should also be just fine for 3.3= =2E > Other changes against version 0.8.0 are only minor buglet fixes. >=20 > October 24 1999. "Gerard Roudier" =20 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 1 12:29:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from x-montana.utcorp.com (x-montana.utcorp.com [146.145.135.26]) by hub.freebsd.org (Postfix) with ESMTP id 7E00B152AD for ; Mon, 1 Nov 1999 12:29:24 -0800 (PST) (envelope-from kseel@utcorp.com) Received: from utcorp.com (x-kspc.utcorp.com [146.145.135.17]) by x-montana.utcorp.com (8.9.3/8.8.8) with ESMTP id QAA34259 for ; Mon, 1 Nov 1999 16:41:33 -0500 (EST) (envelope-from kseel@utcorp.com) Message-ID: <381DF864.FBFF41C@utcorp.com> Date: Mon, 01 Nov 1999 15:30:28 -0500 From: Kurt Seel X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: scsi@FreeBSD.ORG Subject: Help! cdrecord stopped working after upgrade to 3.3 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am desparate to get this to work (it's my primary backup media). I have identical drives running on a 3.2 and a 3.3 system. under 2.2.7 I have been burning CD's fine, I upgraded to 3.3 and horror has ensued. 3.2-R : Dmesg: bt0: rev 0x08 int a irq 5 on pci0.10.0 bt0: BT-958 FW Rev. 5.06I Ultra Wide SCSI Host Adapter, SCSI ID 7, 192 CCBs cd0 at bt0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 6.756MB/s transfers (6.756MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present - tray closed bash-2.03# cdrecord dev=3,0 speed=2 -v -inq Cdrecord release 1.8a21 Copyright (C) 1995-1999 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '3,0' scsibus: 0 target: 3 lun: 0 atapi: 0 Device type : Removable CD-ROM Version : 2 Response Format: 2 Capabilities : SYNC Vendor_info : 'YAMAHA ' Identifikation : 'CRW4416S ' Revision : '1.0g' Device seems to be: Generic mmc CD-RW. 3.3-R Dmesg: cd0 at ahc1 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 8.333MB/s transfers (8.333MHz, offset 15) cd0: cd present [329606 x 2048 byte records] # cdrecord dev=1,4,0 speed=2 -v -inq Cdrecord release 1.8a22 Copyright (C) 1995-1999 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '1,4,0' scsibus: 1 target: 4 lun: 0 cdrecord: No such file or directory. Cannot open SCSI driver. It also sometimes complains about not beinf able to open 'pass9' It also works on a disk : > cdrecord dev=1,3,0 speed=2 -v -inq Cdrecord release 1.8a22 Copyright (C) 1995-1999 Jörg Schilling TOC Type: 1 = CD-ROM scsidev: '1,3,0' scsibus: 1 target: 3 lun: 0 atapi: 0 Device type : Disk Version : 2 Response Format: 2 Capabilities : SYNC CMDQUE Vendor_info : 'COMPAQPC' Identifikation : 'DSP3053LS ' Revision : '442C' Device seems to be: Generic CCS Disk. -- "Signature file failed Preliminary Design Review. Feasibility of a new signature is currently being evaluated." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 1 12:55: 7 1999 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 950CC15315 for ; Mon, 1 Nov 1999 12:54:51 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA34445; Mon, 1 Nov 1999 13:54:10 -0700 (MST) (envelope-from ken) Message-Id: <199911012054.NAA34445@panzer.kdm.org> Subject: Re: Help! cdrecord stopped working after upgrade to 3.3 In-Reply-To: <381DF864.FBFF41C@utcorp.com> from Kurt Seel at "Nov 1, 1999 03:30:28 pm" To: kseel@utcorp.com (Kurt Seel) Date: Mon, 1 Nov 1999 13:54:10 -0700 (MST) Cc: scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kurt Seel wrote... > > I am desparate to get this to work (it's my primary backup media). > I have identical drives running on a 3.2 and a 3.3 system. under 2.2.7 > I > have been burning CD's fine, I upgraded to 3.3 and horror has ensued. [ ... ] > Dmesg: > cd0 at ahc1 bus 0 target 4 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 8.333MB/s transfers (8.333MHz, offset 15) > cd0: cd present [329606 x 2048 byte records] > > # cdrecord dev=1,4,0 speed=2 -v -inq > Cdrecord release 1.8a22 Copyright (C) 1995-1999 J_rg Schilling > TOC Type: 1 = CD-ROM > scsidev: '1,4,0' > scsibus: 1 target: 4 lun: 0 > cdrecord: No such file or directory. Cannot open SCSI driver. > > It also sometimes complains about not beinf able to open 'pass9' Does /dev/pass9 exist? What happens if you do the following: camcontrol devlist camcontrol tur cd0 -v camcontrol inquiry cd0 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 Mon Nov 1 13:13: 1 1999 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 9FD9214CC1 for ; Mon, 1 Nov 1999 13:12:40 -0800 (PST) (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 PAA26029; Mon, 1 Nov 1999 15:12:34 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Mon, 1 Nov 1999 15:12:34 -0600 (CST) From: Chris Dillon To: Gerard Roudier Cc: scsi@FreeBSD.ORG Subject: Re: SYM-0.9.0 ok for 3.3 and -current (was SYM driver available for -stable) 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 Mon, 1 Nov 1999, Gerard Roudier wrote: > > I had updated my local repository last week-end and have had time this > week-end for checking that SYM-0.9.0 compiles ok for 3.3 and -current as > expected, and btw works fine for me under these O/S versions. > > Gérard. > > PS: If I am the only user of this driver, may-be I should switch its > status to production quality immediately. ;-) Since I just borrowed an old DDS2 drive from work to do some backups, I'm not too worried about toasting anything. I'll give this thing a test sometime this week. I've got a Tekram DC-390F (Sym 53C875 based) card, with two IBM DCAS-34330UW drives, an NEC 16X CDROM drive, and a Sony SDT-5200 DAT sitting on it, just in case you wanted to know (or if you wanted to warn me of anything). :-) Come to think of it, I haven't tested out the new aic driver either. It probes/attaches, but I haven't actually plugged anything into it. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 3 9:24:13 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from beagle.epooch.com (beagle.epooch.com [208.232.158.3]) by hub.freebsd.org (Postfix) with ESMTP id 7CCFF155FA for ; Wed, 3 Nov 1999 09:23:46 -0800 (PST) (envelope-from mschroebel@beagle.epooch.com) Received: (from mschroebel@localhost) by beagle.epooch.com (8.9.2/8.9.2) id JAA12257 for scsi@freebsd.org; Sat, 30 Oct 1999 09:59:23 -0400 (EDT) (envelope-from mschroebel) Date: Sat, 30 Oct 1999 09:59:23 -0400 From: Matthew Schroebel To: scsi@freebsd.org Subject: sorry Message-ID: <19991030095923.B12242@beagle.epooch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org just being brain dead, sorry for the subscribe! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 3 9:24:27 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from beagle.epooch.com (beagle.epooch.com [208.232.158.3]) by hub.freebsd.org (Postfix) with ESMTP id 3556315691 for ; Wed, 3 Nov 1999 09:23:46 -0800 (PST) (envelope-from mschroebel@beagle.epooch.com) Received: (from mschroebel@localhost) by beagle.epooch.com (8.9.2/8.9.2) id JAA12238 for scsi@freebsd.org; Sat, 30 Oct 1999 09:56:58 -0400 (EDT) (envelope-from mschroebel) Date: Sat, 30 Oct 1999 09:56:58 -0400 From: Matthew Schroebel To: scsi@freebsd.org Message-ID: <19991030095658.A12230@beagle.epooch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.3i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org subscribe scsi@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Nov 3 21:29:53 1999 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 283EF14E59 for ; Wed, 3 Nov 1999 21:29:50 -0800 (PST) (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 XAA46573; Wed, 3 Nov 1999 23:28:07 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Wed, 3 Nov 1999 23:28:07 -0600 (CST) From: Chris Dillon To: Gerard Roudier Cc: scsi@FreeBSD.ORG Subject: Re: SYM-0.9.0 ok for 3.3 and -current (was SYM driver available for -stable) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 1 Nov 1999, Gerard Roudier wrote: > I had updated my local repository last week-end and have had time this > week-end for checking that SYM-0.9.0 compiles ok for 3.3 and -current as > expected, and btw works fine for me under these O/S versions. Well, I'm beating on your driver as I write with a 'make -j 8 world', a copy of the entire CVS repository from one drive to another, and a restore from tape to a scratch part of a drive, all at the same time. sym0: <875> rev 0x03 int a irq 10 on pci0.18.0 sym0: Tekram NVRAM, ID 7, Fast-20, parity checking sa0 at sym0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 5.000MB/s transfers (5.000MHz, offset 8) cd0 at sym0 bus 0 target 2 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) Everything is working great. I haven't done any type of benchmarking yet to see which driver is faster for me, but so far they appear to be about the same. I don't know if this is because of the sym driver or not, but I have noticed that under all this load there is approximately a .5 (one-half) second freeze every 5 to 10 seconds, and the SCSI activity light goes out entirely. This makes system responsiveness seem "choppy". According to systat -vmstat 1, interrupts for the SCSI controller drop very low (40-50) during the freeze and then peak at about 300 interrupts per second after the freeze is over. Interrupts average 100-125 interrupts per second normally. Since systat is reporting interrupts per second, the freeze is approximately one-half second, and the running average is 100-125 interrupts/second, that would lead me to believe that NO interrupts are occurring for the SCSI controller during that freeze. Tomorrow I'll put the ncr driver under the same load and see if I experience the same choppiness. All of my filesystems are running softupdates, so the large bursts of I/O caused by softupdates might have something to do with it. Well, the 'make -j 8 world' just finished, and everything is happy. Great work, Gerard! -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 4 0: 4:51 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from nagual.pp.ru (deep-thought.demos.su [195.133.1.74]) by hub.freebsd.org (Postfix) with ESMTP id 69F9A14C94; Thu, 4 Nov 1999 00:04:46 -0800 (PST) (envelope-from ache@nagual.pp.ru) Received: (from ache@localhost) by nagual.pp.ru (8.9.3/8.9.3) id LAA02956; Thu, 4 Nov 1999 11:04:00 +0300 (MSK) (envelope-from ache) Date: Thu, 4 Nov 1999 11:03:59 +0300 From: "Andrey A. Chernov" To: scsi@freebsd.org, current@freebsd.org Subject: -current panic on AHA Message-ID: <19991104110359.A2933@nagual.pp.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Organization: Biomechanoid Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Very fresh -current always paniced after detecting SCSI devices on aha0: AHA-1542CF FW Rev. B.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs page fault: supervisor, read page not present Old kernel from Oct 8 works nicely Sorry can't provide more info about panic, it is remote computer. -- Andrey A. Chernov http://nagual.pp.ru/~ache/ MTH/SH/HE S-- W-- N+ PEC>+ D A a++ C G>+ QH+(++) 666+>++ Y To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 4 11:49:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from hotmail.com (law2-f167.hotmail.com [216.32.181.167]) by hub.freebsd.org (Postfix) with SMTP id 64CA814DA1 for ; Thu, 4 Nov 1999 11:49:56 -0800 (PST) (envelope-from mut3x@hotmail.com) Received: (qmail 58809 invoked by uid 0); 4 Nov 1999 19:48:10 -0000 Message-ID: <19991104194810.58808.qmail@hotmail.com> Received: from 206.165.200.116 by www.hotmail.com with HTTP; Thu, 04 Nov 1999 11:48:10 PST X-Originating-IP: [206.165.200.116] From: "Mutex Records USA" To: scsi@freebsd.org Subject: ait drives under freebsd Date: Thu, 04 Nov 1999 11:48:10 PST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm wondering where i can find documentation for the use of AIT drives under freebsd, particularly how i can take advantage of tape partitions, and how to have dump write to a particular partition. thanks adam ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 4 12: 2:43 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id F105715148 for ; Thu, 4 Nov 1999 12:02:33 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id MAA11523; Thu, 4 Nov 1999 12:06:50 -0800 Date: Thu, 4 Nov 1999 12:06:50 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Mutex Records USA Cc: scsi@FreeBSD.ORG Subject: Re: ait drives under freebsd In-Reply-To: <19991104194810.58808.qmail@hotmail.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 Partitions aren't supported by SA (yet, if at all). Setmarks are available, but partitions aren't. On Thu, 4 Nov 1999, Mutex Records USA wrote: > I'm wondering where i can find documentation for the use of AIT drives under > freebsd, particularly how i can take advantage of tape partitions, and how > to have dump write to a particular partition. > > thanks > adam > > ______________________________________________________ > Get Your Private, Free Email at http://www.hotmail.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 4 13:45:43 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front7.grolier.fr (front7.grolier.fr [194.158.96.57]) by hub.freebsd.org (Postfix) with ESMTP id 517FA14EFC for ; Thu, 4 Nov 1999 13:45:32 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-99-160.villette.club-internet.fr [194.158.99.160]) by front7.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id WAA09196; Thu, 4 Nov 1999 22:43:11 +0100 (MET) Date: Fri, 5 Nov 1999 00:06:31 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: Chris Dillon Cc: scsi@FreeBSD.ORG Subject: Re: SYM-0.9.0 ok for 3.3 and -current (was SYM driver available for -stable) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 3 Nov 1999, Chris Dillon wrote: > On Mon, 1 Nov 1999, Gerard Roudier wrote: >=20 > > I had updated my local repository last week-end and have had time this= =20 > > week-end for checking that SYM-0.9.0 compiles ok for 3.3 and -current a= s=20 > > expected, and btw works fine for me under these O/S versions. >=20 > Well, I'm beating on your driver as I write with a 'make -j 8 world', > a copy of the entire CVS repository from one drive to another, and a > restore from tape to a scratch part of a drive, all at the same time. Thanks a lots for reporting your success using the sym driver. =20 > sym0: <875> rev 0x03 int a irq 10 on pci0.18.0 > sym0: Tekram NVRAM, ID 7, Fast-20, parity checking > sa0 at sym0 bus 0 target 5 lun 0 > sa0: Removable Sequential Access SCSI-2 device=20 > sa0: 5.000MB/s transfers (5.000MHz, offset 8) > cd0 at sym0 bus 0 target 2 lun 0 > cd0: Removable CD-ROM SCSI-2 device=20 > cd0: 10.000MB/s transfers (10.000MHz, offset 15) > cd0: Attempt to query device size failed: NOT READY, Medium not > present > da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device=20 > da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) > da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) > da1 at sym0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device=20 > da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) > da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) >=20 > Everything is working great. I haven't done any type of benchmarking > yet to see which driver is faster for me, but so far they appear to be > about the same. I know of all the parts where the drivers have significant differences. Most are also known by the FreeBSD SCSI team, given what I read from them, by the way. The ncr has been a great driver and is now quite fine for most situations, but will not sustain the comparison with the sym in extremes situations. In fact, the sym driver is kind of the ncr driver's son. This point appears clearly in the Header part of all sym driver source files. Consider for example the command overhead without disconnections: - sym : less than 62 micro-seconds - ncr : at least 70 micro-seconds more than the sym (difference measured) Then the reselected pattern with a large number of tags: - sym : 0(1) from SCRIPTS (table of jump addresses indexed by tag) - ncr : 0(number of tags) (list scanned from SCRIPTS) Then the DONE processing from the C code: - sym : DONE queue filled by SCRIPTS and read by C code O(1)/active cmds - ncr : scan of the entire lists of CCBs (can be reduced to active ones) For the 896/895A and further chips as the C1010 - sym : handling of data phase mismatch from SCRIPTS - ncr : handling of data phase mismatch from C code Those are the main enhancements, some other are also very interesting, but= =20 may-be this will make my reply way boring. As you know, only 100 micro-seconds are needed to burst 8KB over an Ultra2 wide SCSI BUS and only 50 micro-seconds will be enough for Ultra3. For this reason, only a SIM/HBA pair that allows low command overhead (using also fast SCSI devices) can gain advantage of such fast data throughput over SCSI for real applications. On the other hand kernels and applications must be smart enough for actual IOs transactions not to be too small for Ultra2/3 SCSI BUSes to be well used.=20 > I don't know if this is because of the sym driver or not, but I have > noticed that under all this load there is approximately a .5 > (one-half) second freeze every 5 to 10 seconds, and the SCSI activity > light goes out entirely. This makes system responsiveness seem > "choppy". According to systat -vmstat 1, interrupts for the SCSI > controller drop very low (40-50) during the freeze and then peak at > about 300 interrupts per second after the freeze is over. Interrupts This might well be due to some cause in the kernel, but I will try to=20 understand what does happen. > average 100-125 interrupts per second normally. Since systat is > reporting interrupts per second, the freeze is approximately one-half > second, and the running average is 100-125 interrupts/second, that > would lead me to believe that NO interrupts are occurring for the SCSI > controller during that freeze. Tomorrow I'll put the ncr driver under > the same load and see if I experience the same choppiness. All of my > filesystems are running softupdates, so the large bursts of I/O caused > by softupdates might have something to do with it. >=20 > Well, the 'make -j 8 world' just finished, and everything is happy. >=20 > Great work, Gerard! Thanks for your confidence in this driver. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 4 14:32:17 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 729E115732 for ; Thu, 4 Nov 1999 14:32:03 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id XAA11081 for scsi@FreeBSD.org; Thu, 4 Nov 1999 23:31:57 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 579688864; Thu, 4 Nov 1999 22:48:08 +0100 (CET) Date: Thu, 4 Nov 1999 22:48:08 +0100 From: Ollivier Robert To: scsi@FreeBSD.org Subject: Re: SYM driver available for -stable Message-ID: <19991104224808.A1140@keltia.freenix.fr> Mail-Followup-To: scsi@FreeBSD.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Gerard Roudier: > I just made available SYM driver 0.9.0 as a tar file that contains full > driver files. This avoids applying 8 nasty patches successively. I'm now running with your new driver and it seems to run fine. Dunno really if it faster or not (seems a bit but Bonnie -- a poor benchmark I know -- is almost the same). BTW, I've the same problem with your driver than I had with the ncr one: the LED is constantly on... With the ncr driver, adding options SCSI_NCR_SYMBIOS_COMPAT # for LEDs "fixes" the problem. Which #define does the same for sym0 ? SYM_OPT_LED0 ? -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ncr0 200 4950 65.8 4938 20.7 1907 9.0 5665 47.8 5867 15.8 91.2 3.6 -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU sym0 200 4902 62.7 4627 16.8 1965 8.2 5005 40.8 5884 13.9 136.0 4.3 The disk is an 5400 rpm IBM. sym0: <875> irq 9 at device 11.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-20, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym1: <810a> irq 11 at device 12.0 on pci0 sym1: No NVRAM, ID 7, Fast-10, parity checking sym0: Downloading SCSI SCRIPTS. (noperiph:sym0:0:-1:-1): SCSI bus reset delivered. Creating DISK da0 Creating DISK da1 Creating DISK da2 Creating DISK da12 da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) BTW I got the following two messages when playing with camcontrol... WARNING: driver xpt should register devices with make_dev() (dev_t = "#xpt/0") WARNING: driver pass should register devices with make_dev() (dev_t = "#pass/0") -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 4 14:32:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front6m.grolier.fr (front6m.grolier.fr [195.36.216.56]) by hub.freebsd.org (Postfix) with ESMTP id 11E5815783 for ; Thu, 4 Nov 1999 14:31:57 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-159-22.villette.club-internet.fr [195.36.159.22]) by front6m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id XAA12978; Thu, 4 Nov 1999 23:30:33 +0100 (MET) Date: Fri, 5 Nov 1999 00:53:48 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: Chris Dillon Cc: scsi@FreeBSD.ORG Subject: Re: SYM-0.9.0 ok for 3.3 and -current (was SYM driver available for -stable) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 3 Nov 1999, Chris Dillon wrote: > sym0: <875> rev 0x03 int a irq 10 on pci0.18.0 > sym0: Tekram NVRAM, ID 7, Fast-20, parity checking [ ... ] > da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device=20 > da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) > da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) > da1 at sym0 bus 0 target 1 lun 0 > da1: Fixed Direct Access SCSI-2 device=20 > da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) > da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) Could you check that tagged commands and disconnections are enabled for your drives. The driver is reading this information from the NVRAM and report this information as USER SETTINGS to CAM, so you should ensure the user setup of the controller has these features enabled for your disks.=20 Once booted you can camcontrol to get the current settings for your disks.= =20 G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 4 14:42: 4 1999 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 C33C61568B for ; Thu, 4 Nov 1999 14:41:59 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA92800; Thu, 4 Nov 1999 15:40:46 -0700 (MST) (envelope-from ken) Message-Id: <199911042240.PAA92800@panzer.kdm.org> Subject: Re: SYM driver available for -stable In-Reply-To: <19991104224808.A1140@keltia.freenix.fr> from Ollivier Robert at "Nov 4, 1999 10:48:08 pm" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Thu, 4 Nov 1999 15:40:46 -0700 (MST) Cc: scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ollivier Robert wrote... > > BTW I got the following two messages when playing with camcontrol... > > WARNING: driver xpt should register devices with make_dev() (dev_t = "#xpt/0") > WARNING: driver pass should register devices with make_dev() (dev_t = "#pass/0") I haven't had time to fix it. (well, I've got a fix for the xpt driver, just not the pass driver yet) In any case, it's nothing to worry about. 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 Thu Nov 4 22:46:16 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from gratis.grondar.za (gratis.grondar.za [196.7.18.133]) by hub.freebsd.org (Postfix) with ESMTP id A0E6F14DA4; Thu, 4 Nov 1999 22:46:06 -0800 (PST) (envelope-from mark@grondar.za) Received: from grondar.za (localhost [127.0.0.1]) by gratis.grondar.za (8.9.3/8.9.3) with ESMTP id IAA46540; Fri, 5 Nov 1999 08:43:35 +0200 (SAST) (envelope-from mark@grondar.za) Message-Id: <199911050643.IAA46540@gratis.grondar.za> To: "Andrey A. Chernov" Cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: -current panic on AHA Date: Fri, 05 Nov 1999 08:43:35 +0200 From: Mark Murray Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Very fresh -current always paniced after detecting SCSI devices on > aha0: AHA-1542CF FW Rev. B.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs > page fault: supervisor, read page not present > Old kernel from Oct 8 works nicely > Sorry can't provide more info about panic, it is remote computer. This is not SCSI specific. It is happening on my Libretto laptop and a dual-cpu PPRO box with SCSI (AHC). M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Nov 4 23: 2: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id B313A1505E for ; Thu, 4 Nov 1999 23:01:56 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id IAA00964 for scsi@FreeBSD.ORG; Fri, 5 Nov 1999 08:00:48 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 183628864; Fri, 5 Nov 1999 00:11:14 +0100 (CET) Date: Fri, 5 Nov 1999 00:11:08 +0100 From: Ollivier Robert To: scsi@FreeBSD.ORG Subject: Re: SYM-0.9.0 ok for 3.3 and -current (was SYM driver available for -stable) Message-ID: <19991105001108.A1825@keltia.freenix.fr> Mail-Followup-To: scsi@FreeBSD.ORG References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Gerard Roudier: > Could you check that tagged commands and disconnections are enabled for Tagged commands are disabled for these drives (IBM DCAS) because it gives them bad perfs in sequential reads/writes. I've re-enabled them on my machine because I think tags help for multiple accesses and I don't care that much for sequential perfs... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 5 3:10: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.powertech.no (intentia.powertech.no [195.159.0.220]) by hub.freebsd.org (Postfix) with ESMTP id 4D2EF14D09 for ; Fri, 5 Nov 1999 03:09:53 -0800 (PST) (envelope-from shamz@login1.powertech.no) Received: from login1.powertech.no (IDENT:root@login1.powertech.no [195.159.0.151]) by mail.powertech.no (8.9.3/8.8.5) with ESMTP id MAA11686 for ; Fri, 5 Nov 1999 12:09:52 +0100 Received: (from shamz@localhost) by login1.powertech.no (8.9.3/8.9.3) id MAA01772 for freebsd-scsi@freebsd.org; Fri, 5 Nov 1999 12:09:51 +0100 Date: Fri, 5 Nov 1999 12:09:51 +0100 From: Shaun Jurrens To: freebsd-scsi@freebsd.org Subject: scsi bus errors Message-ID: <19991105120951.C1083@shamz.net> Reply-To: shaun@shamz.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4us Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, After reading the lists and trying about everything under the sun to get the errors to abate, I am finally writing. The setup is about the same as all the others with SCB timeout errors. The messages started (as far as I can tell) after a makeworld on June 29, 1999. I have a 2940W on a pci card with the same system running the 3.x Stable tree since January. Now that I see that IBM disks get the same errors as my two Quantum drives, it can't just be firmware or termination. The disks run without problems under NT and 95. I have checked the disks with Adaptec's software for bad sectors and no new bad sectors can be detected (to the original default). I have also changed the settings to run the disks below the full transfer rate, based on the ahc man page, but to no avail. The problem is starting to get really annoying because it is clobbering files and crashing programs. I now have to shutdown and fsck at least once a week, independent of load. The system can do a -j16 buildworld without a timeout, but normal operation sometimes causes it. The problem is so irregular, that I haven't been able to determine the cause. I do have softupdates enable (though I don't know for how much longer) but they also have been enabled the entire time. I tried to determine if there was any changes to the ahc driver between April and June which might have affected the performance, but since I am not very versed in C, I can't really work with what I have found. The process of elimination brings me down to the driver, because the system itself has no evident hardware problems. I could try fiddling with the BIOS a little (a FIC-2011? with a K6-2 not overclocked, Matrox graphic card, PCI nic from Realtek), but I hate the eternal reboot cycles (feel like I'm usi! ng NT again). I guess if I wasn't convinced that it was a driver problem I wouldn't have written. I left out the logs because they don't seem to have been more than grounds for speculation about termination and such up until now. Seeing the number of people who are getting these messages on various hardware platforms, I would seem to have reason to suspect the one common denominator: the ahc driver. I would suspect a bad disk if it was just one of the two, but the chances of having bad firmware (Quantum, I have heard, has poor firmware anyway) on two totally different models of harddisks, seems to be relatively improbable. The chance that they both begin to have the same problem at the same time even less probable. I would appreciate some comments from the maintainer of ahc and could really do without speculation. Assume I have used the scientific method over the last four months and have allieviated the most obvious things first. A last note, I currently am not subscribed to the lists because problems with my provider. A cc to me would be greatly appreciated (assuming I'm not bounced for not being on the list in the first place). To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 5 8:54:10 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id D1B151529E for ; Fri, 5 Nov 1999 08:53:55 -0800 (PST) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id QAA33508; Fri, 5 Nov 1999 16:53:19 GMT (envelope-from geoffb) Date: Fri, 5 Nov 1999 16:53:19 +0000 From: Geoff Buckingham To: "Kenneth D. Merry" Cc: Saeki Takashi , freebsd-scsi@FreeBSD.ORG Subject: Re: initio scsi controller Message-ID: <19991105165319.E32862@chuggalug.clues.com> References: <19991031033617P.saeki@ba2.so-net.ne.jp> <199910301920.NAA17716@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199910301920.NAA17716@panzer.kdm.org>; from Kenneth D. Merry on Sat, Oct 30, 1999 at 01:20:53PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, Oct 30, 1999 at 01:20:53PM -0600, Kenneth D. Merry wrote: > Saeki Takashi wrote... > > Hi Thomas, Are you writing the driver for the initio SCSI controller? > > But Initio already provides FreeBSD CAM SCSI drivers for the controller > > on their WebPage. > > > > see http://www.initio.com/download.htm#misc > > > > >> BSD Kernel (9XXX/A100 for BSD) > > >> 1.9M (8/1/99) > > >> v3.0 > > > > > > This drivers seems to be developed for FreeBSD 3.0, but I can compile it > > into FreeBSD 3.3-RELEASE, without hitch. > > Now I am using I/O EXPRESSWAY INI-9200U Dual Channel PCI-Ultra SCSI I/F, > > flawlessly. > > I'm glad to know it works. You're the first person (at least that I can > remember) who I've heard from that has one of these cards. > I too have one of these working (Iwill/SIDE 2935UW) > > I do not know why the drivers are not commited into FreeBSD. > > Commiters, would you please tell me why? > > I would like to see the drivers merged into FreeBSD. > > There are a couple of reasons: > > - lack of hardware > - time > - copyright on one of the drivers > > The driver for their Ultra-Wide SCSI cards consists of three files. One > has a standard BSD-style copyright on it. One has a proprietary copyright > on it. The last one has no copyright. We cannot integrate that driver into > the tree without getting those two files fixed. > > Their Ultra 2 driver, on the other hand, has a BSD-style copyright on both > files. > > The first two problems will hopefully be solved by Thomas. As for the last > one, I think he is going to try to contact Initio about it. Is there anything I can do to assist in 1, 2 or 3 ? -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 5 11:24:31 1999 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 C012A14BE9 for ; Fri, 5 Nov 1999 11:24:28 -0800 (PST) (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 NAA59792; Fri, 5 Nov 1999 13:24:08 -0600 (CST) (envelope-from cdillon@wolves.k12.mo.us) Date: Fri, 5 Nov 1999 13:24:07 -0600 (CST) From: Chris Dillon To: Ollivier Robert Cc: scsi@FreeBSD.ORG Subject: Re: SYM-0.9.0 ok for 3.3 and -current (was SYM driver available for -stable) In-Reply-To: <19991105001108.A1825@keltia.freenix.fr> 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, 5 Nov 1999, Ollivier Robert wrote: > According to Gerard Roudier: > > Could you check that tagged commands and disconnections are enabled for > Tagged commands are disabled for these drives (IBM DCAS) because > it gives them bad perfs in sequential reads/writes. I've > re-enabled them on my machine because I think tags help for > multiple accesses and I don't care that much for sequential > perfs... You have the same drives I do. I forgot that there was a quirk entry for these drives disabling tagged commands. Do you see any "choppyness" using either the old ncr driver or the new sym driver when you have the system under a high I/O load? With tags enabled/disabled? Under heavy CPU load as well? I would spent some time clarifying the "choppyness" I'm seeing a bit better yesterday, but I had to go out and buy a new car instead. Maybe tonight I'll look into it. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and Alpha architectures (SPARC under development). ( http://www.freebsd.org ) "One should admire Windows users. It takes a great deal of courage to trust Windows with your data." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 5 11:54:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 1A8D714D58 for ; Fri, 5 Nov 1999 11:54:16 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id MAA69413; Fri, 5 Nov 1999 12:43:02 -0700 (MST) Date: Fri, 5 Nov 1999 12:43:02 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199911051943.MAA69413@narnia.plutotech.com> To: shaun@shamz.net Cc: scsi@FreeBSD.org Subject: Re: scsi bus errors X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <19991105120951.C1083@shamz.net> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <19991105120951.C1083@shamz.net> you wrote: [ I've reformatted your mail so it fits in 80 columns. This makes it much easier to read. ] > Hi, > > After reading the lists and trying about everything under the sun > to get the errors to abate, I am finally writing. The setup is > about the same as all the others with SCB timeout errors. ... > I left out the logs because they don't seem to have been more than > grounds for speculation about termination and such up until now. As far as I know, we've resolved all other "timeout" type errors with the ahc driver. This was only possible because the people having the problems gave detailed information about their setup and the errors that occurred. In other words, provide the output from 'dmesg' for the system having problems as well as the messages output by the driver when the errors occur and we'll see what we can do. Leave the determination of what is valuable information to the experts. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 5 12:25:35 1999 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 DE7891530F for ; Fri, 5 Nov 1999 12:25:27 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA00785; Fri, 5 Nov 1999 13:23:58 -0700 (MST) (envelope-from ken) Message-Id: <199911052023.NAA00785@panzer.kdm.org> Subject: Re: initio scsi controller In-Reply-To: <19991105165319.E32862@chuggalug.clues.com> from Geoff Buckingham at "Nov 5, 1999 04:53:19 pm" To: geoffb@chuggalug.clues.com (Geoff Buckingham) Date: Fri, 5 Nov 1999 13:23:58 -0700 (MST) Cc: saeki@ba2.so-net.ne.jp (Saeki Takashi), freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Geoff Buckingham wrote... > On Sat, Oct 30, 1999 at 01:20:53PM -0600, Kenneth D. Merry wrote: > > I'm glad to know it works. You're the first person (at least that I can > > remember) who I've heard from that has one of these cards. > > > I too have one of these working (Iwill/SIDE 2935UW) With FreeBSD? > > There are a couple of reasons: > > > > - lack of hardware > > - time > > - copyright on one of the drivers > > > > The driver for their Ultra-Wide SCSI cards consists of three files. One > > has a standard BSD-style copyright on it. One has a proprietary copyright > > on it. The last one has no copyright. We cannot integrate that driver into > > the tree without getting those two files fixed. > > > > Their Ultra 2 driver, on the other hand, has a BSD-style copyright on both > > files. > > > > The first two problems will hopefully be solved by Thomas. As for the last > > one, I think he is going to try to contact Initio about it. > > Is there anything I can do to assist in 1, 2 or 3 ? Sure. Talk to Thomas Graichen , and see if he needs any help testing the driver. If he hasn't already done it, it might also be good to contact Initio and see if they'll fix the copyright on the driver for their Ultra Wide boards/chips. 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 Nov 5 13: 3:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from c99946-a.spokn1.wa.home.com (c99946-a.spokn1.wa.home.com [24.1.30.98]) by hub.freebsd.org (Postfix) with ESMTP id 9625714D64 for ; Fri, 5 Nov 1999 13:03:49 -0800 (PST) (envelope-from ted@stargate.org) Received: from localhost (ted@localhost) by c99946-a.spokn1.wa.home.com (8.9.3/8.9.3) with ESMTP id QAA02015 for ; Fri, 5 Nov 1999 16:48:28 -0800 Date: Fri, 5 Nov 1999 16:48:28 -0800 (PST) From: "T.D. Brace" To: freebsd-scsi@freebsd.org Subject: Scsi problem? (fwd) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I have been having problems with a web server crashing on a regular basis. It's built with an Abit BX6, adaptec 2940uw, PIII 450, and 512mb ram running freebsd 3.1 stable. This machine is in a remote location, so I can't swap out components to find the problem easily. It seems to encounter scsi errors periodically (4-5 times a day) and reboot/crash. I was hoping by posting the error log, someone could give me thier best guess as to the problem. Thanks for any help. -Ted /var/log/messages: ============================================================================== Nov 5 12:15:52 loucha /kernel: ahc0: WARNING no command for scb 40 (cmdcmplt) Nov 5 12:15:52 loucha /kernel: QOUTPOS = 234 Nov 5 12:15:52 loucha /kernel: ahc0: WARNING no command for scb 40 (cmdcmplt) Nov 5 12:15:52 loucha /kernel: QOUTPOS = 235 Nov 5 12:15:52 loucha /kernel: ahc0: WARNING no command for scb 40 (cmdcmplt) Nov 5 12:15:52 loucha /kernel: QOUTPOS = 236 Nov 5 12:15:52 loucha /kernel: ahc0: WARNING no command for scb 40 (cmdcmplt) Nov 5 12:15:52 loucha /kernel: QOUTPOS = 237 Nov 5 12:15:52 loucha /kernel: ahc0: WARNING no command for scb 40 (cmdcmplt) Nov 5 12:15:52 loucha /kernel: QOUTPOS = 238 Nov 5 12:15:52 loucha /kernel: ahc0: WARNING no command for scb 40 (cmdcmplt) Nov 5 12:15:52 loucha /kernel: QOUTPOS = 239 Nov 5 12:15:52 loucha /kernel: ahc0: WARNING no command for scb 40 (cmdcmplt) Nov 5 12:15:52 loucha /kernel: QOUTPOS = 240 Nov 5 12:15:52 loucha /kernel: ahc0: WARNING no command for scb 40 (cmdcmplt) Nov 5 12:15:52 loucha /kernel: QOUTPOS = 241 Nov 5 12:33:10 loucha /kernel: Copyright (c) 1992-1999 FreeBSD Inc. Nov 5 12:33:10 loucha /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Nov 5 12:33:10 loucha /kernel: The Regents of the University of California. All rights reserved. Nov 5 12:33:10 loucha /kernel: FreeBSD 3.1-19990217-STABLE #2: Sat Mar 13 18:20:16 PST 1999 Nov 5 12:33:10 loucha /kernel: xxx@xxx.xxx.xxx:/usr/src/sys/compile/tek Nov 5 12:33:10 loucha /kernel: Timecounter "i8254" frequency 1193182 Hz Nov 5 12:33:10 loucha /kernel: Timecounter "TSC" frequency 350797116 Hz Nov 5 12:33:10 loucha /kernel: CPU: Pentium II/Xeon/Celeron (350.80-MHz 686-class CPU) Nov 5 12:33:10 loucha /kernel: Origin = "GenuineIntel" Id = 0x651 Stepping=1 Nov 5 12:33:10 loucha /kernel: Features=0x183f9ff> Nov 5 12:33:10 loucha /kernel: real memory = 536870912 (524288K bytes) Nov 5 12:33:10 loucha /kernel: avail memory = 519852032 (507668K bytes) Nov 5 12:33:10 loucha /kernel: Preloaded elf kernel "kernel" at 0xf023b000. Nov 5 12:33:10 loucha /kernel: Probing for devices on PCI bus 0: Nov 5 12:33:10 loucha /kernel: chip0: rev 0x02 on pci0.0.0 Nov 5 12:33:10 loucha /kernel: chip1: rev 0x02 on pci0.1.0 Nov 5 12:33:10 loucha /kernel: chip2: rev 0x02 on pci0.7.0 Nov 5 12:33:10 loucha /kernel: chip3: rev 0x02 on pci0.7.3 Nov 5 12:33:10 loucha /kernel: fxp0: rev Nov 5 12:33:10 loucha /kernel: 0x05 int a irq 11 on pci0.9.0 Nov 5 12:33:10 loucha /kernel: fxp0: Ethernet address 00:90:27:1c:30:12 Nov 5 12:33:10 loucha /kernel: ahc0: rev 0x00 int a irq 10 on pci0.13.0 Nov 5 12:33:10 loucha /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Nov 5 12:33:10 loucha /kernel: Probing for devices on PCI bus 1: Nov 5 12:33:10 loucha /kernel: vga0: rev 0x01 int a irq 15 on pci1.0.0 Nov 5 12:33:10 loucha /kernel: Probing for devices on the ISA bus: Nov 5 12:33:10 loucha /kernel: sc0 on isa Nov 5 12:33:10 loucha /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Nov 5 12:33:10 loucha /kernel: atkbdc0 at 0x60-0x6f on motherboard Nov 5 12:33:10 loucha /kernel: atkbd0 irq 1 on isa Nov 5 12:33:10 loucha /kernel: psm0 not found Nov 5 12:33:10 loucha /kernel: vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa Nov 5 12:33:10 loucha /kernel: npx0 on motherboard Nov 5 12:33:10 loucha /kernel: npx0: INT 16 interface Nov 5 12:33:10 loucha /kernel: Waiting 15 seconds for SCSI devices to settle Nov 5 12:33:10 loucha /kernel: changing root device to da0s1a Nov 5 12:33:10 loucha /kernel: da0 at ahc0 bus 0 target 0 lun 0 Nov 5 12:33:10 loucha /kernel: da0: Fixed Direct Access SCSI-2 device Nov 5 12:33:10 loucha /kernel: da0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled Nov 5 12:33:10 loucha /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Nov 5 12:33:10 loucha /kernel: cd0 at ahc0 bus 0 target 1 lun 0 Nov 5 12:33:10 loucha /kernel: cd0: Removable CD-ROM SCSI-2 device Nov 5 12:33:10 loucha /kernel: cd0: 10.0MB/s transfers (10.0MHz, o Nov 5 12:33:10 loucha /kernel: ffset 15) Nov 5 12:33:10 loucha /kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present Nov 5 12:33:10 loucha /kernel: WARNING: / was not properly dismounted Nov 5 12:33:10 loucha named[128]: starting. named 8.1.2 Wed Feb 17 01:10:08 GMT 1999 rk@merlin.rz.tu-clausthal.de:/usr/obj/usr/src/usr.sbin/named Nov 5 12:33:11 loucha named[129]: Ready to answer queries. Nov 5 12:36:21 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 64 Nov 5 12:36:22 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 63 Nov 5 12:36:22 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 62 Nov 5 12:36:22 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 61 Nov 5 12:36:22 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 60 Nov 5 12:36:22 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 59 Nov 5 12:36:22 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 58 Nov 5 12:36:22 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 57 Nov 5 12:36:22 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 56 Nov 5 12:36:22 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 55 Nov 5 12:36:23 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 54 Nov 5 12:36:23 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 53 Nov 5 12:36:23 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 52 Nov 5 12:36:23 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 51 Nov 5 12:36:23 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 50 Nov 5 12:36:27 loucha /kernel: (da0:ahc0:0:0:0): tagged openings now 49 Nov 5 12:45:49 loucha /kernel: Copyright (c) 1992-1999 FreeBSD Inc. Nov 5 12:45:49 loucha /kernel: Copyright (c) 1982, 1986, 1989, 1991, 1993 Nov 5 12:45:49 loucha /kernel: The Regents of the University of California. All rights reserved. Nov 5 12:45:49 loucha /kernel: FreeBSD 3.1-19990217-STABLE #2: Sat Mar 13 18:20:16 PST 1999 Nov 5 12:45:49 loucha /kernel: xxx@xxx.xxx.xxx:/usr/src/sys/compile/tek Nov 5 12:45:49 loucha /kernel: Timecounter "i8254" frequency 1193182 Hz Nov 5 12:45:49 loucha /kernel: Timecounter "TSC" frequency 350797295 Hz Nov 5 12:45:49 loucha /kernel: CPU: Pentium II/Xeon/Celeron (350.80-MHz 686-class CPU) Nov 5 12:45:49 loucha /kernel: Origin = "GenuineIntel" Id = 0x651 Stepping=1 Nov 5 12:45:49 loucha /kernel: Features=0x183f9ff> Nov 5 12:45:49 loucha /kernel: real memory = 536870912 (524288K bytes) Nov 5 12:45:49 loucha /kernel: avail memory = 519852032 (507668K bytes) Nov 5 12:45:49 loucha /kernel: Preloaded elf kernel "kernel" at 0xf023b000. Nov 5 12:45:49 loucha /kernel: Probing for devices on PCI bus 0: Nov 5 12:45:49 loucha /kernel: chip0: rev 0x02 on pci0.0.0 Nov 5 12:45:49 loucha /kernel: chip1: rev 0x02 on pci0.1.0 Nov 5 12:45:49 loucha /kernel: chip2: rev 0x02 on pci0.7.0 Nov 5 12:45:49 loucha /kernel: chip3: rev 0x02 on pci0.7.3 Nov 5 12:45:49 loucha /kernel: fxp0: rev Nov 5 12:45:49 loucha /kernel: 0x05 int a irq 11 on pci0.9.0 Nov 5 12:45:49 loucha /kernel: fxp0: Ethernet address 00:90:27:1c:30:12 Nov 5 12:45:49 loucha /kernel: ahc0: rev 0x00 int a irq 10 on pci0.13.0 Nov 5 12:45:49 loucha /kernel: ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Nov 5 12:45:49 loucha /kernel: Probing for devices on PCI bus 1: Nov 5 12:45:49 loucha /kernel: vga0: rev 0x01 int a irq 15 on pci1.0.0 Nov 5 12:45:49 loucha /kernel: Probing for devices on the ISA bus: Nov 5 12:45:49 loucha /kernel: sc0 on isa Nov 5 12:45:49 loucha /kernel: sc0: VGA color <16 virtual consoles, flags=0x0> Nov 5 12:45:49 loucha /kernel: atkbdc0 at 0x60-0x6f on motherboard Nov 5 12:45:49 loucha /kernel: atkbd0 irq 1 on isa Nov 5 12:45:49 loucha /kernel: psm0 not found Nov 5 12:45:49 loucha /kernel: vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa Nov 5 12:45:49 loucha /kernel: npx0 on motherboard Nov 5 12:45:49 loucha /kernel: npx0: INT 16 interface Nov 5 12:45:49 loucha /kernel: Waiting 15 seconds for SCSI devices to settle Nov 5 12:45:49 loucha /kernel: changing root device to da0s1a Nov 5 12:45:49 loucha /kernel: da0 at ahc0 bus 0 target 0 lun 0 Nov 5 12:45:49 loucha /kernel: da0: Fixed Direct Access SCSI-2 device Nov 5 12:45:49 loucha /kernel: da0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled Nov 5 12:45:49 loucha /kernel: da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) Nov 5 12:45:49 loucha /kernel: cd0 at ahc0 bus 0 target 1 lun 0 Nov 5 12:45:49 loucha /kernel: cd0: Removable CD-ROM SCSI-2 device Nov 5 12:45:49 loucha /kernel: cd0: 10.0MB/s transfers (10.0MHz, o Nov 5 12:45:49 loucha /kernel: ffset 15) Nov 5 12:45:49 loucha /kernel: cd0: Attempt to query device size failed: NOT READY, Medium not present Nov 5 12:45:49 loucha /kernel: WARNING: / was not properly dismounted Nov 5 12:45:49 loucha named[128]: starting. named 8.1.2 Wed Feb 17 01:10:08 GMT 1999 rk@merlin.rz.tu-clausthal.de:/usr/obj/usr/src/usr.sbin/named Nov 5 12:45:50 loucha named[129]: Ready to answer queries. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 5 13:24:58 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front5m.grolier.fr (front5m.grolier.fr [195.36.216.55]) by hub.freebsd.org (Postfix) with ESMTP id 22E9F14D64 for ; Fri, 5 Nov 1999 13:24:42 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-224-24.villette.club-internet.fr [195.36.224.24]) by front5m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id WAA15284; Fri, 5 Nov 1999 22:24:33 +0100 (MET) Date: Fri, 5 Nov 1999 23:47:57 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: Ollivier Robert Cc: scsi@FreeBSD.ORG Subject: Re: SYM driver available for -stable In-Reply-To: <19991104224808.A1140@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 4 Nov 1999, Ollivier Robert wrote: > According to Gerard Roudier: > > I just made available SYM driver 0.9.0 as a tar file that contains full= =20 > > driver files. This avoids applying 8 nasty patches successively. >=20 > I'm now running with your new driver and it seems to run fine. Dunno real= ly if=20 > it faster or not (seems a bit but Bonnie -- a poor benchmark I know -- is > almost the same). BTW, I've the same problem with your driver than I had = with > the ncr one: the LED is constantly on... With the ncr driver, adding >=20 > options SCSI_NCR_SYMBIOS_COMPAT # for LEDs For controllers with NVRAM probed as SYMBIOS format, the driver should drive the LED, but I heven't tested it since my box has no available LED. I had proposed STefan this SCSI_NCR_SYMBIOS_COMPAT option since the ncr driver (and the Linux ncr53c8xx driver) was unable to read the NVRAM at this time. For now, the sym driver is not fully integrated in the kernel options scheme (this will happen for version 1.0). Options are gathered in the sym_conf.h file. You may edit this file, define SYMSETUP_SCSI_LED to 1 and let us know if the 810a now is just fine for your next Christmas tree. :)= =20 > "fixes" the problem. Which #define does the same for sym0 ? SYM_OPT_LED0 = ? >=20 > -------Sequential Output-------- ---Sequential Input-- --Ra= ndom-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Se= eks--- > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /se= c %CPU > ncr0 200 4950 65.8 4938 20.7 1907 9.0 5665 47.8 5867 15.8 91.= 2 3.6 >=20 > -------Sequential Output-------- ---Sequential Input-- --Ra= ndom-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Se= eks--- > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /se= c %CPU > sym0 200 4902 62.7 4627 16.8 1965 8.2 5005 40.8 5884 13.9 136.= 0 4.3 Some differences are strange, especially the random seek one. Even a 1542C against the fastest possible HBA/driver pair should not lead to a so large difference. The CPU difference seems a bit high too. If you have time for, could you check the effect of number of tags with your drive using the sym driver. Basically, the following values should be enough to check if this makes significant differences:=20 1 (no tags), 4, 8, 16. > The disk is an 5400 rpm IBM. >=20 > sym0: <875> irq 9 at device 11.0 on pci0 > sym0: Symbios NVRAM, ID 7, Fast-20, parity checking > sym0: open drain IRQ line driver, using on-chip SRAM > sym1: <810a> irq 11 at device 12.0 on pci0 > sym1: No NVRAM, ID 7, Fast-10, parity checking > sym0: Downloading SCSI SCRIPTS. > (noperiph:sym0:0:-1:-1): SCSI bus reset delivered. > Creating DISK da0 > Creating DISK da1 > Creating DISK da2 > Creating DISK da12 > da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device=20 > da0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing = Enabled > da0: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) >=20 > BTW I got the following two messages when playing with camcontrol... >=20 > WARNING: driver xpt should register devices with make_dev() (dev_t =3D "#= xpt/0") > WARNING: driver pass should register devices with make_dev() (dev_t =3D "= #pass/0") G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 5 14:20:22 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id DB97E15368 for ; Fri, 5 Nov 1999 14:20:17 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id PAA69526; Fri, 5 Nov 1999 15:09:28 -0700 (MST) Date: Fri, 5 Nov 1999 15:09:28 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199911052209.PAA69526@narnia.plutotech.com> To: "T.D. Brace" Cc: scsi@FreeBSD.org Subject: Re: Scsi problem? (fwd) X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > Hello, > > I have been having problems with a web server crashing on a regular basis. > It's built with an Abit BX6, adaptec 2940uw, PIII 450, and 512mb ram > running freebsd 3.1 stable. This machine is in a remote location, so > I can't swap out components to find the problem easily. It seems to > encounter scsi errors periodically (4-5 times a day) and reboot/crash. > > I was hoping by posting the error log, someone could give me thier best > guess as to the problem. > > Thanks for any help. > > -Ted > > /var/log/messages: > ============================================================================== > Nov 5 12:15:52 loucha /kernel: ahc0: WARNING no command for scb 40 (cmdcmplt) > Nov 5 12:15:52 loucha /kernel: QOUTPOS = 234 These messages are somewhat disturbing. They either mean that the drive is continually signaling that the same command has completed even though the kernel has no record of it being outstanding, or the output queue (pointers or data) is corrupted. Can you give me an idea on what kinds of loads cause the error to occur? -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 5 15:34: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from hotmail.com (f26.law4.hotmail.com [216.33.149.26]) by hub.freebsd.org (Postfix) with SMTP id 004AD14DC2 for ; Fri, 5 Nov 1999 15:33:48 -0800 (PST) (envelope-from gandalf24@hotmail.com) Received: (qmail 83206 invoked by uid 0); 5 Nov 1999 23:33:03 -0000 Message-ID: <19991105233303.83205.qmail@hotmail.com> Received: from 165.250.91.68 by www.hotmail.com with HTTP; Fri, 05 Nov 1999 15:33:03 PST X-Originating-IP: [165.250.91.68] From: "Gandalf T. Grey" To: freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: 2nd Query: Is someone 'camifying' ncv0 scsi? Date: Fri, 05 Nov 1999 15:33:03 PST Mime-Version: 1.0 Content-Type: text/plain; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I sent this out recently, but I don't recall getting from the list, and I just searched but couldn't find it in the archives. I never got any responses, so I was hoping the message was just dropped somehow. I'm also including the scsi mailing list, since I'm asking about a scsi driver. OK, here we go again... Can anyone tell me if someone is working on / has worked on /is willing to work on Camifiying ncv0? I've been told that it worked fine under 2.x, and that it just needs to be camified to work under 3.x. I just want to find out whether there is any hope of getting my Panasonic pcmcia scsi (KME KXLC004) working on my ThinkPad 560x running 3.2-RELEASE. TIA for any info you can offer, I'm trying not to give up hope. G. ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 5 15:52: 3 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id 3349F14E7F for ; Fri, 5 Nov 1999 15:51:23 -0800 (PST) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id XAA35249; Fri, 5 Nov 1999 23:50:12 GMT (envelope-from geoffb) Date: Fri, 5 Nov 1999 23:50:12 +0000 From: Geoff Buckingham To: "Kenneth D. Merry" Cc: Saeki Takashi , freebsd-scsi@FreeBSD.ORG Subject: Re: initio scsi controller Message-ID: <19991105235012.A34663@chuggalug.clues.com> References: <19991105165319.E32862@chuggalug.clues.com> <199911052023.NAA00785@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199911052023.NAA00785@panzer.kdm.org>; from Kenneth D. Merry on Fri, Nov 05, 1999 at 01:23:58PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Nov 05, 1999 at 01:23:58PM -0700, Kenneth D. Merry wrote: > Geoff Buckingham wrote... > > On Sat, Oct 30, 1999 at 01:20:53PM -0600, Kenneth D. Merry wrote: > > > I'm glad to know it works. You're the first person (at least that I can > > > remember) who I've heard from that has one of these cards. > > > > > I too have one of these working (Iwill/SIDE 2935UW) > > With FreeBSD? yep 3.3-RELEASE -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 5 15:57:45 1999 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 5FE5215199; Fri, 5 Nov 1999 15:52:19 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id QAA02229; Fri, 5 Nov 1999 16:51:27 -0700 (MST) (envelope-from ken) Message-Id: <199911052351.QAA02229@panzer.kdm.org> Subject: Re: 2nd Query: Is someone 'camifying' ncv0 scsi? In-Reply-To: <19991105233303.83205.qmail@hotmail.com> from "Gandalf T. Grey" at "Nov 5, 1999 03:33:03 pm" To: gandalf24@hotmail.com (Gandalf T. Grey) Date: Fri, 5 Nov 1999 16:51:27 -0700 (MST) Cc: freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gandalf T. Grey wrote... > Hi, > > I sent this out recently, but I don't recall getting from the list, and I > just searched but couldn't find it in the archives. > > I never got any responses, so I was hoping the message was just dropped > somehow. Well, if you get no responses, it generally means no one knows the answer. > I'm also including the scsi mailing list, since I'm asking about a scsi > driver. > > OK, here we go again... > > Can anyone tell me if someone is working on / has worked on /is willing to > work on Camifiying ncv0? > > I've been told that it worked fine under 2.x, and that it just needs to be > camified to work under 3.x. > > I just want to find out whether there is any hope of getting my Panasonic > pcmcia scsi (KME KXLC004) working on my ThinkPad 560x running 3.2-RELEASE. > > TIA for any info you can offer, I'm trying not to give up hope. Well, in view of the fact that I've never even heard of a "ncv" driver, and can't find any reference to such a driver (*) in the pre-CAM -current tree, I think your chances may be kinda slim. (*) I did find one reference to "ncv" in sys/i386/isa/scsi_dvcfg.h, but that's it. So you'll need to explain what driver you're talking about, and what chipset it supports. (i.e. what chipset is in this Panasonic SCSI card) As far as I know, there has never been a "ncv" driver in the tree. 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 Nov 5 16:50:21 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id EEC1A14E0F for ; Fri, 5 Nov 1999 16:50:15 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id BAA18520; Sat, 6 Nov 1999 01:50:07 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 5FFC68711; Sat, 6 Nov 1999 01:01:03 +0100 (CET) Date: Sat, 6 Nov 1999 01:01:03 +0100 From: Ollivier Robert To: Gerard Roudier Cc: scsi@FreeBSD.ORG Subject: Re: SYM driver available for -stable Message-ID: <19991106010103.A2215@keltia.freenix.fr> Mail-Followup-To: Gerard Roudier , scsi@FreeBSD.ORG References: <19991104224808.A1140@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gerard Roudier disait : > sym_conf.h file. You may edit this file, define SYMSETUP_SCSI_LED to 1 and > let us know if the 810a now is just fine for your next Christmas tree. :) Doesn't seem to make any difference. The light (for the first controller that is the 875) is still on permanently. > 1 (no tags), 4, 8, 16. Here are the results: NCR / SYM with 1, 4, 8 and 16 tags -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU ncr-1 200 3098 40.9 2998 12.7 1803 8.1 5791 48.4 5671 14.8 126.7 4.1 sym-1 200 3047 38.7 2983 11.6 1840 7.4 5715 46.2 5839 13.5 125.3 3.9 ncr-4 200 4589 60.2 4658 18.7 1788 8.3 5745 48.5 5794 15.7 130.7 4.5 sym-4 200 4587 58.4 4660 17.0 1896 8.0 4911 39.8 5613 13.4 132.0 4.3 ncr-8 200 4670 61.3 4887 19.5 1900 8.9 5736 48.0 5840 15.6 130.0 4.5 sym-8 200 4811 61.2 4849 17.7 1947 8.3 5729 46.4 5596 13.5 129.2 4.1 ncr-16 200 4687 60.9 4916 19.9 1867 8.8 5748 48.0 5839 15.6 131.3 4.5 sym-16 200 4802 60.8 4697 17.1 1960 8.1 5192 41.9 5785 14.0 126.0 4.2 -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Nov 5 17:51:27 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from c99946-a.spokn1.wa.home.com (c99946-a.spokn1.wa.home.com [24.1.30.98]) by hub.freebsd.org (Postfix) with ESMTP id 3F1F314C37 for ; Fri, 5 Nov 1999 17:51:24 -0800 (PST) (envelope-from ted@stargate.org) Received: from localhost (ted@localhost) by c99946-a.spokn1.wa.home.com (8.9.3/8.9.3) with ESMTP id VAA02978; Fri, 5 Nov 1999 21:36:56 -0800 Date: Fri, 5 Nov 1999 21:36:56 -0800 (PST) From: "T.D. Brace" To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: Scsi problem? (fwd) In-Reply-To: <199911052209.PAA69526@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 5 Nov 1999, Justin T. Gibbs wrote: > > /var/log/messages: > > ============================================================================== > > Nov 5 12:15:52 loucha /kernel: ahc0: WARNING no command for scb 40 (cmdcmplt) > > Nov 5 12:15:52 loucha /kernel: QOUTPOS = 234 > > These messages are somewhat disturbing. They either mean that the > drive is continually signaling that the same command has completed > even though the kernel has no record of it being outstanding, or the > output queue (pointers or data) is corrupted. Can you give me an idea > on what kinds of loads cause the error to occur? > > -- > Justin > Nothing too major. 200-400 processes average, pulling web pages and images. Sql server also (using 4% of the cpu time). Load averages run less than 2.0 at the highest. I'm concerned I have a hardware failure (drive?) coming. Are there any issues with 3.1-S that I am not aware of? Could faulty motherboard / memory cause this kind of errors? We have a dozen or so freebsd boxes, 4 of them are ABit based - these seem to cause us 90% of our problems. Any ideas on where to start would be greatly appreciated. Thanks, -Ted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 6 0: 1: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front3m.grolier.fr (front3m.grolier.fr [195.36.216.53]) by hub.freebsd.org (Postfix) with ESMTP id 79C2914C49 for ; Sat, 6 Nov 1999 00:00:59 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-111-142.villette.club-internet.fr [194.158.111.142]) by front3m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id JAA18676; Sat, 6 Nov 1999 09:00:45 +0100 (MET) Date: Sat, 6 Nov 1999 10:24:11 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: Ollivier Robert Cc: scsi@FreeBSD.ORG Subject: Re: SYM driver available for -stable In-Reply-To: <19991106010103.A2215@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 6 Nov 1999, Ollivier Robert wrote: > Gerard Roudier disait : a os=E9 =E9crire : :-) > > sym_conf.h file. You may edit this file, define SYMSETUP_SCSI_LED to 1 = and > > let us know if the 810a now is just fine for your next Christmas tree. = :)=20 >=20 > Doesn't seem to make any difference. The light (for the first controller = that > is the 875) is still on permanently. Will check the code. The sym does additionnal checking against some initial IO registers and may be this initial IO register value (GPCNTL) is not tested correctly or was not set as expected by BIOS.=20 > > 1 (no tags), 4, 8, 16. >=20 > Here are the results: >=20 > NCR / SYM with 1, 4, 8 and 16 tags >=20 > -------Sequential Output-------- ---Sequential Input-- --Ran= dom-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --See= ks--- > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec= %CPU > ncr-1 200 3098 40.9 2998 12..7 1803 8.1 5791 48.4 5671 14.8 126.7= 4.1 > sym-1 200 3047 38.7 2983 11.6 1840 7.4 5715 46.2 5839 13.5 125.3= 3.9 >=20 > ncr-4 200 4589 60.2 4658 18.7 1788 8.3 5745 48.5 5794 15.7 130.7= 4.5 =20 > sym-4 200 4587 58.4 4660 17.0 1896 8.0 4911 39.8 5613 13.4 132.0= 4.3 >=20 > ncr-8 200 4670 61.3 4887 19.5 1900 8.9 5736 48.0 5840 15.6 130.0= 4.5 > sym-8 200 4811 61.2 4849 17.7 1947 8.3 5729 46.4 5596 13.5 129.2= 4.1 >=20 > ncr-16 200 4687 60.9 4916 19.9 1867 8.8 5748 48.0 5839 15.6 131.3= 4.5 > sym-16 200 4802 60.8 4697 17.1 1960 8.1 5192 41.9 5785 14.0 126.0= 4.2=20 The only differences I expected are CPU load and may-be rewrites. - CPU because the sym driver uses O(1) everywhere. But I am surprised to=20 actually see a noticeable difference with a simple Bonnie benchmark. - Rewrite because: * lower latency may help device caching in this sitiation. * and the sym driver allocates tags in a circular manner (just a differen= ce=20 that seems to be a more soft policy for firmwares, especially broken ones) Other results should not be significantly different given the low throughput and low Transactions/Second that should allow the device to overlap latencies the same way for the both drivers.=20 The 5745/4911 and also the 5748/5192 read char results are extremally bogus IMO, since they not only correspond to -low throughtput/large IOs- cases but the kernel also perform prefetching (asynchronous readahead). A driver bug is obviously possible, but I would be very surprised of such a cause.=20 May-be, some Vinum array using something like 3..6 ultra-fast disks should be used for these kind of comparisons. Thanks a lot for your testing. I will try to understand the LED issue and let you know when I have some diffs. BTW, I donnot see any bad effect of using reasonable numbers tags with your hard disk under Bonnie.=20 Regards, G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 6 0:59:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front6m.grolier.fr (front6m.grolier.fr [195.36.216.56]) by hub.freebsd.org (Postfix) with ESMTP id A906014D12 for ; Sat, 6 Nov 1999 00:59:45 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-160-110.villette.club-internet.fr [195.36.160.110]) by front6m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id JAA03850; Sat, 6 Nov 1999 09:59:41 +0100 (MET) Date: Sat, 6 Nov 1999 11:23:07 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: Ollivier Robert Cc: scsi@FreeBSD.ORG Subject: Re: SYM driver available for -stable In-Reply-To: <19991106010103.A2215@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 6 Nov 1999, Ollivier Robert wrote: > Gerard Roudier disait : > > sym_conf.h file. You may edit this file, define SYMSETUP_SCSI_LED to 1 = and > > let us know if the 810a now is just fine for your next Christmas tree. = :)=20 >=20 > Doesn't seem to make any difference. The light (for the first controller = that > is the 875) is still on permanently. Here is a diff. I haven't checked that the LED handling is now OK since my box is lacking of available LEDs, but gave a try with 3.3 to check the driver hasn't been affected. Btw, the define to 1 of SYMSETUP_SCSI_LED is also required if any of your controller hasn't SYMBIOS NVRAM format detected by the driver. Reason is that only controllers that are compatible with SYMBIOS SDMS are guaranteed about assumption of LED handling through GPIO0 writing being actually safe since SDMS makes this assumption too. --- /tmp/SYM-0.9.0-19991024/sym_hipd.c=09Sun Oct 24 14:32:15 1999 +++ ./sym_hipd.c=09Sat Nov 6 10:52:20 1999 @@ -56,7 +56,7 @@ * SUCH DAMAGE. */ =20 -#define SYM_DRIVER_NAME=09"sym-0.9.0-19991024" +#define SYM_DRIVER_NAME=09"sym-0.9.1-19991106" =20 #include #include =09/* For offsetof */ @@ -9942,7 +9942,7 @@ =09np->scripth0->pm0_data_addr[0] =3D cpu_to_scr(SCRIPT_BA(np,pm0_data)); =09np->scripth0->pm1_data_addr[0] =3D cpu_to_scr(SCRIPT_BA(np,pm1_data)); =20 -#ifdef=09SYM_OPT_LED0 + =09/* =09 * Still some for LED support. =09 */ @@ -9954,7 +9954,7 @@ =09=09np->script0->start[0] =3D =09=09=09=09cpu_to_scr(SCR_REG_REG(gpreg, SCR_AND, 0xfe)); =09} -#endif + =09/* =09 * Load SCNTL4 on reselection for the C10. =09 */ ---------------------- Cut Here -------------------------- As you can see, the C code that patches the SCRIPTS for the LED handling was conditionnaly compiled. Reason is that I changed my mind about the way to set-up the LED handling and forgot to remove the corresponding #ifdef/#endif. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 6 3:23:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.217.82.22]) by hub.freebsd.org (Postfix) with ESMTP id EFFB914BE7; Sat, 6 Nov 1999 03:23:16 -0800 (PST) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id LAA39443; Sat, 6 Nov 1999 11:23:10 GMT (envelope-from geoffb) Date: Sat, 6 Nov 1999 11:23:10 +0000 From: Geoff Buckingham To: "Kenneth D. Merry" Cc: "Gandalf T. Grey" , freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: 2nd Query: Is someone 'camifying' ncv0 scsi? Message-ID: <19991106112310.A39348@chuggalug.clues.com> References: <19991105233303.83205.qmail@hotmail.com> <199911052351.QAA02229@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <199911052351.QAA02229@panzer.kdm.org>; from Kenneth D. Merry on Fri, Nov 05, 1999 at 04:51:27PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Nov 05, 1999 at 04:51:27PM -0700, Kenneth D. Merry wrote: > Gandalf T. Grey wrote... > > Well, in view of the fact that I've never even heard of a "ncv" driver, and > can't find any reference to such a driver (*) in the pre-CAM -current tree, > I think your chances may be kinda slim. > > (*) I did find one reference to "ncv" in sys/i386/isa/scsi_dvcfg.h, but > that's it. > > So you'll need to explain what driver you're talking about, and what > chipset it supports. (i.e. what chipset is in this Panasonic SCSI card) > As far as I know, there has never been a "ncv" driver in the tree. > The ncv driver appears to have been for Q-logic PC-card SCSI controllers imported into PAO for 2.2.x from NetBSD PC98 However PAO for 3.x seems to have lost all scsi support. Is this because of some clash with cam, or simply non of the chipsets have cam drivers? 2.2.8 PAO support SCSI PC-cards: Adaptec SlimSCSI APA-1460 OK aic Adaptec SlimSCSI APA-1460A OK aic Adaptec SlimSCSI APA-1460AJ OK aic Adaptec SlimSCSI APA-1460B OK aic Adaptec SlimSCSI APA-1460J OK aic ALPHA DATA AD-PCS2 NG --- ALPHA DATA AD-PCS201 OK nin *14 CyQ've SFC-201 OK nin *14 Fujitsu FMV-J123 OK aic Fujitsu Towa Electron SC501 OK spc Future Domain SCSI2GO OK stg IBM SCSI PCMCIA Card OK stg ICM PSC-2401 SCSI OK stg *9 IO DATA PCSC-DV OK ncv IO DATA PCSC-F OK nin *14 IO DATA PCSC-II OK ncv IO DATA PCSC-V NG --- KME CDWORKMAN (KXLC002) OK ncv MACNICA MIRACLE SCSI II mPS-110 OK ncv Media Intelligent MSC-110 OK ncv Media Intelligent SCSI-2 PC Card MSC-200 OK ncv MELCO IFC-DC OK ncv MELCO IFC-DC2 (SCSI2) OK aic MELCO IFC-SC OK stg MELCO IFC-SC2 OK ncv MELCO IFC-SCD OK aic NEC PC-9801N-J03 OK ncv NEC PC-9801N-J03R OK ncv New Media BASICS SCSI OK ncv NewMedia BusToaster OK aic Pioneer PCP-PR24 OK nin *14 Pioneer PCP-PW1W OK ncv Qlogic Fast SCSI OK ncv RATOC REX-5535AC OK spc RATOC REX-5535AMC OK spc RATOC REX-5535X OK spc RATOC REX-5535XM OK spc RATOC REX-5536 OK stg RATOC REX-5536AM OK stg *9 RATOC REX-5536M OK stg RATOC REX-5572W (as SCSI) OK ncv RATOC REX-9530 OK ncv RATOC REX-9835X OK spc SONY PRD-250 CD-ROM Diskman OK aic *8 SONY PRD-650 CD-ROM Diskman OK aic *8 TAXAN ICD-400PN (KME KXLC002) OK ncv stg is a future domain card, nin and spc are a mystery to me. -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 6 8:55:10 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (Postfix) with ESMTP id 346C814E68 for ; Sat, 6 Nov 1999 08:54:58 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.3/frmug-2.5/nospam) with UUCP id RAA27644; Sat, 6 Nov 1999 17:54:53 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 671048711; Sat, 6 Nov 1999 10:02:16 +0100 (CET) Date: Sat, 6 Nov 1999 10:02:16 +0100 From: Ollivier Robert To: Gerard Roudier Cc: scsi@FreeBSD.ORG Subject: Re: SYM driver available for -stable Message-ID: <19991106100216.A4922@keltia.freenix.fr> Mail-Followup-To: Gerard Roudier , scsi@FreeBSD.ORG References: <19991106010103.A2215@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii User-Agent: Mutt/1.0pre2i In-Reply-To: X-Operating-System: FreeBSD 4.0-CURRENT/ELF AMD-K6/200 & 2x PPro/200 SMP Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gerard Roudier disait : > May-be, some Vinum array using something like 3..6 ultra-fast disks should > be used for these kind of comparisons. If you give me the disks, I'd happy to do any test you want :-) > Thanks a lot for your testing. I will try to understand the LED issue and > let you know when I have some diffs. Thanks. > BTW, I donnot see any bad effect of using reasonable numbers tags with > your hard disk under Bonnie. Neither am I. I've removed the quirk entry in cam_xpt.c... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 4.0-CURRENT #75: Tue Nov 2 21:03:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 6 9:31:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from rover.village.org (rover.village.org [204.144.255.49]) by hub.freebsd.org (Postfix) with ESMTP id 1A0BE14E97; Sat, 6 Nov 1999 09:31:40 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (harmony.village.org [10.0.0.6]) by rover.village.org (8.9.3/8.9.3) with ESMTP id KAA82505; Sat, 6 Nov 1999 10:31:38 -0700 (MST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost.village.org [127.0.0.1]) by harmony.village.org (8.9.3/8.8.3) with ESMTP id KAA22229; Sat, 6 Nov 1999 10:31:12 -0700 (MST) Message-Id: <199911061731.KAA22229@harmony.village.org> To: "Andrey A. Chernov" Subject: Re: -current panic on AHA Cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG In-reply-to: Your message of "Thu, 04 Nov 1999 11:03:59 +0300." <19991104110359.A2933@nagual.pp.ru> References: <19991104110359.A2933@nagual.pp.ru> Date: Sat, 06 Nov 1999 10:31:12 -0700 From: Warner Losh Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <19991104110359.A2933@nagual.pp.ru> "Andrey A. Chernov" writes: : Very fresh -current always paniced after detecting SCSI devices on : aha0: AHA-1542CF FW Rev. B.0 (ID=45) SCSI Host Adapter, SCSI ID 7, 16 CCBs : page fault: supervisor, read page not present : Old kernel from Oct 8 works nicely : Sorry can't provide more info about panic, it is remote computer. That's very odd. Any chance that you can provide more info on the panic? I'd like to look into this. Warner To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 6 10:42:34 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from front6m.grolier.fr (front6m.grolier.fr [195.36.216.56]) by hub.freebsd.org (Postfix) with ESMTP id 74A9114F61 for ; Sat, 6 Nov 1999 10:42:29 -0800 (PST) (envelope-from groudier@club-internet.fr) Received: from localhost (ppp-164-172.villette.club-internet.fr [195.36.164.172]) by front6m.grolier.fr (8.9.3/No_Relay+No_Spam_MGC990224) with SMTP id TAA25311; Sat, 6 Nov 1999 19:42:21 +0100 (MET) Date: Sat, 6 Nov 1999 21:05:47 +0100 (MET) From: Gerard Roudier X-Sender: groudier@localhost To: Ollivier Robert Cc: scsi@FreeBSD.ORG Subject: Re: SYM driver available for -stable In-Reply-To: <19991106100216.A4922@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 6 Nov 1999, Ollivier Robert wrote: > Gerard Roudier disait : > > May-be, some Vinum array using something like 3..6 ultra-fast disks sho= uld > > be used for these kind of comparisons. >=20 > If you give me the disks, I'd happy to do any test you want :-) If I had them :(, I would have already posted corresponding results. And if I had also equivalent controllers from other brands I would already have posted comparative benchmarks, by the way. > > Thanks a lot for your testing. I will try to understand the LED issue a= nd > > let you know when I have some diffs. >=20 > Thanks. Hope the fix I sent does fit. =20 > > BTW, I donnot see any bad effect of using reasonable numbers tags with > > your hard disk under Bonnie.=20 >=20 > Neither am I. I've removed the quirk entry in cam_xpt.c... My little finger told me that this quirk will be slightly adjusted, at least in -current. ;)=20 G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Nov 6 13:31:14 1999 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 1CB5314C40; Sat, 6 Nov 1999 13:31:06 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA01262; Sat, 6 Nov 1999 14:30:58 -0700 (MST) (envelope-from ken) Message-Id: <199911062130.OAA01262@panzer.kdm.org> Subject: Re: 2nd Query: Is someone 'camifying' ncv0 scsi? In-Reply-To: <19991106112310.A39348@chuggalug.clues.com> from Geoff Buckingham at "Nov 6, 1999 11:23:10 am" To: geoffb@chuggalug.clues.com (Geoff Buckingham) Date: Sat, 6 Nov 1999 14:30:58 -0700 (MST) Cc: gandalf24@hotmail.com (Gandalf T. Grey), freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG From: "Kenneth D. Merry" X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Geoff Buckingham wrote... > On Fri, Nov 05, 1999 at 04:51:27PM -0700, Kenneth D. Merry wrote: > > Gandalf T. Grey wrote... > > > > Well, in view of the fact that I've never even heard of a "ncv" driver, and > > can't find any reference to such a driver (*) in the pre-CAM -current tree, > > I think your chances may be kinda slim. > > > > (*) I did find one reference to "ncv" in sys/i386/isa/scsi_dvcfg.h, but > > that's it. > > > > So you'll need to explain what driver you're talking about, and what > > chipset it supports. (i.e. what chipset is in this Panasonic SCSI card) > > As far as I know, there has never been a "ncv" driver in the tree. > > > The ncv driver appears to have been for Q-logic PC-card SCSI controllers > imported into PAO for 2.2.x from NetBSD PC98 Ahh, okay. It makes a little more sense now. > However PAO for 3.x seems to have lost all scsi support. Is this because > of some clash with cam, or simply non of the chipsets have cam drivers? Well, none of the chipsets have CAM drivers, with one exception: > 2.2.8 PAO support SCSI PC-cards: > > Adaptec SlimSCSI APA-1460 OK aic > Adaptec SlimSCSI APA-1460A OK aic > Adaptec SlimSCSI APA-1460AJ OK aic > Adaptec SlimSCSI APA-1460B OK aic > Adaptec SlimSCSI APA-1460J OK aic The 'aic' driver was ported to CAM a few weeks ago by Luoqi Chen. I don't know whether there is a PCCARD front end for it yet. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message