From owner-freebsd-scsi Sun Feb 7 05:43:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA28466 for freebsd-scsi-outgoing; Sun, 7 Feb 1999 05:43:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from roma.coe.ufrj.br (roma.coe.ufrj.br [146.164.53.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA28460 for ; Sun, 7 Feb 1999 05:43:52 -0800 (PST) (envelope-from jonny@jonny.eng.br) Received: (from jonny@localhost) by roma.coe.ufrj.br (8.8.8/8.8.8) id LAA24335 for scsi@freebsd.org; Sun, 7 Feb 1999 11:43:50 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199902071343.LAA24335@roma.coe.ufrj.br> Subject: Invalidating Pack: ZIP SCSI Problems ? To: scsi@FreeBSD.ORG Date: Sun, 7 Feb 1999 11:43:50 -0200 (EDT) X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, My ZIP drive is very strange, I don't know if every one is just like that. When booting, I SCSI_DELAY is too low and I've just powered on the machine, the ZIP drive is not recognized: (da0:aha0:0:5:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da0:aha0:0:5:0): error code 0 (da0:aha0:0:5:0): fatal error, failed to attach to device (da0:aha0:0:5:0): lost device (da0:aha0:0:5:0): removing device entry At first I thought it was a ZIP problem, disconsidering the fact that DOS/Windows and FreeBSD 2.2 did not have any problem. Today I got an even stranger problem: (da0:aha0:0:5:0): READ(06). CDB: 8 0 1 a0 80 0 (da0:aha0:0:5:0): NOT READY asc:4,3 (da0:aha0:0:5:0): Logical unit not ready, manual intervention required (da0:aha0:0:5:0): Invalidating pack I mounted the ZIP disk (ffs, if this matters), copied a file to hard disk, worked on it and was going to copy it back. Obviously, the ZIP has shut down for power save. When I did a ls, I got these messages, and the disk was ejected. Every other access to da0 returns with "Device not configured" When everything is ok, the relevant part of dmesg is: ... aha0 at 0x334-0x337 irq 11 drq 6 on isa aha0: AHA-1542C FW Rev. 0.1 (ID=44) SCSI Host Adapter, SCSI ID 7, 16 CCBs ... da0 at aha0 bus 0 target 5 lun 0 da0: Removable Direct Access SCSI-2 device da0: 3.300MB/s transfers da0: 96MB (196608 512 byte sectors: 64H 32S/T 96C) cd0 at aha0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 3.333MB/s transfers (3.333MHz, offset 8) cd0: Attempt to query device size failed: NOT READY, Medium not present ... Now, two questions: 1) If the system refuses to detect the disk at boot, is there some form to reattach it ? The pass-through pass1 (I also have a CD) device is present, but not the da0 device. camcontrol rescan does not work as I expected. How could I attach the drive to da0 ? 2) I've never seen this last problem before. Maybe my ZIP drive has some defect ? Or is it a problem in CAM ? I'm using 3.0-stable. Thank in advance, Jonny PS: I do not subscribe to -scsi for a long time. Please, remember to send a copy of the answers directly to me. -- Joao Carlos Mendes Luis M.Sc. Student jonny@jonny.eng.br Universidade Federal do Rio de Janeiro "This .sig is not meant to be politically correct." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 7 10:20:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24006 for freebsd-scsi-outgoing; Sun, 7 Feb 1999 10:20:15 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (castles235.castles.com [208.214.165.235]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA23996; Sun, 7 Feb 1999 10:20:09 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id KAA06425; Sun, 7 Feb 1999 10:15:17 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902071815.KAA06425@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Daren R. Sefcik" cc: "David O'Brien" , freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: low level format--how?? In-reply-to: Your message of "Sat, 06 Feb 1999 17:35:03 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Feb 1999 10:15:16 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Thanks..I ended up just pulling my old Atari out of the closet and doing > the format on it...that seemed to work and I am now up and running. I > would still like to know how to do it under FreeBSD. If the disk wasn't being probed, then you can't format it, period. It sounds to me like you managed to screw the disk up, and the process of pulling it and reinstalling it in your Atari gave it a chance to recover. Rule 1: Never change more than one variable at one time. The correct answer to "how do you low-level format a SCSI disk under FreeBSD" is "if you have to ask, you SHOULD NOT be doing it". It is almost never the right thing to do. > Daren > > > > On Sat, 6 Feb 1999, David O'Brien wrote: > > > You will get more mileage by discussing this type of thing on > > freebsd-scsi@freebsd.org > > > > > > > > Is there ``/sbin/scsiformat''? Or may be you have to use camcontrol now? > > > > > > rover# camcontrol defects -f da0 > > > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > > > cam_lookup_pass: No such file or directory > > > cam_lookup_pass: either the pass driver isn't in your kernel > > > cam_lookup_pass: or da0 doesn't exist > > > rover# camcontrol defects -f /dev/da0 > > > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > > > cam_lookup_pass: No such file or directory > > > cam_lookup_pass: either the pass driver isn't in your kernel > > > cam_lookup_pass: or da0 doesn't exist > > > rover# > > > > -- > > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-current" in the body of the message > -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 7 11:25:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01115 for freebsd-scsi-outgoing; Sun, 7 Feb 1999 11:25:05 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01106; Sun, 7 Feb 1999 11:25:03 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id MAA63805; Sun, 7 Feb 1999 12:24:23 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902071924.MAA63805@panzer.plutotech.com> Subject: Re: low level format--how?? In-Reply-To: <199902071815.KAA06425@dingo.cdrom.com> from Mike Smith at "Feb 7, 1999 10:15:16 am" To: mike@smith.net.au (Mike Smith) Date: Sun, 7 Feb 1999 12:24:23 -0700 (MST) Cc: daren@sefcik.cc, obrien@NUXI.com, freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith wrote... > > Thanks..I ended up just pulling my old Atari out of the closet and doing > > the format on it...that seemed to work and I am now up and running. I > > would still like to know how to do it under FreeBSD. > > If the disk wasn't being probed, then you can't format it, period. That only applies if the passthrough driver didn't probe it. The passthrough driver will attach if the device responds to an inquiry. My guess is that the pass driver did attach in his case, but the da driver did not. I've seen this before with other drives that ended up needing a low-level format. In order for the da driver to attach, the read capacity it does must succeed, or fail with an acceptable "medium not present" type error code. > It sounds to me like you managed to screw the disk up, and the process > of pulling it and reinstalling it in your Atari gave it a chance to > recover. > > Rule 1: Never change more than one variable at one time. Good idea. > The correct answer to "how do you low-level format a SCSI disk under > FreeBSD" is "if you have to ask, you SHOULD NOT be doing it". It is > almost never the right thing to do. In his case, I think it was. The "medium format corrupted" error message can generally be fixed by low-level formatting the disk. But you're right, low-level formatting the disk is often the wrong thing to do. > > Daren > > > > > > > > On Sat, 6 Feb 1999, David O'Brien wrote: > > > > > You will get more mileage by discussing this type of thing on > > > freebsd-scsi@freebsd.org > > > > > > > > > > > Is there ``/sbin/scsiformat''? Or may be you have to use camcontrol now? > > > > > > > > rover# camcontrol defects -f da0 > > > > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > > > > cam_lookup_pass: No such file or directory > > > > cam_lookup_pass: either the pass driver isn't in your kernel > > > > cam_lookup_pass: or da0 doesn't exist > > > > rover# camcontrol defects -f /dev/da0 > > > > camcontrol: cam_lookup_pass: CAMGETPASSTHRU ioctl failed > > > > cam_lookup_pass: No such file or directory > > > > cam_lookup_pass: either the pass driver isn't in your kernel > > > > cam_lookup_pass: or da0 doesn't exist > > > > rover# > > > > > > -- > > > -- David (obrien@NUXI.com -or- obrien@FreeBSD.org) > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-current" in the body of the message > > > > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 7 12:41:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA11244 for freebsd-scsi-outgoing; Sun, 7 Feb 1999 12:41:29 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from www4.gmx.net (www4.gmx.net [195.63.104.44]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA11225 for ; Sun, 7 Feb 1999 12:41:25 -0800 (PST) (envelope-from Ralf.Luettgen@gmx.net) Received: (qmail 25027 invoked by uid 65534); 7 Feb 1999 20:41:22 -0000 Date: Sun, 7 Feb 1999 21:41:22 +0100 (MET) From: Ralf Luettgen To: freebsd-scsi@FreeBSD.ORG Cc: freebsd-bugs@FreeBSD.ORG Subject: system hangs on fdisk on scsi disc 3.0-Stable X-Authenticated-Sender: #0000515563@gmx.net X-Authenticated-IP: [195.14.235.54] Message-Id: <25024.918420082@www.gmx.net> X-Mailer: WWW-Mail 1.02a/b (Global Message Exchange) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. If I try to make a fdisk on my nec scsi disk, the system hangs and the only thing I can do, is to press the reset button. My NEC SCSI DISK: da1: Fixed Direct Access SCSI-2 device da1: 10.0MB/s transfers (10.0MHz, offset 15) da1: 1032MB (2113776 512 byte sectors: 64H 32S/T 1032C) Thanks for help. Ralf --- Sent through Global Message Exchange - http://www.gmx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Feb 7 13:39:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18583 for freebsd-scsi-outgoing; Sun, 7 Feb 1999 13:39:41 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (castles235.castles.com [208.214.165.235]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18515; Sun, 7 Feb 1999 13:38:54 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id NAA07489; Sun, 7 Feb 1999 13:34:00 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199902072134.NAA07489@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" cc: mike@smith.net.au (Mike Smith), daren@sefcik.cc, obrien@NUXI.com, freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: low level format--how?? In-reply-to: Your message of "Sun, 07 Feb 1999 12:24:23 MST." <199902071924.MAA63805@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 07 Feb 1999 13:34:00 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > The correct answer to "how do you low-level format a SCSI disk under > > FreeBSD" is "if you have to ask, you SHOULD NOT be doing it". It is > > almost never the right thing to do. > > In his case, I think it was. The "medium format corrupted" error message > can generally be fixed by low-level formatting the disk. Hmm, mea culpa; I didn't see/register that message. It would, indeed, indicate that a low-level format was required. Daren, my apologies. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 8 09:36:45 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02423 for freebsd-scsi-outgoing; Mon, 8 Feb 1999 09:36:45 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02406; Mon, 8 Feb 1999 09:36:42 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id KAA68144; Mon, 8 Feb 1999 10:35:27 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902081735.KAA68144@panzer.plutotech.com> Subject: Re: system hangs on fdisk on scsi disc 3.0-Stable In-Reply-To: <25024.918420082@www.gmx.net> from Ralf Luettgen at "Feb 7, 1999 9:41:22 pm" To: Ralf.Luettgen@gmx.net (Ralf Luettgen) Date: Mon, 8 Feb 1999 10:35:27 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG, freebsd-bugs@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ralf Luettgen wrote... > Hi. > > > If I try to make a fdisk on my nec scsi disk, the system hangs and > the only thing I can do, is to press the reset button. > > My NEC SCSI DISK: > > da1: Fixed Direct Access SCSI-2 device > da1: 10.0MB/s transfers (10.0MHz, offset 15) > da1: 1032MB (2113776 512 byte sectors: 64H 32S/T 1032C) Hmm. It's kinda hard to know what could be causing the problem. Could you put the following in your kernel config file: options DDB And then, try fdisking the drive. When the machine hangs, type ctrl-alt-esc, and then 'trace' at the DDB prompt. Send the stack trace to the list. That may give us an idea of what is going on. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 8 12:15:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA24023 for freebsd-scsi-outgoing; Mon, 8 Feb 1999 12:15:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA24016 for ; Mon, 8 Feb 1999 12:15:34 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from gosset.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Feb 99 20:14:44 +0000 (GMT) To: freebsd-scsi@FreeBSD.ORG Subject: Vmcore dumping through cam. Date: Mon, 08 Feb 1999 20:14:43 +0000 From: David Malone Message-ID: <9902082014.aa26935@salmon.maths.tcd.ie> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Vmcore dumping through cam seems to take ages. We've a machine with 1GB of ram and it takes ages to dump (~20minutes). I think what is happening is that xpt_polled_action is getting called so quickly that the action is nowhere near complete and so you have to wait atleast another second for it to finish. The timeout is given in the ccb and copied to a unsigned 32 bit number. A nasty way to fix this would be to only wait 1/1000s and multiply the timeout by 1000. (This instead of allowing a 135 year timeout allows a 49 day timeout - which seems OK). I'm going to test the folloing patch, but maybe there is a better way? David. *** cam_xpt.c Mon Feb 8 20:08:15 1999 --- /usr/src/sys/cam/cam_xpt.c Wed Jan 20 23:00:31 1999 *************** *** 3139,3145 **** struct cam_devq *devq; struct cam_ed *dev; ! timeout = start_ccb->ccb_h.timeout * 1000; sim = start_ccb->ccb_h.path->bus->sim; devq = sim->devq; dev = start_ccb->ccb_h.path->device; --- 3139,3145 ---- struct cam_devq *devq; struct cam_ed *dev; ! timeout = start_ccb->ccb_h.timeout; sim = start_ccb->ccb_h.path->bus->sim; devq = sim->devq; dev = start_ccb->ccb_h.path->device; *************** *** 3155,3161 **** while((devq->send_openings <= 0 || dev->ccbq.dev_openings < 0) && (--timeout > 0)) { ! DELAY(1); (*(sim->sim_poll))(sim); swi_camnet(); swi_cambio(); --- 3155,3161 ---- while((devq->send_openings <= 0 || dev->ccbq.dev_openings < 0) && (--timeout > 0)) { ! DELAY(1000); (*(sim->sim_poll))(sim); swi_camnet(); swi_cambio(); *************** *** 3173,3179 **** if ((start_ccb->ccb_h.status & CAM_STATUS_MASK) != CAM_REQ_INPROG) break; ! DELAY(1); } if (timeout == 0) { /* --- 3173,3179 ---- if ((start_ccb->ccb_h.status & CAM_STATUS_MASK) != CAM_REQ_INPROG) break; ! DELAY(1000); } if (timeout == 0) { /* To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 8 12:51:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA29219 for freebsd-scsi-outgoing; Mon, 8 Feb 1999 12:51:32 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id MAA29209 for ; Mon, 8 Feb 1999 12:51:30 -0800 (PST) (envelope-from dwmalone@maths.tcd.ie) Received: from gosset.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 8 Feb 99 20:51:28 +0000 (GMT) To: freebsd-scsi@FreeBSD.ORG Subject: Long vmcore dumps. Date: Mon, 08 Feb 1999 20:51:28 +0000 From: David Malone Message-ID: <9902082051.aa00560@salmon.maths.tcd.ie> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Sorry - confused about the units for delay - that patch doesn't help in the least! Does anyone know what is slowing it? The ide dump code seems to go much faster even on quite old disks.... David. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 9 04:15:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA09189 for freebsd-scsi-outgoing; Tue, 9 Feb 1999 04:15:36 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.26.10.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA09184 for ; Tue, 9 Feb 1999 04:15:32 -0800 (PST) (envelope-from bde@godzilla.zeta.org.au) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.8.7) id TAA16269; Tue, 9 Feb 1999 19:56:26 +1100 Date: Tue, 9 Feb 1999 19:56:26 +1100 From: Bruce Evans Message-Id: <199902090856.TAA16269@godzilla.zeta.org.au> To: dwmalone@maths.tcd.ie, freebsd-scsi@FreeBSD.ORG Subject: Re: Long vmcore dumps. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Sorry - confused about the units for delay - that patch doesn't >help in the least! Does anyone know what is slowing it? The ide >dump code seems to go much faster even on quite old disks.... The IDE dump code normally writes 127.5K at a time. The SCSI dump code normally writes PAGE_SIZE (4K on i386's) at a time. Some drives are challenged by small synchronous i/o's. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 9 09:23:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11750 for freebsd-scsi-outgoing; Tue, 9 Feb 1999 09:23:21 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from outland.cyberwar.com (outland.cyberwar.com [206.88.128.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11718 for ; Tue, 9 Feb 1999 09:23:16 -0800 (PST) (envelope-from billg@cyberwar.com) Received: from zippy (zippy.cyberwar.com [206.88.128.80]) by outland.cyberwar.com (8.9.2/8.9.2) with SMTP id MAA26267 for ; Tue, 9 Feb 1999 12:23:10 -0500 (EST) Message-Id: <4.1.19990209121439.0094ff10@pop.cyberwar.com> X-Sender: billg@pop.cyberwar.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Tue, 09 Feb 1999 12:20:37 -0500 To: freebsd-scsi@FreeBSD.ORG From: Bill G Subject: DPT PM3334UW reboot hangs Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am having trouble with my DPT SmartRaidIV PM3334UW raid controller on FreeBSD 3.0 and later. I am currently running FreeBSD-3.1-BETA cvsup'd on 2/9/99...The problem is that whenever I reboot the machine, it hangs on the DPT bios 'Waiting for adapter'...If I walk over to the machine and hit the reset button it comes up fine...any ideas? Thanks, Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 9 14:25:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16526 for freebsd-scsi-outgoing; Tue, 9 Feb 1999 14:25:52 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from partners.partners-dsi.com (partners.partners-dsi.com [38.240.152.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16510; Tue, 9 Feb 1999 14:25:48 -0800 (PST) (envelope-from daren@partners-dsi.com) Received: from rio (rio [38.240.152.202]) by partners.partners-dsi.com (8.9.1/8.9.1) with SMTP id OAA05806; Tue, 9 Feb 1999 14:27:14 -0800 (PST) Message-ID: <002f01be547a$4c5d9fa0$ca98f026@partnersdsi.com> From: "Daren Sefcik" To: , Subject: LVD Support?? Date: Tue, 9 Feb 1999 14:19:42 -0800 X-Mailer: Microsoft Outlook Express 5.00.0810.800 X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.0810.800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is there any support for the Adaptec 2940U2W or similar LVD controller yet for FreeBSD3.0?? (looking to get the 80MB MByte/sec or so) Daren To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 9 14:47:11 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA19327 for freebsd-scsi-outgoing; Tue, 9 Feb 1999 14:47:11 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dorifer.heim3.tu-clausthal.de (dorifer.heim3.tu-clausthal.de [139.174.243.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA19321 for ; Tue, 9 Feb 1999 14:47:07 -0800 (PST) (envelope-from olli@dorifer.heim3.tu-clausthal.de) Received: (from olli@localhost) by dorifer.heim3.tu-clausthal.de (8.8.8/8.8.8) id XAA16740 for freebsd-scsi@FreeBSD.ORG; Tue, 9 Feb 1999 23:47:00 +0100 (CET) (envelope-from olli) Date: Tue, 9 Feb 1999 23:47:00 +0100 (CET) From: Oliver Fromme Message-Id: <199902092247.XAA16740@dorifer.heim3.tu-clausthal.de> To: freebsd-scsi@FreeBSD.ORG Subject: Re: LVD Support?? Newsgroups: list.freebsd-scsi Organization: Administration Heim 3 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Newsreader: TIN [version 1.2 RZTUC(3) PL2] Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Daren Sefcik wrote in list.freebsd-scsi: > Is there any support for the Adaptec 2940U2W > or similar LVD controller yet for FreeBSD3.0?? > (looking to get the 80MB MByte/sec or so) Excerpt from a dmesg output here: ahc0: rev 0x00 int a irq 9 on pci0.6.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da2: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) This is an ASUS P2B-LS mainboard with onboard Adaptec U2W support, with a bunch of IBM U2W/LVD disks. Works like a charm (FreeBSD 3.0-stable). Regards Oliver -- Oliver Fromme, Leibnizstr. 18/61, 38678 Clausthal, Germany (Info: finger userinfo:olli@dorifer.heim3.tu-clausthal.de) "In jedem Stück Kohle wartet ein Diamant auf seine Geburt" (Terry Pratchett) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 9 17:06:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA10970 for freebsd-scsi-outgoing; Tue, 9 Feb 1999 17:06:44 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ppc1.cybertime.ch (ppc1.cybertime.ch [194.191.120.136]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA10946 for ; Tue, 9 Feb 1999 17:06:40 -0800 (PST) (envelope-from pajarola@cybertime.ch) Received: from tiamat.dlc.cybertime.ch (tiamat.dlc.cybertime.ch [194.191.120.143]) by ppc1.cybertime.ch (8.9.2/8.9.2) with SMTP id CAA05358 for ; Wed, 10 Feb 1999 02:06:26 +0100 Message-Id: <3.0.32.19990210020627.00adc4b0@shrike.overmind.ch> X-Sender: pajarola@shrike.overmind.ch X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 10 Feb 1999 02:06:32 +0100 To: freebsd-scsi@FreeBSD.ORG From: Rico Pajarola Subject: HP Disk Array Controller Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone know what a 'HP Disk Array Controller (DAC) PCI Fast Wide SCSI2' is, and whether any free OS supports it? It was in a HP Netserver LD Pro which was bought in 1997, and I have the chance to get it in exchange for a 2940UW (I guess that's a good trade for me)... I know it's supported by SCO, but I'd rather use FreeBSD or at least another Free OS. regards Rico -- An NT server can be run by an idiot, and usually is. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 10 12:36:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16090 for freebsd-scsi-outgoing; Wed, 10 Feb 1999 12:36:21 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16074 for ; Wed, 10 Feb 1999 12:36:19 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id PAA08299 for ; Wed, 10 Feb 1999 15:36:14 -0500 (EST) Date: Wed, 10 Feb 1999 15:36:14 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: freebsd-scsi@FreeBSD.ORG Subject: compaq raid controller 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 noticed there is a driver available for Compaq's raid cards, but it's not part of the distribution. Is anyone using this, and if so, how has it been working? Any plans to roll it into distribution? Thanks, Charles --- Charles Sprickman spork@super-g.com --- "...there's no idea that's so good you can't ruin it with a few well-placed idiots." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 10 13:07:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA19262 for freebsd-scsi-outgoing; Wed, 10 Feb 1999 13:07:14 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA19254 for ; Wed, 10 Feb 1999 13:07:07 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id OAA23640; Wed, 10 Feb 1999 14:06:53 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902102106.OAA23640@panzer.plutotech.com> Subject: Re: compaq raid controller In-Reply-To: from spork at "Feb 10, 1999 3:36:14 pm" To: spork@super-g.com (spork) Date: Wed, 10 Feb 1999 14:06:53 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org spork wrote... > Hi, > > I noticed there is a driver available for Compaq's raid cards, but it's > not part of the distribution. Is anyone using this, and if so, how has it > been working? Any plans to roll it into distribution? Really? Where? Is it CAM or non-CAM? Is the copyright "okay" by FreeBSD standards? Are there any intellectual property issues with it? (I think I remember it being discussed here on -scsi before, but I can't recall much about it.) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 10 13:52:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA23951 for freebsd-scsi-outgoing; Wed, 10 Feb 1999 13:52:01 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA23932 for ; Wed, 10 Feb 1999 13:51:59 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id QAA15509; Wed, 10 Feb 1999 16:51:24 -0500 (EST) Date: Wed, 10 Feb 1999 16:51:24 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: compaq raid controller In-Reply-To: <199902102106.OAA23640@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org While I was going through the mail archives, I saw it existed at least as long ago as 1996. The gentleman that maintains it has a web page at http://www.doc.ic.ac.uk/~md/ida. I'm assuming it's not CAM :( As for the copyright, I see none whatsoever up top. Thanks, Charles --- Charles Sprickman spork@super-g.com --- On Wed, 10 Feb 1999, Kenneth D. Merry wrote: > spork wrote... > > Hi, > > > > I noticed there is a driver available for Compaq's raid cards, but it's > > not part of the distribution. Is anyone using this, and if so, how has it > > been working? Any plans to roll it into distribution? > > Really? Where? Is it CAM or non-CAM? Is the copyright "okay" by FreeBSD > standards? Are there any intellectual property issues with it? > > (I think I remember it being discussed here on -scsi before, but I can't > recall much about it.) > > Ken > -- > Kenneth Merry > ken@plutotech.com > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 10 15:02:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03100 for freebsd-scsi-outgoing; Wed, 10 Feb 1999 15:02:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03059 for ; Wed, 10 Feb 1999 15:02:32 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id QAA24290; Wed, 10 Feb 1999 16:02:20 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902102302.QAA24290@panzer.plutotech.com> Subject: Re: compaq raid controller In-Reply-To: from spork at "Feb 10, 1999 4:51:24 pm" To: spork@super-g.com (spork) Date: Wed, 10 Feb 1999 16:02:20 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org spork wrote... > On Wed, 10 Feb 1999, Kenneth D. Merry wrote: > > > spork wrote... > > > Hi, > > > > > > I noticed there is a driver available for Compaq's raid cards, but it's > > > not part of the distribution. Is anyone using this, and if so, how has it > > > been working? Any plans to roll it into distribution? > > > > Really? Where? Is it CAM or non-CAM? Is the copyright "okay" by FreeBSD > > standards? Are there any intellectual property issues with it? > > > > (I think I remember it being discussed here on -scsi before, but I can't > > recall much about it.) > While I was going through the mail archives, I saw it existed at least as > long ago as 1996. The gentleman that maintains it has a web page at > http://www.doc.ic.ac.uk/~md/ida. > > I'm assuming it's not CAM :( > > As for the copyright, I see none whatsoever up top. > > Thanks, > > Charles > > --- > Charles Sprickman > spork@super-g.com In this case, it doesn't depend on CAM at all. It is a standalone disk driver, like the IDE driver and a couple of other drivers out there. He has a version for FreeBSD 3.0, which I imagine would probably work fine with -stable or -current at this point. You're right, there is no copyright. Of course, without a copyright, we can't distribute it. We'd also probably need to make sure there aren't any intellectual property concerns with the driver. (The author would probably have an idea whether or not that would be a problem.) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 10 17:46:55 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA27000 for freebsd-scsi-outgoing; Wed, 10 Feb 1999 17:46:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA26978 for ; Wed, 10 Feb 1999 17:46:34 -0800 (PST) (envelope-from shimon@simon-shapiro.org) Received: (qmail 90049 invoked by uid 1000); 11 Feb 1999 02:52:37 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <4.1.19990209121439.0094ff10@pop.cyberwar.com> Date: Wed, 10 Feb 1999 21:52:37 -0500 (EST) X-Face: (&r=uR0&yvh>h^ZL4"-TH61PD}/|Y'~58Z# Gz&BK'&uLAf:2wLb~L7YcWfau{;N(#LR2)\i.l8'ZqVhv~$rNx$]Om6Sv36S'\~5m/U'"i/L)&t$R0&?,)tm0l5xZ!\hZU^yMyCdt!KTcQ376cCkQ^Q_n.GH;Dd-q+ O51^+.K-1Kq?WsP9;cw-Ki+b.iY-5@3!YB5{I$h;E][Xlg*sPO61^5=:5k)JdGet,M|$"lq!1!j_>? $0Yc? Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Bill G Subject: RE: DPT PM3334UW reboot hangs Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Bill G, On 09-Feb-99 you wrote: > > I am having trouble with my DPT SmartRaidIV PM3334UW raid controller on > FreeBSD 3.0 and later. I am currently running FreeBSD-3.1-BETA cvsup'd > on 2/9/99...The problem is that whenever I reboot the machine, it hangs > on the DPT bios 'Waiting for adapter'...If I walk over to the machine > and hit the reset button it comes up fine...any ideas? Known problem. The code in the kernel that is supposed to actually send a reset to the PCI bus does not. It is quite possible that the BIOS on the Motherboard gets the correct call from the kernel, but does not actually go to the PCI bus to reset it all. the DPT driver, at shutdown shuts down the DPT. this is done to ensure that all caches are flushed, etc. Failing to do that may cause up to 64MB of disk WRITEs to not go to disk and trash numerous filessystems. If you are brave (unwise?), you can try the following (in sys/dev/dpt/dpt_scsi.c): Comment out the entire contents of the function dptshutdown. Build a kernel and see if this cures the ``hang''. PLEASE NOTE THE FOLLOWING: IT IS ALMOST CERTAIN THAT THIS PROCEDURE WILL CAUSE SEVERE DATA LOSS AND IRREVERSIBLE DAMAGE TO YOUR FILESYSTEMS!!! Sincerely, Simon Shapiro Research Fellow, Office of Technology ShapiroS@MindSpring.com MindSpring Enterprises, Inc. 404.815.0770 ext. 2057 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 11 12:34:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12930 for freebsd-scsi-outgoing; Thu, 11 Feb 1999 12:34:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12920 for ; Thu, 11 Feb 1999 12:34:07 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id NAA30231; Thu, 11 Feb 1999 13:33:49 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902112033.NAA30231@panzer.plutotech.com> Subject: Re: 2.2.7/3.0-STABLE: tagged command queueing && poor write performance In-Reply-To: <19990211203455.A19293@titan.klemm.gtn.com> from Andreas Klemm at "Feb 11, 1999 8:34:56 pm" To: andreas@klemm.gtn.com (Andreas Klemm) Date: Thu, 11 Feb 1999 13:33:49 -0700 (MST) Cc: gibbs@pluto.plutotech.com, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andreas: > I installed today a self made FreeBSD 3.0 SNAPSHOT from 990203 > on a HP Pentium II, 450 MHz machine, 128 MB RAM. > > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 40.0MB/s transfers (20.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) > Everything went fine and I was glad until measuring the SCSI > disk performance using bonnie, which showed very poor values > for write performance: I think I know what the problem is. See below... > -------Sequential Output-------- ---Sequential Input-- --Random-- > -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- > Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU > 200 2323 10.2 2504 3.2 2477 3.8 12545 54.7 12654 10.4 211.2 2.1 > 200 2377 10.4 1672 2.1 2502 3.9 11887 51.8 12003 10.0 211.9 2.1 > > First I thought it's due to the NCR controller. HP uses the > Symbios Logic Conbi controller, which has Fast Ethernet and > NCR SCSI on the card. But using an AHA 2940UW didn't solve > the problem. I doubt the controller would make a huge difference. The NCR controllers, especially the newer ones, have enough performance to handle your disk drive. > After installing FreeBSD 2.2.7 everything was fine, until I > build a custom kernel with Tagged Command Queuing. > Using Tagged Command Queuing the write performance decreased > from 12MB/sec to about 4 MB/sec !!! Turning off tagged queueing probably disabled most of the effects of the disk's write cache. See below for an explanation... > Stefan Esser told me I should use "iostat 1" to see, how many > MB/sec and transactions are reached. You see very little of > both when using tagged command queuing: > > These are the values when bonnie is doing buffered (intelligent) > write (200 MB). > > tty fd0 da0 sa0 cpu > tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id > 1 51 0.00 0 0.00 14.19 104 1.45 0.00 0 0.00 2 0 1 0 96 > 0 231 0.00 0 0.00 54.09 79 4.16 0.00 0 0.00 0 0 10 2 88 > 0 76 0.00 0 0.00 8.49 113 0.94 0.00 0 0.00 0 0 0 2 98 > 0 76 0.00 0 0.00 9.02 109 0.96 0.00 0 0.00 0 0 0 0100 > 0 76 0.00 0 0.00 8.50 111 0.92 0.00 0 0.00 0 0 1 2 98 > 0 76 0.00 0 0.00 18.45 106 1.91 0.00 0 0.00 1 0 11 0 88 > 0 0 0.00 0 0.00 44.89 84 3.69 0.00 0 0.00 0 0 0 0100 > 0 0 0.00 0 0.00 8.00 113 0.88 0.00 0 0.00 0 0 0 0100 > 0 0 0.00 0 0.00 8.00 111 0.87 0.00 0 0.00 0 0 0 0100 > 0 0 0.00 0 0.00 8.00 111 0.87 0.00 0 0.00 0 0 0 0100 > 0 0 0.00 0 0.00 9.00 111 0.97 0.00 0 0.00 0 0 0 0100 > 0 455 0.00 0 0.00 29.04 92 2.61 0.00 0 0.00 0 0 9 0 91 > 0 76 0.00 0 0.00 24.00 97 2.27 0.00 0 0.00 0 0 0 0100 > 0 76 0.00 0 0.00 8.00 113 0.88 0.00 0 0.00 0 0 0 0100 > 0 76 0.00 0 0.00 9.02 109 0.96 0.00 0 0.00 0 0 0 1 99 > 0 76 0.00 0 0.00 23.12 110 2.48 0.00 0 0.00 0 0 12 0 88 Yep, I've seen I/O patterns like that before... > We have the theory, that 64 tags are too many for the Seagate Disk. I don't think that's really the problem. > Is there a possibility to reduce the number of tags / disk using > syscontrol or camcontrol ? Or where can I reduce the maximum number > of tags for this specific harddisk ? The only way to reduce the number of tags for a given hard disk is to put a quirk entry in the transport layer. (sys/cam/cam_xpt.c) > Stefan told me, that it might have a negative impact on performance, > if so many tags are in use, because the harddisk hardly will service > other requests, if bonnie writes to it like hell ... > > Other observations are, that if tagged command queuing is active > and I start bonnie, I nearly can't login to a second vty. And > commands are delayed for about 10-15 seconds !!! That is, I think, more of a problem with CAM's queueing algorithms. Justin has talked of tuning them, or perhaps the way the upper layer code queues things. > If this theory should be right, that too many tags are useful > or only for special devices ... how can we handle this ??? > > Could we create a kernel option like > CAM_TAGS_MAX 16 > Or could it be tuneable via syscontrol or camcontrol ??? > > For now I'm only looking for a possibility to turn of tagged > command queuing on a 3.0-STABLE system or to reduce the number > of tags .... where is the hook for "rogue" entries .... and > how would an entry be, to reduce tags to 16 or so .... You can do it in cam_xpt.c. > In the attachement more infos .... kernel config file, messages > file, iostat output during the various phases of bonnie, and > an dumpfs of the /home filesys, where I made the bonnie bench > on. I did it on a 5 GB large virgin fs, the last 5 GB of the 9 GB > harddisk ... I think you're probably barking up the wrong tree here. The problem, I think, has to do with write caching, both in FreeBSD and on the disk itself. I have found that with or without softupdates, FreeBSD's write caching policy, when combined with write caching on a disk, can sometimes produce erratic performance for sequential writes. The solution is to disable write caching for that disk, and see if that helps you any. To disable write caching, edit mode page 8: camcontrol modepage -v -n da -u 0 -m 0x8 -e Change the "WCE" bit from 1 to 0, and save it. In my experience, this will definitely increase the throughput you get to the disk for sequential writes. For many of my machines, though, I leave write caching turned on, since I think that in the general case write caching on the disk will help random I/O performance. I am assuming here that your disk has write caching turned on. Many disk drive vendors ship with it turned on. (Seagate does, I think. IBM may not, but I think Quantum does.) If your disk doesn't have write caching enabled, then you've probably got some other problem. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 11 12:55:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA16170 for freebsd-scsi-outgoing; Thu, 11 Feb 1999 12:55:57 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from picalon.gun.de (picalon.gun.de [194.77.0.18] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA16130; Thu, 11 Feb 1999 12:55:35 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id VAA27410; Thu, 11 Feb 1999 21:55:27 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id VAA30353; Thu, 11 Feb 1999 21:55:08 +0100 (CET) (envelope-from andreas) Date: Thu, 11 Feb 1999 21:55:07 +0100 From: Andreas Klemm To: "Kenneth D. Merry" Cc: Andreas Klemm , gibbs@pluto.plutotech.com, scsi@FreeBSD.ORG, se@FreeBSD.ORG Subject: Re: 2.2.7/3.0-STABLE: tagged command queueing && poor write performance Message-ID: <19990211215507.B24839@titan.klemm.gtn.com> References: <19990211203455.A19293@titan.klemm.gtn.com> <199902112033.NAA30231@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199902112033.NAA30231@panzer.plutotech.com>; from Kenneth D. Merry on Thu, Feb 11, 1999 at 01:33:49PM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-STABLE SMP Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Kenneth, first of all, thanks for your quick response. On Thu, Feb 11, 1999 at 01:33:49PM -0700, Kenneth D. Merry wrote: > > > > Other observations are, that if tagged command queuing is active > > and I start bonnie, I nearly can't login to a second vty. And > > commands are delayed for about 10-15 seconds !!! > > That is, I think, more of a problem with CAM's queueing algorithms. Justin > has talked of tuning them, or perhaps the way the upper layer code queues > things. I'll see if this effect goes away with turning off the disks cache... > You can do it in cam_xpt.c. Thanks, already found it. When asking this, I looked into cam/scsi and disn't find entries for that. Found it later one dir above. > The solution is to disable write caching for that disk, and see if that > helps you any. To disable write caching, edit mode page 8: > > camcontrol modepage -v -n da -u 0 -m 0x8 -e > > Change the "WCE" bit from 1 to 0, and save it. Ok, thanks, will try it. > In my experience, this will definitely increase the throughput you get to > the disk for sequential writes. For many of my machines, though, I leave > write caching turned on, since I think that in the general case write > caching on the disk will help random I/O performance. > > I am assuming here that your disk has write caching turned on. Many disk > drive vendors ship with it turned on. (Seagate does, I think. IBM may > not, but I think Quantum does.) If your disk doesn't have write caching > enabled, then you've probably got some other problem. I already looked for this. It's true, the disk has write cache on. I'll try disabling the cache ! Best regards Andreas /// -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 11 16:00:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA08169 for freebsd-scsi-outgoing; Thu, 11 Feb 1999 16:00:13 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from unter.encoding.com ([216.32.0.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA08162 for ; Thu, 11 Feb 1999 16:00:12 -0800 (PST) (envelope-from led@unter.encoding.com) Received: (from led@localhost) by unter.encoding.com (8.8.8/8.9.1) id AAA24356 for scsi@freebsd.org; Fri, 12 Feb 1999 00:00:11 GMT (envelope-from led) Date: Fri, 12 Feb 1999 00:00:11 GMT From: led Message-Id: <199902120000.AAA24356@unter.encoding.com> To: scsi@FreeBSD.ORG Subject: Compaq Proliant 1850R Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My vendor can't tell me what chipset compaq's SCSI adapters use and they are not mentioned in the FreeBSD doc I have; Are they supported? Thanks, Lawrence Doan led@encoding.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 11 17:08:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19081 for freebsd-scsi-outgoing; Thu, 11 Feb 1999 17:08:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from unter.encoding.com ([216.32.0.8]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA19060 for ; Thu, 11 Feb 1999 17:08:04 -0800 (PST) (envelope-from led@unter.encoding.com) Received: (from led@localhost) by unter.encoding.com (8.8.8/8.9.1) id BAA25425 for scsi@freebsd.org; Fri, 12 Feb 1999 01:07:58 GMT (envelope-from led) Date: Fri, 12 Feb 1999 01:07:58 GMT From: led Message-Id: <199902120107.BAA25425@unter.encoding.com> To: scsi@FreeBSD.ORG Subject: Compaq Proliant Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org My vendor came through; the internal SCSI is based upon the Symbios/NCR 53c876, and the optional extra PCI controllers are based on the 53c879. The former is reported by symbios to work identically to the FreeBSD supported 53c875. I have found no mention of the 53c879 though they seem to be of the same family. -L To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 11 17:21:26 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20844 for freebsd-scsi-outgoing; Thu, 11 Feb 1999 17:21:26 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20814 for ; Thu, 11 Feb 1999 17:21:16 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA17624; Fri, 12 Feb 1999 11:51:13 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.2/8.9.0) id LAA92383; Fri, 12 Feb 1999 11:51:13 +1030 (CST) Date: Fri, 12 Feb 1999 11:51:12 +1030 From: Greg Lehey To: led Cc: scsi@FreeBSD.ORG Subject: Re: Compaq Servers and FreeBSD Message-ID: <19990212115112.P71962@freebie.lemis.com> References: <199902120000.AAA24356@unter.encoding.com> <36C305EE.1DE98C12@sportingnews.com> <19990212113728.N71962@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <19990212113728.N71962@freebie.lemis.com>; from Greg Lehey on Fri, Feb 12, 1999 at 11:37:28AM +1030 WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Friday, 12 February 1999 at 0:00:11 +0000, led wrote: > > My vendor can't tell me what chipset compaq's SCSI adapters use > and they are not mentioned in the FreeBSD doc I have; Are they supported? You're the second person to ask this question today. Here's what I answered to the last one: On Friday, 12 February 1999 at 11:37:28 +1030, Greg Lehey wrote: > On Thursday, 11 February 1999 at 11:31:42 -0500, Keith Camden wrote: >> We're thinking about upgrading a FreeBSD box that we have to a new >> computer. We have standardized on Compaq servers for our file servers in >> our organization, and I'm wondering if FreeBSD will support the built-in >> SCSI and Ethernet on the Compaq server. >> >> The server that we are looking at is a rack mount Compaq 1850R with a >> Compaq Netelligent 10/100 TX embedded UTP Controller with full duplex >> Ethernet support and a Compaq Integrated Dual Channel Wide-Ultra SCSI-3 >> Controller. >> >> Will FreeBSD support the Compaq Ethernet card and SCSI controller? >> >> I've checked the FreeBSD support documentation on Ethernet Cards and >> Disk Controllers, and these cards do not appear. > >> From the 3.0 release information: > > (Ethernet boards) > > Texas Instruments ThunderLAN PCI NICs, including the following: > Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 Dual-Port > Compaq Netelligent 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, 10/100 TX UTP > Compaq NetFlex 3P, 3P Integrated, 3P w/ BNC > > There's no mention of Compaq SCSI host adaptors there. Looking at my > saved messages, I find: > >> I believe all of the Compaq SCSI adaptors (except possible the RAID >> ones) are Symbios/NCR chipsets. At least out Proliant 2500 is, and >> there is just one Compaq SCSI HAM driver for Netware, so it must cover >> all the Compaq cards. >> >> -Dan Nelson >> dnelson@emsphone.com > >> The disk controller is a Symbios 53c876 >> (checked by looking at the actual chip), which appears as two 53c875's. >> Below is the boot -v output from 2.2.7. >> >> Anybody have an idea of why PCI probing fails in 3.0-19981006-BETA on this >> Compaq system? Anything more I can do to debug it? (Might try to install >> 3.0 "by hand" tomorrow - this is feasible since I have a running 2.2.7 >> system now, and plenty of disk space). >> >> Steinar Haug, Nethelp consulting, sthaug@nethelp.no >> ---------------------------------------------------------------------- >> Calibrating clock(s) ... i586 clock: 332826782 Hz, i8254 clock: 1193275 Hz >> CLK_USE_I8254_CALIBRATION not specified - using default frequency >> CLK_USE_I586_CALIBRATION not specified - using old calibration method >> CPU: Pentium II (quarter-micron) (332.80-MHz 686-class CPU) >> Origin = "GenuineIntel" Id = 0x651 Stepping=1 >> Features=0x183fbff,,MMX,> >> real memory = 603979776 (589824K bytes) >> Physical memory chunk(s): >> 0x00001000 - 0x0009efff, 647168 bytes (158 pages) >> 0x00221000 - 0x23ffdfff, 601739264 bytes (146909 pages) >> avail memory = 589602816 (575784K bytes) >> eisa0: >> Probing for devices on the EISA bus >> pcibus_setup(1): mode 1 addr port (0x0cf8) is 0x00000000 >> pcibus_setup(1a): mode1res=0x80000000 (0x80000000) >> pcibus_check: device 0 is there (id=00051166) >> Probing for devices on PCI bus 0: >> configuration mode 1 allows 32 devices. >> chip0 rev 3 on pci0:0:0 >> vga0 rev 34 int a irq ?? on pci0:6:0 >> mapreg[10] type=0 addr=c5000000 size=1000000. >> chip1 rev 7 on pci0:15:0 >> chip2 rev 3 on pci0:17:0 >> pci0: uses 16777216 bytes of memory from c5000000 upto c5ffffff. >> Probing for devices on PCI bus 1: >> ncr0 rev 20 int a irq 9 on pci1:4:0 >> mapreg[10] type=1 addr=00005000 size=0100. >> mapreg[14] type=0 addr=c6ffdf00 size=0100. >> mapreg[18] type=0 addr=c6fff000 size=1000. >> reg20: virtual=0xf616ef00 physical=0xc6ffdf00 size=0x100 >> reg24: virtual=0xf616f000 physical=0xc6fff000 size=0x1000 >> ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo >> ncr0: single-ended, open drain IRQ driver, using on-chip SRAM >> ncr0: restart (scsi reset). >> ncr0 scanning for targets 0..6 and 8..15 (V2 pl24 96/12/14) >> ncr0 waiting for scsi devices to settle >> (ncr0:0:0): WIDE SCSI (16 bit) enabled(ncr0:0:0): 10.0 MB/s (200 ns, offset 15) >> (ncr0:0:0): "COMPAQ HD0093172C 3207" type 0 fixed SCSI 2 >> sd0(ncr0:0:0): Direct-Access >> sd0(ncr0:0:0): WIDE SCSI (16 bit) enabled >> sd0(ncr0:0:0): 40.0 MB/s (50 ns, offset 15) >> 8678MB (17773500 512 byte sectors) >> sd0(ncr0:0:0): with 6962 cyls, 12 heads, and an average 212 sectors/track >> (ncr0:1:0): WIDE SCSI (16 bit) enabled(ncr0:1:0): 10.0 MB/s (200 ns, offset 15) >> (ncr0:1:0): "COMPAQ HD0093172C 3207" type 0 fixed SCSI 2 >> sd1(ncr0:1:0): Direct-Access >> sd1(ncr0:1:0): WIDE SCSI (16 bit) enabled >> sd1(ncr0:1:0): 40.0 MB/s (50 ns, offset 15) >> 8678MB (17773500 512 byte sectors) >> sd1(ncr0:1:0): with 6962 cyls, 12 heads, and an average 212 sectors/track >> (ncr0:4:0): WIDE SCSI (16 bit) enabled(ncr0:4:0): 10.0 MB/s (200 ns, offset 15) >> (ncr0:4:0): "COMPAQ HD0093172C 3207" type 0 fixed SCSI 2 >> sd2(ncr0:4:0): Direct-Access >> sd2(ncr0:4:0): WIDE SCSI (16 bit) enabled >> sd2(ncr0:4:0): 40.0 MB/s (50 ns, offset 15) >> 8678MB (17773500 512 byte sectors) >> sd2(ncr0:4:0): with 6962 cyls, 12 heads, and an average 212 sectors/track >> (ncr0:5:0): WIDE SCSI (16 bit) enabled(ncr0:5:0): 10.0 MB/s (200 ns, offset 15) >> (ncr0:5:0): "COMPAQ HD0093172C 3207" type 0 fixed SCSI 2 >> sd3(ncr0:5:0): Direct-Access >> sd3(ncr0:5:0): WIDE SCSI (16 bit) enabled >> sd3(ncr0:5:0): 40.0 MB/s (50 ns, offset 15) >> 8678MB (17773500 512 byte sectors) >> sd3(ncr0:5:0): with 6962 cyls, 12 heads, and an average 212 sectors/track >> ncr1 rev 20 int b irq 10 on pci1:4:1 >> mapreg[10] type=1 addr=00005400 size=0100. >> mapreg[14] type=0 addr=c6ffde00 size=0100. >> mapreg[18] type=0 addr=c6ffe000 size=1000. >> reg20: virtual=0xf6170e00 physical=0xc6ffde00 size=0x100 >> reg24: virtual=0xf6171000 physical=0xc6ffe000 size=0x1000 >> ncr1: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo >> ncr1: single-ended, open drain IRQ driver, using on-chip SRAM >> ncr1: restart (scsi reset). >> ncr1 scanning for targets 0..6 and 8..15 (V2 pl24 96/12/14) >> ncr1 waiting for scsi devices to settle > > In general, Compaq systems seem to cause problems. They're often not > quite compatible, and we hear of an above-average number of problems > with them. It would be a good idea to try booting a boot floppy and > seeing what it finds. > > Greg > -- > See complete headers for address, home page and phone numbers > finger grog@lemis.com for PGP public key > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 11 17:30:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21921 for freebsd-scsi-outgoing; Thu, 11 Feb 1999 17:30:07 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21908 for ; Thu, 11 Feb 1999 17:30:03 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.1/8.9.1) id RAA11634; Thu, 11 Feb 1999 17:30:14 -0800 (PST) (envelope-from ulf) Message-ID: <19990211173014.B5746@TelcoSucks.org> Date: Thu, 11 Feb 1999 17:30:14 -0800 From: Ulf Zimmermann To: led , scsi@FreeBSD.ORG Subject: Re: Compaq Proliant Reply-To: ulf@Alameda.net References: <199902120107.BAA25425@unter.encoding.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <199902120107.BAA25425@unter.encoding.com>; from led on Fri, Feb 12, 1999 at 01:07:58AM +0000 Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.0-19980930-BETA Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Feb 12, 1999 at 01:07:58AM +0000, led wrote: > > My vendor came through; the internal SCSI is based > upon the Symbios/NCR 53c876, and the optional extra > PCI controllers are based on the 53c879. The former > is reported by symbios to work identically to the FreeBSD > supported 53c875. I have found no mention of the 53c879 > though they seem to be of the same family. Search the mailing list archives. I posted that FreeBSD 3.0R works fine on the Proliant 1850R. > > -L > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 11 17:44:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA23638 for freebsd-scsi-outgoing; Thu, 11 Feb 1999 17:44:49 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA23625 for ; Thu, 11 Feb 1999 17:44:46 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id SAA21039; Thu, 11 Feb 1999 18:44:36 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199902120144.SAA21039@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" cc: andreas@klemm.gtn.com (Andreas Klemm), gibbs@plutotech.com, scsi@FreeBSD.ORG Subject: Re: 2.2.7/3.0-STABLE: tagged command queueing && poor write performance In-reply-to: Your message of "Thu, 11 Feb 1999 13:33:49 MST." <199902112033.NAA30231@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Feb 1999 18:36:08 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Is there a possibility to reduce the number of tags / disk using >> syscontrol or camcontrol ? Or where can I reduce the maximum number >> of tags for this specific harddisk ? > >The only way to reduce the number of tags for a given hard disk is to put a >quirk entry in the transport layer. (sys/cam/cam_xpt.c) Camcontrol should be modified to allow a user to reduce or disable tags (and sync rates and wide transfers). The XPT function codes and ccb types are there to do this, they just need to be hooked up. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 11 18:52:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA03749 for freebsd-scsi-outgoing; Thu, 11 Feb 1999 18:52:01 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA03732 for ; Thu, 11 Feb 1999 18:51:58 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (tnt1-208-147-147-16.dialup.HiWAAY.net [208.147.147.16]) by mail.HiWAAY.net (8.9.1a/8.9.0) with ESMTP id UAA02202 for ; Thu, 11 Feb 1999 20:51:56 -0600 (CST) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.9.2/8.9.2) with ESMTP id UAA17736 for ; Thu, 11 Feb 1999 20:51:54 -0600 (CST) (envelope-from dkelly@nospam.hiwaay.net) Message-Id: <199902120251.UAA17736@nospam.hiwaay.net> X-Mailer: exmh version 2.0.2 2/24/98 To: scsi@FreeBSD.ORG From: David Kelly Subject: Re: 2.2.7/3.0-STABLE: tagged command queueing && poor write performance In-reply-to: Message from "Justin T. Gibbs" of "Thu, 11 Feb 1999 18:36:08 MST." <199902120144.SAA21039@pluto.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 11 Feb 1999 20:51:54 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Justin T. Gibbs" writes: > > Camcontrol should be modified to allow a user to reduce or disable tags > (and sync rates and wide transfers). The XPT function codes and ccb > types are there to do this, they just need to be hooked up. That would be nice as a recent install at work using an Asus MB w/ Adaptec built in, plus a Seagate ST19171W (? aw, heck, its a full height 3-1/2" 9G drive) produces a message "reducing tagged openings to 64" quickly/instantly followed by another dropping it to 63. Its quiet after that. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 00:37:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA08547 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 00:37:31 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from gjp.erols.com (alex-va-n008c079.moon.jic.com [206.156.18.89]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA08540 for ; Fri, 12 Feb 1999 00:37:28 -0800 (PST) (envelope-from gjp@gjp.erols.com) Received: from gjp.erols.com (localhost.erols.com [127.0.0.1]) by gjp.erols.com (8.9.1/8.8.7) with ESMTP id DAA61132 for ; Fri, 12 Feb 1999 03:37:26 -0500 (EST) (envelope-from gjp@gjp.erols.com) X-Mailer: exmh version 2.0.1 12/23/97 To: freebsd-scsi@FreeBSD.ORG From: "Gary Palmer" Subject: bad drive? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Feb 1999 03:37:26 -0500 Message-ID: <61128.918808646@gjp.erols.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I found the enclosed messages (appended after my sig) in /var/log/messages on a machine at work. I'm wondering if these imply a fixable error (e.g. bad termination) or if one of the drives is slowly dying? ahc0: rev 0x00 int a irq 11 on pci0.10.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs da1: Fixed Direct Access SCSI-2 device da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da1: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) This is from the 19981216 SNAP code. Thanks, Gary -- Gary Palmer FreeBSD Core Team Member FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info Feb 11 12:46:39 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x1c - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0xc Feb 11 12:46:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 12:46:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 12:46:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 12:46:40 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 12:46:40 virtual /kernel: SEQADDR == 0x157 Feb 11 12:47:39 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x2f - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 12:47:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 12:47:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 12:47:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 12:47:40 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 12:47:40 virtual /kernel: SEQADDR == 0x157 Feb 11 12:48:39 virtual /kernel: (da0:ahc0:0:0:0): SCB 0xc - timed out while idl e, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 12:48:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 12:50:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 12:50:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 12:50:40 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 12:50:40 virtual /kernel: SEQADDR == 0x157 Feb 11 12:50:40 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x35 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 12:50:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 12:50:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 12:50:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 12:50:40 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 12:50:40 virtual /kernel: SEQADDR == 0x157 Feb 11 12:50:40 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x29 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0xa Feb 11 12:50:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 12:50:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 12:50:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 12:50:40 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 12:50:40 virtual /kernel: SEQADDR == 0x157 Feb 11 18:01:41 virtual su: gjp to root on /dev/ttyp0 Feb 11 21:00:40 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x9 - timed out while idl e, LASTPHASE == 0x1, SEQADDR == 0xc Feb 11 21:21:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:41 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:41 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x7 - timed out while idl e, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:41 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:41 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x23 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:41 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:41 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x24 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:41 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:41 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x1c - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0xa Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:41 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:41 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x39 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:41 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:41 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x3a - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:41 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:41 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x1b - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0xa Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:41 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:41 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:41 virtual /kernel: Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x3c - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:41 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:41 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x10 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0xb Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:41 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:41 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:42 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): SCB 0xd - timed out while idl e, LASTPHASE == 0x1, SEQADDR == 0xc Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:42 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:42 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x1e - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): no lon Feb 11 21:21:42 virtual /kernel: ger in timeout, status = 353 Feb 11 21:21:42 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:42 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x2f - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:42 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:42 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x2c - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0xc Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:42 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:42 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x5 - timed out while idl e, LASTPHASE == 0x1, SEQADDR == 0xa Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:42 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:42 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): SCB 0xe - timed out while idl e, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Queuing Feb 11 21:21:42 virtual /kernel: a BDR SCB Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:42 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:42 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x3e - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:42 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:42 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x2b - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0xa Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:42 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:42 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x16 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0xc Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:42 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:42 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:42 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x Feb 11 21:21:43 virtual /kernel: 3b - timed out while idle, LASTPHASE == 0x1, SE QADDR == 0x9 Feb 11 21:21:43 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:43 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:43 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:43 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:43 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:43 virtual /kernel: (da0:ahc0:0:0:0): SCB 0xa - timed out while idl e, LASTPHASE == 0x1, SEQADDR == 0xb Feb 11 21:21:43 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:43 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:43 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:43 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:43 virtual /kernel: SEQADDR == 0x157 Feb 11 21:21:43 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x37 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0xb Feb 11 21:21:43 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:21:43 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:21:43 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:21:43 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:21:43 virtual /kernel: SEQADDR == 0x157 Feb 11 21:22:40 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x29 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0xb Feb 11 21:22:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:22:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:22:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:22:40 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:22:41 virtual /kernel: SEQADDR == 0x157 Feb 11 21:23:40 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x26 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 21:23:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:23:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:23:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:23:40 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:23:41 virtual /kernel: SEQADDR == 0x157 Feb 11 21:24:40 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x35 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0xb Feb 11 21:24:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:24:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:24:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:24:41 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:24:41 virtual /kernel: SEQADDR == 0x157 Feb 11 21:25:40 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x11 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 21:25:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:25:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:25:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:25:40 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:25:41 virtual /kernel: SEQADDR == 0x157 Feb 11 21:26:40 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x36 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0xa Feb 11 21:26:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:26:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:26:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:26:41 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:26:41 virtual /kernel: SEQADDR == 0x157 Feb 11 21:27:40 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x28 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0xb Feb 11 21:28:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:28:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:28:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:28:41 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:28:41 virtual /kernel: SEQADDR == 0x157 Feb 11 21:28:41 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x21 - timed out while id le, LASTPHASE == 0x1, SEQADDR == 0x9 Feb 11 21:28:41 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB Feb 11 21:28:41 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message Sent Feb 11 21:28:41 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, status = 353 Feb 11 21:28:41 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 Feb 11 21:28:41 virtual /kernel: SEQADDR == 0x157 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 03:35:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA25652 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 03:35:13 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from bayer2.bayer-ag.de (bayer2.bayer-ag.de [194.120.191.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA25608 for ; Fri, 12 Feb 1999 03:35:00 -0800 (PST) (envelope-from ANDREAS.KLEMM.AK@bayer-ag.de) From: ANDREAS.KLEMM.AK@bayer-ag.de Received: by bayer2.bayer-ag.de id MAA24813 (SMTP Gateway 3.0 for scsi@freebsd.org); Fri, 12 Feb 1999 12:34:58 +0100 Received: by bayer2.bayer-ag.de (Internal Mail Agent-2); Fri, 12 Feb 1999 12:34:58 +0100 Received: by bayer2.bayer-ag.de (Internal Mail Agent-1); Fri, 12 Feb 1999 12:34:58 +0100 To: " - (052)ken(a)plutotech.com" Cc: " - (052)scsi(a)FreeBSD.ORG" Subject: It%s not the write cache on 3.0-STABLE and not tagged comma Message-Id: <0006800008720961000002L012*@MHS> Date: Fri, 12 Feb 1999 12:34:36 +0100 Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id DAA25646 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi Ken, disabled write cache, same trafficpattern in iostat. Didn*%t cure the problem. Making a regue entry in cam, disabling tagged queuing completely didn*%t solve the problem as well. On 2.2.7 the latter (disabling tagged) solved it. What now ??? Andreas /// To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 05:58:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA13843 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 05:58:06 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA13837 for ; Fri, 12 Feb 1999 05:58:04 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id FAA17810; Fri, 12 Feb 1999 05:57:40 -0800 Date: Fri, 12 Feb 1999 05:57:40 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: ANDREAS.KLEMM.AK@bayer-ag.de cc: " - (052)ken(a)plutotech.com" , " - (052)scsi(a)FreeBSD.ORG" Subject: Re: It%s not the write cache on 3.0-STABLE and not tagged comma In-Reply-To: <0006800008720961000002L012*@MHS> 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 What was the problem? On Fri, 12 Feb 1999 ANDREAS.KLEMM.AK@bayer-ag.de wrote: > > Hi Ken, > > disabled write cache, same trafficpattern in iostat. Didn*%t cure the problem. > Making a regue entry in cam, disabling tagged queuing completely didn*%t > solve the problem as well. On 2.2.7 the latter (disabling tagged) solved it. > > What now ??? > > Andreas /// > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 07:58:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA28500 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 07:58:04 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA28495 for ; Fri, 12 Feb 1999 07:58:02 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id IAA34614; Fri, 12 Feb 1999 08:57:56 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902121557.IAA34614@panzer.plutotech.com> Subject: Re: It%s not the write cache on 3.0-STABLE and not tagged comma In-Reply-To: <0006800008720961000002L012*@MHS> from "ANDREAS.KLEMM.AK@bayer-ag.de" at "Feb 12, 1999 12:34:36 pm" To: ANDREAS.KLEMM.AK@bayer-ag.de Date: Fri, 12 Feb 1999 08:57:56 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ANDREAS.KLEMM.AK@bayer-ag.de wrote... > > Hi Ken, > > disabled write cache, same trafficpattern in iostat. Didn*%t cure the problem. > Making a regue entry in cam, disabling tagged queuing completely didn*%t > solve the problem as well. On 2.2.7 the latter (disabling tagged) solved it. > > What now ??? I dunno. It still sounds like write caching is somehow turned on. If it really is turned off (could you check it again?), I'm stumped for now. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 08:02:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29190 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 08:02:41 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29176 for ; Fri, 12 Feb 1999 08:02:27 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id JAA34641; Fri, 12 Feb 1999 09:02:18 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902121602.JAA34641@panzer.plutotech.com> Subject: Re: It%s not the write cache on 3.0-STABLE and not tagged comma In-Reply-To: from Matthew Jacob at "Feb 12, 1999 5:57:40 am" To: mjacob@feral.com Date: Fri, 12 Feb 1999 09:02:18 -0700 (MST) Cc: ANDREAS.KLEMM.AK@bayer-ag.de, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote... > > What was the problem? He is getting poor performance for sequential writes with a Seagate disk under CAM. Write throughput to the disk is fairly erratic. (i.e., lots of ups and downs) He has the problem under 2.2.7 with tagged queueing enabled, but not when he disables tagged queueing. The problem occurs under 3.0 with or without tagged queueing. I told him to disable write caching, since I have seen similar problems when write caching is enabled, but that didn't seem to fix the problem. Any ideas? Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 08:04:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29332 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 08:04:09 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29326 for ; Fri, 12 Feb 1999 08:04:06 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id IAA18542; Fri, 12 Feb 1999 08:03:52 -0800 Date: Fri, 12 Feb 1999 08:03:52 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Kenneth D. Merry" cc: ANDREAS.KLEMM.AK@bayer-ag.de, scsi@FreeBSD.ORG Subject: Re: It%s not the write cache on 3.0-STABLE and not tagged comma In-Reply-To: <199902121602.JAA34641@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is read performance okay? Also what's "poor"? On Fri, 12 Feb 1999, Kenneth D. Merry wrote: > Matthew Jacob wrote... > > > > What was the problem? > > He is getting poor performance for sequential writes with a Seagate disk > under CAM. Write throughput to the disk is fairly erratic. (i.e., lots of > ups and downs) > > He has the problem under 2.2.7 with tagged queueing enabled, but not when > he disables tagged queueing. The problem occurs under 3.0 with or > without tagged queueing. > > I told him to disable write caching, since I have seen similar problems > when write caching is enabled, but that didn't seem to fix the problem. > > Any ideas? > > Ken > -- > Kenneth Merry > ken@plutotech.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 08:10:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00371 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 08:10:36 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00361 for ; Fri, 12 Feb 1999 08:10:31 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id JAA34695; Fri, 12 Feb 1999 09:10:24 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902121610.JAA34695@panzer.plutotech.com> Subject: Re: It%s not the write cache on 3.0-STABLE and not tagged comma In-Reply-To: from Matthew Jacob at "Feb 12, 1999 8: 3:52 am" To: mjacob@feral.com Date: Fri, 12 Feb 1999 09:10:24 -0700 (MST) Cc: ANDREAS.KLEMM.AK@bayer-ag.de, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote... > > Is read performance okay? > Also what's "poor"? Read performance is fine. (about 12MB/sec) "poor" means between 1 and 3MB/sec. I'll forward you his original mail, I think it probably got nuked by Majordomo's message size filter. > On Fri, 12 Feb 1999, Kenneth D. Merry wrote: > > > Matthew Jacob wrote... > > > > > > What was the problem? > > > > He is getting poor performance for sequential writes with a Seagate disk > > under CAM. Write throughput to the disk is fairly erratic. (i.e., lots of > > ups and downs) > > > > He has the problem under 2.2.7 with tagged queueing enabled, but not when > > he disables tagged queueing. The problem occurs under 3.0 with or > > without tagged queueing. > > > > I told him to disable write caching, since I have seen similar problems > > when write caching is enabled, but that didn't seem to fix the problem. > > > > Any ideas? > > > > Ken > > -- > > Kenneth Merry > > ken@plutotech.com > > Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 08:11:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00456 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 08:11:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00445 for ; Fri, 12 Feb 1999 08:11:49 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id IAA18708; Fri, 12 Feb 1999 08:11:40 -0800 Date: Fri, 12 Feb 1999 08:11:40 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Kenneth D. Merry" cc: ANDREAS.KLEMM.AK@bayer-ag.de, scsi@FreeBSD.ORG Subject: Re: It%s not the write cache on 3.0-STABLE and not tagged comma In-Reply-To: <199902121610.JAA34695@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org No, it *just* arrived.... On Fri, 12 Feb 1999, Kenneth D. Merry wrote: > Matthew Jacob wrote... > > > > Is read performance okay? > > Also what's "poor"? > > Read performance is fine. (about 12MB/sec) "poor" means between 1 and > 3MB/sec. > > I'll forward you his original mail, I think it probably got nuked by > Majordomo's message size filter. > > > On Fri, 12 Feb 1999, Kenneth D. Merry wrote: > > > > > Matthew Jacob wrote... > > > > > > > > What was the problem? > > > > > > He is getting poor performance for sequential writes with a Seagate disk > > > under CAM. Write throughput to the disk is fairly erratic. (i.e., lots of > > > ups and downs) > > > > > > He has the problem under 2.2.7 with tagged queueing enabled, but not when > > > he disables tagged queueing. The problem occurs under 3.0 with or > > > without tagged queueing. > > > > > > I told him to disable write caching, since I have seen similar problems > > > when write caching is enabled, but that didn't seem to fix the problem. > > > > > > Any ideas? > > > > > > Ken > > > -- > > > Kenneth Merry > > > ken@plutotech.com > > > > > Ken > -- > Kenneth Merry > ken@plutotech.com > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 08:15:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA00879 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 08:15:36 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA00872 for ; Fri, 12 Feb 1999 08:15:33 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id JAA34748; Fri, 12 Feb 1999 09:15:27 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902121615.JAA34748@panzer.plutotech.com> Subject: Re: It%s not the write cache on 3.0-STABLE and not tagged comma In-Reply-To: from Matthew Jacob at "Feb 12, 1999 8:11:40 am" To: mjacob@feral.com Date: Fri, 12 Feb 1999 09:15:27 -0700 (MST) Cc: ANDREAS.KLEMM.AK@bayer-ag.de, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Jacob wrote... > > No, it *just* arrived.... Look at the headers closely. You will notice that it didn't go through FreeBSD.ORG, but rather it came from me. (I "bounced" it to you so the MIME stuff would get forwarded as well.) Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 10:17:40 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA14707 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 10:17:40 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA14690 for ; Fri, 12 Feb 1999 10:17:28 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from salomon.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id TAA06514 for ; Fri, 12 Feb 1999 19:17:23 +0100 (MET) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [146.180.31.23]) by salomon.siemens.de (8.9.3/8.9.3) with ESMTP id TAA17475 for ; Fri, 12 Feb 1999 19:17:25 +0100 (MET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id TAA25421 for ; Fri, 12 Feb 1999 19:17:25 +0100 (CET) Date: Fri, 12 Feb 1999 19:17:23 +0100 From: Andre Albsmeier To: freebsd-scsi@FreeBSD.ORG Subject: Is CAM slower than the old SCSI layer for JAZ drives? Message-ID: <19990212191723.A644@internal> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have made an odd observation. Copying a large file from my 100MBit net to a 2GB jaz, I noticed that 3.1-BETA took a lot more time than it used to under 2.2.8-STABLE. Exact (well, as exact as dd can be) measurements told me: 3.1-BETA: 135447409 bytes transferred in 178.638903 secs (758219 bytes/sec) 2.2.8-STABLE: 135447409 bytes transferred in 87.649259 secs (1545334 bytes/sec) This is nearly exact twice the time for 3.1 than for 2.2.8. The network is okay, a dd to /dev/null gives me: 135447409 bytes transferred in 13.553990 secs (9993176 bytes/sec) Copying the same file to a "normal harddrive" results in: 135447409 bytes transferred in 19.716693 secs (6869682 bytes/sec) This I would assume as OK. Is there something special in the CAM layer that has to do with IOMEGA drives (apart from the quirk entry for tagged queuing in cam_xpt.c)? Should I do some debugging? Thanks, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 11:43:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA25135 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 11:43:51 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from super-g.inch.com (super-g.com [207.240.140.161]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA25130 for ; Fri, 12 Feb 1999 11:43:48 -0800 (PST) (envelope-from spork@super-g.com) Received: from localhost (localhost [127.0.0.1]) by super-g.inch.com (8.8.8/8.8.5) with SMTP id OAA23389; Fri, 12 Feb 1999 14:43:10 -0500 (EST) Date: Fri, 12 Feb 1999 14:43:10 -0500 (EST) From: spork X-Sender: spork@super-g.inch.com To: Dag-Erling Smorgrav cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CAM and -stable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 16 Dec 1998, Dag-Erling Smorgrav wrote: > It's not lack of tags that's the problem (64 is pretty good), but the > fact that the firmware (incorrectly) reports that it's out of queue > slots when things get busy. The vendor claims otherwise ;) Can I ask where you came upon that information? Thanks, Charles > DES > -- > Dag-Erling Smorgrav - des@flood.ping.uio.no > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 12:03:07 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27883 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 12:03:07 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: (from jmb@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27853; Fri, 12 Feb 1999 12:02:51 -0800 (PST) (envelope-from jmb) Date: Fri, 12 Feb 1999 12:02:51 -0800 (PST) Message-Id: <199902122002.MAA27853@hub.freebsd.org> From: "Jonathan M. Bresler" To: ken@plutotech.com CC: mjacob@feral.com, ANDREAS.KLEMM.AK@bayer-ag.de, scsi@FreeBSD.ORG In-reply-to: <199902121610.JAA34695@panzer.plutotech.com> (ken@plutotech.com) Subject: Re: It%s not the write cache on 3.0-STABLE and not tagged comma References: <199902121610.JAA34695@panzer.plutotech.com> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > I'll forward you his original mail, I think it probably got nuked by > Majordomo's message size filter. yes it did....never send 100k messages to the lists. please use ftp for items that size and larger. jmb To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 12:35:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA02879 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 12:35:32 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from carme.eclipse.net.uk (carme.eclipse.net.uk [195.188.32.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA02874 for ; Fri, 12 Feb 1999 12:35:29 -0800 (PST) (envelope-from stuart@eclipse.net.uk) Received: from eclipse.net.uk (elara.eclipse.net.uk [195.188.32.31]) by carme.eclipse.net.uk (8.9.3/8.9.3) with ESMTP id UAA00789 for ; Fri, 12 Feb 1999 20:32:47 GMT Message-ID: <36C490C0.79599E02@eclipse.net.uk> Date: Fri, 12 Feb 1999 20:36:16 +0000 From: Stuart Henderson Organization: Eclipse Networking Ltd. X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en-GB MIME-Version: 1.0 To: scsi@FreeBSD.ORG Subject: Symbios 53c895 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone have patches to the NCR driver to run 53c895 chips in 80mbps mode? Stuart To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 16:50:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03894 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 16:50:24 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03885 for ; Fri, 12 Feb 1999 16:50:18 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id BAA72932; Sat, 13 Feb 1999 01:50:10 +0100 (CET) (envelope-from des) To: spork Cc: Dag-Erling Smorgrav , freebsd-scsi@FreeBSD.ORG Subject: Re: CAM and -stable References: From: Dag-Erling Smorgrav Date: 13 Feb 1999 01:50:09 +0100 In-Reply-To: spork's message of "Fri, 12 Feb 1999 14:43:10 -0500 (EST)" Message-ID: Lines: 18 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org spork writes: > On 16 Dec 1998, Dag-Erling Smorgrav wrote: > > It's not lack of tags that's the problem (64 is pretty good), but the > > fact that the firmware (incorrectly) reports that it's out of queue > > slots when things get busy. > The vendor claims otherwise ;) I'm not surprised that the vendor is reluctant to admit that their firmware is buggy. > Can I ask where you came upon that information? It's a quite common bug in SCSI firmware, and I have a disk (Quantum Atlas II) which exhibits the same symptoms. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 17:30:57 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA07603 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 17:30:57 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mana.s.notwork.org (tok184.airnet.ne.jp [210.159.88.184]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id RAA07596 for ; Fri, 12 Feb 1999 17:30:54 -0800 (PST) (envelope-from mrt@notwork.org) Received: (qmail 9075 invoked from network); 13 Feb 1999 01:30:45 -0000 Received: from kotonoha.s.notwork.org (192.168.1.1) by mana.s.notwork.org with SMTP; 13 Feb 1999 01:30:45 -0000 To: scsi@FreeBSD.ORG Subject: Re: Symbios 53c895 X-cite: xcite 1.20 References: <36C490C0.79599E02@eclipse.net.uk> MIME-Version: 1.0 (generated by SEMI 1.13.2 - "Mikawa") Content-Type: text/plain; charset=US-ASCII From: Murata Shuuichirou Date: 13 Feb 1999 10:31:02 +0900 In-Reply-To: <36C490C0.79599E02@eclipse.net.uk> (Stuart Henderson's message of "Fri, 12 Feb 1999 20:36:16 +0000") Message-ID: <87hfsrjdih.fsf@kotonoha.s.notwork.org> Lines: 20 User-Agent: T-gnus/6.10.058 (based on Pterodactyl Gnus v0.76) SEMI/1.13.2 (Mikawa) FLIM/1.12.5 (Hirahata) MULE XEmacs/21.2 (beta10) (Boreas) (i386-unknown-freebsd4.0) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In message <36C490C0.79599E02@eclipse.net.uk>, `stuart@eclipse.net.uk' wrote: > Does anyone have patches to the NCR driver to run 53c895 chips in 80mbps > mode? You can put the line: options SCSI_NCR_DFLT_SYNC=10 to your kernel config file and re-configure and re-make your kernel. Following is excerpt from dmesg: ncr0: rev 0x01 int a irq 16 on pci0.18.0 da1: Fixed Direct Access SCSI-2 device da1: 80.0MB/s transfers (40.0MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) -- Murata Shuuichirou To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 18:07:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA10862 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 18:07:29 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA10855 for ; Fri, 12 Feb 1999 18:07:23 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.7/8.8.7) with ESMTP id SAA21005; Fri, 12 Feb 1999 18:07:13 -0800 Date: Fri, 12 Feb 1999 18:07:13 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Stuart Henderson cc: scsi@FreeBSD.ORG Subject: Re: Symbios 53c895 In-Reply-To: <36C490C0.79599E02@eclipse.net.uk> 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 yes, but only for solaris On Fri, 12 Feb 1999, Stuart Henderson wrote: > Does anyone have patches to the NCR driver to run 53c895 chips in 80mbps > mode? > > Stuart > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 19:38:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA20516 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 19:38:30 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA20510; Fri, 12 Feb 1999 19:38:26 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id UAA38390; Fri, 12 Feb 1999 20:38:20 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902130338.UAA38390@panzer.plutotech.com> Subject: Re: bad drive? In-Reply-To: <61128.918808646@gjp.erols.com> from Gary Palmer at "Feb 12, 1999 3:37:26 am" To: gpalmer@FreeBSD.ORG (Gary Palmer) Date: Fri, 12 Feb 1999 20:38:20 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Gary Palmer wrote... > > I found the enclosed messages (appended after my sig) in /var/log/messages on > a machine at work. I'm wondering if these imply a fixable error (e.g. bad > termination) or if one of the drives is slowly dying? > > ahc0: rev 0x00 int a irq 11 on pci0.10.0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > da1: Fixed Direct Access SCSI-2 device > da1: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da1: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) > da0 at ahc0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 20.0MB/s transfers (10.0MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 2047MB (4194058 512 byte sectors: 255H 63S/T 261C) > > This is from the 19981216 SNAP code. > > Thanks, > > Gary > -- > Gary Palmer FreeBSD Core Team Member > FreeBSD: Turning PC's into workstations. See http://www.FreeBSD.ORG/ for info > > Feb 11 12:46:39 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x1c - timed out while > id > le, LASTPHASE == 0x1, SEQADDR == 0xc > Feb 11 12:46:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB > Feb 11 12:46:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message > Sent > Feb 11 12:46:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, > status > = 353 > Feb 11 12:46:40 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 > Feb 11 12:46:40 virtual /kernel: SEQADDR == 0x157 > Feb 11 12:47:39 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x2f - timed out while > id I suppose it is possible that this could be caused by bad termination or something similar. The problem is that we're queueing transactions to the drive, but it isn't responding before the timeout fires. The I/O timeout for da devices is 60 seconds. So, take that however you will. I would first try to make sure that the cable is okay, as well as termination. Make sure there are no bent pins or anything like that. If everything checks out in the cabling/termination department, I would probably start to suspect that the drive is having trouble. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 12 19:49:08 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21235 for freebsd-scsi-outgoing; Fri, 12 Feb 1999 19:49:08 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA21230 for ; Fri, 12 Feb 1999 19:49:06 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id UAA38439; Fri, 12 Feb 1999 20:47:01 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902130347.UAA38439@panzer.plutotech.com> Subject: Re: Is CAM slower than the old SCSI layer for JAZ drives? In-Reply-To: <19990212191723.A644@internal> from Andre Albsmeier at "Feb 12, 1999 7:17:23 pm" To: andre.albsmeier@mchp.siemens.de (Andre Albsmeier) Date: Fri, 12 Feb 1999 20:47:01 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Andre Albsmeier wrote... > I have made an odd observation. Copying a large file from > my 100MBit net to a 2GB jaz, I noticed that 3.1-BETA took > a lot more time than it used to under 2.2.8-STABLE. > Exact (well, as exact as dd can be) measurements told me: > > 3.1-BETA: > 135447409 bytes transferred in 178.638903 secs (758219 bytes/sec) > > 2.2.8-STABLE: > 135447409 bytes transferred in 87.649259 secs (1545334 bytes/sec) > > This is nearly exact twice the time for 3.1 than for 2.2.8. > The network is okay, a dd to /dev/null gives me: > 135447409 bytes transferred in 13.553990 secs (9993176 bytes/sec) > > Copying the same file to a "normal harddrive" results in: > 135447409 bytes transferred in 19.716693 secs (6869682 bytes/sec) > This I would assume as OK. > > Is there something special in the CAM layer that has to do > with IOMEGA drives (apart from the quirk entry for tagged > queuing in cam_xpt.c)? > > Should I do some debugging? Hmm, it certainly seems odd that CAM would be slower than the old SCSI layer. I would expect the performance to be about the same for something like that. Perhaps you could try a few experiments: - try disabling the quirk entry in the transport layer (i.e., enable tagged queueing) - try enabling tagged queueing, but set the maximum number of I/O requests to 4. I will send you some patches to camcontrol in a separate piece of mail that will enable you to set the number of tagged openings for the device on the fly, without having to recompile your kernel. You will only be able to set them to values within the range set by the maximum and minimum values in the transport layer quirk table. [ The reason I'm not sending the patches to the list is that they aren't quite ready for public consumption. ] Anyway, if you set the minimum and maximum for your Jaz drive to 0 and 255 respectively in the quirk table, you can use camcontrol to experiment with different settings for the number of available tagged openings. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 13 00:25:37 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11264 for freebsd-scsi-outgoing; Sat, 13 Feb 1999 00:25:37 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11259 for ; Sat, 13 Feb 1999 00:25:34 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id AAA14620; Sat, 13 Feb 1999 00:16:35 -0800 (PST) Received: from s204m82.isp.whistle.com(207.76.204.82) via SMTP by alpo.whistle.com, id smtpdI14617; Sat Feb 13 08:16:28 1999 Date: Sat, 13 Feb 1999 00:16:08 -0800 (PST) From: Julian Elischer X-Sender: julian@s204m82.isp.whistle.com To: "Kenneth D. Merry" cc: Andre Albsmeier , freebsd-scsi@FreeBSD.ORG Subject: Re: Is CAM slower than the old SCSI layer for JAZ drives? In-Reply-To: <199902130347.UAA38439@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, 12 Feb 1999, Kenneth D. Merry wrote: > Andre Albsmeier wrote... > > I have made an odd observation. Copying a large file from > > my 100MBit net to a 2GB jaz, I noticed that 3.1-BETA took > > a lot more time than it used to under 2.2.8-STABLE. > > Exact (well, as exact as dd can be) measurements told me: > > > > 3.1-BETA: > > 135447409 bytes transferred in 178.638903 secs (758219 bytes/sec) > > > > 2.2.8-STABLE: > > 135447409 bytes transferred in 87.649259 secs (1545334 bytes/sec) > > > > This is nearly exact twice the time for 3.1 than for 2.2.8. > > The network is okay, a dd to /dev/null gives me: > > 135447409 bytes transferred in 13.553990 secs (9993176 bytes/sec) I've heard from several sources (notibly Simon Shapiro) that something in the CAM code is slowing things down. However I don't think it's likely to be a theoretical thing, but possibly an implimentation gothca.. in THEORY CAM should equal or surpass the old system, with many organisational advantages. > > julian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 13 02:45:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA22139 for freebsd-scsi-outgoing; Sat, 13 Feb 1999 02:45:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from picalon.gun.de (picalon.gun.de [194.77.0.18] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA22134 for ; Sat, 13 Feb 1999 02:45:10 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id LAA16615; Sat, 13 Feb 1999 11:45:06 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id LAA06361; Sat, 13 Feb 1999 11:40:01 +0100 (CET) (envelope-from andreas) Date: Sat, 13 Feb 1999 11:40:01 +0100 From: Andreas Klemm To: "Kenneth D. Merry" Cc: mjacob@feral.com, ANDREAS.KLEMM.AK@bayer-ag.de, scsi@FreeBSD.ORG Subject: Re: It%s not the write cache on 3.0-STABLE and not tagged comma Message-ID: <19990213114001.A6068@titan.klemm.gtn.com> References: <199902121610.JAA34695@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199902121610.JAA34695@panzer.plutotech.com>; from Kenneth D. Merry on Fri, Feb 12, 1999 at 09:10:24AM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-STABLE SMP Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Feb 12, 1999 at 09:10:24AM -0700, Kenneth D. Merry wrote: > > Read performance is fine. (about 12MB/sec) "poor" means between 1 and > 3MB/sec. > > I'll forward you his original mail, I think it probably got nuked by > Majordomo's message size filter. Yes it has been nuked, sorry for that. Jonathan Bresler told me so, but I thought everything is fine, since Ken answered me. -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 13 03:00:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA23294 for freebsd-scsi-outgoing; Sat, 13 Feb 1999 03:00:15 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from picalon.gun.de (picalon.gun.de [194.77.0.18] (may be forged)) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA23288 for ; Sat, 13 Feb 1999 03:00:11 -0800 (PST) (envelope-from andreas@klemm.gtn.com) Received: from klemm.gtn.com (pppak04.gtn.com [194.231.123.169]) by picalon.gun.de (8.8.6/8.8.6) with ESMTP id MAA16920; Sat, 13 Feb 1999 12:00:06 +0100 (MET) Received: (from andreas@localhost) by klemm.gtn.com (8.9.2/8.9.2) id LAA06376; Sat, 13 Feb 1999 11:46:41 +0100 (CET) (envelope-from andreas) Date: Sat, 13 Feb 1999 11:46:41 +0100 From: Andreas Klemm To: "Kenneth D. Merry" Cc: mjacob@feral.com, ANDREAS.KLEMM.AK@bayer-ag.de, scsi@FreeBSD.ORG Subject: Re: It%s not the write cache on 3.0-STABLE and not tagged comma Message-ID: <19990213114641.B6068@titan.klemm.gtn.com> References: <199902121602.JAA34641@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: <199902121602.JAA34641@panzer.plutotech.com>; from Kenneth D. Merry on Fri, Feb 12, 1999 at 09:02:18AM -0700 X-Disclaimer: A free society is one where it is safe to be unpopular X-Operating-System: FreeBSD 3.0-STABLE SMP Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Feb 12, 1999 at 09:02:18AM -0700, Kenneth D. Merry wrote: > > He is getting poor performance for sequential writes with a Seagate disk > under CAM. Write throughput to the disk is fairly erratic. (i.e., lots of > ups and downs) > > He has the problem under 2.2.7 with tagged queueing enabled, but not when > he disables tagged queueing. The problem occurs under 3.0 with or > without tagged queueing. > > I told him to disable write caching, since I have seen similar problems > when write caching is enabled, but that didn't seem to fix the problem. > > Any ideas? BTW, a friend of mine works for VIVA. They have lots of HP Kajak's and he told me _lots_ of problems with firmware, since HP seems to put his _own_ drivers in everything they can ;-) He ponited me to HP's support site to do a firmware upgrade, but I couldn't find something for Harddisks :-/ But if write performance is poor, but actually doesn't eat up that much CPU performance. Why is the FreeBSD machine so much "in-responsive". It means I merely can login on a second console, I have to wait 10-15 seconds for a login. And the execution of commands lags lags lags. Ok, perhaps it's a race condition of the disk .... that perhaps login, csh and other things can't be read from disk, because it's upgly hung or busy transferring things for bonnie ... BTW, when HP puts his own firmware to a disk, do they change the description of the disk ... ? Or in other words, I wrote to you the description of the disk (SEAGATE bla...), doesn somebody other have this disk and such problems ??? -- Andreas Klemm http://www.FreeBSD.ORG/~andreas What gives you 90% more speed, for example, in kernel compilation ? http://www.FreeBSD.ORG/~fsmp/SMP/akgraph-a/graph1.html "NT = Not Today" (Maggie Biggs) ``powered by FreeBSD SMP'' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 13 05:47:54 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA08379 for freebsd-scsi-outgoing; Sat, 13 Feb 1999 05:47:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from www5.gmx.net (www5.gmx.net [195.63.104.45]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id FAA08367 for ; Sat, 13 Feb 1999 05:47:50 -0800 (PST) (envelope-from Ralf.Luettgen@gmx.net) Received: (qmail 8646 invoked by uid 65534); 13 Feb 1999 13:47:46 -0000 Date: Sat, 13 Feb 1999 14:47:46 +0100 (MET) From: Ralf Luettgen To: freebsd-questions@FreeBSD.ORG Cc: freebsd-scsi@FreeBSD.ORG Subject: System hangs after fdisk 3.0-Stable X-Authenticated-Sender: #0000515563@gmx.net X-Authenticated-IP: [195.14.233.175] Message-Id: <8638.918913666@www.gmx.net> X-Mailer: WWW-Mail 1.02a/b (Global Message Exchange) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks for the mail. Sorry, that I answer not earlier, but the box with the problem is 200km away. In the answer of my first question I got the hint to use the kernel debugger. Here ist the result of this. dmesg shows: da1: Fixed Direct Access SCSI-2 device da1: 10.0MB/s transfers (10.0MHz, offset 15) da1: 1032MB (2113776 512 byte sectors: 64H 32S/T 1032C) I use : fdisk /dev/rda1 some informations came on the display and then thy box hangs. I use CTRL-ALT-ESC and type trace this is the result: Debugger("manual escape to debugger") Stopped at Debugger+0x37: movl $0,in_Debugger db> trace Debugger(f0232cf1) at Debugger+0x37 scgetc(f0266f08,2,0,f0266f08,0) at scgetc+0x824 sckbdevent(f0266f08,0,0,0,f4521d00) at sckbdevent+0x50 atkbd_intr(f0266f08,0,0,f01fc4fe,0) at atkbd_intr+0x1f atkbd_isa_intr(0,80000000,10,10,0) at atkbd_isa_intr+0x1e Xresume1() at Xresume1+0x2b --- interrupt, eip = 0xf02045bd, esp = ßxfß23e5ß8, ebp=0 --- Thanks for help Ralf --- Sent through Global Message Exchange - http://www.gmx.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 13 07:15:23 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA13691 for freebsd-scsi-outgoing; Sat, 13 Feb 1999 07:15:23 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from david.siemens.de (david.siemens.de [192.35.17.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA13679 for ; Sat, 13 Feb 1999 07:15:17 -0800 (PST) (envelope-from andre.albsmeier@mchp.siemens.de) X-Envelope-Sender-Is: andre.albsmeier@mchp.siemens.de (at relayer david.siemens.de) Received: from salomon.siemens.de (salomon.siemens.de [139.23.33.13]) by david.siemens.de (8.9.3/8.9.3) with ESMTP id QAA06064 for ; Sat, 13 Feb 1999 16:15:12 +0100 (MET) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [146.180.31.23]) by salomon.siemens.de (8.9.3/8.9.3) with ESMTP id QAA21626 for ; Sat, 13 Feb 1999 16:15:14 +0100 (MET) Received: (from daemon@localhost) by curry.mchp.siemens.de (8.8.8/8.8.8) id QAA02705 for ; Sat, 13 Feb 1999 16:15:14 +0100 (CET) Date: Sat, 13 Feb 1999 16:15:13 +0100 From: Andre Albsmeier To: Julian Elischer Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Is CAM slower than the old SCSI layer for JAZ drives? Message-ID: <19990213161513.B719@internal> References: <199902130347.UAA38439@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.1i In-Reply-To: ; from Julian Elischer on Sat, Feb 13, 1999 at 12:16:08AM -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sat, 13-Feb-1999 at 00:16:08 -0800, Julian Elischer wrote: > > On Fri, 12 Feb 1999, Kenneth D. Merry wrote: > > > Andre Albsmeier wrote... > > > I have made an odd observation. Copying a large file from > > > my 100MBit net to a 2GB jaz, I noticed that 3.1-BETA took > > > a lot more time than it used to under 2.2.8-STABLE. > > > Exact (well, as exact as dd can be) measurements told me: > > > > > > 3.1-BETA: > > > 135447409 bytes transferred in 178.638903 secs (758219 bytes/sec) > > > > > > 2.2.8-STABLE: > > > 135447409 bytes transferred in 87.649259 secs (1545334 bytes/sec) > > > > > > This is nearly exact twice the time for 3.1 than for 2.2.8. > > > The network is okay, a dd to /dev/null gives me: > > > 135447409 bytes transferred in 13.553990 secs (9993176 bytes/sec) > > I've heard from several sources (notibly Simon Shapiro) > that something in the CAM code is slowing things down. > However I don't think it's likely to be a theoretical thing, > but possibly an implimentation gothca.. in THEORY CAM should > equal or surpass the old system, with many organisational advantages. I just mailed Kenneth the results of some experiments he asked me to do. Apart from that, I observed the following: ----------------------- snip --------------------------------- Than I made the experiments by writing a 50.000.000 bytes files to the JAZ. It came from an Ultra-Wide drive which hangs on ahc0. The JAZ is attached to ahc1. Here I made a curiuos observation: Directly after booting (with min/max tags set to 0/255 in the kernel and without ever having used camcontrol) I copied the file from the Ultra-Wide disk on ahc0 onto the JAZ on ahc1: 50000000 bytes transferred in 52.256570 secs (956817 bytes/sec) Being astonished about these 950k I tried it once again: 50000000 bytes transferred in 69.072540 secs (723877 bytes/sec) It was exactly the same command but now, I assume, the file came from the kernel buffers. So there was no activty on the source disk. Than I unmounted the source disk and remounted it. I assume that the kernel now invalidated its buffers for that drive which means that the source file will have to be read again: 50000000 bytes transferred in 53.233707 secs (939255 bytes/sec) Is it possible that the JAZ gets somekind of saturated or something like this ?!? When the kernel has to read the file from the source disk I assume that there are small interruptions in the data flow to the JAZ. The second time all data comes directly from the memory and the bytes are being pumped like hell to the JAZ... Maybe I am talking bullsh*t as well :-) ------------------------ snap ---------------------------- -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 13 08:00:51 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA16952 for freebsd-scsi-outgoing; Sat, 13 Feb 1999 08:00:51 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from moe.nycrc.net (gabriel.nycrc.net [209.73.202.6]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA16947 for ; Sat, 13 Feb 1999 08:00:49 -0800 (PST) (envelope-from vince@nycrc.net) Received: (qmail 592 invoked by uid 1000); 13 Feb 1999 16:01:04 -0000 Message-ID: <19990213110104.A475@nycrc.net> Date: Sat, 13 Feb 1999 11:01:04 -0500 From: Vince Gonzalez To: freebsd-scsi@FreeBSD.ORG Subject: NCR 810 and Sony Spressa 960 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got an NCR 810 scsi card and a Sony Spressa 960. I'm having problems getting this combination to work. I'm running 3.0-RELEASE, with a generic kernel. The boot gets to the line ncr0: SCSI phase error fixup: CCB already dequeued (0xf0862600) and sits there a while. Eventually, the timeout messages start, and a long while later (don't know exactly how long, I left it booting overnight) it gives up and finishes the boot. This whole problem is strange, because this stuff works fine under Linux and Windows 98 (on the same machine). Clearly, BSD does not care for my CD-R. Is this simply a matter of installing a newer kernel? Thanks for any help! Here's my dmesg output: Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-RELEASE #0: Sat Oct 17 17:45:06 GMT 1998 jkh@kickme.freebsd.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz cost 3191 ns CPU: Pentium II (quarter-micron) (300.68-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x652 Stepping=2 Features=0x183f9ff> real memory = 67108864 (65536K bytes) avail memory = 62488576 (61024K bytes) Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x03 on pci0.1.0 chip2: rev 0x02 on pci0.7.0 ide_pci0: rev 0x01 on pci0.7.1 chip3: rev 0x01 int d irq 255 on pci0.7.2 chip4: rev 0x02 on pci0.7.3 fxp0: rev 0x05 int a irq 12 on pci0.11.0 fxp0: Ethernet address 00:a0:c9:e8:1d:51 ncr0: rev 0x02 int a irq 10 on pci0.13.0 Probing for devices on PCI bus 1: vga0: rev 0x21 int a irq 11 on pci1.0.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 fe0 not found at 0x300 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 not found at 0x60 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 9671MB (19807200 sectors), 19650 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 4884MB (10003392 sectors), 9924 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, ovlap, dma, iordy wcd0: 2067Kb/sec, 256Kb cache, audio play, 255 volume levels, ejectable tray wcd0: 120mm data disc loaded, unlocked wt0 not found at 0x300 mcd0 not found at 0x300 matcdc0 not found at 0x230 scd0 not found at 0x230 ie0: unknown board_id: f000 ie0 not found at 0x300 ep0 not found at 0x300 ex0 not found le0 not found at 0x300 lnc0 not found at 0x280 ze0 not found at 0x300 zp0 not found at 0x300 cs0 not found at 0x300 adv0 not found at 0x330 bt0 not found at 0x134 aha0 not found at 0x134 npx0 on motherboard npx0: INT 16 interface Waiting 15 seconds for SCSI devices to settle ncr0: SCSI phase error fixup: CCB already dequeued (0xf0862600) ncr0: timeout nccb=0xf0862600 (skip) ncr0: timeout nccb=0xf0862600 (skip) ncr0: timeout nccb=0xf0862600 (skip) ncr0: timeout nccb=0xf0862600 (skip) ncr0: timeout nccb=0xf0862a00 (skip) ncr0: timeout nccb=0xf0862a00 (skip) ncr0: timeout nccb=0xf0862a00 (skip) ncr0: timeout nccb=0xf0862a00 (skip) ncr0: timeout nccb=0xf0862a00 (skip) ncr0: timeout nccb=0xf0862e00 (skip) ncr0: timeout nccb=0xf0862e00 (skip) ncr0: timeout nccb=0xf0862e00 (skip) ncr0: timeout nccb=0xf0862e00 (skip) ncr0: timeout nccb=0xf0862e00 (skip) ncr0: timeout nccb=0xf0860200 (skip) ncr0: timeout nccb=0xf0860200 (skip) ncr0: timeout nccb=0xf0860200 (skip) ncr0: timeout nccb=0xf0860200 (skip) ncr0: timeout nccb=0xf0860200 (skip) ncr0: timeout nccb=0xf0860600 (skip) ncr0: timeout nccb=0xf0860600 (skip) ncr0: timeout nccb=0xf0860600 (skip) ncr0: timeout nccb=0xf0860600 (skip) ncr0: timeout nccb=0xf0860600 (skip) ncr0: timeout nccb=0xf0860e00 (skip) ncr0: timeout nccb=0xf0860e00 (skip) ncr0: timeout nccb=0xf0860e00 (skip) ncr0: timeout nccb=0xf0860e00 (skip) ncr0: timeout nccb=0xf0860e00 (skip) ncr0: timeout nccb=0xf0865400 (skip) ncr0: timeout nccb=0xf0865400 (skip) ncr0: timeout nccb=0xf0865400 (skip) ncr0: timeout nccb=0xf0865400 (skip) ncr0: timeout nccb=0xf0865400 (skip) changing root device to wd1s1a ncr0: timeout nccb=0xf0862000 (skip) ncr0: timeout nccb=0xf0862000 (skip) (cd0:ncr0:0:1:0): got CAM status 0x4b (cd0:ncr0:0:1:0): fatal error, failed to attach to device(cd0:ncr0:0:1:0): removing device entry To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 13 10:23:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA29884 for freebsd-scsi-outgoing; Sat, 13 Feb 1999 10:23:32 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA29878 for ; Sat, 13 Feb 1999 10:23:29 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id MAA04890 for ; Sat, 13 Feb 1999 12:23:26 -0600 (CST) Received: from free.pcs (free.PCS [148.105.10.51]) by right.PCS (8.6.13/8.6.4) with ESMTP id MAA18544 for ; Sat, 13 Feb 1999 12:19:25 -0600 Received: (from jlemon@localhost) by free.pcs (8.8.6/8.8.5) id MAA25275; Sat, 13 Feb 1999 12:22:55 -0600 (CST) Date: Sat, 13 Feb 1999 12:22:55 -0600 (CST) From: Jonathan Lemon Message-Id: <199902131822.MAA25275@free.pcs> To: freebsd-scsi@FreeBSD.ORG Subject: Re: bad drive? X-Newsgroups: local.mail.freebsd-scsi In-Reply-To: References: Organization: Architecture and Operating System Fanatics Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you write: >Gary Palmer wrote... >> Feb 11 12:46:39 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x1c - timed out while >> id >> le, LASTPHASE == 0x1, SEQADDR == 0xc >> Feb 11 12:46:40 virtual /kernel: (da0:ahc0:0:0:0): Queuing a BDR SCB >> Feb 11 12:46:40 virtual /kernel: (da0:ahc0:0:0:0): Bus Device Reset Message >> Sent >> Feb 11 12:46:40 virtual /kernel: (da0:ahc0:0:0:0): no longer in timeout, >> status >> = 353 >> Feb 11 12:46:40 virtual /kernel: Unexpected busfree. LASTPHASE == 0xa0 >> Feb 11 12:46:40 virtual /kernel: SEQADDR == 0x157 >> Feb 11 12:47:39 virtual /kernel: (da0:ahc0:0:0:0): SCB 0x2f - timed out while >> id > >I suppose it is possible that this could be caused by bad termination or >something similar. I recently had a pile of errors similar to this on a 3.0-BETA machine, where I couldn't do a `make world' or tape backup without getting lots of `Timed out while idle' messages. Taking the SCSI cable out, and hammering on all the connectors to insure a solid fit between the connectors and the cable appears to have solved the problem for me. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 13 12:36:15 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13594 for freebsd-scsi-outgoing; Sat, 13 Feb 1999 12:36:15 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13588 for ; Sat, 13 Feb 1999 12:36:11 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id NAA45976; Sat, 13 Feb 1999 13:34:03 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199902132034.NAA45976@panzer.plutotech.com> Subject: Re: Is CAM slower than the old SCSI layer for JAZ drives? In-Reply-To: from Julian Elischer at "Feb 13, 1999 0:16: 8 am" To: julian@whistle.com (Julian Elischer) Date: Sat, 13 Feb 1999 13:34:03 -0700 (MST) Cc: andre.albsmeier@mchp.siemens.de, freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Julian Elischer wrote... > > On Fri, 12 Feb 1999, Kenneth D. Merry wrote: > > > Andre Albsmeier wrote... > > > I have made an odd observation. Copying a large file from > > > my 100MBit net to a 2GB jaz, I noticed that 3.1-BETA took > > > a lot more time than it used to under 2.2.8-STABLE. > > > Exact (well, as exact as dd can be) measurements told me: > > > > > > 3.1-BETA: > > > 135447409 bytes transferred in 178.638903 secs (758219 bytes/sec) > > > > > > 2.2.8-STABLE: > > > 135447409 bytes transferred in 87.649259 secs (1545334 bytes/sec) > > > > > > This is nearly exact twice the time for 3.1 than for 2.2.8. > > > The network is okay, a dd to /dev/null gives me: > > > 135447409 bytes transferred in 13.553990 secs (9993176 bytes/sec) > > I've heard from several sources (notibly Simon Shapiro) > that something in the CAM code is slowing things down. > However I don't think it's likely to be a theoretical thing, > but possibly an implimentation gothca.. in THEORY CAM should > equal or surpass the old system, with many organisational advantages. I think Justin has said before (not sure whether Simon has confirmed this) that the problem is the bufq_disksort() call in the da driver. The old sd driver did things like this: #ifdef SDDISKSORT bufq_disksort(&sd->buf_queue, bp); #else bufq_insert_tail(&sd->buf_queue, bp); #endif Since SDDISKSORT wasn't defined (that I can tell), buffers were always inserted at the tail. The CAM da driver always uses bufqdisksort(), which supposedly is the thing that is slowing things down somewhat. An easy way to see for sure is to replace the bufqdisksort() call in scsi_da.c with bufq_insert_tail(). Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 13 20:22:58 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA16209 for freebsd-scsi-outgoing; Sat, 13 Feb 1999 20:22:58 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.nacamar.de (mail.nacamar.de [194.162.162.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA16204 for ; Sat, 13 Feb 1999 20:22:56 -0800 (PST) (envelope-from rohrbach@mail.nacamar.de) Received: (from rohrbach@localhost) by mail.nacamar.de (8.8.7/8.8.8MB-19980212) id FAA07564 for freebsd-scsi@freebsd.org; Sun, 14 Feb 1999 05:22:53 +0100 (CET) Message-ID: <19990214052253.A7448@nacamar.net> Date: Sun, 14 Feb 1999 05:22:53 +0100 From: "Karsten W. Rohrbach" To: freebsd-scsi@FreeBSD.ORG Subject: AMI MegaRAID Reply-To: rohrbach@nacamar.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i X-Arbitrary-Number-Of-The-Day: 42 X-Sender: rohrbach@nacamar.net X-Organisation: Nacamar Data Communications GmbH X-Address: Robert-Bosch-Str. 32, 63303 Dreieich, Germany X-Phone: vox: +49 6103 993 870 fax: +49 6103 993 199 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org is somebody else working on an ami megaraid scsi driver? just curious. /k -- "The path of excess leads to the tower of wisdom." -- W. Blake http://www.nacamar.de - http://www.nacamar.net - http://www.webmonster.de http://www.apache.de - http://www.quakeforum.de - finger rohrbach@nacamar.net PGP Key fingerprint = F9 A0 DF 91 74 07 6A 1C 5F 0B E0 6B 4D CD 8C 44 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message