From: "David S. Miller" <davem@redhat.com>
To: Ralf Nyren <ralf@nyren.net>
Cc: <linux-kernel@vger.kernel.org>, kuznet@ms2.inr.ac.ru
Subject: Re: 2.4.4: Kernel crash, possibly tcp related
Date: Sun, 29 Apr 2001 22:10:22 -0700 (PDT) [thread overview]
Message-ID: <15084.62398.56283.772414@pizda.ninka.net> (raw)
In-Reply-To: <Pine.LNX.4.31.0104291552190.523-100000@HADDOCK.100Mbit.nyren.net>
In-Reply-To: <Pine.LNX.4.31.0104291552190.523-100000@HADDOCK.100Mbit.nyren.net>
Ralf Nyren writes:
> The problem appears when this value is set to 40481 or higher. For ex:
> $ tcpblast -d0 -s 40481 another_host 9000
...
> KERNEL: assertion (!skb_queue_empty(&sk->write_queue)) failed at tcp_timer.c(327):
> tcp_retransmit_timer
> Unable to handle kernel NULL pointer dereference...
I'm having a devil of a time finding the tcpblast sources on the
net, can you point me to where I can get them? The one reference
I saw to get the original sources was:
ftp://ftp.xlink.net/pub/network/tcpblast.shar.gz
But even that directory no longer exists.
The kernel error you see is a gross fatal error, the TCP retransmit
timer has fired yet there are no packets on the transmit queue :-)
My current theory is that tcpblast does something erratic when the
error occurs.
Later,
David S. Miller
davem@redhat.com
next prev parent reply other threads:[~2001-04-30 5:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3AED0A7A.7263E27B@uow.edu.au>
2001-04-29 14:29 ` Ralf Nyren
2001-04-30 5:10 ` David S. Miller [this message]
2001-04-30 6:42 ` J Sloan
2001-04-30 6:58 ` David S. Miller
2001-04-30 14:41 ` Ralf Nyren
2001-04-30 16:46 ` Andrea Arcangeli
2001-04-30 17:22 ` Ingo Oeser
2001-04-30 17:00 ` kuznet
2001-05-01 10:47 ` Andrea Arcangeli
2001-05-01 16:44 ` kuznet
2001-05-01 17:09 ` Andrea Arcangeli
2001-05-01 17:25 ` kuznet
2001-05-01 17:32 ` Andrea Arcangeli
2001-05-01 18:10 ` kuznet
2001-05-01 23:08 ` David S. Miller
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=15084.62398.56283.772414@pizda.ninka.net \
--to=davem@redhat.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=ralf@nyren.net \
/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
all inboxes | Powered by JetHome®