From owner-freebsd-scsi Tue Mar 25 11:41:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA03791 for freebsd-scsi-outgoing; Tue, 25 Mar 1997 11:41:00 -0800 (PST) Received: from robkaos.ruhr.de (robkaos.ruhr.de [141.39.227.87]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA03783 for ; Tue, 25 Mar 1997 11:40:55 -0800 (PST) Received: by robkaos.ruhr.de (/\oo/\ Smail3.1.29.1 #29.1) id ; Tue, 25 Mar 97 20:40 MET Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: CD-R audio problem To: freebsd-scsi@freebsd.org Date: Tue, 25 Mar 1997 20:40:23 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yesterday I tried to burn an audio cd with the following commands: wormcontrol select HP 4020i wormcontrol prepdisk double wormcontrol track audio rtprio 5 team -v 1m 5 < track-01.img | dd of=/dev/rworm0 obs=23520 wormcontrol track audio rtprio 5 team -v 1m 5 < track-02.img | dd of=/dev/rworm0 obs=23520 etc... wormcontrol fixate 0 The raw audio data were extracted by using the cdd tool. The burning worked without any problems, but the the resulting CD contained only noise. I repeated the above with the extracted data coming from a DOS program but result is the same: noise. Has anyone burned an audio cd successfully? If yes, how? BTW, the SCSI HA is a SC-200 (on a P6NP5 motherboard). TIA Robert From owner-freebsd-scsi Tue Mar 25 16:05:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA23468 for freebsd-scsi-outgoing; Tue, 25 Mar 1997 16:05:40 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA23456 for ; Tue, 25 Mar 1997 16:05:36 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id BAA17997; Wed, 26 Mar 1997 01:05:34 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id AAA07610; Wed, 26 Mar 1997 00:40:02 +0100 (MET) Message-ID: <19970326004002.TO35612@uriah.heep.sax.de> Date: Wed, 26 Mar 1997 00:40:02 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG Cc: robsch@robkaos.ruhr.de (Robert Schien) Subject: Re: CD-R audio problem References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Robert Schien on Mar 25, 1997 20:40:23 +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Robert Schien wrote: > Has anyone burned an audio cd successfully? If yes, how? Nick Sayer once reported me that he was successful in this. I'm not sure whether he's following this list. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Tue Mar 25 17:03:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA28246 for freebsd-scsi-outgoing; Tue, 25 Mar 1997 17:03:41 -0800 (PST) Received: from burdell.cc.gatech.edu (root@burdell.cc.gatech.edu [130.207.3.207]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA28220 for ; Tue, 25 Mar 1997 17:03:35 -0800 (PST) Received: from oscar.cc.gatech.edu (cau@oscar.cc.gatech.edu [130.207.107.12]) by burdell.cc.gatech.edu (8.8.4/8.6.9) with ESMTP id UAA19764; Tue, 25 Mar 1997 20:03:16 -0500 (EST) Received: (from cau@localhost) by oscar.cc.gatech.edu (8.8.4/8.6.9) id UAA23368; Tue, 25 Mar 1997 20:03:10 -0500 (EST) From: cau@cc.gatech.edu (Carlos Ugarte) Message-Id: <199703260103.UAA23368@oscar.cc.gatech.edu> Subject: Re: CD-R audio problem To: robsch@robkaos.ruhr.de (Robert Schien) Date: Tue, 25 Mar 1997 20:03:10 -0500 (EST) Cc: freebsd-scsi@freebsd.org In-Reply-To: from "Robert Schien" at Mar 25, 97 08:40:23 pm X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > wormcontrol prepdisk double I haven't burned an audio CD (yet), but I thought that audio recording was limited to single speed (I have a Philips CDD2000, which is essentially the same as the HP 4020). Could be wrong, though. Carlos -- Carlos A. Ugarte cau@cc.gatech.edu Author of PageMage, a virtual desktop util for OS/2 http://www.cc.gatech.edu/people/home/cau/ If you understand what you are doing, you are not learning anything From owner-freebsd-scsi Tue Mar 25 22:59:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA21020 for freebsd-scsi-outgoing; Tue, 25 Mar 1997 22:59:11 -0800 (PST) Received: from david.siemens.de (david.siemens.de [139.23.36.11]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA21012 for ; Tue, 25 Mar 1997 22:59:07 -0800 (PST) Received: from salomon.mchp.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.8.5/8.8.5) with ESMTP id HAA03465 for ; Wed, 26 Mar 1997 07:54:20 +0100 (MET) Received: from curry.mchp.siemens.de (1@curry.mchp.siemens.de [146.180.31.23]) by salomon.mchp.siemens.de (8.8.4/8.8.4) with ESMTP id HAA24939 for ; Wed, 26 Mar 1997 07:59:03 +0100 (MET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.5/8.8.5) id HAA04634 for ; Wed, 26 Mar 1997 07:59:02 +0100 (MET) From: Andre Albsmeier Message-Id: <199703260658.HAA08065@server.us.tld> Subject: Re: CD-R audio problem In-Reply-To: <199703260103.UAA23368@oscar.cc.gatech.edu> from Carlos Ugarte at "Mar 25, 97 08:03:10 pm" To: cau@cc.gatech.edu (Carlos Ugarte) Date: Wed, 26 Mar 1997 07:58:53 +0100 (CET) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > wormcontrol prepdisk double > > I haven't burned an audio CD (yet), but I thought that audio > recording was limited to single speed (I have a Philips CDD2000, > which is essentially the same as the HP 4020). Could be wrong, > though. I am writing audio CDs at 4x Speed under win3.1 :-(. They have proved to be very reliable. I think, this is NO windoze special feature... -Andre From owner-freebsd-scsi Tue Mar 25 23:43:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA23521 for freebsd-scsi-outgoing; Tue, 25 Mar 1997 23:43:28 -0800 (PST) Received: from mail.cs.tu-berlin.de (root@mail.cs.tu-berlin.de [130.149.17.13]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA23515 for ; Tue, 25 Mar 1997 23:43:23 -0800 (PST) Received: from blasuarr.cs.tu-berlin.de (uwp@blasuarr.cs.tu-berlin.de [130.149.17.114]) by mail.cs.tu-berlin.de (8.8.5/8.8.5) with ESMTP id IAA18264; Wed, 26 Mar 1997 08:43:17 +0100 (MET) From: Udo Wolter Received: (from uwp@localhost) by blasuarr.cs.tu-berlin.de (8.8.5/8.8.5) id IAA14604; Wed, 26 Mar 1997 08:43:09 +0100 (MET) Message-Id: <199703260743.IAA14604@blasuarr.cs.tu-berlin.de> Subject: Re: CD-R audio problem To: robsch@robkaos.ruhr.de (Robert Schien) Date: Wed, 26 Mar 1997 08:42:57 +0100 (MET) Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: from "Robert Schien" at Mar 25, 97 08:40:23 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi ! > Yesterday I tried to burn an audio cd with the following commands: > > wormcontrol select HP 4020i > wormcontrol prepdisk double > wormcontrol track audio > rtprio 5 team -v 1m 5 < track-01.img | dd of=/dev/rworm0 obs=23520 > wormcontrol track audio > rtprio 5 team -v 1m 5 < track-02.img | dd of=/dev/rworm0 obs=23520 > > etc... > wormcontrol fixate 0 > > The raw audio data were extracted by using the cdd tool. > The burning worked without any problems, but the the resulting CD > contained only noise. I repeated the above with the extracted > data coming from a DOS program but result is the same: noise. > > Has anyone burned an audio cd successfully? If yes, how? > > BTW, the SCSI HA is a SC-200 (on a P6NP5 motherboard). Could it be that there is a problem with byte-order ? I can remember that my philips can use intel-byte-order and vice versa, you have to tell it what you want to use. If you used non-intel byte order on the CD you surely will only get garbage...:-( Bye, Udo -- Udo Wolter, email: uwp@cs.tu-berlin.de, www: http://www.cs.tu-berlin.de/~uwp/ !!! LOW-TECH Page: http://www.cs.tu-berlin.de/~uwp/low-tech.html !!! From owner-freebsd-scsi Wed Mar 26 00:22:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA25319 for freebsd-scsi-outgoing; Wed, 26 Mar 1997 00:22:41 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA25303 for ; Wed, 26 Mar 1997 00:22:35 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA22725; Wed, 26 Mar 1997 09:22:30 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA10127; Wed, 26 Mar 1997 09:17:36 +0100 (MET) Message-ID: <19970326091736.KA53613@uriah.heep.sax.de> Date: Wed, 26 Mar 1997 09:17:36 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.org (FreeBSD SCSI list) Cc: robsch@robkaos.ruhr.de (Robert Schien) Subject: Re: CD-R audio problem References: <199703260103.UAA23368@oscar.cc.gatech.edu> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703260103.UAA23368@oscar.cc.gatech.edu>; from Carlos Ugarte on Mar 25, 1997 20:03:10 -0500 Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk As Carlos Ugarte wrote: > I haven't burned an audio CD (yet), but I thought that audio > recording was limited to single speed (I have a Philips CDD2000, > which is essentially the same as the HP 4020). It's not limited, but i'm not sure whether the vendors guarantee you audio recording for more than single speed. Technically, it should not be a problem. Single speed is only crucial if you wanna actually play the result. :) -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Wed Mar 26 08:01:42 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA18828 for freebsd-scsi-outgoing; Wed, 26 Mar 1997 08:01:42 -0800 (PST) Received: from toybox.ottawa.on.ca (soldier.toybox.ottawa.on.ca [205.250.97.225]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA18822 for ; Wed, 26 Mar 1997 08:01:36 -0800 (PST) Received: (from rhooper@localhost) by toybox.ottawa.on.ca (8.7.4/8.7.3) id LAA17954 for freebsd-scsi@freebsd.org; Wed, 26 Mar 1997 11:17:09 -0500 From: "Roy M. Hooper" Message-Id: <199703261617.LAA17954@toybox.ottawa.on.ca> Subject: AHA2940 bug(s) still exist in 2.2.1 To: freebsd-scsi@freebsd.org Date: Wed, 26 Mar 1997 11:17:08 -0500 (EST) Content-Type: text Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk It would appear that the bugs in the 2940 drivers are still there in 2.2.1. We had the same kind of crash as usual, except the machine didn't come back up this time. We received several "timeout" messages and then the machine froze. The machine is configured as follows: Two AHA2940 cards, 3 2gb disks each CCD striping (interleave of 65536) on all 6 SCSI disks One 2GB IDE disk. It is our news server, and is rather heavily loaded. Before 2.2.1 the machine would reboot and come back up (after fscking the disks for 10-20 minutes). Anyone have any insight(s)? NB - the IDE disk has alot of IO on it too. We've just ordered a 3940 since we want to try to eliminate the possibility that it's hardware related -- the crashing and burning showed up under Solaris 2.5x86 as well. From owner-freebsd-scsi Wed Mar 26 10:13:54 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA03970 for freebsd-scsi-outgoing; Wed, 26 Mar 1997 10:13:54 -0800 (PST) Received: from pluto.plutotech.com (root@pluto.plutotech.com [206.168.67.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA03955 for ; Wed, 26 Mar 1997 10:13:49 -0800 (PST) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id LAA27397; Wed, 26 Mar 1997 11:13:39 -0700 (MST) Message-Id: <199703261813.LAA27397@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: "Roy M. Hooper" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AHA2940 bug(s) still exist in 2.2.1 In-reply-to: Your message of "Wed, 26 Mar 1997 11:17:08 EST." <199703261617.LAA17954@toybox.ottawa.on.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Mar 1997 11:14:00 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >It would appear that the bugs in the 2940 drivers are still there in 2.2.1. >We had the same kind of crash as usual, except the machine didn't come back >up this time. > >We received several "timeout" messages and then the machine froze. I need the exact timeout messages, information about what AHC options you have in your kernel config file, and the dmesg output listing the drives you are using. I will say this though. Using tagged queueing can still be somewhat dangerous with the Quantum Atlas II drives. For one thing, even with only 8 tags outstanding, they can return QUEUE FULL status which the generic FreeBSD code simply does not handle very well. The transaction will be repeatedly requeued by the kernel until it succeeds with no amount of delay between retries which can often cause the drive to simply "give up" and return BUSY status indefinitely. The proper fix for this is in the works, but it comes only once we convert to my new CAM SCSI framework probably a month or two down the line. Even if the drive doesn't return QUEUE FULL, it is very possible that you are experiencing "tag starvation". The driver currently used "Simple Queue" tags for all transactions which allows the drive to reorder the transactions in anyway it sees fit so long as "write followed by read" consistency is maintained. This means that a transaction for a location far from the current head possition can be starved by a continuous stream of transactions that don't require large seeks. The faster and larger the drive, the easier it is to make this happen. I saw it on a Quantum Atlas II last night during two concurrent copies over 100Bt ethernet. The driver does attempt to handle this condition by first attempting to queue an Ordered Tagged transaction to the disk. This should force the drive to finish all pending transactions before starting any others. The current timeout for the Ordered Tagged transaction to be successful is only 1 second which perhaps isn't really long enough. Something that my help this problem is to perform ordered writes for all synch write operations which will be possible with the new SCSI code. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Wed Mar 26 10:38:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA06675 for freebsd-scsi-outgoing; Wed, 26 Mar 1997 10:38:00 -0800 (PST) Received: from toybox.ottawa.on.ca (soldier.toybox.ottawa.on.ca [205.250.97.225]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA06653 for ; Wed, 26 Mar 1997 10:37:55 -0800 (PST) Received: (from rhooper@localhost) by toybox.ottawa.on.ca (8.7.4/8.7.3) id NAA18416; Wed, 26 Mar 1997 13:53:50 -0500 From: "Roy M. Hooper" Message-Id: <199703261853.NAA18416@toybox.ottawa.on.ca> Subject: Re: AHA2940 bug(s) still exist in 2.2.1 To: gibbs@plutotech.com (Justin T. Gibbs) Date: Wed, 26 Mar 1997 13:53:49 -0500 (EST) Cc: rhooper@toybox.ottawa.on.ca, freebsd-scsi@FreeBSD.ORG In-Reply-To: <199703261813.LAA27397@pluto.plutotech.com> from "Justin T. Gibbs" at Mar 26, 97 11:14:00 am Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I need the exact timeout messages, information about what AHC options you > have in your kernel config file, and the dmesg output listing the drives > you are using. The exact timeout message is almost impossible to retreive as the system tends to reboot and come back up 90% of the time. This normally happens without us at the console - since the messages aren't logged to disk, we never see them. One of the tech support guys saw the machine hung and rebooted it for us this morning (without writing down the message). ahc0 rev 3 int a irq 5 on pci0:17 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "SEAGATE ST32151N 0284" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2049MB (4197405 512 byte sectors) (ahc0:1:0): "SEAGATE ST32151N 0284" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 2049MB (4197405 512 byte sectors) (ahc0:2:0): "SEAGATE ST32151N 0284" type 0 fixed SCSI 2 sd2(ahc0:2:0): Direct-Access 2049MB (4197405 512 byte sectors) ahc1 rev 0 int a irq 10 on pci0:18 ahc1: aic7880 Single Channel, SCSI Id=7, 16 SCBs ahc1 waiting for scsi devices to settle (ahc1:0:0): "SEAGATE ST32151N 0284" type 0 fixed SCSI 2 sd3(ahc1:0:0): Direct-Access 2049MB (4197405 512 byte sectors) (ahc1:1:0): "SEAGATE ST32151N 0154" type 0 fixed SCSI 2 sd4(ahc1:1:0): Direct-Access 2049MB (4197405 512 byte sectors) (ahc1:2:0): "SEAGATE ST32430N 0510" type 0 fixed SCSI 2 sd5(ahc1:2:0): Direct-Access 2049MB (4197405 512 byte sectors) There are no AHC options set. > an Ordered Tagged transaction to the disk. This should force the drive to > finish all pending transactions before starting any others. The current > timeout for the Ordered Tagged transaction to be successful is only 1 > second which perhaps isn't really long enough. Something that my help > this problem is to perform ordered writes for all synch write operations > which will be possible with the new SCSI code. Considering the Seagate Barracuda drives we have are rather fast, I would guess that this is the problem. 1 second is rather short. Especially for something that may panic. Wouldn't 5 seconds be a better timeout period? From owner-freebsd-scsi Wed Mar 26 10:43:28 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA07385 for freebsd-scsi-outgoing; Wed, 26 Mar 1997 10:43:28 -0800 (PST) Received: from pluto.plutotech.com (root@pluto.plutotech.com [206.168.67.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA07376 for ; Wed, 26 Mar 1997 10:43:22 -0800 (PST) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id LAA27920; Wed, 26 Mar 1997 11:43:15 -0700 (MST) Message-Id: <199703261843.LAA27920@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: "Roy M. Hooper" cc: gibbs@plutotech.com (Justin T. Gibbs), freebsd-scsi@FreeBSD.ORG Subject: Re: AHA2940 bug(s) still exist in 2.2.1 In-reply-to: Your message of "Wed, 26 Mar 1997 13:53:49 EST." <199703261853.NAA18416@toybox.ottawa.on.ca> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 26 Mar 1997 11:43:36 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> I need the exact timeout messages, information about what AHC options you >> have in your kernel config file, and the dmesg output listing the drives >> you are using. > >The exact timeout message is almost impossible to retreive as the system >tends to reboot and come back up 90% of the time. This normally happens >without us at the console - since the messages aren't logged to disk, we >never see them. One of the tech support guys saw the machine hung and >rebooted it for us this morning (without writing down the message). Can you hook up a serial console? >ahc0 rev 3 int a irq 5 on pci0:17 >ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs >ahc0 waiting for scsi devices to settle >(ahc0:0:0): "SEAGATE ST32151N 0284" type 0 fixed SCSI 2 >sd0(ahc0:0:0): Direct-Access 2049MB (4197405 512 byte sectors) >(ahc0:1:0): "SEAGATE ST32151N 0284" type 0 fixed SCSI 2 >sd1(ahc0:1:0): Direct-Access 2049MB (4197405 512 byte sectors) >(ahc0:2:0): "SEAGATE ST32151N 0284" type 0 fixed SCSI 2 >sd2(ahc0:2:0): Direct-Access 2049MB (4197405 512 byte sectors) >ahc1 rev 0 int a irq 10 on pci0:18 >ahc1: aic7880 Single Channel, SCSI Id=7, 16 SCBs >ahc1 waiting for scsi devices to settle >(ahc1:0:0): "SEAGATE ST32151N 0284" type 0 fixed SCSI 2 >sd3(ahc1:0:0): Direct-Access 2049MB (4197405 512 byte sectors) >(ahc1:1:0): "SEAGATE ST32151N 0154" type 0 fixed SCSI 2 >sd4(ahc1:1:0): Direct-Access 2049MB (4197405 512 byte sectors) >(ahc1:2:0): "SEAGATE ST32430N 0510" type 0 fixed SCSI 2 >sd5(ahc1:2:0): Direct-Access 2049MB (4197405 512 byte sectors) Are these narrow or wide? I should be able to create a similar test setup sometime next week, if/when this motherboard I'm waiting on comes in. >There are no AHC options set. Then it's not the tagged queueing. I would have expected you to have at least AHC_TAGENABLE turned on in you config file. >> an Ordered Tagged transaction to the disk. This should force the drive to >> finish all pending transactions before starting any others. The current >> timeout for the Ordered Tagged transaction to be successful is only 1 >> second which perhaps isn't really long enough. Something that my help >> this problem is to perform ordered writes for all synch write operations >> which will be possible with the new SCSI code. > >Considering the Seagate Barracuda drives we have are rather fast, I would >guess that this is the problem. Not if you don't have the AHC_TAGENABLE option turned on. >1 second is rather short. Especially for something that may panic. It's not supposed to panic. It's supposed to start taking more drastic measures to restore order on the SCSI bus. That's why I want more acurate messages. >Wouldn't 5 seconds be a better timeout period? I already bumped it in my local version. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Wed Mar 26 10:56:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA09006 for freebsd-scsi-outgoing; Wed, 26 Mar 1997 10:56:52 -0800 (PST) Received: from toybox.ottawa.on.ca (soldier.toybox.ottawa.on.ca [205.250.97.225]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA08970 for ; Wed, 26 Mar 1997 10:56:33 -0800 (PST) Received: (from rhooper@localhost) by toybox.ottawa.on.ca (8.7.4/8.7.3) id OAA18583; Wed, 26 Mar 1997 14:12:32 -0500 From: "Roy M. Hooper" Message-Id: <199703261912.OAA18583@toybox.ottawa.on.ca> Subject: Re: AHA2940 bug(s) still exist in 2.2.1 To: gibbs@plutotech.com (Justin T. Gibbs) Date: Wed, 26 Mar 1997 14:12:31 -0500 (EST) Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: <199703261843.LAA27920@pluto.plutotech.com> from "Justin T. Gibbs" at Mar 26, 97 11:43:36 am Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Can you hook up a serial console? I could, but I'd need to figure out how :) The switchbox to the dumbterm has a free port. We also have a printer available. > Are these narrow or wide? I should be able to create a similar test setup > sometime next week, if/when this motherboard I'm waiting on comes in. Narrow. > Then it's not the tagged queueing. I would have expected you to have at > least AHC_TAGENABLE turned on in you config file. I'm pretty new to FreeBSD - I've used Linux and Solaris/SunOS for quite a while though. > It's not supposed to panic. It's supposed to start taking more drastic > measures to restore order on the SCSI bus. That's why I want more acurate > messages. Something about a "timeout in a timeout" From owner-freebsd-scsi Wed Mar 26 11:27:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA12935 for freebsd-scsi-outgoing; Wed, 26 Mar 1997 11:27:59 -0800 (PST) Received: from kremvax.demos.su (kremvax.demos.su [194.87.0.20]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA12899 for ; Wed, 26 Mar 1997 11:27:36 -0800 (PST) Received: by kremvax.demos.su (8.6.13/D) from 0@sinbin.demos.su [194.87.0.31] with ESMTP id WAA04070; Wed, 26 Mar 1997 22:26:08 +0300 Received: by sinbin.demos.su id WAA27096; (8.6.12/D) Wed, 26 Mar 1997 22:25:22 +0300 From: bag@sinbin.demos.su (Alex G. Bulushev) Message-Id: <199703261925.WAA27096@sinbin.demos.su> Subject: Re: AHA2940 bug(s) still exist in 2.2.1 To: gibbs@plutotech.com (Justin T. Gibbs) Date: Wed, 26 Mar 1997 22:25:22 +0300 (MSK) Cc: rhooper@toybox.ottawa.on.ca, gibbs@plutotech.com, freebsd-scsi@FreeBSD.ORG In-Reply-To: <199703261843.LAA27920@pluto.plutotech.com> from "Justin T. Gibbs" at Mar 26, 97 11:43:36 am X-Mailer: ELM [version 2.4 PL24 ME7a] Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >There are no AHC options set. > > Then it's not the tagged queueing. I would have expected you to have at > least AHC_TAGENABLE turned on in you config file. we use p6-200 with two 3940UW and several Barracuda 9GB UW and found that without scsi options in kernel system unstable, reboots o freeze once 2-3h using TAG, SBCs and MEMIO system work 30h, up to now, but this is with old 2.2.1R (aic7xxx 03.16) now we plan to load kernel with new 2.2.1R Alex. > > >> an Ordered Tagged transaction to the disk. This should force the drive to > > -- > Justin T. Gibbs > =========================================== > FreeBSD: Turning PCs into workstations > =========================================== > > > From owner-freebsd-scsi Wed Mar 26 14:03:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA01854 for freebsd-scsi-outgoing; Wed, 26 Mar 1997 14:03:21 -0800 (PST) Received: from m1.cs.man.ac.uk (m1.cs.man.ac.uk [130.88.13.4]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA01846 for ; Wed, 26 Mar 1997 14:03:14 -0800 (PST) Received: from amu5.cs.man.ac.uk by m1.cs.man.ac.uk (4.1/SMI-4.1:AL6) id AA17982; Wed, 26 Mar 97 22:03:10 GMT Received: from gort (annex1-32.mcc.ac.uk) by amu5.cs.man.ac.uk; Wed, 26 Mar 97 22:03:08 GMT Message-Id: <33399CAC.2F04E936@cs.man.ac.uk> Date: Wed, 26 Mar 1997 22:01:16 +0000 From: Dave Gilbert Organization: University of Manchester Computer Science Department X-Mailer: Mozilla 3.01 (X11; I; Linux 2.1.24 i586) Mime-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Re: AHA2940 bug(s) still exist References: <199703261925.WAA27096@sinbin.demos.su> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I don't know about 2.2.1; I'm still on a late 2.2-GAMMA for our server and it seems to be happy until something goes wrong. If the disc gives medium errors then sometimes it reboots rather than just logging them. I'm not sure but this might have been only when I turned on AWRE and ARRE (?). We've got a 2940UW with a 4GB Barracuda as sd0 and a Microp 9GB 1991 as sd1 (both Narrow non-ultra); as I'd previously said the 1991 had some media errors and thats when I hit the problem. Neither of the discs are critical discs to the FreeBSD box; I can imagine problems if they were the root discs (theyre not - theyre on an IDE) - they are exported via NFS. Another problem I've experienced which I'm not sure if its related to the SCSI code is that if I newfs a partition on the 9GB Microp its incredibly slow; and slows the machine to the point where it can't NFS serve. Also sometimes the act of newfs'ing a partition will cause the machine to hang solid part way through (last time with the IDE drive light on). There was nothing in the logs. Dave -- ----------- (Phone: 0161-275-3547) ------------------------ Man can not live - David Alan Gilbert - gilbertd@cs.man.ac.uk - G7FHJ@GB7BEV by bread alone. He ----------- (University of Manchester - AMULET Group) --H-- needs chocolate. - From owner-freebsd-scsi Wed Mar 26 14:22:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA03978 for freebsd-scsi-outgoing; Wed, 26 Mar 1997 14:22:34 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id OAA03963 for ; Wed, 26 Mar 1997 14:22:27 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA01416; Wed, 26 Mar 1997 23:22:19 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA11783; Wed, 26 Mar 1997 22:59:13 +0100 (MET) Message-ID: <19970326225913.DW37034@uriah.heep.sax.de> Date: Wed, 26 Mar 1997 22:59:13 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG Cc: rhooper@toybox.ottawa.on.ca (Roy M. Hooper) Subject: Re: AHA2940 bug(s) still exist in 2.2.1 References: <199703261843.LAA27920@pluto.plutotech.com> <199703261912.OAA18583@toybox.ottawa.on.ca> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703261912.OAA18583@toybox.ottawa.on.ca>; from Roy M. Hooper on Mar 26, 1997 14:12:31 -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Roy M. Hooper wrote: > > Can you hook up a serial console? > > I could, but I'd need to figure out how :) The switchbox to the dumbterm > has a free port. We also have a printer available. Hook it up to the sio0 port, @ 9600 Bd. The simplest way to get a serial console is typing -h at the Boot: prompt on the PC keyboard. There are a number of more automatic ways available if you want, but they all require that you install custom bootblocks (which is not a big deal however). -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Thu Mar 27 12:30:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id MAA19022 for freebsd-scsi-outgoing; Thu, 27 Mar 1997 12:30:35 -0800 (PST) Received: from caliban.dihelix.com (caliban.mrtc.org [199.4.33.251]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA19014; Thu, 27 Mar 1997 12:30:31 -0800 (PST) Received: (from langfod@localhost) by caliban.dihelix.com (8.8.5/8.8.3) id KAA06983; Thu, 27 Mar 1997 10:29:59 -1000 (HST) Message-Id: <199703272029.KAA06983@caliban.dihelix.com> Subject: Re: DLT exchanger In-Reply-To: <199703271913.LAA11872@lestat.nas.nasa.gov> from Jason Thorpe at "Mar 27, 97 11:13:18 am" To: thorpej@nas.nasa.gov Date: Thu, 27 Mar 1997 10:29:59 -1000 (HST) Cc: arman@bico.co.id, freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org From: "David Langford" X-blank-line: This space intentionaly left blank. X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Thu, 27 Mar 1997 23:30:19 +0700 (JVT) > Arman Hazairin Hasan wrote: > > > Does any body knows the SCSI control command for DLT exchanger. > > I want to write a script that control the 'arm' of DLT exchanger > > in order to move the cartridge from repository to it's drive. > >If you're using FreeBSD-current, I believe you can use the chio(1) >command if you have the "ch" driver in your kernel. (Can't say for >sure, since I don't run FreeBSD, but I think my driver was finally >committed :-) >Jason R. Thorpe thorpej@nas.nasa.gov Yes, it was!!! :) I never did publicy thank the FreeBSD team for doing this. So, if you guys are reading this THANK YOU!!!! The driver works well on the cheapo 4mm Archive/Seagate drive. The thing that took me awhile to realize was that you had to be very explicit with chio. You cannot tell it to move a tape into the drive and expect it to return the one it already has. Here is the stupid short write-up I did for someone: The thing to keep in mind is that the tape changer is a robot. Robots are dumb. Robots only do what you tell them to. Unlike Douglas Adams you cannot have tape and no-tape at the same time. You cannot hold two tapes in either the tape drive or the tape slot. When tape starts it holds all tapes in holders and none it the drive. Here is me moving tape from the third slot into the drive and back. Then I move tape in the first slot into the drive. Rule of thumb is: chio "from" "to" www /root% chio status picker 0: slot 0: slot 1: slot 2: slot 3: drive 0: www /root% chio move slot 3 drive 0 www /root% chio status picker 0: slot 0: slot 1: slot 2: slot 3: drive 0: www /root% chio move drive 0 slot 3 www /root% chio status picker 0: slot 0: slot 1: slot 2: slot 3: drive 0: www /root% chio move slot 0 drive 0 www /root% chio status picker 0: slot 0: slot 1: slot 2: slot 3: drive 0: -David Langford langfod@dihelix.com From owner-freebsd-scsi Thu Mar 27 13:16:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA23085 for freebsd-scsi-outgoing; Thu, 27 Mar 1997 13:16:09 -0800 (PST) Received: from apollo.shoreland.com (apollo.shoreland.com [207.67.24.135]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA23074 for ; Thu, 27 Mar 1997 13:16:05 -0800 (PST) Received: from lazarus (makinen@lazarus.shoreland.com [207.67.24.150]) by apollo.shoreland.com (8.8.5/8.7.3) with SMTP id PAA08951 for ; Thu, 27 Mar 1997 15:16:41 -0600 (CST) Message-ID: <333AE4DD.2F54C49A@shoreland.com> Date: Thu, 27 Mar 1997 15:21:33 -0600 From: Jeff Makinen Organization: Shoreland Inc. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.27 i586) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: [Fwd: Problems with Jaz drive.] Content-Type: message/rfc822 Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Message-ID: <333A9AF9.3F6AA884@shoreland.com> Date: Thu, 27 Mar 1997 10:06:17 -0600 From: Jeff Makinen Organization: Shoreland Inc. X-Mailer: Mozilla 3.01Gold (X11; I; Linux 2.0.27 i586) MIME-Version: 1.0 To: freebsd-questions@FreeBSD.ORG Subject: Problems with Jaz drive. Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit While trying to copy tar files to a IOMEGA Jaz drive the following messages occurred: Mar 26 22:00:44 apollo /kernel: ahc0:A:1: unknown scsi bus phase. Attempting to continue Mar 26 22:00:44 apollo last message repeated 6 times Mar 26 22:00:54 apollo /kernel: sd1(ahc0:1:0): imed out in message out phase, SCSISIGI == 0xa6 Mar 26 22:00:54 apollo /kernel: sd1(ahc0:1:0): asserted ATN - device reset in me ssage buffer Mar 26 22:00:56 apollo /kernel: sd1(ahc0:1:0): timed out in message out phase, SCSISIGI == 0xa6 Mar 26 22:00:56 apollo /kernel: ahc0: Issued Channel A Bus Reset #1. 3 SCBs aborted Mar 26 22:00:56 apollo /kernel: ahc0:A:0: refuses syncronous negotiation. Using asyncronous transfers Mar 26 22:00:56 apollo /kernel: sd0(ahc0:0:0): UNIT ATTENTION asc:29,2 Mar 26 22:00:56 apollo /kernel: , retries:3 Mar 26 22:01:06 apollo /kernel: sd1(ahc0:1:0): timed out in message out phase, SCSISIGI == 0xe6 Mar 26 22:01:06 apollo /kernel: sd0(ahc0:0:0): asserted ATN - device reset in message buffer Mar 26 22:01:06 apollo /kernel: ahc_intr: seqint, intstat == 0xd1, scsisigi = 0xb6 Mar 26 22:01:06 apollo /kernel: sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 Mar 26 22:01:06 apollo /kernel: sd1(ahc0:1:0): Power on, reset, or bus device reset occurred Now I get the following error messages: apollo:/var/log$ ls /jaz ls: /jaz: Input/output error apollo:/var/log$ umount /jaz umount: /dev/sd1c: Operation not permitted I am running Free BSD 2.1.6 with an Adaptec controller. The same setup worked fine 2 weeks ago. Any ideas ? Jeff Makinen makinen@execpc.com From owner-freebsd-scsi Thu Mar 27 13:20:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA23506 for freebsd-scsi-outgoing; Thu, 27 Mar 1997 13:20:22 -0800 (PST) Received: from lestat.nas.nasa.gov (lestat.nas.nasa.gov [129.99.50.29]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA23487; Thu, 27 Mar 1997 13:20:14 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by lestat.nas.nasa.gov (8.7.5/8.6.12) with SMTP id NAA14980; Thu, 27 Mar 1997 13:16:20 -0800 (PST) Message-Id: <199703272116.NAA14980@lestat.nas.nasa.gov> X-Authentication-Warning: lestat.nas.nasa.gov: Host localhost [127.0.0.1] didn't use HELO protocol To: "David Langford" Cc: arman@bico.co.id, freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: DLT exchanger Reply-To: Jason Thorpe From: Jason Thorpe Date: Thu, 27 Mar 1997 13:16:18 -0800 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 27 Mar 1997 10:29:59 -1000 (HST) "David Langford" wrote: > The driver works well on the cheapo 4mm Archive/Seagate drive. > The thing that took me awhile to realize was that you had to be very > explicit with chio. You cannot tell it to move a tape into the drive > and expect it to return the one it already has. ...right. This was a concious design decision, which I'll rationalize here: - the driver cannot reasonably keep the state of the changer apparatus; many changers also have front panel controls which may be used at any time by a human operator. - in the case of multiple free slots, who is to make the decision where the in-drive tape should be returned to? This decision is very hard to make, esp. if a human operator has mucked with the front panel controls. - the amount of state one has to keep around gets larger as you add more drives and pickers into the picture. (I've used this with a multi-drive, multi-picker apparatus under NetBSD.) The chio(1) program is meant to be a simple interface for use by scripts/command line. Jason R. Thorpe thorpej@nas.nasa.gov NASA Ames Research Center Home: 408.866.1912 NAS: M/S 258-6 Work: 415.604.0935 Moffett Field, CA 94035 Pager: 415.428.6939 From owner-freebsd-scsi Thu Mar 27 13:47:23 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA25961 for freebsd-scsi-outgoing; Thu, 27 Mar 1997 13:47:23 -0800 (PST) Received: from toybox.ottawa.on.ca (soldier.toybox.ottawa.on.ca [205.250.97.225]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA25944 for ; Thu, 27 Mar 1997 13:47:20 -0800 (PST) Received: (from rhooper@localhost) by toybox.ottawa.on.ca (8.7.4/8.7.3) id RAA23539 for freebsd-scsi@freebsd.org; Thu, 27 Mar 1997 17:03:39 -0500 From: "Roy M. Hooper" Message-Id: <199703272203.RAA23539@toybox.ottawa.on.ca> Subject: SCSI errors (aha2940) To: freebsd-scsi@freebsd.org Date: Thu, 27 Mar 1997 17:03:39 -0500 (EST) Content-Type: text Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here's the errors we got: sd2(ahc0:2:0) SCB 0x5 timed out while idle LASTPHASE=0x1 SCSISIGI=0x0 SEQADDR=0x7 sd2(ahc0:2:0) queuing an ABORT SCB sd2(ahc0:2:0) SCB 0x5.... SEQADDR=0x7 sd2(ahc:2:0) no longer in timeout ahc0 issued channel A bus reset ICCB aborted clearing bus reset [locked up] Sorry if the formatting isn't exactly like that that was produced -- this was written down for my by someone else. From owner-freebsd-scsi Thu Mar 27 13:51:27 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA26443 for freebsd-scsi-outgoing; Thu, 27 Mar 1997 13:51:27 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA26392; Thu, 27 Mar 1997 13:51:12 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id WAA13370; Thu, 27 Mar 1997 22:51:06 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id WAA18836; Thu, 27 Mar 1997 22:30:28 +0100 (MET) Message-ID: <19970327223027.OA35337@uriah.heep.sax.de> Date: Thu, 27 Mar 1997 22:30:27 +0100 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org Cc: langfod@dihelix.com (David Langford) Subject: Re: DLT exchanger References: <199703271913.LAA11872@lestat.nas.nasa.gov> <199703272029.KAA06983@caliban.dihelix.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199703272029.KAA06983@caliban.dihelix.com>; from David Langford on Mar 27, 1997 10:29:59 -1000 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As David Langford wrote: > >If you're using FreeBSD-current, I believe you can use the chio(1) > >command if you have the "ch" driver in your kernel. > Yes, it was!!! :) I never did publicy thank the FreeBSD team for doing this. > So, if you guys are reading this THANK YOU!!!! The thanks belong to Jason who's been submitting the driver. The only thing we FreeBSD folks did with it was leaving it in the GNATS queue for too long. ;-) I'm glad it works well for you, since i had to import it blindly, without ever having a chance to get my hands on a media changer device. Given that some things have been evolving still in FreeBSD since the time Jason submitted the driver, i still had to modify it quite a bit. Good to know it does its job. > Here is the stupid short write-up I did for someone: Can you please submit this to Peter da Silva, for inclusion into the FAQ, or even better, to the docs folks for the handbook? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Thu Mar 27 20:12:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA17649 for freebsd-scsi-outgoing; Thu, 27 Mar 1997 20:12:22 -0800 (PST) Received: from mail.webspan.net (mail.webspan.net [206.154.70.7]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA17626; Thu, 27 Mar 1997 20:12:12 -0800 (PST) Received: from orion.webspan.net (orion.webspan.net [206.154.70.5]) by mail.webspan.net (WEBSPAN/970116) with ESMTP id XAA14577; Thu, 27 Mar 1997 23:10:37 -0500 (EST) Received: from orion.webspan.net (localhost [127.0.0.1]) by orion.webspan.net (WEBSPN/970116) with ESMTP id XAA24221; Thu, 27 Mar 1997 23:10:36 -0500 (EST) To: Jason Thorpe cc: "David Langford" , arman@bico.co.id, freebsd-hackers@freebsd.org, freebsd-scsi@freebsd.org From: "Gary Palmer" Subject: Re: DLT exchanger In-reply-to: Your message of "Thu, 27 Mar 1997 13:16:18 PST." <199703272116.NAA14980@lestat.nas.nasa.gov> Date: Thu, 27 Mar 1997 23:10:36 -0500 Message-ID: <24219.859522236@orion.webspan.net> Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Jason Thorpe wrote in message ID <199703272116.NAA14980@lestat.nas.nasa.gov>: > The chio(1) program is meant to be a simple interface for use > by scripts/command line. On a related note (somewhat) does anyone have a script to interface Amanda to chio(1)? I'd rather not re-invent the wheel :) Thanks, Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info From owner-freebsd-scsi Fri Mar 28 02:09:34 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA01574 for freebsd-scsi-outgoing; Fri, 28 Mar 1997 02:09:34 -0800 (PST) Received: from ami.tom.computerworks.net (root@AMI.RES.CMU.EDU [128.2.95.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id CAA01559 for ; Fri, 28 Mar 1997 02:09:31 -0800 (PST) Received: from bonkers.taronga.com by ami.tom.computerworks.net with smtp (Smail3.1.29.1 #1) id m0wAYau-0021WdC; Fri, 28 Mar 97 05:09 EST Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id EAA02054; Fri, 28 Mar 1997 04:10:48 -0600 Date: Fri, 28 Mar 1997 04:10:48 -0600 From: peter@taronga.com (Peter da Silva) Message-Id: <199703281010.EAA02054@bonkers.taronga.com> To: scsi@freebsd.org Subject: Re: DLT exchanger Newsgroups: taronga.freebsd.scsi In-Reply-To: <19970327223027.OA35337@uriah.heep.sax.de> References: <199703271913.LAA11872@lestat.nas.nasa.gov> <199703272029.KAA06983@caliban.dihelix.com>,<199703272029.KAA06983@caliban.dihelix.com> Organization: none Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In article <19970327223027.OA35337@uriah.heep.sax.de>, J Wunsch wrote: >Can you please submit this to Peter da Silva, for inclusion into the >FAQ, or even better, to the docs folks for the handbook? I already grabbed the entry into my faq-incoming folder. But, yes, if you have an answer for something like this by all means send it to me. From owner-freebsd-scsi Fri Mar 28 07:04:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA13381 for freebsd-scsi-outgoing; Fri, 28 Mar 1997 07:04:56 -0800 (PST) Received: from mailhost.pi.net (root@mailhost.pi.net [145.220.3.9]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA13376 for ; Fri, 28 Mar 1997 07:04:48 -0800 (PST) Received: from kinchenna (ppp16.home.cs.vu.nl [130.37.18.16]) by mailhost.pi.net (8.8.3/8.7.1) with SMTP id QAA28457 for ; Fri, 28 Mar 1997 16:04:27 +0100 (MET) Posted-Date: Fri, 28 Mar 1997 16:04:27 +0100 (MET) Date: Fri, 28 Mar 97 16:03:54 Romance Standard Time From: Guido Kollerie Subject: Status of CAM To: freebsd-scsi@freebsd.org X-Mailer: Chameleon ATX 6.0, Standards Based IntraNet Solutions, NetManage Inc. X-Priority: 3 (Normal) References: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I was wondering what the status of the implementation of CAM is and which of currently available SCSI drivers are being modified/rewritten to adher to the CAM specs? -- Guido Kollerie Never underestimate the bandwith of a station wagon full of tapes hurling down the highway - Andrew S. Tanenbaum From owner-freebsd-scsi Fri Mar 28 08:41:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA19519 for freebsd-scsi-outgoing; Fri, 28 Mar 1997 08:41:18 -0800 (PST) Received: from robkaos.ruhr.de (robkaos.ruhr.de [141.39.227.87]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA19505 for ; Fri, 28 Mar 1997 08:41:14 -0800 (PST) Received: by robkaos.ruhr.de (/\oo/\ Smail3.1.29.1 #29.1) id ; Fri, 28 Mar 97 17:40 MET Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: Re: CD-R audio problem In-Reply-To: <199703260743.IAA14604@blasuarr.cs.tu-berlin.de> from Udo Wolter at "Mar 26, 97 08:42:57 am" To: freebsd-scsi@freebsd.org Date: Fri, 28 Mar 1997 17:40:45 +0100 (MET) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > Has anyone burned an audio cd successfully? If yes, how? > > > > BTW, the SCSI HA is a SC-200 (on a P6NP5 motherboard). > > Could it be that there is a problem with byte-order ? I can remember that > my philips can use intel-byte-order and vice versa, you have to tell it > what you want to use. If you used non-intel byte order on the CD you surely > will only get garbage...:-( > This was exactly the error! I piped the read audio data trough 'dd conv=swab'. That helped! Thanks once more. Robert From owner-freebsd-scsi Sat Mar 29 07:12:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA29753 for freebsd-scsi-outgoing; Sat, 29 Mar 1997 07:12:06 -0800 (PST) Received: from toybox.ottawa.on.ca (soldier.toybox.ottawa.on.ca [205.250.97.225]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA29748 for ; Sat, 29 Mar 1997 07:12:02 -0800 (PST) Received: (from rhooper@localhost) by toybox.ottawa.on.ca (8.7.4/8.7.3) id KAA02613 for freebsd-scsi@freebsd.org; Sat, 29 Mar 1997 10:27:01 -0500 From: "Roy M. Hooper" Message-Id: <199703291527.KAA02613@toybox.ottawa.on.ca> Subject: AHA2940/3940 troubles To: freebsd-scsi@freebsd.org Date: Sat, 29 Mar 1997 10:27:00 -0500 (EST) Content-Type: text Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk No matter what i've tried: - switching the AHA2940s with a AHA3940 - adding all the AHC_ opptions - ugprading to 2.2.1 - etc. I just can't make the FreeBSD box stay up. It almost always goes down on some SCSI driver error and comes back up, but occasionally just locks up and stays locked. This unstability is getting to the point where we will need to scrap FreeBSD and try other operating systems, as much as we do not want to. Any help not covered above would help alot. From owner-freebsd-scsi Sat Mar 29 09:27:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA03603 for freebsd-scsi-outgoing; Sat, 29 Mar 1997 09:27:33 -0800 (PST) Received: from seine.cs.umd.edu (seine.cs.umd.edu [128.8.128.59]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA03596 for ; Sat, 29 Mar 1997 09:27:31 -0800 (PST) Received: by seine.cs.umd.edu (8.8.5/UMIACS-0.9/04-05-88) id MAA07478; Sat, 29 Mar 1997 12:27:29 -0500 (EST) Message-Id: <199703291727.MAA07478@seine.cs.umd.edu> To: scsi@freebsd.org Cc: rohit@cs.umd.edu Subject: Re: AHA2940 bug(s) still exist in 2.2.1 Date: Sat, 29 Mar 1997 12:27:28 -0500 From: Rohit Dube Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I had posted the following to hardware earlier. Am reposting this to scsi with some minor edits in the hope that it may help give the developers some additional clues. --> I am seeing some weird problems with a couple of machines running 2.2-970225-GAMMA Everynight when we run amanda's 'amdump', these machines crash. The crash can also be triggered by a 'dump' to /dev/null or a 'dd'. (Not entirely deterministic but all 3 crash the machines most of the time). We tried 2.1.5, 2.1.7, 2.2-961006-SNAP, 2.2.1 which exhibit the same behaviour. We have the following hardware on the machines which are crashing - (curtailed dmesg output showing only the PCI devices) Probing for devices on PCI bus 0: chip0 rev 3 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 0 int a irq 12 on pci0:9 de0 rev 32 int a irq 10 on pci0:11 de0: SMC 9332BDT 21140A [10-100Mb/s] pass 2.0 de0: address 00:00:c0:03:6b:f9 ahc0 rev 0 int a irq 11 on pci0:12 ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "MICROP 4421-07 0329SJ 0329" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2047MB (4193360 512 byte sectors) (ahc0:6:0): "SONY CD-ROM CDU-76S 1.2d" type 5 removable SCSI 2 cd0(ahc0:6:0): CD-ROM cd present [400000 x 2048 byte records] The console shows the following error messages (which are not logged as the disk is inacessible): sd0(ahc0:0:0): no longer in timeout ahc0: Issued Channel A Bus Reset: 2SCBs aborted Clearing bus reset Clearing 'in-reset' flag Sd0(ahc0:0:0): SCB 0x1 - timed out while idle LASTPHASE == 0x1, SCSIISGI = 0x0 SEQADDR == 0x12 The above message repeats with different values for SEQADDR. The first message which gets printed out says something like 'timed out in command phase'. I can't paraphrase it here as it happened in the middle of the night and scrolled off. After resetting following this occurance, the disk is not visible even to the Adaptec probe on boot-up. We must power-cycle. The block position where the error is triggered varies, by the way. Has somebody else seen a problem like this before? Or would otherwise know what is going on here? Any help greatly appreciated! Just can't afford to have these machines go down every night while doing a backup!! Thanks. --rohit. PS: I am attaching the output of 'scsi -f /dev/rsd0 -m1' and 'df' here, if that is of any use in tracking this problem. #scsi -f /dev/rsd0 -m1 AWRE (Auto Write Reallocation Enbld): 1 ARRE (Auto Read Reallocation Enbld): 1 TB (Transfer Block): 0 RC (Read Continuous): 0 EER (Enable Early Recovery): 0 PER (Post Error): 0 DTE (Disable Transfer on Error): 0 DCR (Disable Correction): 0 Read Retry Count: 14 Correction Span: 28 Head Offset Count: 0 Data Strobe Offset Count: 0 Write Retry Count: 15 Recovery Time Limit: 0 # df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd0a 47183 13098 30311 30% / /dev/sd0s1f 1822738 504147 1172772 30% /usr /dev/sd0s1e 98479 1372 89229 2% /var procfs 4 4 0 100% /proc amd:96 0 0 0 100% /fs <-- From owner-freebsd-scsi Sat Mar 29 10:37:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA06063 for freebsd-scsi-outgoing; Sat, 29 Mar 1997 10:37:33 -0800 (PST) Received: from weenix.guru.org (kmitch@phantasma.bevc.blacksburg.va.us [198.82.200.65]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA06055 for ; Sat, 29 Mar 1997 10:37:31 -0800 (PST) Received: (from kmitch@localhost) by weenix.guru.org (8.8.5/8.8.5) id NAA18674; Sat, 29 Mar 1997 13:37:28 -0500 (EST) Date: Sat, 29 Mar 1997 13:37:28 -0500 (EST) From: Keith Mitchell Message-Id: <199703291837.NAA18674@weenix.guru.org> To: rohit@cs.umd.edu (Rohit Dube) CC: scsi@freebsd.org Subject: Re: AHA2940 bug(s) still exist in 2.2.1 Newsgroups: local.freebsd.scsi In-Reply-To: X-Newsreader: TIN [UNIX 1.3 unoff BETA release 970124] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > ahc0 rev 0 int a irq 11 on pci0:12 > ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs > ahc0 waiting for scsi devices to settle > (ahc0:0:0): "MICROP 4421-07 0329SJ 0329" type 0 fixed SCSI 2 > sd0(ahc0:0:0): Direct-Access 2047MB (4193360 512 byte sectors) Have you tried turning off TAGged command queuing (AHC_TAGENABLE)?? I have a 3940UW with a Microp 4221W and I get similar results. Everything seems ok without tagged command queueing. -- Keith Mitchell Head Administrator: acm.vt.edu Email: kmitch@weenix.guru.org PGP key available upon request http://weenix.guru.org/~kmitch Address and URL (c) 1997 Keith Mitchell - All Rights Reserverd Unauthorized use or duplication prohibited From owner-freebsd-scsi Sat Mar 29 14:17:16 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA16638 for freebsd-scsi-outgoing; Sat, 29 Mar 1997 14:17:16 -0800 (PST) Received: from darling.cs.umd.edu (darling.cs.umd.edu [128.8.128.115]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA16631 for ; Sat, 29 Mar 1997 14:17:12 -0800 (PST) Received: by darling.cs.umd.edu (8.8.5/UMIACS-0.9/04-05-88) id RAA11285; Sat, 29 Mar 1997 17:16:32 -0500 (EST) Message-Id: <199703292216.RAA11285@darling.cs.umd.edu> To: Keith Mitchell cc: rohit@cs.umd.edu (Rohit Dube), scsi@freebsd.org Subject: Re: AHA2940 bug(s) still exist in 2.2.1 In-reply-to: Your message of "Sat, 29 Mar 1997 13:37:28 EST." <199703291837.NAA18674@weenix.guru.org> Date: Sat, 29 Mar 1997 17:16:31 -0500 From: Rohit Dube Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 29 Mar 1997 13:37:28 -0500 (EST) kmitch@weenix.guru.org writes: =>> ahc0 rev 0 int a irq 11 on pci0:12 =>> ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs =>> ahc0 waiting for scsi devices to settle =>> (ahc0:0:0): "MICROP 4421-07 0329SJ 0329" type 0 fixed SCSI 2 =>> sd0(ahc0:0:0): Direct-Access 2047MB (4193360 512 byte sectors) => =>Have you tried turning off TAGged command queuing (AHC_TAGENABLE)?? => =>I have a 3940UW with a Microp 4221W and I get similar results. Everything =>seems ok without tagged command queueing. Yup. Tagged queuing was turned off. We had problems with the same model Controller and Quantum Atlas disks with Tag queuing enabled. Without this option, the Quantums seem to work fine, but this has no effect on the Micropolis disks which continue to crash. --rohit. From owner-freebsd-scsi Sat Mar 29 15:34:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA20884 for freebsd-scsi-outgoing; Sat, 29 Mar 1997 15:34:51 -0800 (PST) Received: from sand.sentex.ca (sand.sentex.ca [206.222.77.6]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA20879 for ; Sat, 29 Mar 1997 15:34:45 -0800 (PST) Received: from gravel (gravel.sentex.ca [205.211.165.210]) by sand.sentex.ca (8.8.5/8.8.3) with SMTP id SAA16090; Sat, 29 Mar 1997 18:37:24 -0500 (EST) Message-Id: <3.0.1.32.19970329182127.00a95310@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Sat, 29 Mar 1997 18:21:27 -0500 To: Rohit Dube , scsi@freebsd.org From: Mike Tancsa Subject: Re: AHA2940 bug(s) still exist in 2.2.1 In-Reply-To: <199703291727.MAA07478@seine.cs.umd.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 12:27 PM 3/29/97 -0500, Rohit Dube wrote: >After resetting following this occurance, the disk is not visible even to >the Adaptec probe on boot-up. We must power-cycle. Its just a shot in the dark, but I have found that with the 2940U's, "ENABLE PLUG & PLAY SCAM SUPPORT" turned on in the card's BIOS, seems to help this problem out... I dont know if it will help your other problems, but I have found it to resolve the issue with the Adeptec BIOS not seeing the drives after a warm reboot. ---Mike ********************************************************************** Mike Tancsa (mike@sentex.net) * To do is to be -- Nietzsche Sentex Communications Corp, * To be is to do -- Sartre Cambridge, Ontario * Do be do be do -- Sinatra (http://www.sentex.net/~mdtancsa) * From owner-freebsd-scsi Sat Mar 29 20:34:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id UAA05958 for freebsd-scsi-outgoing; Sat, 29 Mar 1997 20:34:55 -0800 (PST) Received: from pahtoh.cwu.edu (root@pahtoh.cwu.edu [198.104.65.27]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA05872 for ; Sat, 29 Mar 1997 20:34:47 -0800 (PST) Received: from opus.cts.cwu.edu (skynyrd@opus.cts.cwu.edu [198.104.92.71]) by pahtoh.cwu.edu (8.8.5/8.8.5) with ESMTP id UAA01054; Sat, 29 Mar 1997 20:31:25 -0800 (PST) Received: from localhost (skynyrd@localhost) by opus.cts.cwu.edu (8.8.5/8.8.5) with SMTP id UAA21033; Sat, 29 Mar 1997 20:31:23 -0800 (PST) Date: Sat, 29 Mar 1997 20:31:23 -0800 (PST) From: Chris Timmons To: "Roy M. Hooper" cc: freebsd-scsi@freebsd.org Subject: Re: AHA2940/3940 troubles In-Reply-To: <199703291527.KAA02613@toybox.ottawa.on.ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Roy! I sense that you are getting a little bit frustrated :) If it is any small consolation, I have over 40 gigabytes of storage across 5 machines running the RELENG_ branches of 2_1_0 and 2_2, including a reasonably busy news server as well as cvsup.freebsd.org; all on aha3940W and 2940 controllers and all with no problem. My point is not to make you more frustrated, but to let you know that this stuff normally works really really really well. Now then, you don't mention what kind of hardware you have, but if your disks are not major-label (eg. Seagate, Quantum) you might want to disable tagged command queueing. MEMIO has never worked for me on P5 motherboards from asus, either - producing random lockups and crashes. If you do have major-label drives, is your firmware up-to-date? What kinds of cables are you using? I pay the extra money for adaptec cables with active terminators, and remove all drive termination. What about BIOS settings for the PCI bus? If you have an old MB conceivably there could be problems here. Are you seeing any other problems, like processes randomly exiting on signal 11 or 12? Perhaps your memory timing in BIOS is too aggressive? What about your setup values in the Adaptec setup? You might search this mailing list via the www interface (www.freebsd.org) and look for postings from Justin Gibbs. Hope this helps, -Chris On Sat, 29 Mar 1997, Roy M. Hooper wrote: > > No matter what i've tried: > - switching the AHA2940s with a AHA3940 > - adding all the AHC_ opptions > - ugprading to 2.2.1 > - etc. > > I just can't make the FreeBSD box stay up. It almost always goes down on > some SCSI driver error and comes back up, but occasionally just locks up > and stays locked. > > This unstability is getting to the point where we will need to scrap FreeBSD > and try other operating systems, as much as we do not want to. > > Any help not covered above would help alot. >