From owner-freebsd-scsi Sun May 6 2:20: 6 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 8A62737B422 for ; Sun, 6 May 2001 02:20:03 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id LAA23711; Sun, 6 May 2001 11:20:02 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f4698Y407800; Sun, 6 May 2001 11:08:34 +0200 (MET DST) (envelope-from j) Date: Sun, 6 May 2001 11:08:34 +0200 (MET DST) Message-Id: <200105060908.f4698Y407800@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <001d01c0d571$09711300$0404a8c0@smalweer.nl> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Recovered data with positive head offset field replaceable unit msg X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Cc: "Ron Klinkien" Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Ron Klinkien" wrote: > The SCSI drive is not that old btw, it even has an SCA80 connector, > it's an hot swappable disk that SUN uses in it's E450 machines for > example. I'd take it as an indication of good firmware. You're getting an advance warning, so even if the drive doesn't fail immediately, you know that it might fail some day, and can arrange for it (like keeping a spare one around, or retiring it for non mission-critical data). -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 6 2:20:10 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id F2F2037B422 for ; Sun, 6 May 2001 02:20:06 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id LAA23713 for freebsd-scsi@freebsd.org; Sun, 6 May 2001 11:20:06 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f469CnU07813; Sun, 6 May 2001 11:12:49 +0200 (MET DST) (envelope-from j) Date: Sun, 6 May 2001 11:12:49 +0200 (MET DST) Message-Id: <200105060912.f469CnU07813@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <20010426110542.A50185@uriah.heep.sax.de> <200104261435.f3QEZLs23573@aslan.scsiguy.com> <20010426190714.E50185@uriah.heep.sax.de> <20010428231227.A37369@panzer.kdm.org> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Another problem with the new CAM error handling X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" wrote: > Since SF_RETRY_UA isn't set on normal I/O for the pt(4) driver unless a > bus reset or BDR has been sent, unit attentions are not being retried. > > The attached patch should fix your problem. I finally got an opportunity to reboot and thus take the new kernel into action -- my system panicked yesterday. :-/ So yes, the problem with the pt(4) driver going mad on a power-on UA is gone, except that it still prints out a message even in the !bootverbose case: (pt0:sym1:0:5:0): SEND(06). CDB: a 0 0 0 2 0 (pt0:sym1:0:5:0): CAM Status: SCSI Status Error (pt0:sym1:0:5:0): SCSI Status: Check Condition (pt0:sym1:0:5:0): UNIT ATTENTION (pt0:sym1:0:5:0): Retrying Command For me it's minor, and i can ignore it, but based on experience with our user base, i know this kind of message makes some people nervous... (in particular in countries like here, where the people's knowledge of English is not always that ideal). -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 6 2:20:16 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 65F0C37B424; Sun, 6 May 2001 02:20:09 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id LAA23715; Sun, 6 May 2001 11:20:08 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f469JrT07865; Sun, 6 May 2001 11:19:53 +0200 (MET DST) (envelope-from j) Date: Sun, 6 May 2001 11:19:53 +0200 (MET DST) Message-Id: <200105060919.f469JrT07865@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: freebsd-scsi@freebsd.org Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <15083.9059.887489.356984@ultrahot.Finland.Sun.COM> <20010428224047.A37268@panzer.kdm.org> <15083.65379.523173.371122@ultrahot.Finland.Sun.COM> <20010430101214.A46826@panzer.kdm.org> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: camcontrol stop / restart broken X-Original-Newsgroups: local.freebsd.current To: freebsd-current@freebsd.org, freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [F'up changed to freebsd-scsi] "Kenneth D. Merry" wrote: > This should be fixed as of rev 1.22 of scsi_all.c. There was an errant > search and replace that caused the 'start' bit in the start/stop unit to > always be set to 0 (stop). So automatic spinups wouldn't work, and > 'camcontrol start' wouldn't work. I've got: uriah # cvs stat /sys/cam/scsi/scsi_all.c =================================================================== File: scsi_all.c Status: Up-to-date Working revision: 1.24 Result of merge Repository revision: 1.24 /home/ncvs/src/sys/cam/scsi/scsi_all.c,v Sticky Tag: (none) Sticky Date: (none) Sticky Options: (none) ....and still have the problem that the "camcontrol start" doesn't work. It returns immediately to the caller, claiming a "unit started successfully", while the drive hasn't started at all. Issuing a "camcontrol command daX -c '1b 0 0 0 1 0'" works. I didn't try whether the kernel-implied startup on disk access would work, though, since it would IMHO risk a hanging kernel and controller timeout. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 6 6:35:34 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from hamilton.th.physik.uni-bonn.de (hamilton.th.physik.uni-bonn.de [131.220.162.85]) by hub.freebsd.org (Postfix) with ESMTP id 72C2937B423 for ; Sun, 6 May 2001 06:35:31 -0700 (PDT) (envelope-from conrad@th.physik.uni-bonn.de) Received: from merlin.th.physik.uni-bonn.de (merlin.th.physik.uni-bonn.de [131.220.161.121]) by hamilton.th.physik.uni-bonn.de (Postfix) with ESMTP id 6C9445D0E for ; Sun, 6 May 2001 15:35:30 +0200 (CEST) Received: by merlin.th.physik.uni-bonn.de (Postfix, from userid 145) id 0D1843640E; Sun, 6 May 2001 15:35:29 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by merlin.th.physik.uni-bonn.de (Postfix) with ESMTP id F2B7A3260E for ; Sun, 6 May 2001 15:35:29 +0200 (CEST) Date: Sun, 6 May 2001 15:35:29 +0200 (CEST) From: Jan Conrad To: Subject: Write Cacheing on SCSI controllers? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I am setting up a new file server right now so I have some time to play around setting WCE on or off. To my surprise it did'nt matter that much! Just dd'ing 400MB of zeros to the disc gives me about 32MB/s, (nearly) no matter how WCE is set. (29160, IBM DDYS-T18350N) (softupdates on/off does'nt matter that much either...) This is in sharp contrast to ATA disks, where the write throughput drops by a factor of 3 when disabling WC. Is it possible that the SCSI controller does the write cacheing, compensating for the drive not doing it? regards Jan -- Physikalisches Institut der Universitaet Bonn Nussallee 12 D-53115 Bonn GERMANY To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 6 8:20: 8 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id A46A637B422 for ; Sun, 6 May 2001 08:20:04 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id RAA15899 for freebsd-scsi@freebsd.org; Sun, 6 May 2001 17:20:03 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f46ErfL08783; Sun, 6 May 2001 16:53:41 +0200 (MET DST) (envelope-from j) Date: Sun, 6 May 2001 16:53:41 +0200 (MET DST) Message-Id: <200105061453.f46ErfL08783@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Write Cacheing on SCSI controllers? X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jan Conrad wrote: > Is it possible that the SCSI controller does the write cacheing, > compensating for the drive not doing it? Nope, but i'd assume that is due to tagged command queuing. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 6 10:52:50 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 3652C37B423; Sun, 6 May 2001 10:52:45 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA94785; Sun, 6 May 2001 11:52:44 -0600 (MDT) (envelope-from ken) Date: Sun, 6 May 2001 11:52:44 -0600 From: "Kenneth D. Merry" To: freebsd-scsi@FreeBSD.ORG Cc: freebsd-current@FreeBSD.ORG Subject: Re: camcontrol stop / restart broken Message-ID: <20010506115244.A94763@panzer.kdm.org> References: <15083.9059.887489.356984@ultrahot.Finland.Sun.COM> <20010428224047.A37268@panzer.kdm.org> <15083.65379.523173.371122@ultrahot.Finland.Sun.COM> <20010430101214.A46826@panzer.kdm.org> <200105060919.f469JrT07865@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200105060919.f469JrT07865@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Sun, May 06, 2001 at 11:19:53AM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, May 06, 2001 at 11:19:53 +0200, J Wunsch wrote: > [F'up changed to freebsd-scsi] > > "Kenneth D. Merry" wrote: > > > This should be fixed as of rev 1.22 of scsi_all.c. There was an errant > > search and replace that caused the 'start' bit in the start/stop unit to > > always be set to 0 (stop). So automatic spinups wouldn't work, and > > 'camcontrol start' wouldn't work. > > I've got: > > uriah # cvs stat /sys/cam/scsi/scsi_all.c > =================================================================== > File: scsi_all.c Status: Up-to-date > > Working revision: 1.24 Result of merge > Repository revision: 1.24 /home/ncvs/src/sys/cam/scsi/scsi_all.c,v > Sticky Tag: (none) > Sticky Date: (none) > Sticky Options: (none) > > ....and still have the problem that the "camcontrol start" doesn't > work. It returns immediately to the caller, claiming a "unit started > successfully", while the drive hasn't started at all. camcontrol uses scsi_start_stop() to build the start unit CDB. scsi_start_stop() is in libcam, which compiles a number of kernel files in userland. (including scsi_all.c) So you need to rebuild world to fix camcontrol. > Issuing a "camcontrol command daX -c '1b 0 0 0 1 0'" works. That bypasses the CDB builder function (scsi_start_stop()), so I would expect it to work. > I didn't try whether the kernel-implied startup on disk access would > work, though, since it would IMHO risk a hanging kernel and controller > timeout. That should work now. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 6 10:57:27 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 1451B37B424 for ; Sun, 6 May 2001 10:57:22 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA94821; Sun, 6 May 2001 11:57:18 -0600 (MDT) (envelope-from ken) Date: Sun, 6 May 2001 11:57:18 -0600 From: "Kenneth D. Merry" To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Another problem with the new CAM error handling Message-ID: <20010506115718.B94763@panzer.kdm.org> References: <20010426110542.A50185@uriah.heep.sax.de> <200104261435.f3QEZLs23573@aslan.scsiguy.com> <20010426190714.E50185@uriah.heep.sax.de> <20010428231227.A37369@panzer.kdm.org> <200105060912.f469CnU07813@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200105060912.f469CnU07813@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Sun, May 06, 2001 at 11:12:49AM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, May 06, 2001 at 11:12:49 +0200, J Wunsch wrote: > "Kenneth D. Merry" wrote: > > > Since SF_RETRY_UA isn't set on normal I/O for the pt(4) driver unless a > > bus reset or BDR has been sent, unit attentions are not being retried. > > > > The attached patch should fix your problem. > > I finally got an opportunity to reboot and thus take the new kernel > into action -- my system panicked yesterday. :-/ > > So yes, the problem with the pt(4) driver going mad on a power-on UA > is gone, except that it still prints out a message even in the > !bootverbose case: > > (pt0:sym1:0:5:0): SEND(06). CDB: a 0 0 0 2 0 > (pt0:sym1:0:5:0): CAM Status: SCSI Status Error > (pt0:sym1:0:5:0): SCSI Status: Check Condition > (pt0:sym1:0:5:0): UNIT ATTENTION > (pt0:sym1:0:5:0): Retrying Command > > For me it's minor, and i can ignore it, but based on experience with > our user base, i know this kind of message makes some people > nervous... (in particular in countries like here, where the people's > knowledge of English is not always that ideal). It's debateable whether we should print errors that get retried. At least it says "retrying command". It is an exceptional condition, though. We expect unit attentions on boot, and after a bus reset, but not in the course of normal operation. So it's probably good to notify the user, in case they didn't know someone powered their device off and back on again. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 6 11: 6:19 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id D694D37B424 for ; Sun, 6 May 2001 11:06:15 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA94877; Sun, 6 May 2001 12:06:11 -0600 (MDT) (envelope-from ken) Date: Sun, 6 May 2001 12:06:11 -0600 From: "Kenneth D. Merry" To: Jan Conrad Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Write Cacheing on SCSI controllers? Message-ID: <20010506120611.C94763@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from conrad@th.physik.uni-bonn.de on Sun, May 06, 2001 at 03:35:29PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, May 06, 2001 at 15:35:29 +0200, Jan Conrad wrote: > Hi, > > I am setting up a new file server right now so I have some time to play > around setting WCE on or off. > > To my surprise it did'nt matter that much! Just dd'ing 400MB of zeros to > the disc gives me about 32MB/s, (nearly) no matter how WCE is set. > (29160, IBM DDYS-T18350N) (softupdates on/off does'nt matter that much > either...) > > This is in sharp contrast to ATA disks, where the write throughput drops > by a factor of 3 when disabling WC. > > Is it possible that the SCSI controller does the write cacheing, > compensating for the drive not doing it? I don't know of any modern SCSI controllers that do caching. The 29160 definitely doesn't cache. (RAID controllers are another story.) So no, the controller isn't doing it. As Joerg pointed out, what you're probably seeing is the effect of tagged queueing. With SCSI, (and with some ATA drives), tagged queueing gives you the ability to queue a whole bunch of commands to the disk and then wait for completion. Without tagged queueing (often the case with ATA), you can only issue one command to the disk and then you have to wait for completion. If you've got write caching turned on, though, the disk can acknowledge the command immediately, even though it hasn't been committed to disk. So the time between writes goes down and you're better able to saturate the disk. If you want to see a difference in performance with a SCSI disk with and without write caching, try a whole bunch of random I/O. (newfs used to be a good test, although that may have been fixed recently.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 6 11:12:28 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id E1C7A37B422 for ; Sun, 6 May 2001 11:12:23 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA94930; Sun, 6 May 2001 12:12:21 -0600 (MDT) (envelope-from ken) Date: Sun, 6 May 2001 12:12:20 -0600 From: "Kenneth D. Merry" To: Jan Conrad Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Write Cacheing on SCSI controllers? Message-ID: <20010506121220.A94905@panzer.kdm.org> References: <20010506120611.C94763@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010506120611.C94763@panzer.kdm.org>; from ken@kdm.org on Sun, May 06, 2001 at 12:06:11PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, May 06, 2001 at 12:06:11 -0600, Kenneth D. Merry wrote: > On Sun, May 06, 2001 at 15:35:29 +0200, Jan Conrad wrote: > > Hi, > > > > I am setting up a new file server right now so I have some time to play > > around setting WCE on or off. > > > > To my surprise it did'nt matter that much! Just dd'ing 400MB of zeros to > > the disc gives me about 32MB/s, (nearly) no matter how WCE is set. > > (29160, IBM DDYS-T18350N) (softupdates on/off does'nt matter that much > > either...) > > > > This is in sharp contrast to ATA disks, where the write throughput drops > > by a factor of 3 when disabling WC. > > > > Is it possible that the SCSI controller does the write cacheing, > > compensating for the drive not doing it? > > I don't know of any modern SCSI controllers that do caching. The 29160 > definitely doesn't cache. (RAID controllers are another story.) So no, > the controller isn't doing it. > > As Joerg pointed out, what you're probably seeing is the effect of tagged > queueing. With SCSI, (and with some ATA drives), tagged queueing gives you > the ability to queue a whole bunch of commands to the disk and then wait > for completion. > > Without tagged queueing (often the case with ATA), you can only issue one > command to the disk and then you have to wait for completion. If you've > got write caching turned on, though, the disk can acknowledge the command > immediately, even though it hasn't been committed to disk. So the time > between writes goes down and you're better able to saturate the disk. > > If you want to see a difference in performance with a SCSI disk with and > without write caching, try a whole bunch of random I/O. (newfs used to be > a good test, although that may have been fixed recently.) One thing I should point out is that newfs runs through the raw device, so it issues one command at a time. Therefore the lower latency you get with write caching enabled translates into increased performance. If you're using the filesystem, though, you can queue more than one transaction to the disk at a time, so the effect of write caching might not be as noticeable. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 6 12:13:19 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from syzyf.ids.gda.pl (syzyf.ids.gda.pl [153.19.20.10]) by hub.freebsd.org (Postfix) with ESMTP id 1567937B422; Sun, 6 May 2001 12:13:14 -0700 (PDT) (envelope-from jacol@ids.gda.pl) Received: from ids.gda.pl (jacol@kaliope01.ids.gda.pl [153.19.20.17]) by syzyf.ids.gda.pl (8.9.3/8.9.1) with ESMTP id f46JD5p11304; Sun, 6 May 2001 21:13:06 +0200 Message-ID: <3AF5A2D9.22DCE7BA@ids.gda.pl> Date: Sun, 06 May 2001 21:15:37 +0200 From: Jacek =?iso-8859-2?Q?J=EAdrzejczak?= Reply-To: jacol@ids.gda.pl X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.4.3 i686) X-Accept-Language: pl, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org, freebsd-stable@freebsd.org Subject: mylex dac960pl and FreeBSD 4.3 - bus_dmamap_load Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm trying to install FreeBSD 4.3 on an old HP NetServer LH Plus server, with Mylex DAC960PL (2.73-0-00 firmware, 4MB) card, with no luck. mlx0: DAC96PL, 2 channels, firmware 2.73-0-00, 4MB mlxd0: on mlx0 mlxd0: 20335MB (41646080 sectors) RAID 5 (online) No matter which installation process i choose (floppies - kern.flp & mfsroot.flp or bootable cd) i always get this error message: bus_dmamap_load: Too many segs! buf_len = 0xaa0 mlx0: I/O error - attempt to write beyond end of drive The strange thing is that i was able to install FreeBSD 4.2 with no problem at all. Installation went smoothly and 4.2 was running just fine. Any thoughts/comments/solutions ? Thanks in advance, Jacol. ---------------------------------------------------------------------------- Jacek Jedrzejczak e-mail: jacol@ids.gda.pl -----------------[ It takes a good man to admit a mistake ]----------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 6 13:49:38 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from femail1.rdc1.on.home.com (femail1.rdc1.on.home.com [24.2.9.88]) by hub.freebsd.org (Postfix) with ESMTP id 0CB1937B422; Sun, 6 May 2001 13:49:35 -0700 (PDT) (envelope-from pnmurphy1@home.com) Received: from home.com ([24.150.36.162]) by femail1.rdc1.on.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010506204749.JAPB20469.femail1.rdc1.on.home.com@home.com>; Sun, 6 May 2001 13:47:49 -0700 Message-ID: <3AF5B8C2.9020306@home.com> Date: Sun, 06 May 2001 16:49:06 -0400 From: Paul Murphy User-Agent: Mozilla/5.0 (X11; U; FreeBSD 4.3-STABLE i386; en-US; 0.8.1) Gecko/20010425 X-Accept-Language: en MIME-Version: 1.0 To: jacol@ids.gda.pl Cc: freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG, pnmurphy1@home.com Subject: Re: mylex dac960pl and FreeBSD 4.3 - bus_dmamap_load References: <3AF5A2D9.22DCE7BA@ids.gda.pl> Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jacek Jędrzejczak wrote: > > mlx0: DAC96PL, 2 channels, firmware 2.73-0-00, 4MB > mlxd0: on mlx0 > mlxd0: 20335MB (41646080 sectors) RAID 5 (online) > > No matter which installation process i choose (floppies - kern.flp & > mfsroot.flp or bootable cd) i always get this error message: > > > bus_dmamap_load: Too many segs! buf_len = 0xaa0 > mlx0: I/O error - attempt to write beyond end of drive > I have the exact same machine with the exact same problem! I sure would like to know the answer too. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 6 22:20: 5 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id B128437B422 for ; Sun, 6 May 2001 22:19:59 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id HAA02045 for freebsd-scsi@freebsd.org; Mon, 7 May 2001 07:19:58 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f474pfN11471; Mon, 7 May 2001 06:51:41 +0200 (MET DST) (envelope-from j) Date: Mon, 7 May 2001 06:51:41 +0200 (MET DST) Message-Id: <200105070451.f474pfN11471@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <20010426110542.A50185@uriah.heep.sax.de> <200104261435.f3QEZLs23573@aslan.scsiguy.com> <20010426190714.E50185@uriah.heep.sax.de> <20010428231227.A37369@panzer.kdm.org> <200105060912.f469CnU07813@uriah.heep.sax.de> <20010506115718.B94763@panzer.kdm.org> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Another problem with the new CAM error handling X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" wrote: > It is an exceptional condition, though. We expect unit attentions > on boot, and after a bus reset, but not in the course of normal > operation. So it's probably good to notify the user, in case they > didn't know someone powered their device off and back on again. Argument accepted. ;-) However :), the old SCSI code was IMHO a little more detailed here. IIRC, it said: ``Unit attention. Power on, bus device reset or bus reset occurred.'' For someone who's knowledgable in SCSIland, that's quite self-understanding, but the innocent user who just knows where the power button is probably can't handle the term `unit attention'. Actually, a lot of the SCSI terminology seems to have been created by strange people... And at least here on the German newsgroups, we get sorrowful inquiries even about obvious messages. I don't want to have changed something immediately, but ``if it fits again'', maybe we could rearrange this or that. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun May 6 22:20: 7 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 1029137B424 for ; Sun, 6 May 2001 22:20:02 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id HAA02053 for freebsd-scsi@freebsd.org; Mon, 7 May 2001 07:20:01 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f474s3f11655; Mon, 7 May 2001 06:54:03 +0200 (MET DST) (envelope-from j) Date: Mon, 7 May 2001 06:54:03 +0200 (MET DST) Message-Id: <200105070454.f474s3f11655@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <15083.9059.887489.356984@ultrahot.Finland.Sun.COM> <20010428224047.A37268@panzer.kdm.org> <15083.65379.523173.371122@ultrahot.Finland.Sun.COM> <20010430101214.A46826@panzer.kdm.org> <200105060919.f469JrT07865@uriah.heep.sax.de> <20010506115244.A94763@panzer.kdm.org> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: camcontrol stop / restart broken X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" wrote: > camcontrol uses scsi_start_stop() to build the start unit CDB. > scsi_start_stop() is in libcam, which compiles a number of kernel > files in userland. (including scsi_all.c) So you need to rebuild > world to fix camcontrol. Ooops, OK. I didn't want to rebuild the world since -current, ahem, looks not quite that stable right now. ;-) Allright. Rebuilding libcam and camcontrol works. Never mind. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 7 8: 8:43 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.johnrshannon.com (mail.johnrshannon.com [208.141.183.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A8BA37B423 for ; Mon, 7 May 2001 08:08:41 -0700 (PDT) (envelope-from john@johnrshannon.com) Received: from pablo.johnrshannon.com (pablo.johnrshannon.com [192.168.1.3]) by mail.johnrshannon.com (Postfix) with ESMTP id 67EBE1D881 for ; Mon, 7 May 2001 09:08:29 -0600 (MDT) Received: (from john@localhost) by pablo.johnrshannon.com (8.11.3/8.11.3) id f47F8Ta08620 for freebsd-scsi@freebsd.org; Mon, 7 May 2001 09:08:29 -0600 (MDT) (envelope-from john) Content-Type: text/plain; charset="iso-8859-1" From: "John R. Shannon" Reply-To: john@johnrshannon.com Organization: johnrshannon.com To: freebsd-scsi@freebsd.org Subject: vm_fault page read error Date: Mon, 7 May 2001 09:08:29 -0600 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01050709082900.08599@pablo.johnrshannon.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org FreeBSD aslsystem.johnrshannon.com 4.3-RELEASE ASUS K7M motherboard Advansys DC-390U3W SCSI controller After running without problems for a week, my computer locked up with error messages spewing to the monitor: vm_fault page read error ... (I was unable to read the whole message) On reset, the SCSI controller found no devices. After powering down and back up, and scanning the SCSI bus from the the controller's set-up menu, it found the devices and rebooted. The syslog's report nothing that may hint at the problem. Is there any known problems with Advansys DC-390U3w controllers? Any configuration requirements? The relevent sections of dmesg: sym0: <1010-33> port 0xc000-0xc0ff mem 0xefffa000-0xefffbfff,0xeffff800-0xeffffbff irq 11 at device 13.0 on pci0 sym0: Symbios NVRAM, ID 7, Fast-80, LVD, parity checking sym0: open drain IRQ line driver, using on-chip SRAM sym0: using LOAD/STORE-based firmware. sym0: handling phase mismatch from SCRIPTS. sym1: <1010-33> port 0xd000-0xd0ff mem 0xefffc000-0xefffdfff,0xeffffc00-0xefffffff irq 11 at device 13.1 on pci0 sym1: Symbios NVRAM, ID 7, Fast-80, SE, parity checking sym1: open drain IRQ line driver, using on-chip SRAM sym1: using LOAD/STORE-based firmware. sym1: handling phase mismatch from SCRIPTS. da0 at sym0 bus 0 target 6 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 160.000MB/s transfers (80.000MHz, offset 62, 16bit), Tagged Queueing Enabled da0: 8759MB (17938985 512 byte sectors: 255H 63S/T 1116C) -- John R. Shannon john@johnrshannon.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 7 16:11:51 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 9F6E437B422 for ; Mon, 7 May 2001 16:11:47 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA03730; Mon, 7 May 2001 17:11:43 -0600 (MDT) (envelope-from ken) Date: Mon, 7 May 2001 17:11:42 -0600 From: "Kenneth D. Merry" To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Another problem with the new CAM error handling Message-ID: <20010507171142.A3692@panzer.kdm.org> References: <20010426110542.A50185@uriah.heep.sax.de> <200104261435.f3QEZLs23573@aslan.scsiguy.com> <20010426190714.E50185@uriah.heep.sax.de> <20010428231227.A37369@panzer.kdm.org> <200105060912.f469CnU07813@uriah.heep.sax.de> <20010506115718.B94763@panzer.kdm.org> <200105070451.f474pfN11471@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="OgqxwSJOaUobr8KG" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200105070451.f474pfN11471@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Mon, May 07, 2001 at 06:51:41AM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, May 07, 2001 at 06:51:41 +0200, J Wunsch wrote: > "Kenneth D. Merry" wrote: > > > It is an exceptional condition, though. We expect unit attentions > > on boot, and after a bus reset, but not in the course of normal > > operation. So it's probably good to notify the user, in case they > > didn't know someone powered their device off and back on again. > > Argument accepted. ;-) > > However :), the old SCSI code was IMHO a little more detailed here. > IIRC, it said: ``Unit attention. Power on, bus device reset or bus > reset occurred.'' For someone who's knowledgable in SCSIland, that's > quite self-understanding, but the innocent user who just knows where > the power button is probably can't handle the term `unit attention'. Hmm, the new code should be printing out the asc/ascq description if the asc and ascq are non-zero. As far as that goes, it's the same as the old code. Try the attached patch and see if you get any additional printouts. > Actually, a lot of the SCSI terminology seems to have been created by > strange people... And at least here on the German newsgroups, we get > sorrowful inquiries even about obvious messages. > > I don't want to have changed something immediately, but ``if it fits > again'', maybe we could rearrange this or that. Well, I'm curious to see why you're only getting back unit attention instead of the full sense information. That seems kinda odd. You might also try powering the device off and back on again and then see what camcontrol reports via 'camcontrol tur pt0 -v'. (It should be the same as the kernel, since the code is the same.) Ken -- Kenneth Merry ken@kdm.org --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="scsi_all.c.20010507" ==== //depot/FreeBSD-ken/src/sys/cam/scsi/scsi_all.c#10 - /usr/home/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_all.c ==== *** /tmp/tmp.855.0 Mon May 7 17:07:16 2001 --- /usr/home/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_all.c Mon May 7 17:06:57 2001 *************** *** 2009,2018 **** } } ! if (asc || ascq) { ! sbuf_printf(sb, " asc:%x,%x\n%s%s", asc, ascq, ! path_str, asc_desc); ! } if (sense->extra_len >= 7 && sense->fru) { sbuf_printf(sb, " field replaceable unit: %x", --- 2009,2016 ---- } } ! sbuf_printf(sb, " asc:%x,%x\n%s%s", asc, ascq, ! path_str, asc_desc); if (sense->extra_len >= 7 && sense->fru) { sbuf_printf(sb, " field replaceable unit: %x", --OgqxwSJOaUobr8KG-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon May 7 21:34:59 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from joliet.groenquist.com (cx707588-b.santab1.ca.home.com [65.5.150.38]) by hub.freebsd.org (Postfix) with ESMTP id 5B30C37B422; Mon, 7 May 2001 21:34:54 -0700 (PDT) (envelope-from root@groenquist.com) Received: from localhost (root@localhost) by joliet.groenquist.com (8.11.3/8.11.2) with ESMTP id f484Yct13643; Mon, 7 May 2001 21:34:38 -0700 (PDT) (envelope-from root@groenquist.com) Date: Mon, 7 May 2001 21:34:38 -0700 (PDT) From: Matt Groener Reply-To: Matt Groener To: Paul Murphy Cc: jacol@ids.gda.pl, freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: mylex dac960pl and FreeBSD 4.3 - bus_dmamap_load In-Reply-To: <3AF5B8C2.9020306@home.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have been trying to get anyone to respond to this issue as well. I have offered both my time and the fact that I own many many Mylex cards and would be happy to test, mail them out, perform magic tricks, etc., to get some assistance. Greg Loomis (of vinum fame) helped me out with a problem with Mylex RAID's and vinum, only to have it fail again at this point. (He is not responsible for this error or Mylex drivers; I only mention this because he bailed me out last minute and then I still got stuck with this driver issue, which was a bummer for me). The problem is confirmed to not be present at 4.2-RELEASE. I have back-ported Greg's fix for 4.2-RELEASE to get around the Mylex problem for the time being. I am not using the Mylex card as a boot device if that is of concern. I only have Mylex cards with 2.73 firmware or lower (they are mostly scavenged cards from Alpha's now running in Intel chassis). It is possible that others do not experience with problem with other Mylex cards besides the 960's, or with newer firmware. Anyone comment on what has changed, or can the Mylex driver maintainer (looks to be msmith?) offer any thoughts for us stuck with cards that no longer work? Thanks, -matt On Sun, 6 May 2001, Paul Murphy wrote: > Jacek Jędrzejczak wrote: > > > > > mlx0: DAC96PL, 2 channels, firmware 2.73-0-00, 4MB > > mlxd0: on mlx0 > > mlxd0: 20335MB (41646080 sectors) RAID 5 (online) > > > > No matter which installation process i choose (floppies - kern.flp & > > mfsroot.flp or bootable cd) i always get this error message: > > > > > > bus_dmamap_load: Too many segs! buf_len = 0xaa0 > > mlx0: I/O error - attempt to write beyond end of drive > > > > I have the exact same machine with the exact same problem! > > I sure would like to know the answer too. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 8 0:52:13 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [209.247.77.155]) by hub.freebsd.org (Postfix) with ESMTP id 3E78337B423; Tue, 8 May 2001 00:52:08 -0700 (PDT) (envelope-from gordont@bluemtn.net) Received: from localhost (gordont@localhost) by sdmail0.sd.bmarts.com (8.11.3/8.11.2/BMA1.1) with ESMTP id f487nsB59058; Tue, 8 May 2001 00:49:54 -0700 (PDT) Date: Tue, 8 May 2001 00:49:54 -0700 (PDT) From: Gordon Tetlow X-X-Sender: To: Matt Groener Cc: Paul Murphy , , , Subject: Re: mylex dac960pl and FreeBSD 4.3 - bus_dmamap_load In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hmm, I just went through all of the mlx related files and none of them changed between 4.2-RELEASE and 4.3-RELEASE. So it looks like there is something more sinister going on. -gordon On Mon, 7 May 2001, Matt Groener wrote: > I have been trying to get anyone to respond to this issue as well. > I have offered both my time and the fact that I own many many Mylex > cards and would be happy to test, mail them out, perform magic > tricks, etc., to get some assistance. > > Greg Loomis (of vinum fame) helped me out with a problem with > Mylex RAID's and vinum, only to have it fail again at this point. > (He is not responsible for this error or Mylex drivers; I only > mention this because he bailed me out last minute and then I still > got stuck with this driver issue, which was a bummer for me). > The problem is confirmed to not be present at 4.2-RELEASE. I have > back-ported Greg's fix for 4.2-RELEASE to get around the Mylex > problem for the time being. > > I am not using the Mylex card as a boot device if that is of concern. > > I only have Mylex cards with 2.73 firmware or lower (they are mostly > scavenged cards from Alpha's now running in Intel chassis). It is possibl= e > that others do not experience with problem with other Mylex cards besides > the 960's, or with newer firmware. > > Anyone comment on what has changed, or can the Mylex driver maintainer > (looks to be msmith?) offer any thoughts for us stuck with cards that no > longer work? > > Thanks, > -matt > > > On Sun, 6 May 2001, Paul Murphy wrote: > > > Jacek J=EAdrzejczak wrote: > > > > > > > > mlx0: DAC96PL, 2 channels, firmware 2.73-0-00, 4MB > > > mlxd0: on mlx0 > > > mlxd0: 20335MB (41646080 sectors) RAID 5 (online) > > > > > > No matter which installation process i choose (floppies - kern.flp & > > > mfsroot.flp or bootable cd) i always get this error message: > > > > > > > > > bus_dmamap_load: Too many segs! buf_len =3D 0xaa0 > > > mlx0: I/O error - attempt to write beyond end of drive > > > > > > > I have the exact same machine with the exact same problem! > > > > I sure would like to know the answer too. > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 8 0:59:52 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 6BCEF37B422; Tue, 8 May 2001 00:59:43 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f4885Ji01622; Tue, 8 May 2001 01:05:19 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200105080805.f4885Ji01622@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Gordon Tetlow Cc: Matt Groener , Paul Murphy , jacol@ids.gda.pl, freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: mylex dac960pl and FreeBSD 4.3 - bus_dmamap_load In-reply-to: Your message of "Tue, 08 May 2001 00:49:54 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Tue, 08 May 2001 01:05:19 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hmm, I just went through all of the mlx related files and none of them > changed between 4.2-RELEASE and 4.3-RELEASE. So it looks like there is > something more sinister going on. This is a known problem. I don't know what's up, and I can't reproduce = it (as I don't have any of these cards). I suspect that it may be an = issue with non-page-aligned I/O and the very limited scatter-gather that = these cards support. You might try overriding the assignment in mlx_disk.c: 279 dsk->si_iosize_max =3D imin(s1, s2); = = and change it to eg. (8 * PAGE_SIZE) instead to see if this masks the = problem. > -gordon > = > On Mon, 7 May 2001, Matt Groener wrote: > = > > I have been trying to get anyone to respond to this issue as well. > > I have offered both my time and the fact that I own many many Mylex > > cards and would be happy to test, mail them out, perform magic > > tricks, etc., to get some assistance. > > > > Greg Loomis (of vinum fame) helped me out with a problem with > > Mylex RAID's and vinum, only to have it fail again at this point. > > (He is not responsible for this error or Mylex drivers; I only > > mention this because he bailed me out last minute and then I still > > got stuck with this driver issue, which was a bummer for me). > > The problem is confirmed to not be present at 4.2-RELEASE. I have > > back-ported Greg's fix for 4.2-RELEASE to get around the Mylex > > problem for the time being. > > > > I am not using the Mylex card as a boot device if that is of concern.= > > > > I only have Mylex cards with 2.73 firmware or lower (they are mostly > > scavenged cards from Alpha's now running in Intel chassis). It is pos= sible > > that others do not experience with problem with other Mylex cards bes= ides > > the 960's, or with newer firmware. > > > > Anyone comment on what has changed, or can the Mylex driver maintaine= r > > (looks to be msmith?) offer any thoughts for us stuck with cards that= no > > longer work? > > > > Thanks, > > -matt > > > > > > On Sun, 6 May 2001, Paul Murphy wrote: > > > > > Jacek J=EAdrzejczak wrote: > > > > > > > > > > > mlx0: DAC96PL, 2 channels, firmware 2.73-0-00, 4MB > > > > mlxd0: on mlx0 > > > > mlxd0: 20335MB (41646080 sectors) RAID 5 (online) > > > > > > > > No matter which installation process i choose (floppies - kern.fl= p & > > > > mfsroot.flp or bootable cd) i always get this error message: > > > > > > > > > > > > bus_dmamap_load: Too many segs! buf_len =F0xaa0 > > > > mlx0: I/O error - attempt to write beyond end of drive > > > > > > > > > > I have the exact same machine with the exact same problem! > > > > > > I sure would like to know the answer too. > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > = > = > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 8 1:11:56 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sdmail0.sd.bmarts.com (sdmail0.sd.bmarts.com [209.247.77.155]) by hub.freebsd.org (Postfix) with ESMTP id E7DFC37B422; Tue, 8 May 2001 01:11:51 -0700 (PDT) (envelope-from gordont@bluemtn.net) Received: from localhost (gordont@localhost) by sdmail0.sd.bmarts.com (8.11.3/8.11.2/BMA1.1) with ESMTP id f488AAi60164; Tue, 8 May 2001 01:10:10 -0700 (PDT) Date: Tue, 8 May 2001 01:10:10 -0700 (PDT) From: Gordon Tetlow X-X-Sender: To: Mike Smith Cc: Matt Groener , Paul Murphy , , , Subject: Re: mylex dac960pl and FreeBSD 4.3 - bus_dmamap_load In-Reply-To: <200105080805.f4885Ji01622@mass.dis.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 8 May 2001, Mike Smith wrote: > This is a known problem. I don't know what's up, and I can't reproduce > it (as I don't have any of these cards). I suspect that it may be an > issue with non-page-aligned I/O and the very limited scatter-gather that > these cards support. > > > On Mon, 7 May 2001, Matt Groener wrote: > > > > > I have been trying to get anyone to respond to this issue as well. > > > I have offered both my time and the fact that I own many many Mylex > > > cards and would be happy to test, mail them out, perform magic > > > tricks, etc., to get some assistance. Perhaps you and Matt can coordinate since he seems willing to give up a card for a while? Don't want to impose, but if you have time (a scarce resource for sure) to take a look, I know that at least 2 people would be grateful. -gordon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 8 9:54:36 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from kumquat.hlcca.org (kumquat.hlcca.org [209.244.192.145]) by hub.freebsd.org (Postfix) with SMTP id 5F09837B422 for ; Tue, 8 May 2001 09:54:28 -0700 (PDT) (envelope-from dakota@kumquat.hlcca.org) Received: (qmail 355 invoked by uid 143); 8 May 2001 12:53:45 -0000 Received: from localhost (HELO kumquat.hlcca.org) (sendmail-bs@127.0.0.1) by localhost with SMTP; 8 May 2001 12:53:45 -0000 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: freebsd-scsi@freebsd.org From: lists@mediumgreen.com X-image-url: http://www.mediumgreen.com/dakota.gif Subject: Tekram DC-390U2W problems Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 May 2001 12:53:45 +0000 Message-Id: <20010508165428.5F09837B422@hub.freebsd.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. I've gone through and read the archives for the list from last year regarding the Tekram 390U2W, but am unclear exactly what the outcome was - it sounded like the sym driver was updated already. I'm seeing some problems on my machine with one of these cards - and occasional panics (which I'm not sure are related). Here are some recent messages logs: kumquat.hlcca.org: 34 > grep sym /var/log/messages May 2 17:30:09 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS reset detected. May 2 17:30:09 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. May 3 12:36:04 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS reset detected. May 3 12:36:06 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. May 3 15:19:38 kumquat /kernel: sym0:0: message d sent on bad reselection. May 3 15:20:38 kumquat /kernel: sym0:0:control msgout: 80 20 73 d. May 3 15:20:38 kumquat /kernel: sym0:0: message d sent on bad reselection. May 5 02:59:19 kumquat /kernel: sym0: <895> port 0xa400-0xa4ff mem 0xd6000000-0xd6000fff,0xd6800000-0xd68000ff irq 12 at device 10.0 on pci0 May 5 02:59:19 kumquat /kernel: sym0: Tekram NVRAM, ID 7, Fast-40, SE, parity checking May 5 02:59:19 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. May 5 02:59:19 kumquat /kernel: sa0 at sym0 bus 0 target 4 lun 0 May 5 02:59:19 kumquat /kernel: da0 at sym0 bus 0 target 0 lun 0 May 5 02:59:19 kumquat /kernel: ch0 at sym0 bus 0 target 4 lun 1 May 5 19:58:40 kumquat /kernel: (da0:sym0:0:0:0): WRITE(10). CDB: 2a 0 0 d7 0 ef 0 0 10 0 May 5 19:58:40 kumquat /kernel: (da0:sym0:0:0:0): ABORTED COMMAND asc:4e,0 May 5 19:58:40 kumquat /kernel: (da0:sym0:0:0:0): Overlapped commands attempted field replaceable unit: 1 May 5 20:08:47 kumquat /kernel: sym0: <895> port 0xa400-0xa4ff mem 0xd6000000-0xd6000fff,0xd6800000-0xd68000ff irq 12 at device 10.0 on pci0 May 5 20:08:47 kumquat /kernel: sym0: Tekram NVRAM, ID 7, Fast-40, SE, parity checking May 5 20:08:47 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. May 5 20:08:47 kumquat /kernel: sa0 at sym0 bus 0 target 4 lun 0 May 5 20:08:47 kumquat /kernel: da0 at sym0 bus 0 target 0 lun 0 May 5 20:08:47 kumquat /kernel: ch0 at sym0 bus 0 target 4 lun 1 May 7 12:58:47 kumquat /kernel: sym0: <895> port 0xa400-0xa4ff mem 0xd6000000-0xd6000fff,0xd6800000-0xd68000ff irq 12 at device 10.0 on pci0 May 7 12:58:47 kumquat /kernel: sym0: Tekram NVRAM, ID 7, Fast-40, SE, parity checking May 7 12:58:48 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. May 7 12:58:48 kumquat /kernel: sa0 at sym0 bus 0 target 4 lun 0 May 7 12:58:48 kumquat /kernel: da0 at sym0 bus 0 target 0 lun 0 May 7 12:58:48 kumquat /kernel: ch0 at sym0 bus 0 target 4 lun 1 May 8 09:52:52 kumquat /kernel: sym0: <895> port 0xa400-0xa4ff mem 0xd6000000-0xd6000fff,0xd6800000-0xd68000ff irq 12 at device 10.0 on pci0 May 8 09:52:52 kumquat /kernel: sym0: Tekram NVRAM, ID 7, Fast-40, SE, parity checking May 8 09:52:52 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. May 8 09:52:52 kumquat /kernel: sa0 at sym0 bus 0 target 4 lun 0 May 8 09:52:52 kumquat /kernel: da0 at sym0 bus 0 target 0 lun 0 May 8 09:52:52 kumquat /kernel: ch0 at sym0 bus 0 target 4 lun 1 May 8 12:38:19 kumquat /kernel: sym0: <895> port 0xa400-0xa4ff mem 0xd6000000-0xd6000fff,0xd6800000-0xd68000ff irq 12 at device 10.0 on pci0 May 8 12:38:19 kumquat /kernel: sym0: Tekram NVRAM, ID 7, Fast-40, SE, parity checking May 8 12:38:19 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. May 8 12:38:19 kumquat /kernel: sa0 at sym0 bus 0 target 4 lun 0 May 8 12:38:19 kumquat /kernel: da0 at sym0 bus 0 target 0 lun 0 May 8 12:38:19 kumquat /kernel: ch0 at sym0 bus 0 target 4 lun 1 I'm worried about the errors from May 3 & 5. I'm kinda hoping that fixing this problem will also fix the problem of machine panic's. What can I do next to determine what the cause of those errors is? Thank you -matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 8 9:57: 5 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from siamese.engr.3ware.com (mail.3ware.com [209.213.222.214]) by hub.freebsd.org (Postfix) with ESMTP id 9F8AA37B422 for ; Tue, 8 May 2001 09:57:03 -0700 (PDT) (envelope-from jdchung@3WARE.com) Received: by siamese with Internet Mail Service (5.5.2653.19) id ; Tue, 8 May 2001 09:57:02 -0700 Message-ID: <53B208BD9A7FD311881A009027B6BBFB644967@siamese> From: Jeffrey Chung To: "'freebsd-scsi@freebsd.org'" Subject: iSCSI?? Date: Tue, 8 May 2001 09:56:56 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C0D7DF.E3EB2050" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C0D7DF.E3EB2050 Content-Type: text/plain; charset="iso-8859-1" Anyone working on an iSCSI stack for FreeBSD? -Jeffrey ------_=_NextPart_001_01C0D7DF.E3EB2050 Content-Type: text/html; charset="iso-8859-1"
Anyone working on an iSCSI stack for FreeBSD?
 
-Jeffrey
------_=_NextPart_001_01C0D7DF.E3EB2050-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 8 13:20:13 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id D0A1E37B424 for ; Tue, 8 May 2001 13:20:10 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id WAA08764 for freebsd-scsi@freebsd.org; Tue, 8 May 2001 22:20:09 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f48K5NW25041; Tue, 8 May 2001 22:05:23 +0200 (MET DST) (envelope-from j) Date: Tue, 8 May 2001 22:05:23 +0200 (MET DST) Message-Id: <200105082005.f48K5NW25041@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <20010508165428.5F09837B422@hub.freebsd.org> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Tekram DC-390U2W problems X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org lists@mediumgreen.com wrote: > May 5 02:59:19 kumquat /kernel: sym0: <895> port 0xa400-0xa4ff mem > 0xd6000000-0xd6000fff,0xd6800000-0xd68000ff irq 12 at device 10.0 on pci0 > May 5 02:59:19 kumquat /kernel: sym0: Tekram NVRAM, ID 7, Fast-40, SE, parity checking I've got a: sym0: <895> port 0xd000-0xd0ff mem 0xefffa000-0xefffafff,0xefffbe00-0xefffbeff irq 12 at device 10.0 on pci0 sym0: Tekram NVRAM, ID 7, Fast-40, LVD, parity checking (probably the same as yours, ah no, you've got an SE one only) running on -current without (controller related) problems. > May 5 02:59:19 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode change from SE to SE. Those messages seem to be normal occasionally, seen them here, too. > May 5 19:58:40 kumquat /kernel: (da0:sym0:0:0:0): WRITE(10). CDB: 2a 0 0 d7 0 ef 0 0 10 0 > May 5 19:58:40 kumquat /kernel: (da0:sym0:0:0:0): ABORTED COMMAND asc:4e,0 > May 5 19:58:40 kumquat /kernel: (da0:sym0:0:0:0): Overlapped commands attempted field replaceable unit: 1 What disk is da0? -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 8 13:26: 0 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from kumquat.hlcca.org (kumquat.hlcca.org [209.244.192.145]) by hub.freebsd.org (Postfix) with SMTP id 4484D37B423 for ; Tue, 8 May 2001 13:25:54 -0700 (PDT) (envelope-from dakota@kumquat.hlcca.org) Received: (qmail 1800 invoked by uid 143); 8 May 2001 16:25:05 -0000 Received: from localhost (HELO kumquat.hlcca.org) (sendmail-bs@127.0.0.1) by localhost with SMTP; 8 May 2001 16:25:05 -0000 X-Mailer: exmh version 2.3.1 01/18/2001 with nmh-1.0.4 To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-scsi@freebsd.org From: lists@mediumgreen.com Subject: Re: Tekram DC-390U2W problems In-Reply-To: Message from j@uriah.heep.sax.de (J Wunsch) of "Tue, 08 May 2001 22:05:23 +0200." <200105082005.f48K5NW25041@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 May 2001 16:25:05 +0000 Message-Id: <20010508202554.4484D37B423@hub.freebsd.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I think I heard J Wunsch say: >lists@mediumgreen.com wrote: > >> May 5 02:59:19 kumquat /kernel: sym0: <895> port 0xa400-0xa4ff mem >> 0xd6000000-0xd6000fff,0xd6800000-0xd68000ff irq 12 at device 10.0 on pci0 >> May 5 02:59:19 kumquat /kernel: sym0: Tekram NVRAM, ID 7, Fast-40, SE, pari >ty checking > >I've got a: > >sym0: <895> port 0xd000-0xd0ff mem 0xefffa000-0xefffafff,0xefffbe00-0xefffbeff > irq 12 at device 10.0 on pci0 >sym0: Tekram NVRAM, ID 7, Fast-40, LVD, parity checking > >(probably the same as yours, ah no, you've got an SE one only) running >on -current without (controller related) problems. > >> May 5 02:59:19 kumquat /kernel: (noperiph:sym0:0:-1:-1): SCSI BUS mode chan >ge from SE to SE. > >Those messages seem to be normal occasionally, seen them here, too. Good to know that I'm not the only one :) >> May 5 19:58:40 kumquat /kernel: (da0:sym0:0:0:0): WRITE(10). CDB: 2a 0 0 d7 > 0 ef 0 0 10 0 >> May 5 19:58:40 kumquat /kernel: (da0:sym0:0:0:0): ABORTED COMMAND asc:4e,0 >> May 5 19:58:40 kumquat /kernel: (da0:sym0:0:0:0): Overlapped commands attem >pted field replaceable unit: 1 > >What disk is da0? May 8 09:52:52 kumquat /kernel: da0 at sym0 bus 0 target 0 lun 0 May 8 09:52:52 kumquat /kernel: da0: Fixed Direct Access SCSI-3 device May 8 09:52:52 kumquat /kernel: da0: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled May 8 09:52:52 kumquat /kernel: da0: 8761MB (17942584 512 byte sectors: 255H 63S/T 1116C) -matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 8 14:15:23 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from jhs.muc.de (jhs.muc.de [193.149.49.84]) by hub.freebsd.org (Postfix) with ESMTP id BB27737B423 for ; Tue, 8 May 2001 14:15:15 -0700 (PDT) (envelope-from jhs@jhs.muc.de) Received: from park.jhs.private (localhost [127.0.0.1]) by jhs.muc.de (8.11.0/8.11.0) with ESMTP id f47LvVs42257; Mon, 7 May 2001 21:57:31 GMT (envelope-from jhs@park.jhs.private) Message-Id: <200105072157.f47LvVs42257@jhs.muc.de> To: freebsd-scsi@FreeBSD.ORG Cc: pechter@ureach.com, "Ron Klinkien" Subject: Re: Recovered data with positive head offset field replaceable unit msg In-Reply-To: Message from Bill Pechter of "Sat, 05 May 2001 07:55:49 EDT." <200105051155.HAA22713@stage21.ureach.com> Date: Mon, 07 May 2001 23:57:31 +0200 From: "Julian Stacey Jhs@jhs.muc.de" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill Pechter wrote: > > Hi SCSI wizards, > > > > On one of my FreeBSD machines I found > > this rather strange scsi message: > > > > > (da1:sym0:0:8:0): READ(06). CDB: 8 8 1 90 10 0 > > > (da1:sym0:0:8:0): RECOVERED ERROR info:80198 asc:17,2 > > (da1:sym0:0:8:0): Recovered data with positive head offset > field replaceable unit: df sks:80,12 > > > > Thanks in advance. > > > > Regards, > > Ron. > > Haven't seen something like that in years. > In the old days of SMD disks and DEC RP06's and RM05's (mid > 80's), I'd have said it was a servo tracking issue with the > heads missing the data by a bit (possible bad spot on disk) > which was recovered by the disk controller offsetting the heads > a bit towards the center of the drive just a bit. > > The data was recoverable... by the drive moving the head just a > little. Things like this were caused by bad spot on disk (servo > platter or data platter) misalignment, dirt on the drive rails > that caused the heads to bounce a bit while seeking or trying to > stay on track, power fluctuations. Some idiot banging into the > disks during a read operation. I'd heard (pre '85 I think) that if someone deleted data, & a country's spy service wanted to get the data back, they `just' recalibrated the seek offset servos, increased the op amp gain factor, & read as before, (or repeat scanned if necessary) to recover at least most of the deleted data. There are normal occasions when the owner too wants to recover his own data. Anyone know if SCSI (&/or IDE come to that) provides hooks [doc'd or undoc'd ] ? It's possible to recover most text data from bad floppies by repeat scanning, even without varying the offset, even with failing CRCs: I wrote a program that does that in ~87 http://bim.bsn.com/~jhs/src/bsd/jhs/bin/public/valid/valid.c & valid.1 (The recover part of the program's now larger functionality runs only on DOS though, not on Unix, as DOS passes filled buffers back even when read() returns CRC error, whereas FreeBSD discards the buffer content on error. Julian - Julian Stacey Unix Consultant - Munich Germany http://bim.bsn.com/~jhs/ Ihr Rauchen => mein allergischer Kopfschmerz ! Kau/Schnupftabak probieren ! Like Linux ? Then also look at FreeBSD with its 5000+ packages ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 8 14:33:55 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from joliet.groenquist.com (cx707588-b.santab1.ca.home.com [65.5.150.38]) by hub.freebsd.org (Postfix) with ESMTP id 44EFC37B423; Tue, 8 May 2001 14:33:51 -0700 (PDT) (envelope-from root@groenquist.com) Received: from localhost (root@localhost) by joliet.groenquist.com (8.11.3/8.11.2) with ESMTP id f48LXi515595; Tue, 8 May 2001 14:33:44 -0700 (PDT) (envelope-from root@groenquist.com) Date: Tue, 8 May 2001 14:33:44 -0700 (PDT) From: Matt Groener Reply-To: Matt Groener To: Gordon Tetlow Cc: Mike Smith , Matt Groener , Paul Murphy , jacol@ids.gda.pl, freebsd-scsi@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: mylex dac960pl and FreeBSD 4.3 - bus_dmamap_load 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 As I said, I can give up either a card which exhibits the problem, or you can feed me ideas (I will try the one you suggested, Mike), and I will plug them in and see what happens. I know no one has time for their day jobs much less anything else. I'm the same way, but we might find we can fix this or mask it in the meantime. Thanks everyone for comments and ideas to date. -matt On Tue, 8 May 2001, Gordon Tetlow wrote: > On Tue, 8 May 2001, Mike Smith wrote: > > > This is a known problem. I don't know what's up, and I can't reproduce > > it (as I don't have any of these cards). I suspect that it may be an > > issue with non-page-aligned I/O and the very limited scatter-gather that > > these cards support. > > > > > On Mon, 7 May 2001, Matt Groener wrote: > > > > > > > I have been trying to get anyone to respond to this issue as well. > > > > I have offered both my time and the fact that I own many many Mylex > > > > cards and would be happy to test, mail them out, perform magic > > > > tricks, etc., to get some assistance. > > Perhaps you and Matt can coordinate since he seems willing to give up a > card for a while? Don't want to impose, but if you have time (a scarce > resource for sure) to take a look, I know that at least 2 people would be > grateful. > > -gordon > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue May 8 15:44:39 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 46B7937B423; Tue, 8 May 2001 15:44:37 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.3) with ESMTP id f48MoZi03651; Tue, 8 May 2001 15:50:36 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200105082250.f48MoZi03651@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrew Heybey Cc: msmith@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: AMI MegaRAID on 4.2-RELEASE and bus_dmamap_load errors In-reply-to: Your message of "02 May 2001 09:01:29 EDT." <85y9sf7vme.fsf@stiegl.niksun.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 08 May 2001 15:50:35 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > To follow up on my own email: > > If I change rawio to page-align the buffer it uses for I/O, then the error > messages go away. Thanks for noticing this; I have a class of these issues to deal with at some point. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 9 0:20:13 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 0E2F337B422 for ; Wed, 9 May 2001 00:20:11 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id JAA14469 for freebsd-scsi@freebsd.org; Wed, 9 May 2001 09:20:09 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f497Bwr27407; Wed, 9 May 2001 09:11:58 +0200 (MET DST) (envelope-from j) Date: Wed, 9 May 2001 09:11:58 +0200 (MET DST) Message-Id: <200105090711.f497Bwr27407@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <200105051155.HAA22713@stage21.ureach.com> <200105072157.f47LvVs42257@jhs.muc.de> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Recovered data with positive head offset field replaceable unit msg X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Julian Stacey Jhs@jhs.muc.de" wrote: > I wrote a program that does that in ~87 > http://bim.bsn.com/~jhs/src/bsd/jhs/bin/public/valid/valid.c & > valid.1 > (The recover part of the program's now larger > functionality runs > only on DOS though, not on Unix, as DOS > passes filled buffers back > even when read() returns CRC error, > whereas FreeBSD discards the > buffer content on error. Arranging for a `read track' functionality in the FreeBSD floppy driver should be possible. This will return you the entire /bit/ contents of the track, no CRC checks &c. Only the first sector ID will be synchronized, the remainder of the track is returned as it appears on the floppy; you need to manually bit-dealign and perhaps bit-reverse the remaining data. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 9 11:50:51 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 6F47B37B424 for ; Wed, 9 May 2001 11:50:39 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id UAA28360 for freebsd-scsi@FreeBSD.ORG; Wed, 9 May 2001 20:50:38 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f49InJU29154 for freebsd-scsi@FreeBSD.ORG; Wed, 9 May 2001 20:49:19 +0200 (MET DST) (envelope-from j) Date: Wed, 9 May 2001 20:49:19 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Subject: Re: Another problem with the new CAM error handling Message-ID: <20010509204919.H12728@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <20010426110542.A50185@uriah.heep.sax.de> <200104261435.f3QEZLs23573@aslan.scsiguy.com> <20010426190714.E50185@uriah.heep.sax.de> <20010428231227.A37369@panzer.kdm.org> <200105060912.f469CnU07813@uriah.heep.sax.de> <20010506115718.B94763@panzer.kdm.org> <200105070451.f474pfN11471@uriah.heep.sax.de> <20010507171142.A3692@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010507171142.A3692@panzer.kdm.org>; from ken@kdm.org on Mon, May 07, 2001 at 05:11:42PM -0600 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Kenneth D. Merry wrote: > Well, I'm curious to see why you're only getting back unit attention > instead of the full sense information. That seems kinda odd. > > You might also try powering the device off and back on again and then see > what camcontrol reports via 'camcontrol tur pt0 -v'. (It should be the > same as the kernel, since the code is the same.) OK, i tried your patch. Here's the result: uriah # camcontrol tur pt0 -v Unit is not ready (pass6:sym1:0:5:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (pass6:sym1:0:5:0): CAM Status: SCSI Status Error (pass6:sym1:0:5:0): SCSI Status: Check Condition (pass6:sym1:0:5:0): UNIT ATTENTION asc:0,0 (pass6:sym1:0:5:0): No additional sense information You're right, this rather seems to be a bug in the scanner's SCSI implementation. For comparision, i just issued a BDR to a less used disk, here's the result: uriah # camcontrol tur da3 -v Unit is not ready (pass2:sym0:0:4:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (pass2:sym0:0:4:0): CAM Status: SCSI Status Error (pass2:sym0:0:4:0): SCSI Status: Check Condition (pass2:sym0:0:4:0): UNIT ATTENTION asc:29,0 (pass2:sym0:0:4:0): Power on, reset, or bus device reset occurred Should/could we add a quirk for the scanner that synthesizes an ASC/ASCQ of 29,0 in that case? Here's the inquiry data: uriah # camcontrol inquiry pt0 pass6: Fixed Processor SCSI-2 device pass6: 3.300MB/s transfers -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 9 12: 5:12 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id C268037B422 for ; Wed, 9 May 2001 12:05:08 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id NAA17145; Wed, 9 May 2001 13:04:59 -0600 (MDT) (envelope-from ken) Date: Wed, 9 May 2001 13:04:59 -0600 From: "Kenneth D. Merry" To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Another problem with the new CAM error handling Message-ID: <20010509130459.A17074@panzer.kdm.org> References: <20010426110542.A50185@uriah.heep.sax.de> <200104261435.f3QEZLs23573@aslan.scsiguy.com> <20010426190714.E50185@uriah.heep.sax.de> <20010428231227.A37369@panzer.kdm.org> <200105060912.f469CnU07813@uriah.heep.sax.de> <20010506115718.B94763@panzer.kdm.org> <200105070451.f474pfN11471@uriah.heep.sax.de> <20010507171142.A3692@panzer.kdm.org> <20010509204919.H12728@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010509204919.H12728@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Wed, May 09, 2001 at 08:49:19PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, May 09, 2001 at 20:49:19 +0200, J Wunsch wrote: > As Kenneth D. Merry wrote: > > > Well, I'm curious to see why you're only getting back unit attention > > instead of the full sense information. That seems kinda odd. > > > > You might also try powering the device off and back on again and then see > > what camcontrol reports via 'camcontrol tur pt0 -v'. (It should be the > > same as the kernel, since the code is the same.) > > OK, i tried your patch. Here's the result: > > uriah # camcontrol tur pt0 -v > Unit is not ready > (pass6:sym1:0:5:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (pass6:sym1:0:5:0): CAM Status: SCSI Status Error > (pass6:sym1:0:5:0): SCSI Status: Check Condition > (pass6:sym1:0:5:0): UNIT ATTENTION asc:0,0 > (pass6:sym1:0:5:0): No additional sense information > > You're right, this rather seems to be a bug in the scanner's SCSI > implementation. For comparision, i just issued a BDR to a less used > disk, here's the result: Ahh. > uriah # camcontrol tur da3 -v > Unit is not ready > (pass2:sym0:0:4:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (pass2:sym0:0:4:0): CAM Status: SCSI Status Error > (pass2:sym0:0:4:0): SCSI Status: Check Condition > (pass2:sym0:0:4:0): UNIT ATTENTION asc:29,0 > (pass2:sym0:0:4:0): Power on, reset, or bus device reset occurred > > Should/could we add a quirk for the scanner that synthesizes an > ASC/ASCQ of 29,0 in that case? Here's the inquiry data: I'm not sure it would really be worth it. We don't have the quirk framework at the moment to synthesize ASC/ASCQs from sense keys anyway. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed May 9 13:50: 6 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id EEC4D37B422 for ; Wed, 9 May 2001 13:50:01 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id WAA01228 for freebsd-scsi@FreeBSD.ORG; Wed, 9 May 2001 22:50:00 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f49KZ4929535 for freebsd-scsi@FreeBSD.ORG; Wed, 9 May 2001 22:35:04 +0200 (MET DST) (envelope-from j) Date: Wed, 9 May 2001 22:35:04 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Subject: Re: Another problem with the new CAM error handling Message-ID: <20010509223504.I12728@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <20010426110542.A50185@uriah.heep.sax.de> <200104261435.f3QEZLs23573@aslan.scsiguy.com> <20010426190714.E50185@uriah.heep.sax.de> <20010428231227.A37369@panzer.kdm.org> <200105060912.f469CnU07813@uriah.heep.sax.de> <20010506115718.B94763@panzer.kdm.org> <200105070451.f474pfN11471@uriah.heep.sax.de> <20010507171142.A3692@panzer.kdm.org> <20010509204919.H12728@uriah.heep.sax.de> <20010509130459.A17074@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <20010509130459.A17074@panzer.kdm.org>; from ken@kdm.org on Wed, May 09, 2001 at 01:04:59PM -0600 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Kenneth D. Merry wrote: > > Should/could we add a quirk for the scanner that synthesizes an > > ASC/ASCQ of 29,0 in that case? Here's the inquiry data: > > I'm not sure it would really be worth it. We don't have the quirk > framework at the moment to synthesize ASC/ASCQs from sense keys anyway. OK, may it rest in peace then. ;-) Thanks for the help, Ken, to clarify the reason! -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu May 10 4:33:17 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from cvis28.marconicomms.com (cvis28.marconicomms.com [195.99.244.60]) by hub.freebsd.org (Postfix) with ESMTP id 01CB537B422; Thu, 10 May 2001 04:33:14 -0700 (PDT) (envelope-from sje2bk@marconi.com) Received: from cvis01.gpt.co.uk (unverified) by cvis28.marconicomms.com (Content Technologies SMTPRS 4.1.5) with ESMTP id ; Thu, 10 May 2001 12:33:09 +0100 Received: from bkrzu6.de.marconicomms.com by cvis01.gpt.co.uk with ESMTP (8.8.8+Sun/cvms-31) id MAA20916; Thu, 10 May 2001 12:33:03 +0100 (BST) Received: from bk4957.de.marconicomms.com (bk4957.de.marconicomms.com [172.28.39.232]) by bkrzu6.de.marconicomms.com (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id NAA24500; Thu, 10 May 2001 13:32:51 +0200 (METDST) Received: (from sje2bk@localhost) by bk4957.de.marconicomms.com (8.11.1/8.11.1) id f4ABWlr14294; Thu, 10 May 2001 13:32:47 +0200 (CEST) (envelope-from sje2bk) Date: Thu, 10 May 2001 13:32:47 +0200 From: Jens Schweikhardt To: freebsd-scsi@freebsd.org Cc: schweikh@freebsd.org Subject: read trouble with Yamaha CRW6416 Message-ID: <20010510133247.D13838@bk4957.de.marconicomms.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hello, world\n I've got the following cd burner in my FreeBSD 4.2 box: # camcontrol inquiry cd0 pass1: Removable CD-ROM SCSI-2 device pass1: 10.000MB/s transfers (10.000MHz, offset 15) This 6x4x16 had problems from day 1 reading (non-burnt) CDs, e.g. the Walnut Creek CDs: $ cd packages/All; for i in *.tgz; do gzip -tv $i; done gzip: 4va-1.21.tgz: invalid compressed data--format violated 9e-1.0.tgz: OK 9menu-1.5.tgz: OK gzip: 9term-1.6.3.tgz: invalid compressed data--crc error gzip: 9wm-1.1.tgz: invalid compressed data--crc error gzip: Cgraph-2.04.tgz: invalid compressed data--format violated ... (only about 1/3 of packages are ok) Note that there are no I/O errors, it's just garbage that's in the files. A 10X Pioneer CD Reader in the same system reads all those CDs without a hitch, so it's definitely the Yamaha that's icky. The CDs look perfect, no scratches or anything, so read errors due to that should not be the real problem. The Yamaha reads its self-burnt CDs just fine. So my question is: what can I do/test/ configure/update/tune to make my Yamaha read other CDs correctly? Any insights deeply appreciated. Thanks! Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri May 11 23:37:25 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from jhs.muc.de (jhs.muc.de [193.149.49.84]) by hub.freebsd.org (Postfix) with ESMTP id 3A07637B43C for ; Fri, 11 May 2001 23:37:18 -0700 (PDT) (envelope-from jhs@jhs.muc.de) Received: from park.jhs.private (localhost [127.0.0.1]) by jhs.muc.de (8.11.0/8.11.0) with ESMTP id f4AIi6d59201; Thu, 10 May 2001 18:44:38 GMT (envelope-from jhs@park.jhs.private) Message-Id: <200105101844.f4AIi6d59201@jhs.muc.de> To: Jens Schweikhardt Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: read trouble with Yamaha CRW6416 From: "Julian Stacey" Organization: Vector Systems Ltd - Munich Unix & Internet consultancy X-Web: http://www.jhs.muc.de http://bim.bsn.com/~jhs/ In-reply-to: Your message of "Thu, 10 May 2001 13:32:47 +0200." <20010510133247.D13838@bk4957.de.marconicomms.com> Date: Thu, 10 May 2001 20:44:06 +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Jens Schweikhardt wrote: > Note that there are no I/O errors, it's just garbage that's > in the files. Nasty. > A 10X Pioneer CD Reader in the same system reads all those CDs > without a hitch, so it's definitely the Yamaha that's icky. The > CDs look perfect, no scratches or anything, so read errors due > to that should not be the real problem. The Yamaha reads its > self-burnt CDs just fine. So my question is: what can I do/test/ > configure/update/tune to make my Yamaha read other CDs correctly? > Any insights deeply appreciated. Thanks! Dont assume WC Inc CDs that look unscratched are perfect: On more than one set of WC Inc CDs over the years I've seen errors, & they weren't scratched AFAIR., though there were sometimes optical effects more like waves, (as if they'd been washed). I make an on-line index of all my off line CDs, inc. md5 of every file on CDs, thus I read aprox the whole surface, so I suppose I see more errors than others ( script at http://bim.bsn.com/~jhs/bin/.sh/new_cd ) . I normally see IO errors on my console though ( xterm -C ) . BTW WC are very good about replacing bad CDs. I've got a lot of drives (mostly very old), Different cd drives can read different media, it's do with optical sensitivity, differentiating, some writeable half see through greenish CDs a friend wrote were particularly problematic. Rewriteables are apparently harder to read than than writables, which in turn are harder to read (need more differential sensitivity) than plain old manufacturer supplied cdroms. Julian - Julian Stacey Unix Consultant - Munich Germany http://bim.bsn.com/~jhs/ Ihr Rauchen => mein allergischer Kopfschmerz ! Kau/Schnupftabak probieren ! Like Linux ? Then also look at FreeBSD with its 5000+ packages ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message