Subject: RE: IP stack stop responding
To: None <firstname.lastname@example.org>
From: Jan H. van Gils <JanVG@Knoware.NL>
Date: 11/16/2004 12:18:43
On zondag 14 november 2004 14:59 Timo wrote:
>> grep -i 3com /var/log/messages
>> Nov 14 14:28:22 borg /netbsd: ex0 at pci0 dev 10 function 0:
>> 00 Ethernet (rev. 0x24)
>> Nov 14 14:28:22 borg /netbsd: ex0: interrupting at irq 10
>> Nov 14 14:28:22 borg /netbsd: ex0: MAC address 00:10:4b:06:80:9a
>> Nov 14 14:28:22 borg /netbsd: exphy0 at ex0 phy 24: 3Com
>> So messages is not giving a lot of extra information ;-)
>so there seems no 'useful' information on your system...
No I agree, no extra information ;-(
>is your 10mbps hub manageable? or do you have one handy? if so, there
>maybe a hint in it's logs.
No, I don't have a manageble Hub.
>second, if you don't have any manageable devices handy, try
>tcpdump and try to reproduce the failure. maybe the dump shows what's
A tcpdump is also not soming any information
One thing that could be a problem is this:
Here a part of the src/UPDATING file:
The method by which athhal-elf.o gets pulled into i386
kernel builds has been changed again. The latest version
of bsd.files.mk is no longer required.
I seem to have problems with this object file when building the
kernel. I get the message that this file (athhal-elf.o) is missing when
the kernel. Could this be a problem ?