On Sun, May 07, 2000 at 06:44:39PM +0930, Greg Lehey wrote:
I've just built a new kernel, based on a cvsup at 2030 UTC on 6 May,
and since then *some* Ethernet transactions don't work. I've checked
that it's not just a dead card: the previous kernel works fine. I
have the funny situation
Eines schoenen Tages schrieb Andrey A. Chernov:
On Sun, May 07, 2000 at 06:44:39PM +0930, Greg Lehey wrote:
I've just built a new kernel, based on a cvsup at 2030 UTC on 6 May,
and since then *some* Ethernet transactions don't work. I've checked
that it's not just a dead card: the
Eines schoenen Tages schrieb Oliver Schonefeld:
[snip]
It is not dead card, it is broken TCP, see my similar report in -current, I
notice it several hours ago right after TCP changes was commited.
Same thing here, but the problems have gone to -stabe too. due to a probable
tcp breakage i
-On [2507 14:50], Andrey A. Chernov ([EMAIL PROTECTED]) wrote:
It is not dead card, it is broken TCP, see my similar report in -current, I
notice it several hours ago right after TCP changes was commited.
I assume you mean the NewReno commit submitted by Jayanth?
--
Jeroen Ruigrok van der
On Sun, May 07, 2000 at 04:15:57PM +0200, Jeroen Ruigrok van der Werven wrote:
-On [2507 14:50], Andrey A. Chernov ([EMAIL PROTECTED]) wrote:
It is not dead card, it is broken TCP, see my similar report in -current, I
notice it several hours ago right after TCP changes was commited.
I
On Sun, May 07, 2000 at 04:15:57PM +0200, Jeroen Ruigrok van der Werven wrote:
-On [2507 14:50], Andrey A. Chernov ([EMAIL PROTECTED]) wrote:
It is not dead card, it is broken TCP, see my similar report in -current, I
notice it several hours ago right after TCP changes was commited.
On Sun, 7 May 2000, Mike Smith wrote:
Since there's a sysctl you can use to turn the former off, perhaps it
would have been smart to take a few seconds to narrow it down?
Those changes wouldn't have affected ICMP, but we tried that anyway.
The problem was that the code changed the