At 11:20 -0700 10/19/98, Jason Thorpe wrote:

>Note, the problem with spray and fxp0 IS NOT mb_map filling up.  There
>seems to be a bug in the transmit loop in the fxp driver, which I have
>seen occasionally but have been unable to reproduce reliably.  I suspect
>some race condition which causes the chip to lose the chain of command
>descriptors (hence the "device timeout").  You'll get ENOBUFS once the
>driver says - "No, you can't queue any more packets right now, I'm at
>my self-imposed limit."

This error message should be changed for this condition. It is inaccurate,
and the cause of much confusion. There should be an EQFULL instead, so that
people don't go looking at "netstat -m" after getting ENOBUFS and then
scratching their heads when they see that there's plenty of mbuf RAM.

	Erik