I'm getting these messages in my logfiles:
Oct 27 00:18:23 planetzork kernel: eth0: Interrupted while interrupts are masked! isr=0x0 imr=0x0.
Oct 27 00:23:00 planetzork kernel: eth0: Interrupted while interrupts are masked! isr=0x2 imr=0x0.
I'm using a LanPro isa ne2k-clone. Is this a known problem? Here are some
more infos:
[root@planetzork linux]# lsmod
Module Size Used by
hisax 103488 2 (autoclean)
isdn 98876 5 (autoclean) [hisax]
ne 5896 1 (autoclean)
8390 5784 0 (autoclean) [ne]
[root@planetzork linux]# cat /proc/interrupts
CPU0 CPU1
0: 9811502 9847354 IO-APIC-edge timer
1: 1085 1151 IO-APIC-edge keyboard
2: 0 0 XT-PIC cascade
4: 161 97 IO-APIC-edge serial
8: 1 0 IO-APIC-edge rtc
9: 3 0 IO-APIC-edge HiSax
10: 5498206 5580359 IO-APIC-edge NE2000
12: 1 0 IO-APIC-edge PS/2 Mouse
13: 1 0 XT-PIC fpu
15: 503295 506992 IO-APIC-edge HiSax
19: 201078 200878 IO-APIC-level aic7xxx
NMI: 0
IPI: 0
[root@planetzork linux]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Bcast:127.255.255.255 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:83384 errors:0 dropped:0 overruns:0
TX packets:0 errors:34491379 dropped:83384 overruns:0
eth0 Link encap:Ethernet HWaddr 00:00:B4:32:4C:87
inet addr:195.37.122.246 Bcast:195.37.122.255 Mask:255.255.255.255
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3601718 errors:0 dropped:0 overruns:0
TX packets:314 errors:467227426 dropped:8078595 overruns:0
Interrupt:10 Base address:0x280
eth0:0 Link encap:Ethernet HWaddr 00:00:B4:32:4C:87
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
No statistics available.
Interrupt:10 Base address:0x280
I'm having not that much traffic on my network because there are only
two machines on it. One server and one linux client used as x-terminal.
If you need more infos to debug this just let me know. If somebody wants
me to test some patches or to track down the bugs I'd like to help as much
as I can.
Regards,
Jogi
Whoops, the machine is running 2.1.126-pre2-ac2 smp. Although the problem
exists with previous kernels too.
--Well, yeah ... I suppose there's no point in getting greedy, is there?
<< Calvin & Hobbes >>
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/