From owner-freebsd-sparc64@FreeBSD.ORG Sun Feb 5 12:45:37 2006 Return-Path: X-Original-To: sparc64@freebsd.org Delivered-To: freebsd-sparc64@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E069C16A420 for ; Sun, 5 Feb 2006 12:45:37 +0000 (GMT) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (newtrinity.zeist.de [217.24.217.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 50E6043D46 for ; Sun, 5 Feb 2006 12:45:37 +0000 (GMT) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (localhost [127.0.0.1]) by newtrinity.zeist.de (8.12.11/8.12.11/ZEIST.DE) with ESMTP id k15CjaOL007260; Sun, 5 Feb 2006 13:45:36 +0100 (CET) (envelope-from marius@newtrinity.zeist.de) Received: (from marius@localhost) by newtrinity.zeist.de (8.12.11/8.12.10/Submit) id k15CjUmk007259; Sun, 5 Feb 2006 13:45:30 +0100 (CET) (envelope-from marius) Date: Sun, 5 Feb 2006 13:45:30 +0100 From: Marius Strobl To: Yasholomew Yashinski Message-ID: <20060205134530.B5136@newtrinity.zeist.de> References: <20060204110201.W77754@mail.yashy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20060204110201.W77754@mail.yashy.com>; from yashy@mail.yashy.com on Sat, Feb 04, 2006 at 11:14:47AM -0500 X-AntiVirus-modified: yes X-AntiVirus: checked by AntiVir Milter (version: 1.1.2-1; AVE: 6.33.0.31; VDF: 6.33.0.204; host: newtrinity.zeist.de) Cc: sparc64@freebsd.org Subject: Re: vr(4) issue on Ultra 10 X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 05 Feb 2006 12:45:38 -0000 On Sat, Feb 04, 2006 at 11:14:47AM -0500, Yasholomew Yashinski wrote: > > I'm intending to use a U10 as a firewall/gateway, so I'm trying to add > one of my spare PCI NICs, to use along with the hme0. Trying dc(4) brought > my OS down (writing another email), so I'm trying vr(4) which is flooding > dmesg/syslog with errors. > Vr(4) has to be converted to use bus_dma(9) and probably also made endian-clean in order to also work on sparc64. Currently it has no chance to work on sparc64 and that's why it is commented out in the sparc64 GENERIC. As for your dc(4) problem; dc(4) generally is know to work on sparc64 but looks like there's a problem with the dcphy(4) pseudo PHY driver used for some variants. I can't spot any problem in its code and frame 6 of your dump appears to be corrupted. Could you maybe get the backtrace from a DDB-enabled kernel instead of a dump? Marius -- This mail was scanned by AntiVir Milter. This product is licensed for non-commercial use. See www.antivir.de for details.