From owner-freebsd-current  Thu Apr  4 10:32:25 2002
Delivered-To: freebsd-current@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP id 940BA37B41F
	for <freebsd-current@freebsd.org>; Thu,  4 Apr 2002 10:32:04 -0800 (PST)
Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30])
	by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id NAA27092;
	Thu, 4 Apr 2002 13:32:03 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.6/8.9.1) id g34IVXF98735;
	Thu, 4 Apr 2002 13:31:33 -0500 (EST)
	(envelope-from gallatin@cs.duke.edu)
From: Andrew Gallatin <gallatin@cs.duke.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <15532.39941.670795.769478@grasshopper.cs.duke.edu>
Date: Thu, 4 Apr 2002 13:31:33 -0500 (EST)
To: mjacob@feral.com
Cc: freebsd-current@freebsd.org
Subject: BUS_SPACE_MAXSIZE & isp driver.
X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG


I just booted a recent current (or rather attempted to) and saw this
when attempting to mount root from a qlogic card on my miata:


bus_dmamap_load: Too many segs! buf_len = 0x2000
spec_getpages:(da0a) I/O read failure: (error=22) bp
0xfffffe0004087ae8 vp 0xfffffe000ae90000
               size: 98304, resid: 98304, a_count: 98304, valid: 0x0
               nread: 0, reqpage: 7, pindex: 59, pcount: 12
vm_fault: pager read error, pid 1 (init)

<... more of same ...>

The only way I could get the system to boot was to increase
BUS_SPACE_MAXSIZE to 128K to match MAXPHYS.  I don't know why they
don't match in the first place (they don't match on x86 either, so the
driver will probably puke there too.)

#define BUS_SPACE_MAXSIZE    (128 * 1024)

Does anybody know why BUS_SPACE_MAXSIZE != MAXPHYS on some platforms?

Thanks,

Drew

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message