hello,
Does anybody have an idea what does these logs mean in /var/log/messages.


May 25 00:21:07 kernel: eth1: Too much work at interrupt, IntrStatus=0x0001.
May 25 00:21:07 kernel: klogd 1.4.1, ---------- state change ----------
May 25 00:21:07 kernel: Inspecting /boot/System.map-2.4.20-4GB
May 25 00:21:07 kernel: Loaded 20952 symbols from /boot/System.map-2.4.20-4GB.
May 25 00:21:07 kernel: Symbols match kernel version 2.4.20.
May 25 00:21:07 kernel: Loaded 829 symbols from 28 modules.
May 25 00:21:15 kernel: eth1: PCI Bus error 1000.
May 25 00:21:15 kernel: eth1: PCI Bus error 1000.
May 25 00:21:15 kernel: eth1: PCI Bus error 8290.
May 25 00:21:15 last message repeated 14 times
May 25 00:21:15 kernel: eth1: Too much work at interrupt, IntrStatus=0x0020.
May 25 00:22:00 /USR/SBIN/CRON[12675]: (root) CMD (/bin/sh /root/.getmail/get_design)
May 25 00:23:49 kernel: NETDEV WATCHDOG: eth1: transmit timed out
May 25 00:23:49 kernel: eth1: Tx queue start entry 4100160 dirty entry 4100156.
May 25 00:23:49 kernel: eth1: Tx descriptor 0 is 00002000. (queue head)
May 25 00:23:49 kernel: eth1: Tx descriptor 1 is 00002000.
May 25 00:23:49 kernel: eth1: Tx descriptor 2 is 00002000.
May 25 00:23:49 kernel: eth1: Tx descriptor 3 is 00002000.
May 25 00:23:49 kernel: eth1: Setting 100mbps full-duplex based on auto-negotiated partner ability 41e1.
May 25 00:23:55 kernel: eth1: Too much work at interrupt, IntrStatus=0x0001.
May 25 00:24:00 /USR/SBIN/CRON[12688]: (root) CMD (/bin/sh /root/.getmail/get_others)
May 25 00:24:00 /USR/SBIN/CRON[12691]: (root) CMD (/bin/sh /root/.getmail/get_marketing)
May 25 00:24:08 Kernel: eth1: Too much work at interrupt, IntrStatus=0x0001.


Thanks,
Prashant.

It means that the NIC adapter is requesting too much atention from the PCI bus, this means that other devices might get no answer from PCI 'couse it is too busy!

There is a paremeter in the kernel module (or using sysctl) to put a higher limit on the NIC adaptar, but you should not do that unless you have sure what you are doing.

This is pretty normal when somebody is trying to spoof you using some IP spoof trick.

Check you iptables and try to use some "ant-spoof" rule.

[]'s, FMC!