-----BEGIN PGP SIGNED MESSAGE-----
Harshul Nayak (ealcatraz) wanted us to know:
>one of the servers which is under my administration is a Linux box with dual
>processor, currently running redhat 7.3
>while checking through the logs (/var/log/messages) found out this error
>Jul 31 19:03:46 XXXXX kernel: ISR called reentrantly!!
>Jul 31 19:26:55 XXXXX kernel: ISR called reentrantly!!
>Jul 31 22:27:50 XXXXX kernel: ISR called reentrantly!!
It seems you are running a Dell server with the MegaRAID controller.
This is an error that a few people have seen according to google.
>When interacting with the hosting company they said it is BIOS issue , hence
>we updated the BIOS.
>then upgraded the kernel.
>Linux version 2.4.20-19.7smp
>Linux version 2.4.18-24.7.xsmp
Try a newer one too.
>Well after the BIOS upgrade everything seemed fine , till I enabled the
>The list has roughly around 1500 users.
>The ISR reentrant message has started to appear again.
>What is the relationship between sendmail and ISR reentrant messages or is
>it related to majordomo ?
It's taxing the I/O subsystem of the controller. Not much you can do
about it other than use different hardware or find a kernel which
doesn't have the bug which allows the OS to call the interrupt handler
while it's already in the interrupt handler. That's what reentrant
At any rate, this is no longer appropriate for this list as it's a Dell
hardware and kernel issue. MJ and Sendmail just happen to be taxing the
system. If you start a kernel compile on this box (known for taxing
kernel/systems) you would probably see similar results.
Blue skies... Todd Public key: http://www.mrball.net/todd.asc
I think we in the open source movement are the invisible hand of
the market, baby, or its middle finger, anyway." --Eric S. Raymond
Linux kernel 2.4.21-0.25mdk 6 users, load average: 0.15, 0.10, 0.03
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
-----END PGP SIGNATURE-----