From owner-freebsd-firewire@FreeBSD.ORG Fri Jun 27 04:02:08 2003 Return-Path: Delivered-To: freebsd-firewire@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7671837B401 for ; Fri, 27 Jun 2003 04:02:08 -0700 (PDT) Received: from internal.mail.uk.tiscali.com (internal.mail.uk.tiscali.com [212.74.96.51]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9F91143F3F for ; Fri, 27 Jun 2003 04:02:05 -0700 (PDT) (envelope-from b.candler@pobox.com) Received: from [212.74.113.66] (helo=vaio.linnet.org) by internal.mail.uk.tiscali.com with asmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.12) id 19VqzT-0006pO-00 for freebsd-firewire@freebsd.org; Fri, 27 Jun 2003 12:02:03 +0100 Received: from brian by vaio.linnet.org with local (Exim 4.20) id 19Vr0g-000Frh-1a for freebsd-firewire@freebsd.org; Fri, 27 Jun 2003 12:03:18 +0100 Date: Fri, 27 Jun 2003 12:03:17 +0100 From: Brian Candler To: freebsd-firewire@freebsd.org Message-ID: <20030627110317.GA60951@uk.tiscali.com> References: <20030627101841.GA60838@uk.tiscali.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030627101841.GA60838@uk.tiscali.com> User-Agent: Mutt/1.4.1i Subject: Re: Firewire resets/performance problems X-BeenThere: freebsd-firewire@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Vendors pre-release coordination List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 Jun 2003 11:02:08 -0000 On Fri, Jun 27, 2003 at 11:18:41AM +0100, Brian Candler wrote: > (1) Data transfer is extremely slow. Using 'dd' to read from /dev/da0, I get > perhaps 10MB per minute; using 'dd' to write is maybe 3MB per minute max. Supplementary information: My system also has a SCSI card with a couple of CD-ROMs on it, so that's scbus0 and the firewire is scbus1. I just tried removing the SCSI card and the firewire is zooming along (8MB per second!) This may or may not be a red herring - perhaps it's just the fact that I did a reboot - but is it possible that something is wrongly assuming the device to be on scbus0 when it's on scbus1 ? Regards, Bran.