From owner-freebsd-stable Wed May 3 12:41:18 2000 Delivered-To: freebsd-stable@freebsd.org Received: from mass.cdrom.com (mass.cdrom.com [204.216.28.234]) by hub.freebsd.org (Postfix) with ESMTP id 7632537B622 for ; Wed, 3 May 2000 12:41:15 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id MAA00506; Wed, 3 May 2000 12:49:23 -0700 (PDT) (envelope-from msmith@mass.cdrom.com) Message-Id: <200005031949.MAA00506@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Shawn Barnhart" Cc: freebsd-stable@FreeBSD.ORG Subject: Re: HPDA/DAC960PL errors In-reply-to: Your message of "Wed, 03 May 2000 13:40:40 CDT." <00c801bfb52f$150f2e30$b8209fc0@marlowe> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 03 May 2000 12:49:23 -0700 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > | (Just to continue talking to myself) - The reason I never ran into this, > | I realised, is that I did all my work on the 2.x firmware in Alpha > | systems which have an 8k page size. With a 64k d_maxio, you'll never see > | more than 9 segments. > | > | Sorry about this. > > I'm just glad I found the problem for you. > > I'd like to get this server built using this DAC sooner rather than later, > and it's likely I can get 3.x firmware from Mylex before you'll update the > driver (no offense meant). None taken. Unfortunately the 3.x firmware is probably going to have the same problem; we cap at 16 S/G segments there as well. > If there's a ghost of a chance you might have a > fix you want tested completed before this time next week, let me know and > I'll hold off installing 3.x chips to test the fix -- an install, full CVS > update, and a make world ought to be a decent test? I could probably do > something That'd do it, certainly. > I have two other DAC960s, but they both suffer from the ""couldn't allocate > mailbox window" problem you're also working on, so they might not be decent > test subjects unless you want to try to fix both problems at once. :) I know what's going on there - I don't support I/O mapped controllers at all. I'm not sure that I want to, either, yet; there is a performance cost that extends to other controllers if I do. If you can narrow down the differences between the controllers that come up I/O mapped and those that come up memory-mapped, I'd really appreciate it. It's possible that the I/O mapped ones can be convinced to memory-map if I can work out what's wrong. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message