Date: Wed, 26 Oct 2005 22:06:10 +0200 From: Thierry Herbelot <thierry@herbelot.com> To: freebsd-current@freebsd.org Cc: Bill Paul <wpaul@freebsd.org> Subject: Re: error messages with ed(4) and current Message-ID: <200510262206.12508.thierry@herbelot.com> In-Reply-To: <20051026194801.0625816A421@hub.freebsd.org> References: <20051026194801.0625816A421@hub.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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<BROADCAST,SIMPLEX,MULTICAST> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200510262206.12508.thierry>