From owner-freebsd-scsi Sun Feb 21 4:53:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp04.wxs.nl (smtp04.wxs.nl [195.121.6.59]) by hub.freebsd.org (Postfix) with ESMTP id 6BA12118BF for ; Sun, 21 Feb 1999 04:53:29 -0800 (PST) (envelope-from asmodai@wxs.nl) Received: from daemon.ninth-circle.org ([195.121.56.51]) by smtp04.wxs.nl (Netscape Messaging Server 3.61) with ESMTP id AAA1049; Sun, 21 Feb 1999 13:53:25 +0100 Received: from daemon.ninth-circle.org (daemon.ninth-circle.org [192.168.0.1]) by daemon.ninth-circle.org (8.9.3/8.9.3) with ESMTP id OAA00537; Sun, 21 Feb 1999 14:02:32 +0100 (CET) (envelope-from asmodai@wxs.nl) Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <000301be5bc4$0fde5820$0d20dfd0@elderdragon.empire.net> Date: Sun, 21 Feb 1999 14:02:32 +0100 (CET) Organization: Ninth Circle Enterprises From: Jeroen Ruigrok/Asmodai To: Robert Kirkpatrick Subject: RE: Adaptec AAA-133sa raid card question Cc: FreeBSD SCSI Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 19-Feb-99 Robert Kirkpatrick wrote: > trying to use a Adaptec AAA-133sa raid card > > Will this card work ? or not ? > I know the compaq raid card smart p2 works and I thought they were the > same. I don't know, best bet would be to ask our friends in SCSI. Julian, Kenneth or Wilco will probably know the answer ;) --- Jeroen Ruigrok van der Werven http://www.freebsdzine.org> asmodai(at)wxs.nl This is my Truth, tell me your's... Network/Security Specialist *BSD: Powered by Knowledge & Know-how To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 21 14:15:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from qix (hibou.obs-besancon.fr [193.52.184.7]) by hub.freebsd.org (Postfix) with ESMTP id 7846C10EB7 for ; Sun, 21 Feb 1999 14:15:39 -0800 (PST) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix (8.9.3/8.8.7) id XAA00376; Sun, 21 Feb 1999 23:18:58 +0100 (MET) Date: Sun, 21 Feb 1999 23:18:58 +0100 (MET) Message-Id: <199902212218.XAA00376@qix> X-Authentication-Warning: qix: jmz set sender to jmz@qix using -f From: Jean-Marc Zucconi To: scsi@FreeBSD.ORG Subject: LVD transfer rate X-Mailer: Emacs Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just installed a LVD drive and the boot message reports only 40MB/s transfer rate. I expected 80MB/s - did I something wrong ? da1: Fixed Direct Access SCSI-2 device da1: Serial Number RE205733 da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) This is the only device on the LVD bus (Adaptec controller on a Asus P2BDS). I also have drives on the 50pin connector, but this should not be the problem ? Jean-Marc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 21 14:24: 1 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DE6D116A8; Sun, 21 Feb 1999 14:23:58 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id PAA21380; Sun, 21 Feb 1999 15:23:58 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902212223.PAA21380@panzer.plutotech.com> Subject: Re: LVD transfer rate In-Reply-To: <199902212218.XAA00376@qix> from Jean-Marc Zucconi at "Feb 21, 1999 11:18:58 pm" To: jmz@FreeBSD.ORG (Jean-Marc Zucconi) Date: Sun, 21 Feb 1999 15:23:57 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jean-Marc Zucconi wrote... > I just installed a LVD drive and the boot message reports only 40MB/s > transfer rate. I expected 80MB/s - did I something wrong ? > > da1: Fixed Direct Access SCSI-2 device > da1: Serial Number RE205733 > da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled > da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) > > This is the only device on the LVD bus (Adaptec controller on a Asus > P2BDS). I also have drives on the 50pin connector, but this should not > be the problem ? There are several things to check: - some drives have a single-ended-only jumper. You should make sure the jumper settings are correct for LVD operation. - make sure there aren't any settings in the SCSI BIOS that would prevent things from going at LVD speeds. I seriously doubt this is your problem, but I've got a machine at work with two 18G Seagate Cheetah II's on a Super Micro motherboard with an onboard 7890. The problem is that the drives are SCA, and the SCA to 68-pin converters we put on them apparantly inhibit LVD. So they only run at 20MHz instead of 40MHz. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 21 14:52:48 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from qix (hibou.obs-besancon.fr [193.52.184.7]) by hub.freebsd.org (Postfix) with ESMTP id 855F811545 for ; Sun, 21 Feb 1999 14:52:37 -0800 (PST) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix (8.9.3/8.8.7) id XAA73327; Sun, 21 Feb 1999 23:55:44 +0100 (MET) Date: Sun, 21 Feb 1999 23:55:44 +0100 (MET) Message-Id: <199902212255.XAA73327@qix> X-Authentication-Warning: qix: jmz set sender to jmz@qix using -f From: Jean-Marc Zucconi To: ken@plutotech.com Cc: scsi@FreeBSD.ORG In-reply-to: <199902212223.PAA21380@panzer.plutotech.com> (ken@plutotech.com) Subject: Re: LVD transfer rate X-Mailer: Emacs Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> Kenneth D Merry writes: > Jean-Marc Zucconi wrote... >> I just installed a LVD drive and the boot message reports only 40MB/s >> transfer rate. I expected 80MB/s - did I something wrong ? >> >> da1: Fixed Direct Access SCSI-2 device >> da1: Serial Number RE205733 >> da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled >> da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) >> >> This is the only device on the LVD bus (Adaptec controller on a Asus >> P2BDS). I also have drives on the 50pin connector, but this should not >> be the problem ? > There are several things to check: > - some drives have a single-ended-only jumper. You should make sure the > jumper settings are correct for LVD operation. I have a jumper labelled `SE mode', and this jumper is ON, however the drive does not work if I remove the jumper: the drive appears in the SCSIselect utility, but it does not reports its capacity, and trying to format fails (Not ready, asc/ascq= 40/80). > - make sure there aren't any settings in the SCSI BIOS that would prevent > things from going at LVD speeds. It is set to 80MB/s > I seriously doubt this is your problem, but I've got a machine at work with > two 18G Seagate Cheetah II's on a Super Micro motherboard with an onboard > 7890. The problem is that the drives are SCA, and the SCA to 68-pin > converters we put on them apparantly inhibit LVD. So they only run at > 20MHz instead of 40MHz. No - connectors and cables are standard (80pins) Jean-Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 21 15: 2: 2 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 19C1410EC2; Sun, 21 Feb 1999 15:01:57 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id QAA21624; Sun, 21 Feb 1999 16:01:53 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902212301.QAA21624@panzer.plutotech.com> Subject: Re: LVD transfer rate In-Reply-To: <199902212255.XAA73327@qix> from Jean-Marc Zucconi at "Feb 21, 1999 11:55:44 pm" To: jmz@FreeBSD.ORG (Jean-Marc Zucconi) Date: Sun, 21 Feb 1999 16:01:53 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jean-Marc Zucconi wrote... > >>>>> Kenneth D Merry writes: > > > Jean-Marc Zucconi wrote... > >> I just installed a LVD drive and the boot message reports only 40MB/s > >> transfer rate. I expected 80MB/s - did I something wrong ? > >> > >> da1: Fixed Direct Access SCSI-2 device > >> da1: Serial Number RE205733 > >> da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled > >> da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) > >> > >> This is the only device on the LVD bus (Adaptec controller on a Asus > >> P2BDS). I also have drives on the 50pin connector, but this should not > >> be the problem ? > > > There are several things to check: > > > - some drives have a single-ended-only jumper. You should make sure the > > jumper settings are correct for LVD operation. > > I have a jumper labelled `SE mode', and this jumper is ON, however the > drive does not work if I remove the jumper: the drive appears in the > SCSIselect utility, but it does not reports its capacity, and trying > to format fails (Not ready, asc/ascq= 40/80). That jumper forces it into Single Ended mode. What kind of cable do you have? LVD drives don't have internal terminators. You need an LVD cable (one of the "twisty" 68-pin cables) with a terminator block on the end. > > - make sure there aren't any settings in the SCSI BIOS that would prevent > > things from going at LVD speeds. > > It is set to 80MB/s Good. > > I seriously doubt this is your problem, but I've got a machine at work with > > two 18G Seagate Cheetah II's on a Super Micro motherboard with an onboard > > 7890. The problem is that the drives are SCA, and the SCA to 68-pin > > converters we put on them apparantly inhibit LVD. So they only run at > > 20MHz instead of 40MHz. > > No - connectors and cables are standard (80pins) You have SCA disks? Is the cable terminated? Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 21 15: 5:47 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from verdi.nethelp.no (verdi.nethelp.no [158.36.41.162]) by hub.freebsd.org (Postfix) with SMTP id F0BAD116E4 for ; Sun, 21 Feb 1999 15:05:42 -0800 (PST) (envelope-from sthaug@nethelp.no) Received: (qmail 28704 invoked by uid 1001); 21 Feb 1999 23:05:41 +0000 (GMT) To: jmz@FreeBSD.ORG Cc: ken@plutotech.com, scsi@FreeBSD.ORG Subject: Re: LVD transfer rate From: sthaug@nethelp.no In-Reply-To: Your message of "Sun, 21 Feb 1999 23:55:44 +0100 (MET)" References: <199902212255.XAA73327@qix> X-Mailer: Mew version 1.05+ on Emacs 19.34.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Mon, 22 Feb 1999 00:05:41 +0100 Message-ID: <28702.919638341@verdi.nethelp.no> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > - some drives have a single-ended-only jumper. You should make sure the > > jumper settings are correct for LVD operation. > > I have a jumper labelled `SE mode', and this jumper is ON, however the > drive does not work if I remove the jumper: the drive appears in the > SCSIselect utility, but it does not reports its capacity, and trying > to format fails (Not ready, asc/ascq= 40/80). There's your answer. The "Force SE Mode" jumper must be off, and you need a separate LVD terminator. The disk *does not* have a jumper-selectable LVD terminator. See http://www.storage.ibm.com/techsup/hddtech/ddrs/ddrsjum.htm Btw, the same disk is working great here at 80 MB/s. Steinar Haug, Nethelp consulting, sthaug@nethelp.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 21 15:17:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from qix (hibou.obs-besancon.fr [193.52.184.7]) by hub.freebsd.org (Postfix) with ESMTP id 802CC10F74 for ; Sun, 21 Feb 1999 15:17:30 -0800 (PST) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix (8.9.3/8.8.7) id AAA23952; Mon, 22 Feb 1999 00:20:46 +0100 (MET) Date: Mon, 22 Feb 1999 00:20:46 +0100 (MET) Message-Id: <199902212320.AAA23952@qix> X-Authentication-Warning: qix: jmz set sender to jmz@qix using -f From: Jean-Marc Zucconi To: ken@plutotech.com Cc: scsi@FreeBSD.ORG In-reply-to: <199902212301.QAA21624@panzer.plutotech.com> (ken@plutotech.com) Subject: Re: LVD transfer rate X-Mailer: Emacs Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> Kenneth D Merry writes: >> I have a jumper labelled `SE mode', and this jumper is ON, however the >> drive does not work if I remove the jumper: the drive appears in the >> SCSIselect utility, but it does not reports its capacity, and trying >> to format fails (Not ready, asc/ascq= 40/80). > That jumper forces it into Single Ended mode. OK. this explain why I only get 40MB/s > What kind of cable do you have? LVD drives don't have internal > terminators. You need an LVD cable (one of the "twisty" 68-pin cables) > with a terminator block on the end. I have the right cable, the terminator block is currently removed, but during my tests without the SE jumper, I got similar results with and without the terminator block. >> > I seriously doubt this is your problem, but I've got a machine at work with >> > two 18G Seagate Cheetah II's on a Super Micro motherboard with an onboard >> > 7890. The problem is that the drives are SCA, and the SCA to 68-pin >> > converters we put on them apparantly inhibit LVD. So they only run at >> > 20MHz instead of 40MHz. >> >> No - connectors and cables are standard (80pins) > You have SCA disks? Is the cable terminated? The disk has a SCA connector. The cable is not terminated (the drive is currently at the very end of the cable). Jean-Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 21 16:11: 4 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 15CD31177D; Sun, 21 Feb 1999 16:10:12 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id RAA21911; Sun, 21 Feb 1999 17:10:11 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902220010.RAA21911@panzer.plutotech.com> Subject: Re: LVD transfer rate In-Reply-To: <199902212320.AAA23952@qix> from Jean-Marc Zucconi at "Feb 22, 1999 0:20:46 am" To: jmz@FreeBSD.ORG (Jean-Marc Zucconi) Date: Sun, 21 Feb 1999 17:10:11 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jean-Marc Zucconi wrote... > >>>>> Kenneth D Merry writes: > > >> I have a jumper labelled `SE mode', and this jumper is ON, however the > >> drive does not work if I remove the jumper: the drive appears in the > >> SCSIselect utility, but it does not reports its capacity, and trying > >> to format fails (Not ready, asc/ascq= 40/80). > > > That jumper forces it into Single Ended mode. > > OK. this explain why I only get 40MB/s > > > What kind of cable do you have? LVD drives don't have internal > > terminators. You need an LVD cable (one of the "twisty" 68-pin cables) > > with a terminator block on the end. > > I have the right cable, the terminator block is currently removed, but > during my tests without the SE jumper, I got similar results with and > without the terminator block. > > >> > I seriously doubt this is your problem, but I've got a machine at work with > >> > two 18G Seagate Cheetah II's on a Super Micro motherboard with an onboard > >> > 7890. The problem is that the drives are SCA, and the SCA to 68-pin > >> > converters we put on them apparantly inhibit LVD. So they only run at > >> > 20MHz instead of 40MHz. > >> > >> No - connectors and cables are standard (80pins) > > > You have SCA disks? Is the cable terminated? > > The disk has a SCA connector. The cable is not terminated (the drive > is currently at the very end of the cable). You'll need to terminate the cable one way or another, because the drive does not have terminators. You might also check for bent pins on the cable; Justin has had trouble with bent pins on some of his LVD cables. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 21 16:41: 8 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (Postfix) with ESMTP id 9076710FA6 for ; Sun, 21 Feb 1999 16:41:02 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id TAA42499; Sun, 21 Feb 1999 19:40:58 -0500 (EST) (envelope-from gjp@gjp.erols.com) To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG From: "Gary Palmer" Subject: Re: bad drive? In-reply-to: Your message of "Fri, 12 Feb 1999 20:38:20 MST." <199902130338.UAA38390@panzer.plutotech.com> Date: Sun, 21 Feb 1999 19:40:58 -0500 Message-ID: <42495.919644058@gjp.erols.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" wrote in message ID <199902130338.UAA38390@panzer.plutotech.com>: > I suppose it is possible that this could be caused by bad termination or > something similar. > > The problem is that we're queueing transactions to the drive, but it isn't > responding before the timeout fires. The I/O timeout for da devices is 60 > seconds. > > So, take that however you will. I would first try to make sure that the > cable is okay, as well as termination. Make sure there are no bent pins or > anything like that. > > If everything checks out in the cabling/termination department, I would > probably start to suspect that the drive is having trouble. Well, I guess it was a bad drive. It crashed the server and wiped out the boot record a few days later. Drive was replaced and machine seems to be much happier (I Hope :) ) Thanks Ken, Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 21 16:48:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from qix (ppp003.infranet.fr [195.68.70.130]) by hub.freebsd.org (Postfix) with ESMTP id 8F53411067 for ; Sun, 21 Feb 1999 16:48:52 -0800 (PST) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix (8.9.3/8.8.7) id BAA00437; Mon, 22 Feb 1999 01:52:06 +0100 (MET) Date: Mon, 22 Feb 1999 01:52:06 +0100 (MET) Message-Id: <199902220052.BAA00437@qix> X-Authentication-Warning: qix: jmz set sender to jmz@qix using -f From: Jean-Marc Zucconi To: ken@plutotech.com Cc: scsi@FreeBSD.ORG In-reply-to: <199902220010.RAA21911@panzer.plutotech.com> (ken@plutotech.com) Subject: Re: LVD transfer rate X-Mailer: Emacs Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> Kenneth D Merry writes: >> > You have SCA disks? Is the cable terminated? >> >> The disk has a SCA connector. The cable is not terminated (the drive >> is currently at the very end of the cable). I am stupid. Yes I am stupid. In fact the drive has a 68pin connector. I was confused because the cable was different fron a ``normal'' SCSI cable and I assumed that it was a 80pin cable. My second error was to not look carefully where I plugged the cable on the mainboard. I have 3 connectors: 1 50pin, 1 wide, and 1 UW2. The cable was not on the UW2 but on the wide connector :-/ I am stupid but I am happy: da1: 80.000MB/s transfers (40.000MHz, offset 15, 16bit), Tagged Queueing Enabled :-) Thanks for your help! Jean-Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 21 17:50:18 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.nacamar.de (mail.nacamar.de [194.162.162.200]) by hub.freebsd.org (Postfix) with ESMTP id C3A6A115B4 for ; Sun, 21 Feb 1999 17:50:15 -0800 (PST) (envelope-from rohrbach@mail.nacamar.de) Received: (from rohrbach@localhost) by mail.nacamar.de (8.8.7/8.8.8MB-19980212) id CAA12481; Mon, 22 Feb 1999 02:49:59 +0100 (CET) Message-ID: <19990222024959.D12320@nacamar.net> Date: Mon, 22 Feb 1999 02:49:59 +0100 From: "Karsten W. Rohrbach" To: "Kenneth D. Merry" Cc: dwmalone@maths.tcd.ie, r3cgm@cdrom.com, freebsd-scsi@FreeBSD.ORG Subject: Re: Unusual CAM Error w/FreeBSD 3.1 (tosha) Reply-To: rohrbach@nacamar.net Mail-Followup-To: "Kenneth D. Merry" , dwmalone@maths.tcd.ie, r3cgm@cdrom.com, freebsd-scsi@FreeBSD.ORG References: <19990219132746.A4754@nacamar.net> <199902191758.KAA03342@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199902191758.KAA03342@panzer.plutotech.com>; from Kenneth D. Merry on Fri, Feb 19, 1999 at 10:58:45AM -0700 X-Arbitrary-Number-Of-The-Day: 42 X-Sender: rohrbach@nacamar.net X-Organisation: Nacamar Data Communications GmbH X-Address: Robert-Bosch-Str. 32, 63303 Dreieich, Germany X-Phone: vox: +49 6103 993 870 fax: +49 6103 993 199 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org so maybe someone is willing to "invent" a joe user safe system for automagically chmoding this stuff kinda (okay please dont hurt me) windows nt style ("fixing system permissions") in a way more transparent way. it could serve as a kind of tripwire-lite for looking after suid/sgid binaries, some kind of system security manager for the userland. this would increase popularity in my opinion. freebsd installation and everything gets easier and easier all the time, but running system management is still limited to 'vi /etc/something' which, imho, keeps freebsd on the second choice place for internet-newbie-but-me-wants-no-windoze-server people ;-) if you look at yast (suse linux) or the redhat tools, they are a nice attempt but not really a choice for everyday use, so maybe the freebsd community comes up with something better :) /k Kenneth D. Merry (ken@plutotech.com) @ Fri, Feb 19, 1999 at 10:58:45AM -0700: > Karsten W. Rohrbach wrote... > > definately, but also some of the "hook-devs" in /dev like xpt? for example > > should be root.operator and mode 660 or root.wheel or whatever. if theres no > > standardization in the next time, a lot of audio/multimedia packages will > > grow wild with suid executables where we wont need/want them i guess - and > > theres no harder pain in the ass than defect hardware and suid binaries. > > The xpt and pass devices are owned by root.operator, just like disk > devices. > > They are quite intentionally chmoded 600 by default. The reason for that > is that you can use the pass device at least to reformat hard disks and > things like that, so it should default to being very secure, and sysadmins > can selectively reduce the security if they want. > > For my own machines, I chmod the xpt and pass devices 660, and put myself > in the operator group. So I can use camcontrol, tosha, etc., without having > to su or make the binaries setuid. > > I can sympathize with the desire to make things easier for Joe User to use > the xpt/pass devices, but I would rather not compromise security to do it. > > As far as I know, none of the applications that currently use the xpt/pass > devices are installed setuid. So access policies are determined by how the > system administrator chmods the files in /dev. > > > David Malone (dwmalone@maths.tcd.ie) @ Fri, Feb 19, 1999 at 12:18:51PM +0000: > > > > > %ls -l tosha > > > > > -rwsr-xr-x 1 bin bin 21304 Feb 18 03:07 tosha > > > > > > Surely suid bin isn't going to be very useful to tosha? > > > Shouldn't it be suid root or sgid operator or something? > > > > > Argh!! I didn't see that! Christopher, that's your problem. The binary > was setuid bin, but /dev/xpt* and /dev/pass* are owned by root. So setuid > bin won't do you any good. > > Ken > -- > Kenneth Merry > ken@plutotech.com -- "The path of excess leads to the tower of wisdom." -- W. Blake http://www.nacamar.de - http://www.nacamar.net - http://www.webmonster.de http://www.apache.de - http://www.quakeforum.de - finger rohrbach@nacamar.net PGP Key fingerprint = F9 A0 DF 91 74 07 6A 1C 5F 0B E0 6B 4D CD 8C 44 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 22 15:37: 5 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9FAE9111D0 for ; Mon, 22 Feb 1999 15:36:50 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id SAA13665 for ; Mon, 22 Feb 1999 18:36:48 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.2/8.9.1) id SAA19074; Mon, 22 Feb 1999 18:36:42 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Mon, 22 Feb 1999 18:36:42 -0500 (EST) To: freebsd-scsi@freebsd.org Subject: dual-channel U2W scsi performance X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14033.59216.903659.321869@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have several servers whose motherboards have on-board dual-channel Ultra2 SCSI controllers such as: ahc0: rev 0x00 int a irq 0 on pci0.14.0 ahc1: rev 0x00 int a irq 0 on pci0.14.1 I understand I should be able to hook older Ultra-Wide devices to each channel. Assuming I do this, and the theoretical max of each channel is reduced to the Ultra-Wide 40MB/sec max, should I be able to come close to getting 80MB/sec out of the adapter when saturating both channels simultaneously? ( Assuming I have a memory system & PCI bus that can handle it, enough drives/buses, using a striped filesystem, etc... ) Essentially, I'm wondering if I need to purchase another 2940UW for each server, or if the above on-board dual-channel controller will really be able to run 2 Ultra-Wide busses close to flat out. Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 22 17:31:15 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 CF16911A8F for ; Mon, 22 Feb 1999 17:31:10 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id SAA11068; Mon, 22 Feb 1999 18:22:21 -0700 (MST) Date: Mon, 22 Feb 1999 18:22:21 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199902230122.SAA11068@narnia.plutotech.com> To: Andrew Gallatin Cc: scsi@FreeBSD.org Subject: Re: dual-channel U2W scsi performance X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <14033.59216.903659.321869@grasshopper.cs.duke.edu> 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 <14033.59216.903659.321869@grasshopper.cs.duke.edu> you wrote: > > Essentially, I'm wondering if I need to purchase another 2940UW for > each server, or if the above on-board dual-channel controller will > really be able to run 2 Ultra-Wide busses close to flat out. The only way to know for sure is to test it, and I have not performed such a test here. Based on the efficiency of past Adaptec PCI parts, I don't think it will have a problem saturating both channels assuming the rest of the system is up to the task and you have sufficient spare PCI bus bandwidth (no other big hogs). -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 23 5: 2:14 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from shell.monmouth.com (bg-tc-ppp727.monmouth.com [209.191.63.163]) by hub.freebsd.org (Postfix) with ESMTP id BED2A10FF5 for ; Tue, 23 Feb 1999 05:02:10 -0800 (PST) (envelope-from pechter@shell.monmouth.com) Received: (from pechter@localhost) by shell.monmouth.com (8.9.2/8.9.1) id IAA01623 for freebsd-scsi@freebsd.org; Tue, 23 Feb 1999 08:02:03 -0500 (EST) (envelope-from pechter) From: Bill Pechter Message-Id: <199902231302.IAA01623@shell.monmouth.com> Subject: Flashpoint SCSI driver To: freebsd-scsi@freebsd.org Date: Tue, 23 Feb 1999 08:02:03 -0500 (EST) Reply-To: bpechter@shell.monmouth.com X-Phone-Number: 908-389-3592 X-OS-Type: FreeBSD 3.0-Stable X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Since the folks at Mylex have allowed the FlashPoint driver to enter the mainstream Linux distribution and the Flashpoint's now fully supported within Linux, is there anyone willing to work on a FreeBSD driver? I'd be willing to loan out a card for this purpose. Bill --- Bill Gates is a Persian cat and a monocle away from being a villain in a James Bond movie -- Dennis Miller bpechter@shell.monmouth.com|pechter@pechter.nws.net|pechter@pechter.ddns.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 23 7:48:41 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 7F7F211E88 for ; Tue, 23 Feb 1999 07:48:33 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id IAA11962; Tue, 23 Feb 1999 08:39:10 -0700 (MST) Date: Tue, 23 Feb 1999 08:39:10 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199902231539.IAA11962@narnia.plutotech.com> To: bpechter@shell.monmouth.com Cc: scsi@FreeBSD.org Subject: Re: Flashpoint SCSI driver X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <199902231302.IAA01623@shell.monmouth.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199902231302.IAA01623@shell.monmouth.com> you wrote: > > Since the folks at Mylex have allowed the FlashPoint driver to > enter the mainstream Linux distribution and the Flashpoint's now fully > supported within Linux, is there anyone willing to work on a > FreeBSD driver? > > I'd be willing to loan out a card for this purpose. I'm writing a driver. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 23 11:50:44 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 8C2E310E7C for ; Tue, 23 Feb 1999 11:50:36 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id OAA03025; Tue, 23 Feb 1999 14:50:35 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.2/8.9.1) id OAA24462; Tue, 23 Feb 1999 14:50:27 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 23 Feb 1999 14:50:26 -0500 (EST) To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: dual-channel U2W scsi performance In-Reply-To: <199902230122.SAA11068@narnia.plutotech.com> References: <14033.59216.903659.321869@grasshopper.cs.duke.edu> <199902230122.SAA11068@narnia.plutotech.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14034.65025.537279.428755@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs writes: > In article <14033.59216.903659.321869@grasshopper.cs.duke.edu> you wrote: > > > > Essentially, I'm wondering if I need to purchase another 2940UW for > > each server, or if the above on-board dual-channel controller will > > really be able to run 2 Ultra-Wide busses close to flat out. > > The only way to know for sure is to test it, and I have not performed > such a test here. Based on the efficiency of past Adaptec PCI parts, > I don't think it will have a problem saturating both channels assuming > the rest of the system is up to the task and you have sufficient spare > PCI bus bandwidth (no other big hogs). > > -- > Justin I just tried, and I initially coouldn't get the second scsi channel working at all. The end result is that the first channel appears to probe the bus fine, if I move a chain which works just fine on the first channel to the second channel, I see parity errors whenever a disk is accessed when the bus is probed: <..> (probe0:ahc1:0:0:2): parity error during Message-In phase. SEQADDR == 0x15d SCSIRATE == 0x95 (probe0:ahc1:0:0:2): parity error during Data-In phase. byte 3278 <.....> da0: Fixed Direct Access SCSI-2 device da0: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4339MB (8887184 512 byte sectors: 255H 63S/T 553C) (da1:ahc1:0:1:0): parity error during Command phase. SEQADDR == 0x15d SCSIRATE == 0x95 da1 at ahc1 bus 0 target 1 lun 0 <...> The parity errors seem to disappear for reads if I disable parity from SCSI select. However, I see parity errors on both channels when I attempt to label the disks. This happens on both channels, with parity set to disabled in scsi select for both channels: login: (da0:ahc0:0:0:0): WRITE(06). CDB: a 0 0 0 10 0 (da0:ahc0:0:0:0): ABORTED COMMAND asc:47,0 (da0:ahc0:0:0:0): SCSI parity error field replaceable unit: 3 The performance is pretty good for just doing 8 dd if=/dev/rdaXc of=/dev/null bs=64k from 8 cheetahs (about 9MB/sec per drive), or about 72MB/sec overall. However, the parity error problems concern me. The kernel is built from 4.0-current sources cvsupped late last week. The machine is a single 450Mhz Xeon sitting in a Tyan S1952DLU Thunder X motherboard. Here's a full dmesg: Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #4: Sat Feb 20 11:51:17 EST 1999 gallatin@grasshopper.cs.duke.edu:/freebsd/src/sys/compile/TPZ Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 451025157 Hz CPU: Pentium II/Xeon/Celeron (451.03-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x653 Stepping=3 Features=0x183fbff> real memory = 134217728 (131072K bytes) avail memory = 127447040 (124460K bytes) Preloaded elf kernel "kernel" at 0xf02fb000. Probing for devices on PCI bus 0: chip0: rev 0x00 on pci0.0.0 chip1: rev 0x00 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x02 on pci0.7.3 ahc0: rev 0x00 int a irq 10 on pci0.14.0 ahc0: aic7896/97 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 10 on pci0.14.1 ahc1: aic7896/97 Wide Channel B, SCSI Id=7, 16/255 SCBs mlanai0: rev 0x01 int a irq 11 on pci0.15.0 tpz0: Myrinet LANai 4.1 address 00:60:dd:e0:00:f1 (M2F-PCI32-10241) tpz0: Duke TPZ/IP driver version $Id: if_tpz.c,v 1.12 1999/02/05 20:16:56 gallatin Exp $ fxp0: rev 0x05 int a irq 10 on pci0.16.0 fxp0: Ethernet address 00:a0:c9:e7:8e:9c Probing for devices on PCI bus 1: Probing for PnP devices: Probing for devices on the ISA bus: sc0 not found atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip0: on ppbus 0 ppi0: on ppbus 0 psm0 not found at 0x60 pcm0 not found fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ff0ff on isa wdc0: unit 0 (wd0): , LBA, DMA, 32-bit, multi-block-16, sleep-hack wd0: 4892MB (10018890 sectors), 623 cyls, 255 heads, 63 S/T, 512 B/S vga0 not found npx0 flags 0x1 on motherboard npx0: INT 16 interface RTC BIOS diagnostic error 20 lo0 XXX: driver didn't set ifq_maxlen cda0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4211MB (8625052 512 byte sectors: 255H 63S/T 536C) da4 at ahc1 bus 0 target 0 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da4: 4339MB (8887184 512 byte sectors: 255H 63S/T 553C) da7 at ahc1 bus 0 target 4 lun 0 da7: Fixed Direct Access SCSI-2 device da7: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da7: 4339MB (8887184 512 byte sectors: 255H 63S/T 553C) da6 at ahc1 bus 0 target 3 lun 0 da6: Fixed Direct Access SCSI-2 device da6: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da6: 4339MB (8887184 512 byte sectors: 255H 63S/T 553C) da5 at ahc1 bus 0 target 1 lun 0 da5: Fixed Direct Access SCSI-2 device da5: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da5: 4339MB (8887184 512 byte sectors: 255H 63S/T 553C) da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da3: 4211MB (8625052 512 byte sectors: 255H 63S/T 536C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 4211MB (8625052 512 byte sectors: 255H 63S/T 536C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4211MB (8625052 512 byte sectors: 255H 63S/T 536C) hanging root device to wd0s1a ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates (da0:ahc0:0:0:0): WRITE(06). CDB: a 0 0 0 10 0 (da0:ahc0:0:0:0): ABORTED COMMAND asc:47,0 (da0:ahc0:0:0:0): SCSI parity error field replaceable unit: 3 (da1:ahc0:0:1:0): WRITE(06). CDB: a 0 0 0 10 0 (da1:ahc0:0:1:0): ABORTED COMMAND asc:47,0 (da1:ahc0:0:1:0): SCSI parity error field replaceable unit: 3 (da6:ahc1:0:3:0): WRITE(06). CDB: a 0 0 0 10 0 (da6:ahc1:0:3:0): ABORTED COMMAND asc:47,0 (da6:ahc1:0:3:0): SCSI parity error field replaceable unit: 3 ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 23 12:20:40 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id B3E24115F5 for ; Tue, 23 Feb 1999 12:20:36 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id NAA13242; Tue, 23 Feb 1999 13:20:33 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199902232020.NAA13242@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Andrew Gallatin Cc: scsi@FreeBSD.org Subject: Re: dual-channel U2W scsi performance In-reply-to: Your message of "Tue, 23 Feb 1999 14:50:26 EST." <14034.65025.537279.428755@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 23 Feb 1999 13:11:51 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I just tried, and I initially coouldn't get the second scsi channel >working at all. The end result is that the first channel appears to >probe the bus fine, if I move a chain which works just fine on the >first channel to the second channel, I see parity errors whenever a >disk is accessed when the bus is probed: > ><..> >(probe0:ahc1:0:0:2): parity error during Message-In phase. >SEQADDR == 0x15d >SCSIRATE == 0x95 There must be something wrong with your cables. I've had several instances where a loose connector pin caused intermittent parity-errors. If both the driver and the end device are reporting errors, they can't be wrong. I've tested SE operation on the aic7896, so I know that it can work with the current driver. One other thing that may be interesting is a dmesg from a -v boot. It could be that the driver is not setting the termination properly, but this is fairly straight forward for the aic789X series. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 23 13:28: 7 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 9D68011747 for ; Tue, 23 Feb 1999 13:28:03 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id QAA05221; Tue, 23 Feb 1999 16:28:02 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.2/8.9.1) id QAA24846; Tue, 23 Feb 1999 16:27:53 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 23 Feb 1999 16:27:52 -0500 (EST) To: "Justin T. Gibbs" Cc: scsi@FreeBSD.org Subject: Re: dual-channel U2W scsi performance In-Reply-To: <199902232020.NAA13242@pluto.plutotech.com> References: <14034.65025.537279.428755@grasshopper.cs.duke.edu> <199902232020.NAA13242@pluto.plutotech.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14035.5458.71518.652907@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Justin T. Gibbs writes: > > There must be something wrong with your cables. I've had several instances > where a loose connector pin caused intermittent parity-errors. If both > the driver and the end device are reporting errors, they can't be wrong. > I've tested SE operation on the aic7896, so I know that it can work > with the current driver. Before I turned off parity in scsi-select, I tried all possible combinations of cabling (my setup is motherboard connecter -> internal cable -> external connector-> external cable -> box w/2 4G cheetahs -> active terminator), I switched out both cables, the external connector, the terminator & the box w/2 cheetahs.. No combination worked on the second channel. All combinations worked on the first channel. (by worked, I mean probed w/o parity errors) > One other thing that may be interesting is a dmesg from a -v boot. It > could be that the driver is not setting the termination properly, but > this is fairly straight forward for the aic789X series. Here you go. My message buffer isn't quite big enough, so I've captured the serial console output for you. The last bits (after the login prompt) are from <4:23pm>scone/gallatin:~>sudo disklabel -wr da0 auto disklabel: write: Input/output error Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 BIOS basemem (639K) != RTC basemem (640K), setting to BIOS value Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 4.0-CURRENT #4: Sat Feb 20 11:51:17 EST 1999 gallatin@grasshopper.cs.duke.edu:/freebsd/src/sys/compile/TPZ Calibrating clock(s) ... TSC clock: 450981231 Hz, i8254 clock: 1193072 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method Timecounter "TSC" frequency 451024656 Hz CPU: Pentium II/Xeon/Celeron (451.02-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x653 Stepping=3 Features=0x183fbff> real memory = 134217728 (131072K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x00308000 - 0x07ffdfff, 131031040 bytes (31990 pages) avail memory = 127447040 (124460K bytes) Found BIOS32 Service Directory header at 0xf00fdb50 Entry = 0xfdb60 (0xf00fdb60) Rev = 0 Len = 1 PCI BIOS entry at 0xdb81 SMIBIOS header at 0xf00f0080 Version 2.1 Table at 0xf0770, 33 entries, 1010 bytes, largest entry 74 bytes DMI header at 0xf00f0090 Version 2.1 Table at 0xf0770, 33 entries, 1010 bytes Other BIOS signatures found: ACPI: 00000000 $PnP: 000f7420 Preloaded elf kernel "kernel" at 0xf02fb000. pci_open(1): mode 1 addr port (0x0cf8) is 0x8000005c pci_open(1a): mode1res=0x80000000 (0x80000000) pci_cfgcheck: device 0 [class=060000] [hdr=00] is there (id=71a08086) Probing for devices on PCI bus 0: found-> vendor=0x8086, dev=0x71a0, revid=0x00 class=06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 3, range 32, base f8000000, size 26 chip0: rev 0x00 on pci0.0.0 found-> vendor=0x8086, dev=0x71a1, revid=0x00 class=06-04-00, hdrtype=0x01, mfdev=0 subordinatebus=1 secondarybus=1 chip1: rev 0x00 on pci0.1.0 found-> vendor=0x8086, dev=0x7110, revid=0x02 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip2: rev 0x02 on pci0.7.0 found-> vendor=0x8086, dev=0x7111, revid=0x01 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 0000ffa0, size 4 ide_pci0: rev 0x01 on pci0.7.1 intel_piix_status: primary master sample = 3, master recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary slave sample = 5, slave recovery = 4 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 24 from port: 0000ffa2 ide_pci: ide0:0 has been configured for DMA by BIOS intel_piix_status: secondary master sample = 5, master recovery = 4 intel_piix_status: secondary master fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled intel_piix_status: secondary slave sample = 5, slave recovery = 4 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000ffaa found-> vendor=0x8086, dev=0x7112, revid=0x01 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=255 map[0]: type 4, range 32, base 0000ef80, size 5 found-> vendor=0x8086, dev=0x7113, revid=0x02 class=06-80-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip3: rev 0x02 on pci0.7.3 found-> vendor=0x9005, dev=0x005f, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000e400, size 8 map[1]: type 1, range 64, base ffafe000, size 12 map[2]: type 0, range 0, base 00000000, size 0 ahc0: rev 0x00 int a irq 10 on pci0.14.0 ahc0: Reading SEEPROM...done. ahc0: BIOS eeprom not present ahc0: Primary Low Byte termination Enabled ahc0: Primary High Byte termination Enabled ahc0: aic7896/97 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: Downloading Sequencer Program... 392 instructions downloaded found-> vendor=0x9005, dev=0x005f, revid=0x00 class=01-00-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 4, range 32, base 0000e800, size 8 map[1]: type 1, range 64, base ffaff000, size 12 map[2]: type 0, range 0, base 00000000, size 0 ahc1: rev 0x00 int a irq 10 on pci0.14.1 using shared irq10. ahc1: Reading SEEPROM...done. ahc1: BIOS eeprom not present ahc1: Primary Low Byte termination Enabled ahc1: Primary High Byte termination Enabled ahc1: aic7896/97 Wide Channel B, SCSI Id=7, 16/255 SCBs ahc1: Downloading Sequencer Program... 392 instructions downloaded found-> vendor=0x10e8, dev=0x8043, revid=0x01 class=00-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=11 map[0]: type 3, range 32, base feb00000, size 20 mlanai0: rev 0x01 int a irq 11 on pci0.15.0 tpz0: Myrinet LANai 4.1 address 00:60:dd:e0:00:f1 (M2F-PCI32-10241) tpz0: Duke TPZ/IP driver version $Id: if_tpz.c,v 1.12 1999/02/05 20:16:56 gallatin Exp $ found-> vendor=0x8086, dev=0x1229, revid=0x05 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=10 map[0]: type 3, range 32, base feaff000, size 12 map[1]: type 4, range 32, base 0000ef40, size 5 map[2]: type 1, range 32, base ff900000, size 20 fxp0: rev 0x05 int a irq 10 on pci0.16.0 fxp0: Ethernet address 00:a0:c9:e7:8e:9c bpf: fxp0 attached Probing for devices on PCI bus 1: Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 Trying Read_Port at 283 Trying Read_Port at 2c3 Trying Read_Port at 303 Trying Read_Port at 343 Trying Read_Port at 383 Trying Read_Port at 3c3 No Plug-n-Play devices were found Probing for devices on the ISA bus: sc0: no video adapter is found. sc0 not found atkbdc0 at 0x60-0x6f on motherboard kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 atkbd0 irq 1 on isa kbd0: atkbd0, generic (3), config:0x0, flags:0x1f0000 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. psm0 not found sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A, console sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A ppc: parallel port found at 0x378 PC873xx probe at 0x2e got unknown ID 0x0 ppc0: SPP ppc0 at 0x378 irq 7 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode plip: irq 7 plip0: on ppbus 0 bpf: lp0 attached ppi0: on ppbus 0 psm0: current command byte:0065 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. psm0 not found at 0x60 mss_probe: no address supplied, try default 0x530 mss_detect error, busy still set (0xff) sb_probe: no address supplied, try defaults (0x220,0x240) pcm0 not found fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ff0ff on isa wdc0: unit 0 (wd0): , LBA, DMA, 32-bit, multi-block-16, sleep-hack wd0: 4892MB (10018890 sectors), 623 cyls, 255 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0007, apio = 0003, udma = 0407 vga0 not found npx0 flags 0x1 on motherboard npx0: INT 16 interface imasks: bio c0084040, tty c003009a, net c0060c00 BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. RTC BIOS diagnostic error 20 bpf: lo0 attached lo0 XXX: driver didn't set ifq_maxlen (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. (noperiph:ahc1:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. ahc0: Selection Timeout on A:4. 1 SCBs aborted ahc1: Selection Timeout on A:2. 1 SCBs aborted ahc0: Selection Timeout on A:5. 1 SCBs aborted ahc1: Selection Timeout on A:5. 1 SCBs aborted ahc0: Selection Timeout on A:6. 1 SCBs aborted ahc1: Selection Timeout on A:6. 1 SCBs aborted ahc0: Selection Timeout on A:8. 1 SCBs aborted ahc1: Selection Timeout on A:8. 1 SCBs aborted ahc0: Selection Timeout on A:9. 1 SCBs aborted ahc1: Selection Timeout on A:9. 1 SCBs aborted ahc0: Selection Timeout on A:10. 1 SCBs aborted ahc1: Selection Timeout on A:10. 1 SCBs aborted ahc0: Selection Timeout on A:11. 1 SCBs aborted ahc1: Selection Timeout on A:11. 1 SCBs aborted ahc0: Selection Timeout on A:12. 1 SCBs aborted ahc1: Selection Timeout on A:12. 1 SCBs aborted ahc0: Selection Timeout on A:13. 1 SCBs aborted ahc1: Selection Timeout on A:13. 1 SCBs aborted ahc0: Selection Timeout on A:14. 1 SCBs aborted ahc1: Selection Timeout on A:14. 1 SCBs aborted ahc0: Selection Timeout on A:15. 1 SCBs aborted ahc0: target 0 using 16bit transfers ahc1: Selection Timeout on A:15. 1 SCBs aborted ahc0: target 0 synchronous at 20.0MHz, offset = 0xf ahc0: target 3 using 16bit transfers ahc0: target 3 synchronous at 20.0MHz, offset = 0xf ahc0: target 2 using 16bit transfers ahc0: target 2 synchronous at 20.0MHz, offset = 0xf ahc1: target 0 using 16bit transfers ahc1: target 0 synchronous at 20.0MHz, offset = 0xf ahc0: target 1 using 16bit transfers ahc0: target 1 synchronous at 20.0MHz, offset = 0xf ahc1: target 4 using 16bit transfers ahc1: target 4 synchronous at 20.0MHz, offset = 0xf ahc1: target 3 using 16bit transfers ahc1: target 3 synchronous at 20.0MHz, offset = 0xf ahc1: target 1 using 16bit transfers ahc1: target 1 synchronous at 20.0MHz, offset = 0xf pass0 at ahc0 bus 0 target 0 lun 0 pass0: Fixed Direct Access SCSI-2 device pass0: Serial Number LG606047 pass0: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled pass1 at ahc0 bus 0 target 1 lun 0 pass1: Fixed Direct Access SCSI-2 device pass1: Serial Number LG604374 pass1: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled pass2 at ahc0 bus 0 target 2 lun 0 pass2: Fixed Direct Access SCSI-2 device pass2: Serial Number LG117621 pass2: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled pass3 at ahc0 bus 0 target 3 lun 0 pass3: Fixed Direct Access SCSI-2 device pass3: Serial Number LG996535 pass3: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled pass4 at ahc1 bus 0 target 0 lun 0 pass4: Fixed Direct Access SCSI-2 device pass4: Serial Number LG164004 pass4: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled pass5 at ahc1 bus 0 target 1 lun 0 pass5: Fixed Direct Access SCSI-2 device pass5: Serial Number LG604613 pass5: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled pass6 at ahc1 bus 0 target 3 lun 0 pass6: Fixed Direct Access SCSI-2 device pass6: Serial Number LG243960 pass6: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled pass7 at ahc1 bus 0 target 4 lun 0 pass7: Fixed Direct Access SCSI-2 device pass7: Serial Number LG161427 pass7: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number LG606047 da0: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4211MB (8625052 512 byte sectors: 255H 63S/T 536C) da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-2 device da3: Serial Number LG996535 da3: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da3: 4211MB (8625052 512 byte sectors: 255H 63S/T 536C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: Serial Number LG117621 da2: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 4211MB (8625052 512 byte sectors: 255H 63S/T 536C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: Serial Number LG604374 da1: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4211MB (8625052 512 byte sectors: 255H 63S/T 536C) da4 at ahc1 bus 0 target 0 lun 0 da4: Fixed Direct Access SCSI-2 device da4: Serial Number LG164004 da4: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da4: 4339MB (8887184 512 byte sectors: 255H 63S/T 553C) da7 at ahc1 bus 0 target 4 lun 0 da7: Fixed Direct Access SCSI-2 device da7: Serial Number LG161427 da7: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da7: 4339MB (8887184 512 byte sectors: 255H 63S/T 553C) da6 at ahc1 bus 0 target 3 lun 0 da6: Fixed Direct Access SCSI-2 device da6: Serial Number LG243960 da6: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da6: 4339MB (8887184 512 byte sectors: 255H 63S/T 553C) da5 at ahc1 bus 0 target 1 lun 0 da5: Fixed Direct Access SCSI-2 device da5: Serial Number LG604613 da5: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled da5: 4339MB (8887184 512 byte sectors: 255H 63S/T 553C) Considering FFS root f/s. changing root device to wd0s1a wd0s1: type 0xa5, start 63, end = 10018889, size 10018827 : OK swapon: adding /dev/wd0s1b as swap device Automatic reboot in progress... /dev/rwd0s1a: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/rwd0s1a: clean, 64268 free (268 frags, 8000 blocks, 0.3% fragmentation) /dev/rwd0s1f: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/rwd0s1f: clean, 2209762 free (11026 frags, 274842 blocks, 0.4% fragmentation) /dev/rwd0s1e: FILESYSTEM CLEAN; SKIPPING CHECKS /dev/rwd0s1e: clean, 1012987 free (211 frags, 126597 blocks, 0.0% fragmentation) ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates Doing initial network setup: hostname domain. fxp0: flags=8843 mtu 1500 inet 152.3.145.37 netmask 0xffffff00 broadcast 152.3.145.255 ether 00:a0:c9:e7:8e:9c media: 100baseTX status: active supported media: autoselect 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP net.inet.tcp.sendspace: 16384 -> 131072 net.inet.tcp.recvspace: 16384 -> 131072 net.inet.udp.maxdgram: 9216 -> 57344 net.inet.udp.recvspace: 41600 -> 65535 kern.ipc.maxsockbuf: 262144 -> 2097152 ifconfig: interface myri0 does not exist ifconfig: interface myri0 does not exist lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 add net default: gateway 152.3.145.240 Additional routing options:. routing daemons:. Mounting NFS file systems. recording kernel -c changes additional daemons: syslogdFeb 23 15:56:38 scone /kernel: kbdc: RESET_AUX return code:00fe Feb 23 15:56:38 scone last message repeated 2 times Feb 23 15:56:38 scone /kernel: kbdc: DIAGNOSE status:0055 Feb 23 15:56:38 scone /kernel: kbdc: TEST_KBD_PORT status:0000 Feb 23 15:56:38 scone /kernel: kbdc: TEST_AUX_PORT status:0000 Feb 23 15:56:38 scone /kernel: kbdc: RESET_AUX return code:00fe Feb 23 15:56:38 scone last message repeated 2 times Feb 23 15:56:38 scone /kernel: kbdc: DIAGNOSE status:0055 Feb 23 15:56:38 scone /kernel: kbdc: TEST_KBD_PORT status:0000 . checking for core dump...savecore: no core dump Doing additional network setup: ntpdate xntpd portmap ypbind. Starting final network daemons: nfsiod. setting ELF ldconfig path: /usr/lib /usr/lib/compat /usr/X11R6/lib /usr/local/lib setting a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout /usr/X11R6/lib/aout /usr/local/lib/aout starting standard daemons: inetd cron. Initial rc.i386 initialization: linuxLinux-ELF exec handler installed . rc.i386 configuring syscons:. Local package initialization: Modula-3 printer. starting local daemons:. Tue Feb 23 15:56:43 EST 1999 FreeBSD (scone.cs.duke.edu) (ttyd0) login: da0: invalid primary partition table: no magic ahc0: target 0 using asynchronous transfers ahc0: target 0 synchronous at 20.0MHz, offset = 0xf ahc0: target 0 using asynchronous transfers ahc0: target 0 synchronous at 20.0MHz, offset = 0xf ahc0: target 0 using asynchronous transfers ahc0: target 0 synchronous at 20.0MHz, offset = 0xf ahc0: target 0 using asynchronous transfers ahc0: target 0 synchronous at 20.0MHz, offset = 0xf ahc0: target 0 using asynchronous transfers ahc0: target 0 synchronous at 20.0MHz, offset = 0xf (da0:ahc0:0:0:0): WRITE(06). CDB: a 0 0 0 10 0 (da0:ahc0:0:0:0): ABORTED COMMAND asc:47,0 (da0:ahc0:0:0:0): SCSI parity error field replaceable unit: 3 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 23 18:14:14 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from luke.pmr.com (luke.pmr.com [207.170.114.132]) by hub.freebsd.org (Postfix) with ESMTP id 24465115E1; Tue, 23 Feb 1999 18:14:06 -0800 (PST) (envelope-from bob@luke.pmr.com) Received: (from bob@localhost) by luke.pmr.com (8.9.2/8.9.2) id UAA34076; Tue, 23 Feb 1999 20:14:06 -0600 (CST) (envelope-from bob) Date: Tue, 23 Feb 1999 20:14:05 -0600 From: Bob Willcox To: Jean-Marc Zucconi Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: LVD transfer rate Message-ID: <19990223201405.A33936@luke.pmr.com> Reply-To: Bob Willcox References: <199902212218.XAA00376@qix> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199902212218.XAA00376@qix>; from Jean-Marc Zucconi on Sun, Feb 21, 1999 at 11:18:58PM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have two of these drives on my system (3.1-stable as of a couple of days ago) which includes an ASUS GX DLS motherboard with an Adaptec 7896 dual channel SCSI adapter on it. Both of my drives show up as so: da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) This is on channal A which has a total of three drives on it (all LVD: 1 Seagate Cheeta and two of the IBM DDRS's). Could you give some further details about your system (FreeBSD release, what Adaptec chipset, etc.)? On Sun, Feb 21, 1999 at 11:18:58PM +0100, Jean-Marc Zucconi wrote: > I just installed a LVD drive and the boot message reports only 40MB/s > transfer rate. I expected 80MB/s - did I something wrong ? > > da1: Fixed Direct Access SCSI-2 device > da1: Serial Number RE205733 > da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit), Tagged Queueing Enabled > da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) > > This is the only device on the LVD bus (Adaptec controller on a Asus > P2BDS). I also have drives on the 50pin connector, but this should not > be the problem ? > > Jean-Marc. > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message -- Bob Willcox The man who follows the crowd will usually get no bob@luke.pmr.com further than the crowd. The man who walks alone is Austin, TX likely to find himself in places no one has ever been. -- Alan Ashley-Pitt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 25 3:32:18 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from excalibur.oceanis.net (ns.dotcom.fr [195.154.74.11]) by hub.freebsd.org (Postfix) with ESMTP id 2919A14D32 for ; Thu, 25 Feb 1999 03:32:15 -0800 (PST) (envelope-from arnaud@excalibur.oceanis.net) Received: (from arnaud@localhost) by excalibur.oceanis.net (8.9.1/8.9.1) id LAA00804 for scsi@FreeBSD.ORG; Thu, 25 Feb 1999 11:31:59 GMT From: Arnaud KOPP Message-Id: <199902251131.LAA00804@excalibur.oceanis.net> Subject: [3.1-RELEASE] Fujitsu M2513A 640MB MO ? To: scsi@FreeBSD.ORG Date: Thu, 25 Feb 1999 12:31:58 +0100 (MET) Organization: DotCom ( Communication Numerique ) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm trying to correctly use my FUJITSU M2513A MO drive with FreeBSD and get some SCSI errors when trying to unmount my tape : # umount /mnt (da1:ahc0:0:4:0): SCB 0x2 - timed out in command phase, SEQADDR == 0x154 (da1:ahc0:0:4:0): BDR message in message buffer (da1:ahc0:0:4:0): SCB 0x2 - timed out in command phase, SEQADDR == 0x154 (da1:ahc0:0:4:0): no longer in timeout, status = 34b ahc0: Issued Channel A Bus Reset. 1 SCBs aborted So here's my setup : Motherboard : Gigabyte GA-6BXDS with 2 SCSI integrated buses. (http://www.gigabyte.com.tw/gigabyte-web/products/ga6bxds.htm) # dmesg Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.1-RELEASE #0: Wed Feb 24 18:56:00 CET 1999 root@cray.dotcom.fr:/usr/src/sys/compile/CRAY Timecounter "i8254" frequency 1193182 Hz CPU: Pentium II/Xeon/Celeron (686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183fbff> real memory = 134217728 (131072K bytes) avail memory = 127737856 (124744K bytes) Programming 24 pins in IOAPIC #0 FreeBSD/SMP: Multiprocessor motherboard cpu0 (BSP): apic id: 0, version: 0x00040011, at 0xfee00000 cpu1 (AP): apic id: 1, version: 0x00040011, at 0xfee00000 io0 (APIC): apic id: 2, version: 0x00170011, at 0xfec00000 Preloaded elf kernel "kernel" at 0xf02b8000. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x02 on pci0.7.3 ax0: rev 0x03 int a irq 19 on pci0.11.0 ax0: Ethernet address: 00:40:95:4a:01:28 ax0: autoneg complete, link status good (half-duplex, 10Mbps) ahc0: rev 0x04 int a irq 16 on pci0.12.0 ahc0: aic7895 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x04 int b irq 16 on pci0.12.1 ahc1: Using left over BIOS settings ahc1: aic7895 Wide Channel B, SCSI Id=7, 16/255 SCBs Probing for devices on PCI bus 1: vga0: rev 0xf3 int a irq 255 on pci1.1.0 Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 not found sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface APIC_IO: Testing 8254 interrupt delivery APIC_IO: routing 8254 via pin 2 Waiting 15 seconds for SCSI devices to settle SMP: AP CPU #1 Launched! changing root device to da0s1a da1 at ahc0 bus 0 target 4 lun 0 da1: Removable Direct Access SCSI-2 device da1: 10.0MB/s transfers (10.0MHz, offset 10) da1: 606MB (310352 2048 byte sectors: 64H 32S/T 151C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) My disktab says : MO640|Fujitsu 2513A MO drive 640 Mb:\ :dt=SCSI:ty=removable:\ :nc#19397:ns#16:nt#1:\ :se#2048:rm#3600:\ :pa#310352:oa#0:ta=4.2BSD:ba#4096:fa#2048:\ :pc#310352:oc#0:\ :pd#310352:od#0: # disklabel -w -r od1 MO640 # newfs -m 0 -o space -i 12288 -u 16 -t 1 -c 413 /dev/rod1a /dev/rod1a: 1241408 sectors in 19397 cylinders of 1 tracks, 64 sectors 606.2MB in 47 cyl groups (413 c/g, 12.91MB/g, 1088 i/g) super-block backups (for fsck -b #) at: 32, 26464, 52896, 79328, 105760, 132192, 158624, 185056, 211488, 237920, 264352, 290784, 317216, 343648, 370080, 396512, 422944, 449376, 475808, 502240, 528672, 555104, 581536, 607968, 634400, 660832, 687264, 713696, 740128, 766560, 792992, 819424, 845856, 872288, 898720, 925152, 951584, 978016, 1004448, 1030880, 1057312, 1083744, 1110176, 1136608, 1163040, 1189472, 1215904, # mount /dev/od1a /mnt # umount /mnt That's OK. but : # mount /dev/od1a /mnt # cd /mnt # dd if=/dev/zero of=test bs=2048 count=10000 10000+0 records in 10000+0 records out 20480000 bytes transferred in 24.621793 secs (831783 bytes/sec) # cd / # umount /mnt (pause ....) Feb 25 12:26:08 cray /kernel: (da1:ahc0:0:4:0): SCB 0x3 - timed out in command phase, SEQADDR == 0x154 Feb 25 12:26:25 cray /kernel: (da1:ahc0:0:4:0): BDR message in message buffer Feb 25 12:26:25 cray /kernel: (da1:ahc0:0:4:0): SCB 0x3 - timed out in command phase, SEQADDR == 0x154 Feb 25 12:26:25 cray /kernel: (da1:ahc0:0:4:0): no longer in timeout, status = 34b Feb 25 12:26:25 cray /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted # mount /dev/od1a /mnt mount: Operation not permitted Feb 25 12:27:54 cray /kernel: WARNING: R/W mount of /mnt denied. Filesystem is not clean - run fsck Feb 25 12:27:54 cray /kernel: WARNING: R/W mount of /mnt denied. Filesystem is not clean - run fsck # fsck /dev/od1a ** /dev/rod1a ** Last Mounted on /mnt ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 2 files, 10013 used, 296852 free (2 frags, 148425 blocks, 0.0% fragmentation) ***** FILE SYSTEM MARKED CLEAN ***** (pause ...) Feb 25 12:28:33 cray /kernel: (da1:ahc0:0:4:0): SCB 0x2 - timed out in command phase, SEQADDR == 0x154 Feb 25 12:28:50 cray /kernel: (da1:ahc0:0:4:0): BDR message in message buffer Feb 25 12:28:50 cray /kernel: (da1:ahc0:0:4:0): SCB 0x2 - timed out in command phase, SEQADDR == 0x154 Feb 25 12:28:50 cray /kernel: (da1:ahc0:0:4:0): no longer in timeout, status = 34b Feb 25 12:28:50 cray /kernel: ahc0: Issued Channel A Bus Reset. 1 SCBs aborted # fsck /dev/od1a ** /dev/rod1a ** Last Mounted on /mnt ** Phase 1 - Check Blocks and Sizes ** Phase 2 - Check Pathnames ** Phase 3 - Check Connectivity ** Phase 4 - Check Reference Counts ** Phase 5 - Check Cyl groups 2 files, 10013 used, 296852 free (2 frags, 148425 blocks, 0.0% fragmentation) # mount /dev/od1a /mnt Any idea of what could be happening ? I know this drive has a write cache enabled, maybe that's the point ? Arnaud. -- /| / Arnaud KOPP @ DotCOM - UnixWare7 - Irix - Linux - {Net,Free,Open}BSD /-|< Work: +33 1 46 67 51 00 Email : arnaud@dotcom.fr / | \ Fax : +33 1 46 67 51 01 WWW : http://www.DotCom.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 25 10:12: 1 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (Postfix) with ESMTP id D672F14D7E for ; Thu, 25 Feb 1999 10:11:36 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (tiburon [158.227.6.111]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id TAA16404; Thu, 25 Feb 1999 19:08:33 +0100 (MET) Message-ID: <36D591A0.F6BF4420@we.lc.ehu.es> Date: Thu, 25 Feb 1999 19:08:32 +0100 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dept. de Electricidad y Electronica X-Mailer: Mozilla 4.08 [en] (X11; U; FreeBSD 3.0-STABLE i386) MIME-Version: 1.0 To: Arnaud KOPP Cc: scsi@FreeBSD.ORG Subject: Re: [3.1-RELEASE] Fujitsu M2513A 640MB MO ? References: <199902251131.LAA00804@excalibur.oceanis.net> Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Arnaud KOPP wrote: > > # disklabel -w -r od1 MO640 > # newfs -m 0 -o space -i 12288 -u 16 -t 1 -c 413 /dev/rod1a > /dev/rod1a: 1241408 sectors in 19397 cylinders of 1 tracks, 64 sectors > 606.2MB in 47 cyl groups (413 c/g, 12.91MB/g, 1088 i/g) > super-block backups (for fsck -b #) at: > 32, 26464, 52896, 79328, 105760, 132192, 158624, 185056, 211488, 237920, > 264352, 290784, 317216, 343648, 370080, 396512, 422944, 449376, 475808, > 502240, 528672, 555104, 581536, 607968, 634400, 660832, 687264, 713696, > 740128, 766560, 792992, 819424, 845856, 872288, 898720, 925152, 951584, > 978016, 1004448, 1030880, 1057312, 1083744, 1110176, 1136608, 1163040, > 1189472, 1215904, > > # mount /dev/od1a /mnt > # umount /mnt > I have one of those MO drives and it works fine. However, I don't use the "od" device, but the "da" (direct access) device. -- JMA ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | mailto:jmas@es.FreeBSD.ORG Dpto. de Electricidad y Electrónica | http://www.we.lc.ehu.es/~jose Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 25 12: 4:12 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 4386514E8C for ; Thu, 25 Feb 1999 12:03:49 -0800 (PST) (envelope-from darrylo@sr.hp.com) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id MAA19440; Thu, 25 Feb 1999 12:03:29 -0800 (PST) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA126193006; Thu, 25 Feb 1999 12:03:26 -0800 Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_14041)/8.7.3 TIS 5.0) id MAA06761; Thu, 25 Feb 1999 12:03:25 -0800 (PST) Message-Id: <199902252003.MAA06761@mina.sr.hp.com> To: Andrew Gallatin Cc: scsi@FreeBSD.ORG Subject: Re: dual-channel U2W scsi performance Reply-To: Darryl Okahata In-Reply-To: Your message of "Tue, 23 Feb 1999 16:27:52 EST." <14035.5458.71518.652907@grasshopper.cs.duke.edu> Mime-Version: 1.0 (generated by tm-edit 1.1.1.1) Content-Type: text/plain; charset=US-ASCII Date: Thu, 25 Feb 1999 12:03:25 -0800 From: Darryl Okahata Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andrew Gallatin wrote: > Justin T. Gibbs writes: > > > > There must be something wrong with your cables. I've had several instance > s > > where a loose connector pin caused intermittent parity-errors. If both > > the driver and the end device are reporting errors, they can't be wrong. > > I've tested SE operation on the aic7896, so I know that it can work > > with the current driver. > > Before I turned off parity in scsi-select, I tried all possible > combinations of cabling (my setup is motherboard connecter -> internal > cable -> external connector-> external cable -> box w/2 4G cheetahs -> > active terminator), I switched out both cables, the external > connector, the terminator & the box w/2 cheetahs.. No combination > worked on the second channel. All combinations worked on the first > channel. (by worked, I mean probed w/o parity errors) How long is the total cable length, starting at the motherboard? At 20MHz, the max cable length is something like 1.5 meters, or a bit less than 5 feet. Also, you are using high-quality external cables, right? -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 25 13:40:16 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.242]) by hub.freebsd.org (Postfix) with ESMTP id 0290B14D84 for ; Thu, 25 Feb 1999 13:40:14 -0800 (PST) (envelope-from darrylo@sr.hp.com) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by palrel1.hp.com (8.8.6/8.8.5tis) with ESMTP id NAA18576 for ; Thu, 25 Feb 1999 13:40:00 -0800 (PST) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA168608797; Thu, 25 Feb 1999 13:39:57 -0800 Received: from localhost (darrylo@mina.sr.hp.com [15.4.42.247]) by mina.sr.hp.com with ESMTP (8.8.6 (PHNE_14041)/8.7.3 TIS 5.0) id NAA07348 for ; Thu, 25 Feb 1999 13:39:57 -0800 (PST) Message-Id: <199902252139.NAA07348@mina.sr.hp.com> To: scsi@FreeBSD.ORG Subject: Re: LVD transfer rate Reply-To: Darryl Okahata In-Reply-To: Your message of "Mon, 22 Feb 1999 00:05:41 +0100." <28702.919638341@verdi.nethelp.no> Mime-Version: 1.0 (generated by tm-edit 1.1.1.1) Content-Type: text/plain; charset=US-ASCII Date: Thu, 25 Feb 1999 13:39:56 -0800 From: Darryl Okahata Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org sthaug@nethelp.no wote: > There's your answer. The "Force SE Mode" jumper must be off, and you need > a separate LVD terminator. The disk *does not* have a jumper-selectable > LVD terminator. See > > http://www.storage.ibm.com/techsup/hddtech/ddrs/ddrsjum.htm Going off on a tangent, will an LVD drive work in SE mode with a plain wide SCSI controller (non-LVD)? I've got the same drive (DDRS-39130), and my vendor appears to have shipped me the LVD version instead of the plain FW one. If it does, I assume that the drive doesn't have any termination, and I'll have to terminate the cable myself. -- Darryl Okahata darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 25 14: 0:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 0B2BC14D57 for ; Thu, 25 Feb 1999 14:00:11 -0800 (PST) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.1/8.9.1) with ESMTP id QAA20212; Thu, 25 Feb 1999 16:59:54 -0500 (EST) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.2/8.9.1) id QAA35810; Thu, 25 Feb 1999 16:59:41 -0500 (EST) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 25 Feb 1999 16:59:41 -0500 (EST) To: Darryl Okahata Cc: scsi@FreeBSD.ORG Subject: Re: dual-channel U2W scsi performance In-Reply-To: <199902252003.MAA06761@mina.sr.hp.com> References: <14035.5458.71518.652907@grasshopper.cs.duke.edu> <199902252003.MAA06761@mina.sr.hp.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14037.50689.119860.239392@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Darryl Okahata writes: > Andrew Gallatin wrote: > > > Justin T. Gibbs writes: > > > > > > There must be something wrong with your cables. I've had several instance > > s > > > where a loose connector pin caused intermittent parity-errors. If both > > > the driver and the end device are reporting errors, they can't be wrong. > > > I've tested SE operation on the aic7896, so I know that it can work > > > with the current driver. > > > > Before I turned off parity in scsi-select, I tried all possible > > combinations of cabling (my setup is motherboard connecter -> internal > > cable -> external connector-> external cable -> box w/2 4G cheetahs -> > > active terminator), I switched out both cables, the external > > connector, the terminator & the box w/2 cheetahs.. No combination > > worked on the second channel. All combinations worked on the first > > channel. (by worked, I mean probed w/o parity errors) > > How long is the total cable length, starting at the motherboard? > At 20MHz, the max cable length is something like 1.5 meters, or a bit > less than 5 feet. Also, you are using high-quality external cables, > right? I'd estimate the total cable length at <= 1m. The cables are good quality, and the internal cable & external connector were actually temporarily borrowed from the secondary channel of a DPT raid setup (where the external connection is to an identical cable & identical box with 2 identical cheetahs). I trust the cables.. ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 25 14:54:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id A8B5414E30 for ; Thu, 25 Feb 1999 14:54:29 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id PAA47903; Thu, 25 Feb 1999 15:54:01 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902252254.PAA47903@panzer.plutotech.com> Subject: Re: [3.1-RELEASE] Fujitsu M2513A 640MB MO ? In-Reply-To: <199902251131.LAA00804@excalibur.oceanis.net> from Arnaud KOPP at "Feb 25, 1999 12:31:58 pm" To: arnaud@DotCom.FR (Arnaud KOPP) Date: Thu, 25 Feb 1999 15:54:01 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Arnaud KOPP wrote... > I'm trying to correctly use my FUJITSU M2513A MO drive with FreeBSD > and get some SCSI errors when trying to unmount my tape : > > > # umount /mnt > > (da1:ahc0:0:4:0): SCB 0x2 - timed out in command phase, SEQADDR == 0x154 > (da1:ahc0:0:4:0): BDR message in message buffer > (da1:ahc0:0:4:0): SCB 0x2 - timed out in command phase, SEQADDR == 0x154 > (da1:ahc0:0:4:0): no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 1 SCBs aborted The 'timed out in command phase' error indicates that you may have a cabling or termination problem. > da1 at ahc0 bus 0 target 4 lun 0 > da1: Removable Direct Access SCSI-2 device > da1: 10.0MB/s transfers (10.0MHz, offset 10) > da1: 606MB (310352 2048 byte sectors: 64H 32S/T 151C) > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) > > > > My disktab says : > > > MO640|Fujitsu 2513A MO drive 640 Mb:\ > :dt=SCSI:ty=removable:\ > :nc#19397:ns#16:nt#1:\ > :se#2048:rm#3600:\ > :pa#310352:oa#0:ta=4.2BSD:ba#4096:fa#2048:\ > :pc#310352:oc#0:\ > :pd#310352:od#0: > > > # disklabel -w -r od1 MO640 > # newfs -m 0 -o space -i 12288 -u 16 -t 1 -c 413 /dev/rod1a > /dev/rod1a: 1241408 sectors in 19397 cylinders of 1 tracks, 64 sectors > 606.2MB in 47 cyl groups (413 c/g, 12.91MB/g, 1088 i/g) > super-block backups (for fsck -b #) at: > 32, 26464, 52896, 79328, 105760, 132192, 158624, 185056, 211488, 237920, > 264352, 290784, 317216, 343648, 370080, 396512, 422944, 449376, 475808, > 502240, 528672, 555104, 581536, 607968, 634400, 660832, 687264, 713696, > 740128, 766560, 792992, 819424, 845856, 872288, 898720, 925152, 951584, > 978016, 1004448, 1030880, 1057312, 1083744, 1110176, 1136608, 1163040, > 1189472, 1215904, > > # mount /dev/od1a /mnt > # umount /mnt Why are you using the 'od' device? The od device is no longer supported in FreeBSD 3.x, and I'm actually kinda amazed that you're able to do any I/O at all to it. The od device has been replaced by the 'da' device. That's why your MO drive shows up as da1. > That's OK. > > > but : > > # mount /dev/od1a /mnt > # cd /mnt > # dd if=/dev/zero of=test bs=2048 count=10000 > 10000+0 records in > 10000+0 records out > 20480000 bytes transferred in 24.621793 secs (831783 bytes/sec) [ ... ] > Any idea of what could be happening ? I know this drive has a write > cache enabled, maybe that's the point ? I think you probably have a cabling or termination problem. Turning write caching on or off won't make a difference. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 26 3: 8:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from frolic.no-support.loc (ppp39-93.hrz.uni-bielefeld.de [129.70.39.93]) by hub.freebsd.org (Postfix) with ESMTP id 3C58B14F1F for ; Fri, 26 Feb 1999 03:07:50 -0800 (PST) (envelope-from bfischer@Techfak.Uni-Bielefeld.DE) Received: from broccoli.no-support.loc (broccoli.no-support.loc [192.168.43.99]) by frolic.no-support.loc (8.9.2/8.8.8/Debian/GNU) with ESMTP id MAA00706; Fri, 26 Feb 1999 12:05:09 +0100 (CET) From: Bjoern Fischer Received: (from bjoern@localhost) by broccoli.no-support.loc (8.9.2/8.9.2) id MAA00325; Fri, 26 Feb 1999 12:04:34 +0100 (CET) (envelope-from bjoern) Date: Fri, 26 Feb 1999 12:04:33 +0100 To: "Kenneth D. Merry" Cc: freebsd-scsi@freebsd.org Subject: oddities in CAM/cdrecord/DFLTPHYS Message-ID: <19990226120433.A285@broccoli.no-support.loc> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Kenneth, you sent a patch to Joern Schilling changing scsi_maxdma() to return (DFLTPHYS - PAGESIZE) instead of (DFLTPHYS). Although cdrecord only works for me with (DFLTPHYS - PAGESIZE), there are some oddities in either cdrecord's libscg/scsi-bsd.c or in cam/cam_periph.c. cdrecord uses buffers which are already page aligned, so I don't see the necessitiy of (DFLTPHYS - PAGESIZE). But looking at the buffer pointer in cam/cam_periph.c:543 one sees that it has lost it's page alignment. After the correction the buffer is too large. Is it possible that the buffer pointer looses it's alignment in kernel space (e.g. by adding a header or s.t.)? Thanks Bjoern -- -----BEGIN GEEK CODE BLOCK----- GCS d--(+) s++: a- C+++(-) UBL++++OSI++++$ P+++(-) L+++(-) !E W- N+ o>+ K- !w !O !M !V PS++ PE- PGP++ t+++ !5 X++ tv- b+++ D++ G e+ h-- y+ ------END GEEK CODE BLOCK------ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 26 4:56:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from qix (hibou.obs-besancon.fr [193.52.184.7]) by hub.freebsd.org (Postfix) with ESMTP id B543B14BE3 for ; Fri, 26 Feb 1999 04:56:27 -0800 (PST) (envelope-from jmz@FreeBSD.ORG) Received: (from jmz@localhost) by qix (8.9.3/8.8.7) id BAA08074; Fri, 26 Feb 1999 01:50:51 +0100 (MET) Date: Fri, 26 Feb 1999 01:50:51 +0100 (MET) Message-Id: <199902260050.BAA08074@qix> X-Authentication-Warning: qix: jmz set sender to jmz@qix using -f From: Jean-Marc Zucconi To: darrylo@sr.hp.com Cc: scsi@FreeBSD.ORG In-reply-to: <199902252139.NAA07348@mina.sr.hp.com> (message from Darryl Okahata on Thu, 25 Feb 1999 13:39:56 -0800) Subject: Re: LVD transfer rate X-Mailer: Emacs Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>>>> Darryl Okahata writes: > sthaug@nethelp.no wote: >> There's your answer. The "Force SE Mode" jumper must be off, and you need >> a separate LVD terminator. The disk *does not* have a jumper-selectable >> LVD terminator. See >> >> http://www.storage.ibm.com/techsup/hddtech/ddrs/ddrsjum.htm > Going off on a tangent, will an LVD drive work in SE mode with a > plain wide SCSI controller (non-LVD)? I've got the same drive > (DDRS-39130), and my vendor appears to have shipped me the LVD version > instead of the plain FW one. If it does, I assume that the drive > doesn't have any termination, and I'll have to terminate the cable > myself. It will work because it was my original configuration: I had the SE jumper on (my first mistake) and I connected it on the wide connector instead of the LVD connector (my second mistake). It worked also without terminator. Jean-Marc -- Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 26 7:32:47 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from excalibur.oceanis.net (ns.dotcom.fr [195.154.74.11]) by hub.freebsd.org (Postfix) with ESMTP id 047CF14FBF for ; Fri, 26 Feb 1999 07:32:41 -0800 (PST) (envelope-from arnaud@excalibur.oceanis.net) Received: (from arnaud@localhost) by excalibur.oceanis.net (8.9.1/8.9.1) id PAA24236; Fri, 26 Feb 1999 15:32:15 GMT From: Arnaud KOPP Message-Id: <199902261532.PAA24236@excalibur.oceanis.net> Subject: Re: [3.1-RELEASE] Fujitsu M2513A 640MB MO ? In-Reply-To: <199902252254.PAA47903@panzer.plutotech.com> from "Kenneth D. Merry" at "Feb 25, 1999 3:54: 1 pm" To: ken@plutotech.com (Kenneth D. Merry) Date: Fri, 26 Feb 1999 16:32:15 +0100 (MET) Cc: scsi@freebsd.org Organization: DotCom ( Communication Numerique ) 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 > Arnaud KOPP wrote... > > > > (da1:ahc0:0:4:0): SCB 0x2 - timed out in command phase, SEQADDR == 0x154 > > (da1:ahc0:0:4:0): BDR message in message buffer > > (da1:ahc0:0:4:0): SCB 0x2 - timed out in command phase, SEQADDR == 0x154 > > (da1:ahc0:0:4:0): no longer in timeout, status = 34b > > ahc0: Issued Channel A Bus Reset. 1 SCBs aborted > > > The 'timed out in command phase' error indicates that you may have a > cabling or termination problem. > > # mount /dev/od1a /mnt > > # umount /mnt > > Why are you using the 'od' device? The od device is no longer supported in > FreeBSD 3.x, and I'm actually kinda amazed that you're able to do any I/O > at all to it. > > The od device has been replaced by the 'da' device. That's why your MO > drive shows up as da1. od = da . Major/minor are the same. I'll check the termination system since the SCSI chip has 2 Channels and the first is devided into UW and Narrow bus. I'll check the motherboard to be sure what terminator I have to setup. Arnaud. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 26 8: 7:23 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.elpost.com (unknown [193.15.1.54]) by hub.freebsd.org (Postfix) with ESMTP id ADDD914CBE; Fri, 26 Feb 1999 08:07:14 -0800 (PST) (envelope-from johan@granlund.nu) Received: from phoenix.granlund.nu (t2o29p63.telia.com [194.236.214.183]) by mail.elpost.com (2.5 Build 2626 (Berkeley 8.8.6)/8.8.4) with ESMTP id RAA00351; Fri, 26 Feb 1999 17:06:50 +0100 Received: from kyosho.granlund.nu (kyosho.granlund.nu [192.168.0.4]) by phoenix.granlund.nu (8.9.3/8.9.2) with ESMTP id QAA39944; Fri, 26 Feb 1999 16:50:59 +0100 (CET) (envelope-from johan@granlund.nu) Date: Fri, 26 Feb 1999 16:46:22 +0100 (CET) From: Johan Granlund X-Sender: johan@localhost To: Jean-Marc Zucconi Cc: darrylo@sr.hp.com, scsi@FreeBSD.ORG Subject: Re: LVD transfer rate In-Reply-To: <199902260050.BAA08074@qix> 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, 26 Feb 1999, Jean-Marc Zucconi wrote: > >>>>> Darryl Okahata writes: > > > sthaug@nethelp.no wote: > >> There's your answer. The "Force SE Mode" jumper must be off, and you need > >> a separate LVD terminator. The disk *does not* have a jumper-selectable > >> LVD terminator. See > >> > >> http://www.storage.ibm.com/techsup/hddtech/ddrs/ddrsjum.htm > > > Going off on a tangent, will an LVD drive work in SE mode with a > > plain wide SCSI controller (non-LVD)? I've got the same drive > > (DDRS-39130), and my vendor appears to have shipped me the LVD version > > instead of the plain FW one. If it does, I assume that the drive > > doesn't have any termination, and I'll have to terminate the cable > > myself. > > It will work because it was my original configuration: I had the SE > jumper on (my first mistake) and I connected it on the wide connector > instead of the LVD connector (my second mistake). It worked also > without terminator. It's a _wery_ bad idea to run without termination!! I got a LVD drive as a replacement for a failed drive. It had a jumper for "term enable" according to the paper on top of the drive. It didnt work. I got a ton of timeouts and other errors. After installing a external active termination block it works like a charm. This is on a Adaptec 2940UW /Johan > > Jean-Marc > > -- > Jean-Marc Zucconi PGP Key: finger jmz@FreeBSD.ORG > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 26 8:56:26 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 480BB14F8B for ; Fri, 26 Feb 1999 08:55:58 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id JAA51953; Fri, 26 Feb 1999 09:54:48 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902261654.JAA51953@panzer.plutotech.com> Subject: Re: oddities in CAM/cdrecord/DFLTPHYS In-Reply-To: <19990226120433.A285@broccoli.no-support.loc> from Bjoern Fischer at "Feb 26, 1999 12: 4:33 pm" To: bfischer@Techfak.Uni-Bielefeld.DE (Bjoern Fischer) Date: Fri, 26 Feb 1999 09:54:48 -0700 (MST) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bjoern Fischer wrote... > Hello Kenneth, > > you sent a patch to Joern Schilling changing scsi_maxdma() to return > (DFLTPHYS - PAGESIZE) instead of (DFLTPHYS). Although cdrecord only > works for me with (DFLTPHYS - PAGESIZE), there are some oddities in > either cdrecord's libscg/scsi-bsd.c or in cam/cam_periph.c. cdrecord > uses buffers which are already page aligned, so I don't see the > necessitiy of (DFLTPHYS - PAGESIZE). But looking at the buffer pointer > in cam/cam_periph.c:543 one sees that it has lost it's page alignment. > After the correction the buffer is too large. Is it possible that > the buffer pointer looses it's alignment in kernel space (e.g. by > adding a header or s.t.)? What's a 's.t.'? As far as I know, there's no code in the kernel that manipulates the user-passed-in data pointer. At least not up to that point. Of course we temporarily exchange it for a pointer to the same space mapped into the kernel's virtual address space lower down in cam_periph_mapmem(). Here's what I would suggest: - print out the data pointer that is put into the CCB. This will be sp->addr in scsi_send(). - In the pass driver in the kernel, print out the address that it gets. You'll probably want to print it out in passsendccb(), before and after the xpt_merge_ccb() call. (in sys/cam/scsi/scsi_pass.c) From there the CCB is run through cam_periph_mapmem(). My guess is that the buffer is getting thrown out of page alignment somewhere in cdrecord, but I could be wrong of course. If we are manipulating the pointer, then that probably indicates a bug. :) I told Joerg to use DFLTPHYS - PAGESIZE mainly because cdda2wav was sending in non-page-aligned buffers, which eventually would cause problems. I never did enough testing on cdrecord to conclusively say whether or not he was using page aligned buffers. Anyway, let me know what you find. If there's a bug, in the kernel or in cdrecord, we should get it fixed. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 26 10:43:57 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from excalibur.oceanis.net (ns.dotcom.fr [195.154.74.11]) by hub.freebsd.org (Postfix) with ESMTP id CB37815056 for ; Fri, 26 Feb 1999 10:43:51 -0800 (PST) (envelope-from arnaud@excalibur.oceanis.net) Received: (from arnaud@localhost) by excalibur.oceanis.net (8.9.1/8.9.1) id SAA27254 for scsi@freebsd.org; Fri, 26 Feb 1999 18:43:34 GMT From: Arnaud KOPP Message-Id: <199902261843.SAA27254@excalibur.oceanis.net> Subject: Re: [3.1-RELEASE] Fujitsu M2513A 640MB MO ? In-Reply-To: <199902251131.LAA00804@excalibur.oceanis.net> from Arnaud KOPP at "Feb 25, 1999 12:31:58 pm" To: scsi@freebsd.org Date: Fri, 26 Feb 1999 19:43:34 +0100 (MET) Organization: DotCom ( Communication Numerique ) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I'm trying to correctly use my FUJITSU M2513A MO drive with FreeBSD > and get some SCSI errors when trying to unmount my tape : > > > # umount /mnt > > (da1:ahc0:0:4:0): SCB 0x2 - timed out in command phase, SEQADDR == 0x154 > (da1:ahc0:0:4:0): BDR message in message buffer > (da1:ahc0:0:4:0): SCB 0x2 - timed out in command phase, SEQADDR == 0x154 > (da1:ahc0:0:4:0): no longer in timeout, status = 34b > ahc0: Issued Channel A Bus Reset. 1 SCBs aborted > Any idea of what could be happening ? I know this drive has a write > cache enabled, maybe that's the point ? I tried every SCSI cable I had there. And every bios config... with no luck. Finally, I tried disabling write cache at the drive and everything is running right now. Arnaud. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 26 11:43:59 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (Postfix) with ESMTP id 4C71914FFC for ; Fri, 26 Feb 1999 11:43:39 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id OAA01307 for ; Fri, 26 Feb 1999 14:43:23 -0500 (EST) Date: Fri, 26 Feb 1999 14:43:23 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: freebsd-scsi@freebsd.org Subject: RAID saga Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, We've just about given up on CMD as a SCSI-SCSI controller, so now we're looking around to see what else is out there. So far I've heard good things about two others: Mylex DAC960-S(X/U)I (Does anyone see what the differences in these two controllers are? The specs seem the same) See www.mylex.com - this is intel 960-based Infortrend ??A Lots of models there, not real detailed info. See www.infortrend.com.tw for more info. This one is 486 based. Anyone have any experience with either of these? I know one of the Mylex models is being used for wcarchive, I assume under CAM. It appears each of these controllers support growing the array, which is something not possible with the CMD. Of course the most important factor is whether any quirks show up under FreeBSD (in this case a 2.2.7 SNAP with CAM patches). Our issue with the CMD is that under load we get timeouts unless I disable disconnection in the Adaptec card (2940UW) bios. Checked cabling, termination, swapped cables, etc... CMD has been incredibly lame in dealing with this as well, the ol' "I never heard of that OS" line after we buy the product specifically because it "works with any OS". At this point they are telling us to go to our reseller for support, which is kind of silly as the problem seems beyond tech support and more like something that needs some developer attention. If anyone else is running the CRD-5440 with two host channels and two drive channels, please contact me so we can compare notes. The drive side seems OK, the only thing the cmd logs is the reset that the scsi layer sends to wack it back into shape... Thanks, Charles --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 26 13:21: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from news.IAEhv.nl (news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (Postfix) with ESMTP id B78FD14E0F for ; Fri, 26 Feb 1999 13:20:04 -0800 (PST) (envelope-from volf@oasis.IAEhv.nl) Received: from oasis.IAEhv.nl (uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id WAA04493 for freebsd.org!freebsd-scsi; Fri, 26 Feb 1999 22:19:48 +0100 (MET) Received: from LOCAL (volf@localhost) by avalon.oasis.IAEhv.nl (8.9.2/1.63); pid 2181 on Fri, 26 Feb 1999 21:20:10 GMT; id VAA02181 efrom: volf; eto: freebsd-scsi@freebsd.org From: volf@oasis.IAEhv.nl (Frank Volf) Message-Id: <199902262120.VAA02181@avalon.oasis.IAEhv.nl> Subject: ahc error message To: freebsd-scsi@freebsd.org Date: Fri, 26 Feb 1999 22:20:10 +0100 (CET) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Can somebody please explain the following error message: SEQADDR == 0x155 (da0:ahc0:0:0:0): SCB 0x9 - timed out while idle, LASTPHASE == 0x1, SEQADDR == (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): Bus Device Reset Message Sent (da0:ahc0:0:0:0): no longer in timeout, status = 353 Unexpected busfree. LASTPHASE == 0xa0 SEQADDR == 0x155 (da0:ahc0:0:0:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR == (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): Bus Device Reset Message Sent (da0:ahc0:0:0:0): no longer in timeout, status = 353 Unexpected busfree. LASTPHASE == 0xa0 SEQADDR == 0x155 (da0:ahc0:0:0:0): SCB 0x15 - timed out while idle, LASTPHASE == 0x1, SEQADDR == (da0:ahc0:0:0:0): Queuing a BDR SCB (da0:ahc0:0:0:0): Bus Device Reset Message Sent (da0:ahc0:0:0:0): no longer in timeout, status = 353 Unexpected busfree. LASTPHASE == 0xa0 SEQADDR == 0x155 I'v got dozens of them with different numbers after SCB. Is this a serious problem? How can it be fixed? The system is a 3.1-STABLE system upgraded last week. Before that it was a 2.6-RELEASE, in which I never noticed this or similar SCSI messages. Thanks, Frank ---------------------------------------------------------------------------- Frank Volf - Internet Access Eindhoven ---------------------------------------------------------------------------- || volf@oasis.IAEhv.nl - use for personal mail || || volf@IAEhv.nl - use for Internet Access Eindhoven related mail || ---------------------------------------------------------------------------- IAE Public Access Unix System - Dial +31.40.2439436 and login as new. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 26 13:25:25 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (Postfix) with ESMTP id 170C415153 for ; Fri, 26 Feb 1999 13:25:14 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m10GUkg-000I5mC; Fri, 26 Feb 1999 16:24:54 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: RELENG_3 ncr0 driver To: scsi@freebsd.org Date: Fri, 26 Feb 1999 16:24:54 -0500 (EST) Cc: tom@tomqnx.com X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 593 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have been running without scsi problems on my ASUS SC875 since my last cvsup about a week ago. I did a cvsup at about 23:00 EST last night, and since then the driver leaves the controller in a funny state that prevents a reboot. I get: ncr0: SCSI Phase error fixup: CCB already dequeued during the boot process - it does not recover. It is followed by an endless stream of "ncr0: timeout nccb= xxxxxxxx (skip)". The only way I can reboot the system again without problems is to first boot the system under Win98. The next boot under RELENG_3 is fine (until I reboot again). Cheers, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 26 14: 2:30 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from TomQNX.tomqnx.com (cpu2745.adsl.bellglobal.com [207.236.55.214]) by hub.freebsd.org (Postfix) with ESMTP id 44E4B150BC for ; Fri, 26 Feb 1999 14:02:26 -0800 (PST) (envelope-from tom@tomqnx.com) Received: by TomQNX.tomqnx.com (Smail3.2 #1) id m10GVKj-000I5mC; Fri, 26 Feb 1999 17:02:09 -0500 (EST) Message-Id: From: tom@tomqnx.com (Tom Torrance at home) Subject: RELENG_3 sa0 driver To: scsi@freebsd.org Date: Fri, 26 Feb 1999 17:02:09 -0500 (EST) Cc: tom@tomqnx.FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 273 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I cvsup'd and rebuilt my system last night. Today, I did a system backup, and discovered that although dump was using /dev/nrsa0, the tape was automatically rewinding when closed. Easy to miss, and pretty dangerous when multi-file backup tapes are involved. Cheers, Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 26 15:17:47 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 331B214DFB for ; Fri, 26 Feb 1999 15:17:45 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id QAA53929; Fri, 26 Feb 1999 16:17:21 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902262317.QAA53929@panzer.plutotech.com> Subject: Re: ahc error message In-Reply-To: <199902262120.VAA02181@avalon.oasis.IAEhv.nl> from Frank Volf at "Feb 26, 1999 10:20:10 pm" To: volf@oasis.IAEhv.nl (Frank Volf) Date: Fri, 26 Feb 1999 16:17:21 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Frank Volf wrote... > > Hi, > > Can somebody please explain the following error message: > > SEQADDR == 0x155 > (da0:ahc0:0:0:0): SCB 0x9 - timed out while idle, LASTPHASE == 0x1, SEQADDR > == > (da0:ahc0:0:0:0): Queuing a BDR SCB > (da0:ahc0:0:0:0): Bus Device Reset Message Sent > (da0:ahc0:0:0:0): no longer in timeout, status = 353 > Unexpected busfree. LASTPHASE == 0xa0 > SEQADDR == 0x155 > (da0:ahc0:0:0:0): SCB 0x0 - timed out while idle, LASTPHASE == 0x1, SEQADDR > == > (da0:ahc0:0:0:0): Queuing a BDR SCB > (da0:ahc0:0:0:0): Bus Device Reset Message Sent > (da0:ahc0:0:0:0): no longer in timeout, status = 353 > Unexpected busfree. LASTPHASE == 0xa0 > SEQADDR == 0x155 > (da0:ahc0:0:0:0): SCB 0x15 - timed out while idle, LASTPHASE == 0x1, SEQADDR > == > (da0:ahc0:0:0:0): Queuing a BDR SCB > (da0:ahc0:0:0:0): Bus Device Reset Message Sent > (da0:ahc0:0:0:0): no longer in timeout, status = 353 > Unexpected busfree. LASTPHASE == 0xa0 > SEQADDR == 0x155 > > I'v got dozens of them with different numbers after SCB. Is this a serious > problem? How can it be fixed? The system is a 3.1-STABLE system upgraded > last week. Before that it was a 2.6-RELEASE, in which I never noticed this > or similar SCSI messages. The 'timed out while idle' messages mean that the drive did not return a command before the timeout period expired, and there was nothing going on on the bus at the time. The timeout period for the da driver is 60 seconds, so if a drive doesn't return a transaction in that period of time, something is certainly wrong. This indicates that the drive is "going out to lunch" for some reason, and not responding to commands. There are several possible explanations: - it could be a cabling or termination problem - it could be your drive has buggy firmware. What kind of drive is it, and how heavily loaded is it? What was going on when the errors popped up? - it could be your drive is dying Some firmware revisions of the Quantum Atlas II showed symptoms like that under heavy load. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 26 16: 4:19 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 04CDF14FEB for ; Fri, 26 Feb 1999 16:02:40 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id QAA03952; Fri, 26 Feb 1999 16:02:19 -0800 Date: Fri, 26 Feb 1999 16:02:19 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Tom Torrance at home Cc: scsi@FreeBSD.ORG, tom@tomqnx.FreeBSD.ORG Subject: Re: RELENG_3 sa0 driver 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 Really? That's pretty bad. News to me. Better get a newer kernel. On Fri, 26 Feb 1999, Tom Torrance at home wrote: > I cvsup'd and rebuilt my system last night. > Today, I did a system backup, and discovered that > although dump was using /dev/nrsa0, the tape was automatically > rewinding when closed. Easy to miss, and pretty dangerous > when multi-file backup tapes are involved. > > Cheers, > Tom > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 26 16:28:27 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from quackerjack.cc.vt.edu (quackerjack.cc.vt.edu [198.82.160.250]) by hub.freebsd.org (Postfix) with ESMTP id 9258D14BD4 for ; Fri, 26 Feb 1999 16:28:25 -0800 (PST) (envelope-from gemorga2@vt.edu) Received: from sable.cc.vt.edu (sable.cc.vt.edu [128.173.16.30]) by quackerjack.cc.vt.edu (8.8.8/8.8.8) with ESMTP id TAA28775 for ; Fri, 26 Feb 1999 19:28:07 -0500 (EST) Received: from gemorga2.campus.vt.edu (gemorga2.campus.vt.edu [198.82.100.219]) by sable.cc.vt.edu (8.8.8/8.8.8) with SMTP id TAA29537 for ; Fri, 26 Feb 1999 19:28:07 -0500 (EST) Message-Id: <199902270028.TAA29537@sable.cc.vt.edu> From: "George Morgan" To: freebsd-scsi@freebsd.org Date: Fri, 26 Feb 1999 19:28:07 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Problem with non-bootable install... X-mailer: Pegasus Mail for Win32 (v3.01d) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have tried to install FreeBSD 3.0-Release to the second primary partition on the second (scsi ID #1) scsi hard drive on my system. I successfully installed the software (ftp install via bootable floppy) but when I point my boot manager at that partition it does not boot. I already have Linux installed in the first primary on that drive and I can boot it with my boot manager (Boot Magic, by PowerQuest) I realize that this is not the best boot manager, but it should be able to boot FreeBSD if it can boot Linux on a "second drive".. Thank you for your time and please feel free to forward this message to the correct party. George Morgan Virginia Tech Electrical Engineering Class of 2000! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 27 1:40:29 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from linteuto.teuto.de (linteuto.teuto.de [194.77.23.26]) by hub.freebsd.org (Postfix) with ESMTP id DB1661512C for ; Sat, 27 Feb 1999 01:40:15 -0800 (PST) (envelope-from martin@rumolt.teuto.de) Received: from rumolt.teuto.de (root@rumolt.teuto.de [212.8.203.81]) by linteuto.teuto.de (8.8.7/8.8.7) with ESMTP id KAA26458 for ; Sat, 27 Feb 1999 10:39:57 +0100 Received: (from martin@localhost) by rumolt.teuto.de (8.8.8/8.8.7) id KAA10530 for freebsd-scsi@FreeBSD.ORG; Sat, 27 Feb 1999 10:39:57 +0100 (MET) From: Martin Husemann Message-Id: <199902270939.KAA10530@rumolt.teuto.de> Subject: Install doesn't work (fwd) To: freebsd-scsi@FreeBSD.ORG Date: Sat, 27 Feb 1999 10:39:56 +0100 (MET) Organization: Crusaders Catering Services Inc. ;-) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just in case the right people don't see it, I'm forwarding this message I just sent to freebsd-stable. Sorry for the duplicate if you already got this (I didn't know about freebsd-scsi). Martin Forwarded message: > From martin Sat Feb 27 08:22:41 1999 > Subject: Install doesn't work > To: freebsd-stable@freebsd.org > Date: Sat, 27 Feb 1999 08:22:41 +0100 (MET) > Organization: Crusaders Catering Services Inc. ;-) > X-Mailer: ELM [version 2.4 PL24] > MIME-Version: 1.0 > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: 8bit > Content-Length: 3218 > > Hello! > > I tried to boot FreeBSD 3.1 stable (fetched form ftp.releng3 about February > 20) on a machine here where I usualy run NetBSD on. > > It didn't work, as during the "Probing for devices" phase there is a > kernel panic (integer divide) after a lot of ILLEGAL REQUEST messages > apparently from the SCSI driver probing the QIC tape. This tape device > has a quirks entry on NetBSD because it responds to all LUN's (without > that quirk it would attach as eight devices). > > I can't disbale EISA devices in the kernel configuration, and can't block > SCSI devices, so is there any way around this? > > > Martin > > > P.S.: just for reference, this particualr machine runs NetBSD just fine, > dmesg output follows: > > NetBSD 1.3I (RUMOLT) #0: Fri Feb 26 16:41:34 MET 1999 > martin@asprian.teuto.de:/usr/src/sys-i4b/arch/i386/compile/RUMOLT > cpu0: Intel 486DX (486-class) > real mem = 33161216 > avail mem = 29143040 > using 430 buffers containing 1761280 bytes of memory > mainbus0 (root) > eisa0 at mainbus0 > ahb0 at eisa0 slot 1: Adaptec AHA-1742A SCSI > ahb0: interrupting at irq 11 > scsibus0 at ahb0: 8 targets, 8 luns per target > sd0 at scsibus0 targ 0 lun 0: SCSI2 0/direct fixed > sd0: 501MB, 2448 cyl, 6 head, 69 sec, 512 bytes/sect x 1027548 sectors > st0 at scsibus0 targ 3 lun 0: SCSI1 1/sequential removable > st0: drive empty > cd0 at scsibus0 targ 4 lun 0: SCSI2 5/cdrom removable > sd1 at scsibus0 targ 6 lun 0: SCSI2 0/direct fixed > sd1: 4134MB, 8205 cyl, 6 head, 171 sec, 512 bytes/sect x 8467200 sectors > device ATI4400 at eisa0 slot 3 not configured > ep0 at eisa0 slot 4: 3Com 3Com 3C597 Fast Etherlink TX > ep0: interrupting at irq 10 > ep0: address 00:10:4b:24:be:a8, 64KB word-wide FIFO, 3:1 Rx:Tx split > ep0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX (default 10baseT) > isa0 at mainbus0 > com0 at isa0 port 0x3f8-0x3ff irq 4: ns8250 or ns16450, no fifo > com1 at isa0 port 0x2f8-0x2ff irq 3: ns16550a, working fifo > lpt0 at isa0 port 0x378-0x37b irq 7 > we0 at isa0 port 0x300-0x31f iomem 0xe0000-0xe3fff irq 15 > we0: WD8013EP Ethernet (16-bit) > we0: Ethernet address 00:00:c0:11:48:2d > npx0 at isa0 port 0xf0-0xff: using exception 16 > vt0 at isa0 port 0x60-0x6f irq 1 > vt0: generic, 80 col, color, 8 scr, mf2-kbd, [R3.32] > vt0: console > fdc0 at isa0 port 0x3f0-0x3f7 irq 6 drq 2 > fd0 at fdc0 drive 0: 1.44MB, 80 cyl, 2 head, 18 sec > isic0 at isa0 port 0x340-0x347 irq 5 > isic0: AVM A1 or AVM Fritz!Card > isic0: ISAC 2085 Version V2.3 (B3) (IOM-2) > isic0: HSCX 82525 Version A3 > isic1 at isa0 port 0xd80-0xd87 irq 12 > isic1: Teles S0/16.3 > isic1: ISAC 2085 Version A1/A2 or 2086/2186 Version 1.1 (IOM-2) > isic1: HSCX 82525 or 21525 Version 2.1 > biomask 840 netmask 9c60 ttymask 9ce2 > i4b: ISDN call control device attached > i4btrc: 2 ISDN trace device(s) attached > i4bctl: ISDN system control port attached > i4brbch: 4 raw B channel access device(s) attached > i4btel: 2 ISDN telephony interface device(s) attached > i4bipr: 2 IP over raw HDLC ISDN device(s) attached (VJ header compression) > i4bisppp: 2 ISDN SyncPPP device(s) attached > boot device: sd0 > root on sd0a dumps on sd0b > root file system type: ffs > IP Filter: initialized. Default = pass all, Logging = disabled > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 27 11:27:27 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from news.IAEhv.nl (news.IAEhv.nl [194.151.64.4]) by hub.freebsd.org (Postfix) with ESMTP id ECAF41516F for ; Sat, 27 Feb 1999 11:27:03 -0800 (PST) (envelope-from volf@oasis.IAEhv.nl) Received: from oasis.IAEhv.nl (uucp@localhost) by news.IAEhv.nl (8.9.1/8.9.1) with IAEhv.nl id UAA25375; Sat, 27 Feb 1999 20:26:41 +0100 (MET) Received: from LOCAL (volf@localhost) by avalon.oasis.IAEhv.nl (8.9.2/1.63); pid 980 on Sat, 27 Feb 1999 19:23:17 GMT; id TAA00980 efrom: volf; eto: UNKNOWN From: volf@oasis.IAEhv.nl (Frank Volf) Message-Id: <199902271923.TAA00980@avalon.oasis.IAEhv.nl> Subject: Re: ahc error message In-Reply-To: <199902262317.QAA53929@panzer.plutotech.com> from "Kenneth D. Merry" at "Feb 26, 1999 4:17:21 pm" To: ken@plutotech.com (Kenneth D. Merry) Date: Sat, 27 Feb 1999 20:23:17 +0100 (CET) Cc: volf@oasis.IAEhv.nl, freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry wrote: > The 'timed out while idle' messages mean that the drive did not return a > command before the timeout period expired, and there was nothing going on > on the bus at the time. The timeout period for the da driver is 60 > seconds, so if a drive doesn't return a transaction in that period of time, > something is certainly wrong. > > This indicates that the drive is "going out to lunch" for some reason, and > not responding to commands. > > There are several possible explanations: > > - it could be a cabling or termination problem Seems unlikely. Never experienced problems with FreeBSD 2.2.6 nor with windows/NT that is installed on another partition. > - it could be your drive has buggy firmware. What kind of drive is it, > and how heavily loaded is it? What was going on when the errors popped > up? Yes, there was heavy disk activity going on at the moment the error occured. > Some firmware revisions of the Quantum Atlas II showed symptoms like that > under heavy load. ahc0: rev 0x00 int a irq 10 on pci0.6.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ... da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) Is this the quantum drive you are talking about? I have no clue how to determine the firmware version of this drive. Nor do I have a utility to upgrade the firmware. Sigh... Regards, Frank ---------------------------------------------------------------------------- Frank Volf - Internet Access Eindhoven ---------------------------------------------------------------------------- || volf@oasis.IAEhv.nl - use for personal mail || || volf@IAEhv.nl - use for Internet Access Eindhoven related mail || ---------------------------------------------------------------------------- IAE Public Access Unix System - Dial +31.40.2439436 and login as new. ---------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 27 12:41:13 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (Postfix) with ESMTP id 5A2EF1509C for ; Sat, 27 Feb 1999 12:41:12 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id NAA62936; Sat, 27 Feb 1999 13:40:47 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902272040.NAA62936@panzer.plutotech.com> Subject: Re: ahc error message In-Reply-To: <199902271923.TAA00980@avalon.oasis.IAEhv.nl> from Frank Volf at "Feb 27, 1999 8:23:17 pm" To: volf@oasis.IAEhv.nl (Frank Volf) Date: Sat, 27 Feb 1999 13:40:47 -0700 (MST) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Frank Volf wrote... > Kenneth D. Merry wrote: > > The 'timed out while idle' messages mean that the drive did not return a > > command before the timeout period expired, and there was nothing going on > > on the bus at the time. The timeout period for the da driver is 60 > > seconds, so if a drive doesn't return a transaction in that period of time, > > something is certainly wrong. > > > > This indicates that the drive is "going out to lunch" for some reason, and > > not responding to commands. > > > > There are several possible explanations: > > > > - it could be a cabling or termination problem > > Seems unlikely. Never experienced problems with FreeBSD 2.2.6 nor with > windows/NT that is installed on another partition. Neither FreeBSD 2.2.6 nor Windows NT are capable of putting as much load on disks as FreeBSD/CAM. > > - it could be your drive has buggy firmware. What kind of drive is it, > > and how heavily loaded is it? What was going on when the errors popped > > up? > > Yes, there was heavy disk activity going on at the moment the error occured. > > > Some firmware revisions of the Quantum Atlas II showed symptoms like that > > under heavy load. > > ahc0: rev 0x00 int a irq 10 on pci0.6.0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > > ... > > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) > > Is this the quantum drive you are talking about? I have no clue how to > determine the firmware version of this drive. Nor do I have a utility to > upgrade the firmware. Sigh... The firmware version is LXY4. I had problems very similar to the problems you're having with my Atlas II's (I have 4, unfortunately) until I upgraded to the LYK8 firmware: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) Quantum has firmware upgrades and a firmware upgrade utility on ftp.quantum.com. (it seems to be down now) You'll need a bootable DOS floppy with ASPI drivers for your SCSI card to run the firmware loader and do the upgrade. You'll probably want to back your system up first, although I have done four firmware upgrades, and haven't lost any data. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message