From owner-freebsd-sparc64@FreeBSD.ORG Sun Aug 17 20:47:28 2003 Return-Path: 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 DEC1D37B401 for ; Sun, 17 Aug 2003 20:47:28 -0700 (PDT) Received: from mail.seekingfire.com (coyote.seekingfire.com [24.72.10.212]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0EC5243F85 for ; Sun, 17 Aug 2003 20:47:28 -0700 (PDT) (envelope-from tillman@seekingfire.com) Received: from blues.seekingfire.prv (blues.seekingfire.prv [192.168.23.211]) by mail.seekingfire.com (Postfix) with ESMTP id 07DD928D for ; Sun, 17 Aug 2003 21:47:27 -0600 (CST) Received: (from tillman@localhost) by blues.seekingfire.prv (8.11.6/8.11.6) id h7I3lQQ27949 for sparc64@freebsd.org; Sun, 17 Aug 2003 21:47:26 -0600 Date: Sun, 17 Aug 2003 21:47:26 -0600 From: Tillman To: sparc64@freebsd.org Message-ID: <20030817214726.G15005@seekingfire.com> References: <20030815121010.I97608@beagle.fokus.fraunhofer.de> <20030815135034.GA701@crow.dom2ip.de> <20030815080055.O22214@seekingfire.com> <20030815143404.GB701@crow.dom2ip.de> <20030815110221.T22214@seekingfire.com> <20030815223159.F22214@seekingfire.com> <20030816051419.GA32579@dhcp42.pn.xcllnt.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20030816051419.GA32579@dhcp42.pn.xcllnt.net>; from marcel@xcllnt.net on Fri, Aug 15, 2003 at 10:14:19PM -0700 X-Urban-Legend: There is lots of hidden information in headers Subject: Re: Sparc slowdown - problem identified... X-BeenThere: freebsd-sparc64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the Sparc List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Aug 2003 03:47:29 -0000 On Fri, Aug 15, 2003 at 10:14:19PM -0700, Marcel Moolenaar wrote: > On Fri, Aug 15, 2003 at 10:31:59PM -0600, Tillman wrote: > > > > hme0: mem 0xe0000000-0xe0007fff at device 1.1 on pci1 > > hme0: Ethernet address: 08:00:20:c6:7f:c7 > > > > hme1: mem 0x2800000-0x2807fff at device 0.1 on pci3 > > hme1: Ethernet address: 08:00:20:c6:7f:c7 > > > > arp: 192.168.23.3 is on hme0 but got reply from 00:10:4b:69:2a:86 on hme1 > > arp: 192.168.23.3 is on hme0 but got reply from 00:10:4b:69:2a:86 on hme1 > > arp: 192.168.23.3 is on hme0 but got reply from 00:10:4b:69:2a:86 on hme1 > > > > Any ideas? > > Both hme0 and hme1 have the same MAC address. Suspicious... > > > Is it possible that the hme interfaces are numbered in a > > different order with the new kernel, similar to how the disk devices > > could have been renumbered (but that wasn't an issue for me)? > > Yes, definitely. When you enable OFW_NEWPCI, compare the old dmesg(8) > with the new one to see what has changed and correct your setup > accordingly. Results: Old buildkernel time: real 477m30.067s user 400m42.592s sys 24m45.618s New buildkernel time: real 151m42.832s user 125m20.230s sys 13m10.643s For folks attempting this, note that my 4-port ethernet card is now detected /after/ the onboard interface. Thus, I have hme0 & hme[1-4] instead of hme[0-3] & hme4. Rather than reconfigure, it was easier to just change cables around :-) -T -- Yield to temptation; it may not pass your way again. - Robert Heinlein