6.3 nfe: dead after system reset

[Luigi Rizzo]

On Fri, Jul 04, 2008 at 12:26:39AM +0300, Andriy Gapon wrote:
> 
> As they say - long time, no see :-)
> I am back with some more details, but still with no insights.
> 
> Let me refresh an essence of the issue.
> The issue: after 'abrupt' reset/reboot of a system my nfe interface is dead.
> That is, if I do a graceful reboot (e.g. via shutdown -r) everything is 
> ok, ditto if I do power-down (whether graceful or not) and the power-up.
> The problem happens only if I press reset button and then boot up.
> 
> Details.
> The issue can not be reproduced with nve driver.
> Moreover, when I reproduce the problem with nfe, then kldunload nfe 
> driver, kldload nve driver - nve interface is alive. Then kldunload nve, 
> kldload nfe - nfe interface is dead again.
> 
> Specification of dead.
> There are no errors. ifconfig shows the same output (active, media, up, 
> etc) as in normal case. But I can not ping any host on local network 
> (connected to the same switch), ping outputs "Host is down". tcpdump 
> also doesn't show any incoming traffic.
> 
> More details.
> I was able to verify that packets do actually go through the interface. 
> When I try to ping some machine I see (on the other host) arp requests 
> for its ethernet address. All address in arp packets are correct 
> (ethernet and ip). So the interface works for outgoing packets, but 
> somehow loses incoming arp replies. Not sure if thap happens in the NIC 
> or in the driver itself (see the above nve/nfe live replacement experiment).

these symptoms (outgoing traffic is ok, incoming not received)
are similar to what i see in other conditions on my machine, see

http://www.mavetju.org/mail/view_message.php?list=freebsd-net&id=2730309

it is interesting that if_nve works ok, maybe we can compare the
two drivers and see if they initialize the device in different
ways (or test for receive interrupts in different ways)

cheers
luigi