public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: shuz@isolate.net
To: linux-kernel@vger.kernel.org
Subject: kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229)
Date: Mon, 13 Jan 2003 11:33:12 -0500	[thread overview]
Message-ID: <69415931157.20030113113312@isolate.net> (raw)

Hi,

First let me apologize if this doesn't belong on the list, I wasn't
sure where to ask and I want to make sure this is a non-fatal error
(100% of the time).

www1 is a Dual PIII 733, 1G ram, eepro100 network card. gets around
15-35mbits of traffic.

www3 is a Dual P3 1GHZ with 1G ram, and also an eepro100 network card.
load balanced with www1, 15-35mbits of traffic.

around 5 days ago I updated to 2.4.20 (from 2.4.18) and noticed these
kernel (errors?) this morning at around the same time on each server.

Jan 13 09:12:38 www1 kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229)
Jan 13 09:12:38 www1 kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689)

Jan 13 09:08:44 www3 kernel: KERNEL: assertion (newsk->state != TCP_SYN_RECV) failed at tcp.c(2229)
Jan 13 09:08:44 www3 kernel: KERNEL: assertion ((1<<sk2->state)&(TCPF_ESTABLISHED|TCPF_CLOSE_WAIT|TCPF_CLOSE)) failed at af_inet.c(689)  

if someone could please provide insight on exactly what is happening
when this happens, it would be greatly appreciated. are there any side
effects? is this a kernel bug?

if you need more information please let me know.

Thanks,
Mike



                 reply	other threads:[~2003-01-13 16:24 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=69415931157.20030113113312@isolate.net \
    --to=shuz@isolate.net \
    --cc=linux-kernel@vger.kernel.org \
    /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