From owner-freebsd-alpha  Wed Nov 29  6:31:19 2000
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 27C5B37B401
	for <freebsd-alpha@FreeBSD.ORG>; Wed, 29 Nov 2000 06:31:13 -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 JAA26065;
	Wed, 29 Nov 2000 09:31:12 -0500 (EST)
Received: (from gallatin@localhost)
	by grasshopper.cs.duke.edu (8.11.1/8.9.1) id eATEVC583674;
	Wed, 29 Nov 2000 09:31:12 -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: Wed, 29 Nov 2000 09:31:11 -0500 (EST)
To: "M. Lara" <mlara@zec.lodz.pl>
Cc: freebsd-alpha@FreeBSD.ORG
Subject: Re: NIC driver vx0 
In-Reply-To: <3A24F240.1469FF61@zec.lodz.pl>
References: <3A24F240.1469FF61@zec.lodz.pl>
X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs  Lucid
Message-ID: <14885.3966.70843.920555@grasshopper.cs.duke.edu>
Sender: owner-freebsd-alpha@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


M. Lara writes:
 > I have FreeBSD 4.1 on UP1000 motherboard with Alpha 264 CPU, and 3Com590
 > Etherlink III adapter. When i try config this adapter FreeBSD hangs with
 > message:
 > 
 > #ifconfig vx0 inet 10.1.1.100
 > 
 > fatal kernel trap:
 >     trap entry = 0x4    (unaligned access fault)
 >     a0 = 0xfffffe00002f16d2
 >     a1 = 0x28
 >     a2 = 0x11
 >     pc = 0xfffffc0000387a34
 >     ra = 0xfffffc00003879e0
 >     curproc = 0xfffffe00065acb40
 >         pid = 194, comm = ifconfig
 >     panic: trap
 > 
 > On FreeBSD 2.2.x and i386 this adapter work good.

This problem (unaligned access fault) is specific to the alpha.

Can you compile a kernel with debugging enabled (config -g CONFIGFILE)
and map the PC and RA to lines in the source code?  Eg:

	% gdb kernel.debug
	<..>
	(gdb) l *0xfffffc0000387a34

Please crash the machine with the new kernel and use the pc/ra
numbers from the new crash with the new kernel.

The fastest path to getting your machine working might be to get
another network card (3c90x, Intel EtherExpress Pro, a tulip based
cards are known to be good).

Drew


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