Subject: Re: IP stack stop responding
To: Jan H. van Gils <JanVG@Knoware.NL>
From: =?ISO-8859-1?Q?Timo_Sch=F6ler?= <firstname.lastname@example.org>
Date: 11/18/2004 09:46:11
>>>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.
...so i guess next best is matthias' (scheler) advice to backtrace this
problem via gdb on NetBSD ;)
>>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
that is (IMHO) kinda strange =8-)
> 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 ?
might be, but unfortunately i'm not able to reproduce that here at the