From owner-freebsd-alpha  Sat Jan  6 13: 4:33 2001
From owner-freebsd-alpha@FreeBSD.ORG  Sat Jan  6 13:04:31 2001
Return-Path: <owner-freebsd-alpha@FreeBSD.ORG>
Delivered-To: freebsd-alpha@freebsd.org
Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1])
	by hub.freebsd.org (Postfix) with ESMTP id 3FBE137B400
	for <freebsd-alpha@freebsd.org>; Sat,  6 Jan 2001 13:04:31 -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 QAA13097;
	Sat, 6 Jan 2001 16:04:30 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.1/8.9.1) id f06L4U474937;
	Sat, 6 Jan 2001 16:04:30 -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
Date: Sat,  6 Jan 2001 16:04:30 -0500 (EST)
To: Wilko Bulte <wkb@freebie.demon.nl>
Cc: freebsd-alpha@freebsd.org
Subject: Re: debugging fpa / FDDI panic
In-Reply-To: <20010106214357.X77275@freebie.demon.nl>
References: <20010106214357.X77275@freebie.demon.nl>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14935.34600.806565.787237@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Wilko Bulte writes:
 > Now that I have -current running on my Miata I'm trying to find out why the
 > fpa driver causes a panic on boot:
 > 
 > isp0: interrupting at CIA irq 16
 > pci1: <network, ethernet> at 10.0 (no driver attached)
 > fpa0: <Digital DEFPA PCI FDDI Controller> port 0x9000-0x907f mem
 > 0x80950000-0x8095ffff,0x80960000-0x8096007f irq 4 at device 11.0 on pci0
 > 
 > fatal kernel trap:
 > 
 >     trap entry = 0x2 (memory management fault)
 >     a0         = 0x80960014

This is a bus address, not a virtual address.

Change the bus_alloc_resource call in pdq_pci_attach() to

	memres = bus_alloc_resource(dev, SYS_RES_MEMORY, &rid, 0, ~0, 1,
		     RF_ACTIVE|PCI_RF_DENSE);

We should either have pci_alloc_resource default to RF_DENSE or panic
if neither PCI_RF_DENSE nor PCI_RF_BWX are specified.  The current
state of affairs makes no sense..

Drew



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