From: Christopher Chan <cchan@outblaze.com>
To: Andrew Morton <akpm@osdl.org>
Cc: netdev@oss.sgi.com
Subject: Re: linux 2.6.9 still having network code problems
Date: Tue, 02 Nov 2004 16:38:34 +0800 [thread overview]
Message-ID: <4187478A.1040002@outblaze.com> (raw)
In-Reply-To: <20041102011918.2b453e21.akpm@osdl.org>
>>Previously with 2.6.7 I had to use this values in sysctl to be able to
>>continue to access the box:
>>
>>net.ipv4.tcp_max_syn_backlog = 2048
>>net.ipv4.route.gc_thresh = 65536
>>net.ipv4.route.max_size = 1048576
>
>
> Why?
without these, i get dst cache overflow errors and the similar
networking error messages and the box is inaccessible via the network
and unusable via serial console.
>
>
>>2.6.9 without this values gave me similar problems with 2.6.7 without
>>the above values.
>
>
> What problems?
See above.
>
>
> You ran out of memory. All your memory is in use by userspace processes.
DOH. the kernel swapped the controller order on me...fstab entries
referred to the wrong device names...
>
>
>
> Try mounting some swapspace.
swapon -a issued :P
>
>
>>Nov 1 03:16:00 spf5-3 kernel: Out of Memory: Killed process 21861 (smtpd).
>>Nov 1 03:16:00 spf5-3 kernel: KERNEL: assertion (flags & MSG_PEEK)
>>failed at net/ipv4/tcp.c (1284)
>>Nov 1 03:16:00 spf5-3 kernel: recvmsg bug: copied 1E619F78 seq 1E61A378
>>Nov 1 03:16:00 spf5-3 kernel: KERNEL: assertion (flags & MSG_PEEK)
>>failed at net/ipv4/tcp.c (1284)
>>Nov 1 03:16:00 spf5-3 kernel: recvmsg bug: copied 1E619F78 seq 1E61A378
>>Nov 1 03:16:00 spf5-3 kernel: KERNEL: assertion (tp->copied_seq ==
>>tp->rcv_nxt || (flags & (MSG_PEEK | MSG_TRUNC))) failed at
>>net/ipv4/tcp.c (1348)
>>Nov 1 03:16:00 spf5-3 kernel: KERNEL: assertion (flags & MSG_PEEK)
>>failed at net/ipv4/tcp.c (1284)
>>Nov 1 03:16:00 spf5-3 kernel: recvmsg bug: copied 1E619F78 seq 1E61A378
>>Nov 1 03:16:00 spf5-3 kernel: KERNEL: assertion (tp->copied_seq ==
>>tp->rcv_nxt || (flags & (MSG_PEEK | MSG_TRUNC))) failed at
>>net/ipv4/tcp.c (1348)
>>Nov 1 03:16:00 spf5-3 kernel: KERNEL: assertion (flags & MSG_PEEK)
>>failed at net/ipv4/tcp.c (1284)
>>Nov 1 03:16:00 spf5-3 kernel: recvmsg bug: copied 1E619F78 seq 1E61A378
>>Nov 1 03:16:00 spf5-3 kernel: KERNEL: assertion (tp->copied_seq ==
>>tp->rcv_nxt || (flags & (MSG_PEEK | MSG_TRUNC))) failed at
>>net/ipv4/tcp.c (1348)
>
>
> This is a networking bug.
>
Yes...it's the same one that won't allow me to use the e100 driver with
NAPI enabled with or without them sysctl tweaks and the same one that
forces me to use the tweaks without NAPI enabled for the e100 driver.
With NAPI enabled, I see the problem when under pressure.
FYI, the 2.6.9 kernel is running with NAPI enabled.
next prev parent reply other threads:[~2004-11-02 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 8:14 linux 2.6.9 still having network code problems Christopher Chan
2004-11-02 9:19 ` Andrew Morton
2004-11-02 8:38 ` Christopher Chan [this message]
2004-11-02 9:41 ` Andrew Morton
2004-11-04 1:08 ` Christopher Chan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4187478A.1040002@outblaze.com \
--to=cchan@outblaze.com \
--cc=akpm@osdl.org \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).