Too much work at interrupt
Donald Becker
becker@cesdis1.gsfc.nasa.gov
Sat Nov 7 01:23:43 1998
On Sat, 7 Nov 1998, Daniel Veillard wrote:
> message (while they show the "SMP simultaneous entry of an interrupt handler"
> occasionnaly but apparently without damage on 1.03).
Try the SMP patch from Loic Prylli <Loic.Prylli@ens-lyon.fr>
http://beowulf.gsfc.nasa.gov/linux/misc/smp-bug.html
> Any chance that both are variations of the same 2.0.xx SMP kernel bug ?
> Shoudl I upgrade to 1.05 ? Should I try to increase the
> static int max_interrupt_work = 20;
> increase as suggested in a past mail ?
Yes, upgrade if you use multicast.
You can increase the max_interrupt_work value when loading the module:
echo "options eepro100 max_interrupt_work=40" >> /etc/conf.module
> Our servers are all using the EEPro100 and that's the first time I see
> this, is it just bad luck of something related to some hardware setup ?
> I had pushed the machine under a double 100MBps ping flood without seeing
> the error which occured only when starting pushing the HTTP and AFS setup.
This is probably occuring because the machine is under high load.
If the machine doesn't have real-time responsibilities, increasing the work
permitted is safe.
Donald Becker becker@cesdis.gsfc.nasa.gov
USRA-CESDIS, Center of Excellence in Space Data and Information Sciences.
Code 930.5, Goddard Space Flight Center, Greenbelt, MD. 20771
301-286-0882 http://cesdis.gsfc.nasa.gov/people/becker/whoiam.html