From owner-freebsd-scsi Thu Dec 2 10:19:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D22CD14D09 for ; Thu, 2 Dec 1999 10:19:18 -0800 (PST) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.8.7/8.8.7) with ESMTP id KAA02563; Thu, 2 Dec 1999 10:20:19 -0800 Date: Thu, 2 Dec 1999 10:20:19 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Kenneth D. Merry" Cc: Stephen McKay , freebsd-scsi@FreeBSD.ORG Subject: Re: Tape driver problems In-Reply-To: <199912021816.LAA50614@panzer.kdm.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > > This is an "old" problem, ie more than 2 weeks, at least. :-) > > > > > > "mt status" with a tape loaded gives the correct values (including density), > > > but the kernel spits out: > > > > > > Dec 3 00:44:36 bucket /kernel: bus_dmamap_load: Too many segs! buf_len = 0x3000 > > > > > > The last bit changes. I've seen 0xb000 or 0xd000 or 0xe000 or 0xf000 also. > > > This is a new problem related to the density autodetection read. I expect > > > that an aha1542B just can't read MAXPHYS bytes from anything. > > > > Hmm, indeed. The density determining code does indeed issue a read of > > MAXPHYS bytes. It seems to me that all HBA's should at least support that! > > The maintainer for the 1542X will have to speak to this tho... > > I'm not the aha maintainer (Warner is), but I do know that it cannot do I didn't say you were. > more than 64K at a time. So you shouldn't be using any more than that. Nonsense. That's what bounce buffers can or *should* be used for too. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message