Too much work at interrupt?

[Chris Sterling]

	I appreciate the help! I'll give that a shot. It looks like I've
got 0.99B, but the code for that is the same. I'll try 1.03 if I have any
problems with the one I have. 

	Do you know a way to test the setup?  The ethernet load has not
been very high when this happens. 

Thanks!

--------------------------------
Chris Sterling					
System Administrator
EazeNet					     
lemmy@eaze.net
Office:	817-557-3038
Fax:	817-557-3468


On Wed, 28 Oct 1998, James Stevens wrote:

> Chris Sterling wrote:
> > 
> > kernel: eth0: Too much work at interrupt, status=0x4050
> 
> ...Before you read this e-mail accept that I did not write the driver
> and I my be wrong in what I say, but I am doing my best to help...
> 
> I can tell you what this means if it is any help.
> 
> When the card pulls an interupt the eepro driver will service any jobs
> the card wants done (e.g. Rx any waiting packets) not just the first
> one. However, to try and prevent the driver from going into a infinite
> loop the driver has a hard coded limit on the number of waiting requests
> that it will service per interupt.
> 
> This error message means that you have exceeded the maximum number of
> waiting requests on the card for the one interupt. You could probably
> safely increase the limit a bit without causing too much trouble.
> 
> At line 40 in 1.03 of the driver you will find the lines :-
> 
> /* Maximum events (Rx packets, etc.) to handle at each interrupt. */
> static int max_interrupt_work = 20;
> 
> increase the 20 and see how it goes.
> 
> James
>