Was running 2.2.15pre18 with no eepro problems.
Upgraded to 2.2.18pre20 and started experiencing transmit timed out errors
a day into the boot. eth0 was unresponsive in/out. down/uping the
interface had no effect. System was not under any big network load.
See attached text file for related kernel messages.
System is Intel PR440FX mobo, SMP, glibc 2.1.3, gcc 2.95.2
Thanx,
-Tony
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Anthony J. Biacco Network Administrator/Engineer
[email protected] Intergrafix Internet Services
"Dream as if you'll live forever, live as if you'll die today"
http://www.asteroid-b612.org http://www.intergrafix.net
.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-._.-.
Hello,
On Thu, Nov 16, 2000 at 09:28:44AM -0500, Admin Mailing Lists wrote:
> Was running 2.2.15pre18 with no eepro problems.
> Upgraded to 2.2.18pre20 and started experiencing transmit timed out errors
> a day into the boot. eth0 was unresponsive in/out. down/uping the
> interface had no effect. System was not under any big network load.
> See attached text file for related kernel messages.
> System is Intel PR440FX mobo, SMP, glibc 2.1.3, gcc 2.95.2
The problem isn't in the kernel version.
The bug just shows not with 100% frequency.
Investigations are in progress.
Best regards
Andrey V.
Savochkin