eth0 interrupt handler problem in 2.1.10x on alpha

Christian Iseli (chris@ludwig-alpha.unil.ch)
Tue, 09 Jun 1998 10:55:42 +0300


Hi folks,

I have tried 2.1.105 (and some previous ones too) on an AlphaPC 164 LX (Durango
II) machine. Hardware is 600 MHz alpha EV56, 128 MB RAM, Adaptec 2940,
ncr53c810a, PCI NE2000 clone, ES1688 AudioDrive.

Software is RH 5.0, BFD 2.9.1.0.4, EGCS 1.0.3, plus the recommended updates
from the Changes file.

I can compile the kernel without problems. Compiled *without* SMP.

When I boot the kernel, the first strange thing are three messages saying
unhandled interrupt 3
unhandled interrupt 4
unhandled interrupt 14 (14 seem to be the ide)

Then things seem to go normally, until the system tries to mount NFS
partitions, at which point a whole bunch of messages are displayed:
eth0: Reentering the interrupt handler! isr=0x70 imr=0x0.
eth0: Reentering the interrupt handler! isr=0x1 imr=0x0.

endlessly, with short pauses.

There are also messages about portmap and lockd:
portmap: RPC call returned error 61
RPC: task of released request still queued!
RPC: (task is on xprt_pending)
portmap: RPC call returned error 61
RPC: task of released request still queued!
RPC: (task is on xprt_pending)
lockd_up: makesock failed, error=-61

lockd_up: no pid, 3 users??

Also, the start of the log is garbled:
Jun 8 18:54:55 ludwig-alpha kernel: Symbols match kernel version 2.1.105.
Jun 8 18:54:56 ludwig-alpha kernel: Error seeking in /dev/kmem
Jun 8 18:54:56 ludwig-alpha kernel: Error adding kernel module table entry.
Jun 8 18:54:56 ludwig-alpha kernel: rrupt handler! isr=0x1 imr=0x0.
Jun 8 18:54:56 ludwig-alpha kernel: eth0: Reentering the interrupt handler! isr=0x1 imr=0x0.
Jun 8 18:54:56 ludwig-alpha last message repeated 15 times

Except for the endless flow of error messages on the console, the system
appears to be running normally.

I once tried, with a previous kernel, to disable the printk of the error
message. The kernel then froze.

Does anybody have any clue of what the problem might be ?

Christian

P.S. Some nit-picking... why do all my kernels, regardless of version (2.0.x,
2.1.x) always say "Error seeking in /dev/kmem" ?

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu