One (and only one) of them is giving me problems :
stock 2.0.23 kernel + 0.28c version of 3c59x.c
eth0: 3Com 3c590 Vortex 10Mbps at 0xff80, 00:a0:24:52:1c:a3, IRQ 15
Internal config register is 320010, transceivers 0xe138.
8K byte-wide RAM 1:1 Rx:Tx split, 10base2 interface.
3c59x.c:v0.28c 8/25/96 email@example.com
I have this on syslog :
Oct 22 09:20:09 ganymede kernel: eth0: Transmitter access conflict.
Oct 22 09:20:09 ganymede last message repeated 22 times
Those messages seemed to be harmless, but after a week of uptime, the
3c590 is now dead, that is no more ethernet packets (in or out).
The other eth card (an ne2000) on the computer is still OK.
I must say that I saw the problem on the very same machine with 2.0.22
+ original driver. (with v0.25 of 3c59x, i didn't even see the Transmitter
access conflict error)
Is it an hardware problem ? This machine is a P133 we used without
problems for months. We have problems since last month, but i'm not
sure this is related to a special kernel version.
Any ideas ?
-- Yann.-- _ _ ___ _________________________________ | | || . \ | Fac des sciences de Nantes. | \ /| | | _ | Tel : 40373069 / 40374945 | |_| |___/<_> | firstname.lastname@example.org | ---------------------------------