'llo,
I've been using the 2.1.xxx kernels for some time now, although I hadi
to stop after 129 because for some reason the kernel would freeze solid with
a "Unable to dereference NULL kernel pointer" message (which I only got to
see if I were at console at lock time) after 1-2 days of continuous running.
(X, enlightenment, web/ftp/smb server, rc5).
With the 2.1.132 kernel, however, the pci-ne2k driver simply quits
transmitting correctly after only a few hours, swamping /var/log/messages
with
Dec 26 15:18:52 azimuth kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR
=0x3, t=1000.
Dec 26 15:19:02 azimuth kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR
=0x2, t=1000.
Dec 26 15:19:12 azimuth kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR
=0x3, t=1000.
Dec 26 15:20:57 azimuth kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR
=0x3, t=10500.
Dec 26 15:32:57 azimuth kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR
=0x3, t=72000.
(I've got 2 LanPro cards, both called from the pci-ne2k driver. works fine under
2.0.xx)
System is a dual P2-333, Soyo 6KD mainboard and 64Mb ram.
I compile the 2.1.xxx kernels with gcc version pgcc-2.91.60 19981201 , using
the standard C flags in the makefile.
Any suggestions what may ba causing this?
Thanks in advance,
Rens Houben.
-
Linux SMP list: FIRST see FAQ at http://www.irisa.fr/prive/mentre/smp-faq/
To Unsubscribe: send "unsubscribe linux-smp" to [EMAIL PROTECTED]
