(usagi-users 03671) Re: Problems with stateless autoconf tests ...

Hi again!

I checked my machine with a different NIC (rtl8150) and it worked 
without problems!

Seems that this is related to the dmfe network driver. Any ideas what 
could cause a network driver to behave like this?

Kind regards,
Heiko


Mitsuru Chinen wrote:

> Hi,
>
> Heiko Gerstung wrote:
>
>>> 2.6.14 or former kernel had an issue - when the auto-negotiation
>>> took long time, DAD NS was lost.  This issue looks like that issue.
>>
>
> (snip)
>
>>> However, 2.6.15 should not have this issue.
>>> To make sure, could you try to let the auto-negotiation off?
>>
>>
>> I switched off auto negotiation on the NUT (Linux 2.6.15usagi with 
>> Davicom DM9xxx driver), but unfortunately the behaviour did not 
>> change. What else can I do? It seems that the unit is not sending DAD 
>> packets at all (checked with tcpdump), maybe there is something I can 
>> change in the kernel to initiate DAD manually after I loaded the 
>> network driver module?
>
>
> I tried somes NIC (requeired e100, e1000 and tg3), I don't
> faces this issue. So, it may be an issue of NIC / driver.
>
> I don't know it's related or not as I don't have Davicom NIC,
> it seems that 2.6.15 kernel has an issue with Davicom NIC.
> Regarding udev, kernel gets the tulip driver. It seems to cause
> some troubles.
>
>   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=326723
>
> Let me suggest you try the way written at the above-mentioned page.
>
> Best Regards,
> ----
> Mitsuru Chinen <[email protected]>
>
>
>