Date: Fri, 27 Oct 2000 22:30:09 -0700 (PDT)
From: Clayton Weaver <cgweav@eskimo.com>
To: linux-kernel@vger.kernel.org
Subject: update: i21143 (tulip) and 2.2.17 (upgrade to .91-g and egcs-1.1.2 seems to have fixed it)
Message-ID: <Pine.SUN.3.96.1001027221305.9711A-100000@eskimo.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: linux-kernel-owner@vger.kernel.org

Update on the hang during ftp on stock Debian potato (2.2.17-pre6 IIRC)
with i21143 tulip pci ethernet:

I changed to gcc-2.91.66 (egcs-1.1.2; Debian afaik used gcc 2.7.2.3
or 2.95.2 to compile the pre-compiled vanilla distribution kernel in
potato) and upgraded the 2.2.17-pre_something kernel to the final 2.2.17
(with the .91-g tulip driver), using binutils-2.9.1.0.25, glibc-2.1.3,
and compiled a monolithic kernel while running 2.0.38.

Everything seems ok (simple needs). Too many changes to pin down the cause
of the earlier deadlock that I reported, and it's too soon to see if there
will still be sporadic wrong ext2fs block counts at e2fsck time, but no
deadlocks so far, no oopses, ftp works, ping works, http works, etc.

So the kernel upgrade and kernel compiler change in combination is at
least much more stable, without being to say why exactly (ie "for anyone
that had doubts, there are kernels after 2.0.38 where a real tulip card
is reliable, if you have the lucky compiler").

:-),

Clayton Weaver
<mailto:cgweav@eskimo.com>
(Seattle)

"Everybody's ignorant, just in different subjects."  Will Rogers


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/