> > I talked to Don about this at the Expo. Don's theory is that its the SMbus
> > management stuff (the onboard eepro and firmwar eof their own accord
> > support stuff like 'machine tampered with' and 'reboot' packets). Intel
> > apparently havent provided enough documentation to handle this right now.
> > > So there's definitely something fishy going on with the combination of
> > > eepro100 and IPv6. Bad, since I really want to start deploying IPv6
> > > in our local test bed here (as soon as RIPE hands out some v6 addresses).
> > Ok. The Ipv6 may be cause or a symptom Im not sure which.
I don't think it is ipv6. I have two machines w/ eepro100 cards, one onboard.
Every 10-30 seconds, the cards storm the network, totally disabling it for
anywhere between 5 and 30 seconds -unless- the card is in promiscuous mode. If
the card is left in promisc, it'll function perfectly.
While this storm is going on, the machine originating it appears completely
unaware of the activity. tcpdump on that machine shows nothing however any other
machine shows the packet flood. The packet flood is entirely comprised of one
specific packet for that particular flood. Perhaps it is the last packet being
sent and the transmitter gets wedged?
This has been happening since early 2.2.x.
If anyone wishes tcpdump captures, I'll be happy to provide them.
-d
-- This is Linux Country. On a quiet night, you can hear Windows NT reboot! Do you remember how to -think- ? Do you remember how to experiment? Linux __ is an operating system that brings back the fun and adventure in computing. \/ for linux-kernel: please read linux/Documentation/* before posting problems
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/