Follow-up: in the mean time I upgraded to test13-pre3. Things look fine so
far, but I got this in the kernel log:
TCP: peer 203.65.190.178:25/57885 shrinks window 2375104836:0:2375106284. Bad, what
else can I say?
On Sun, Dec 10, 2000 at 02:57:21AM -0800, David S. Miller wrote:
>Date: Sun, 10 Dec 2000 13:10:33 +0200
>From: Petru Paler <[EMAIL PROTECTED]>
>
>So should I apply your patch ?
>
> Yes, this new OOPS you've sent me is in the same place.
Ok, applied. Will email again when/if somethin
Date: Sun, 10 Dec 2000 13:10:33 +0200
From: Petru Paler <[EMAIL PROTECTED]>
So should I apply your patch ?
Yes, this new OOPS you've sent me is in the same place.
Later,
David S. Miller
[EMAIL PROTECTED]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the b
On Sun, Dec 10, 2000 at 02:38:28AM -0800, David S. Miller wrote:
> Is this always the _first_ OOPS though? That is what is important,
> because after the first OOPS all the others are likely just side
> effects of the first one.
No, it was not the first one. Here's the ksymoops'ed first one:
ks
Date: Sun, 10 Dec 2000 10:55:53 +0200
From: Petru Paler <[EMAIL PROTECTED]>
[5.] Output of Oops.. message (if applicable) with symbolic information
resolved (see Documentation/oops-tracing.txt)
This is only one of the repeated o
Let me know if you need additional info or testing done.
Bug report (in standard format):
[1.] One line summary of the problem:
Repeated kernel oopses, after a while of functioning under
heavy load.
[2.] Full description of the probl
6 matches
Mail list logo
