Subject: Re: re0 failing after reboot.
To: None <tech-kern@netbsd.org>
From: theo borm <theo4490@borm.org>
List: tech-kern
Date: 05/20/2005 12:33:22
theo borm wrote:

> theo borm wrote:
>
>>
>> re0 at pci0 dev 10 function 0: RealTek 8169S Single-chip Gigabit 
>> Ethernet
>> ukphy0 at re0 phy 7: Generic IEEE 802.3u media interface
>> re0: diagnostic failed, failed to receive packet in loopback mode
>> re0: attach aborted due to hardware diag failure
>
>
>
> Another datapoint: just now a machine hangs just after printing the
> line "Adding interface aliases" (haven't defined any) with its network
> acivity led on the switch blinking like mad. After unplugging and
> re-plugging the cable from the switch it starts to respond to pings
> again, and booting continues.....
>
> should I manually configure media types?, and could incorrect
> autoselection of media type be related to the loopback failure?

Ok, it seems related to media type setting/negotiation failure.

To summarize:

ifconfig       media-led   communications possible
10baseT,fdx    10MB        yes
10baseT        10MB        yes
100baseTX,fdx  100MB       no
100baseTX      100MB       no
1000baseT,fdx  100MB       no
1000baseT      100MB       no
autoselect     1000MB      yes

Could this mean that some bits are being fiddled the wrong way
round? Autoselect sometimes fails, and if that happens any media
led can be on, and communications impossible.

:-/ where to go from here? replace the switch? replace the NICs?
replace the cables? check kernel sources? sigh......


cheers, Theo.