From owner-freebsd-current@FreeBSD.ORG Wed Oct 26 20:06:23 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CC78516A41F; Wed, 26 Oct 2005 20:06:23 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from smtp3-g19.free.fr (smtp3-g19.free.fr [212.27.42.29]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5889143D48; Wed, 26 Oct 2005 20:06:23 +0000 (GMT) (envelope-from thierry@herbelot.com) Received: from herbelot.dyndns.org (bne75-4-82-227-159-103.fbx.proxad.net [82.227.159.103]) by smtp3-g19.free.fr (Postfix) with ESMTP id 4A39F36E4E; Wed, 26 Oct 2005 22:06:22 +0200 (CEST) Received: from diversion.herbelot.nom (diversion.herbelot.nom [192.168.2.6]) by herbelot.dyndns.org (8.13.3/8.13.3) with ESMTP id j9QK6JjB027865; Wed, 26 Oct 2005 22:06:21 +0200 (CEST) From: Thierry Herbelot To: freebsd-current@freebsd.org Date: Wed, 26 Oct 2005 22:06:10 +0200 User-Agent: KMail/1.8.2 References: <20051026194801.0625816A421@hub.freebsd.org> In-Reply-To: <20051026194801.0625816A421@hub.freebsd.org> X-Warning: Windows can lose your files X-Op-Sys: Le FriBi de la mort qui tue X-Org: TfH&Co X-MailScanner: Found to be clean MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200510262206.12508.thierry@herbelot.com> Cc: Bill Paul Subject: Re: error messages with ed(4) and current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: thierry@herbelot.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Oct 2005 20:06:23 -0000 Le Wednesday 26 October 2005 21:48, Bill Paul a écrit : > > Getting a few watchdog timeouts is not unexpected in this case, since > it means you lost an interrupt somewhere, which I suppose can happen > if the host CPU is slow or very heavily loaded (which I guess it > would be if you're building world). Hopefully it recovers quickly. indeed : this (slow) machine has recovered from the timeouts and is valiantly compiling its world (and I forgot to set CFLAGS to just -O : next time will be faster) > > > the NIC is detected as : > > %grep ed2 /var/run/dmesg.boot > > ed2 at port 0x300-0x31f iomem 0xd8000 irq 10 on isa0 > > ed2: Ethernet address: 52:54:4c:1b:90:1b > > ed2: type RTL8019 (16 bit) > [SNIP] > > Bit 1 is set in your address (the 2 in '52') which means either the > code to read the station address from the NIC is broken, or the > EEPROM on your card is scrambled. Or both. then I've got one more bogus NIC on the same machine (this one PCI-based) : ed1: flags=8802 mtu 1500 ether 52:54:00:e5:36:06 as all of these are just junk chinese old NIC's, a snafu from the manufacturer could also be a valid explanation. interestingly (?), my other ISA-based ed board is seen as : ed0 at port 0x280-0x29f iomem 0xd8000 irq 9 on isa0 ed0: Ethernet address: 00:40:05:61:20:3e ed0: type NE2000 (16 bit) (that is, with a correct MAC address) TfH