Greg Troxel <g...@work.lexort.com> writes: I posted about a net5501 newly running netbsd-6 with
> sys/dev/pci/if_vr.c 1.112 via patch > > Reset the vr(4) chip if the tx engine gets stuck. No need to > do a full reset when enabling/disabling promiscuous mode. > [taca, ticket #783] and had said: > booting from applying power worked fine > > rebooting led to the system being up but vr0 being nonfunctional > > on the up/no-vr0 system, running tcpdump printed a message: > vr0: using force reset command. > and then it worked ok. I did 33 reboots, and got 4 vr0 wedges. Closer inpsection makes me think that the ethernet is receiving packets fine. The system records that packets are being sent fine (opkts, no oerrs), but they don't seem to actually go out. If I do 'tcpdump -n -p -i vr0' (to avoid toggling promiscuous mode), I can see incoming packets. If I do 'ifconfig vr0 down;ifconfig vr0 up', I get Feb 27 14:50:12 hostname /netbsd: vr0: using force reset command. and it recovers. Using tcpdump without -p also forces a reset. It's been pointed out to be that the OpenBSD driver has a number of improvements, so I'll look at this, but it seems the chip is in a special out-to-lunch mode where tx packet processing falsely appears to succeed.
pgp1DUZc96Ek2.pgp
Description: PGP signature
_______________________________________________ Soekris-tech mailing list Soekris-tech@lists.soekris.com http://lists.soekris.com/mailman/listinfo/soekris-tech
