From owner-freebsd-alpha@FreeBSD.ORG  Thu Apr 24 09:36:08 2003
Return-Path: <owner-freebsd-alpha@FreeBSD.ORG>
Delivered-To: freebsd-alpha@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 60D1B37B401; Thu, 24 Apr 2003 09:36:08 -0700 (PDT)
Received: from gatekeeper.oremut01.us.wh.verio.net
	(gatekeeper.oremut01.us.wh.verio.net [198.65.168.16])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 97EE443FBF; Thu, 24 Apr 2003 09:36:07 -0700 (PDT)
	(envelope-from fclift@verio.net)
Received: from mx.dmz.orem.verio.net (mx.dmz.orem.verio.net [10.1.1.10])
	by gatekeeper.oremut01.us.wh.verio.net (Postfix) with ESMTP
	id 2FDB83BF14B; Thu, 24 Apr 2003 10:36:07 -0600 (MDT)
Received: from vespa.dmz.orem.verio.net (vespa.dmz.orem.verio.net [10.1.1.59])
	by mx.dmz.orem.verio.net (8.11.6p2/8.11.6) with ESMTP id h3OGa6F77674;
	Thu, 24 Apr 2003 10:36:06 -0600 (MDT)
Date: Thu, 24 Apr 2003 10:40:29 -0600 (MDT)
From: Fred Clift <fclift@verio.net>
X-X-Sender: <fred@vespa.dmz.orem.verio.net>
To: <freebsd-alpha@freebsd.org>
Message-ID: <20030424070850.O68602-100000@vespa.dmz.orem.verio.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: re: fxp unaligned access 
X-BeenThere: freebsd-alpha@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting FreeBSD to the Alpha <freebsd-alpha.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-alpha>,
	<mailto:freebsd-alpha-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-alpha>
List-Post: <mailto:freebsd-alpha@freebsd.org>
List-Help: <mailto:freebsd-alpha-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-alpha>,
	<mailto:freebsd-alpha-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Apr 2003 16:36:08 -0000


Here is the trace on that unaligned access I previously mentioned.



So now that I know the unaligned access was in fxp_add_rfabuf in
src/sys/dev/fxp/if_fxp.c, So, how can I track this down to a specific line
of code? (I'm off to read the ddb manpage right now, so perhaps this is
just a dumb newbie quesiton...)



<much of boot -v removed here for brevity>

pcib1: device fxp0 requested decoded memory range 0x90800000-0x90800fff
fxp0: using memory space register mapping

fatal kernel trap:

    trap entry     = 0x4 (unaligned access fault)
    faulting va    = 0xfffffe00004b780e
    opcode         = 0x28
    register       = 0x1
    pc             = 0xfffffc00003bb180
    ra             = 0xfffffc00003bb13c
    sp             = 0xfffffc00008639a0
    usp            = 0x0
    curthread      = 0xfffffc0000725ea8
        pid = 0, comm = swapper

Stopped at      fxp_add_rfabuf+0x80:    zapnot  t0,#0xf3,t0     <t0=0x10>
db> t
fxp_add_rfabuf() at fxp_add_rfabuf+0x80
fxp_attach() at fxp_attach+0xd7c
device_probe_and_attach() at device_probe_and_attach+0xc8
bus_generic_attach() at bus_generic_attach+0x28
pci_attach() at pci_attach+0xe4
device_probe_and_attach() at device_probe_and_attach+0xc8
bus_generic_attach() at bus_generic_attach+0x28
pcib_attach() at pcib_attach+0x68
device_probe_and_attach() at device_probe_and_attach+0xc8
bus_generic_attach() at bus_generic_attach+0x28
pci_attach() at pci_attach+0xe4
device_probe_and_attach() at device_probe_and_attach+0xc8
bus_generic_attach() at bus_generic_attach+0x28
device_probe_and_attach() at device_probe_and_attach+0xc8
bus_generic_attach() at bus_generic_attach+0x28
cia_attach() at cia_attach+0x1f0
device_probe_and_attach() at device_probe_and_attach+0xc8
root_bus_configure() at root_bus_configure+0x38
configure() at configure+0x40
mi_startup() at mi_startup+0x144
locorestart() at locorestart+0x64
--- root of call graph ---


Fred

--
Fred Clift - fclift@verio.net -- Remember: If brute
force doesn't work, you're just not using enough.