From: volodya@mindspring.com
To: Jeremiah Johnson <miah@netcis.com>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@mandrakesoft.com>
Subject: Re: Re[4]: 2.4.9 UDP broke?
Date: Wed, 5 Sep 2001 16:28:39 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.20.0109051626440.25127-100000@node2.localnet.net> (raw)
In-Reply-To: <111202114514.20010904191953@netcis.com>
On Tue, 4 Sep 2001, Jeremiah Johnson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: MD5
>
> Hello volodya,
>
> I found the answer to the problem today. It has to do with a bug in
> one of these options:
>
> CONFIG_TULIP_MWI
> CONFIG_TULIP_MMIO
>
You are absolutely correct - once I enabled both of these it works
great. My guess is that whoever tested the patches was concentrated on the
case when options were enabled.
Vladimir Dergachev
> Since the system is a older dual p100 I didn't really want to sit
> through the 2 hours of compilation to "test" which one it is. I'm
> willing to bet its CONFIG_TULIP_MWI though since its still marked as
> experimental. With both of these options disabled 2.4.9 works fine on
> that system though as it does on my other boxes. Whoever maintains
> the code for those two config options might want to do some testing.
> I can provide more information about the system if needed.
>
> Sunday, September 02, 2001, 7:25:44 PM, you wrote:
>
> vmc> I had a very similar experience. In my case it turned out that for some
> vmc> reason no UDP packets above 5524 would not come through (try pinging with
> vmc> larger than default packet sizes). The solution was to restrict NFS to
> vmc> 5000 (actually 4096) size packets. I have not been able to figure out the
> vmc> cause of this yet. (and yes, tcpdump was able to see them fine).
>
> vmc> Vladimir Dergachev
>
>
> - --
> Best regards,
> Jeremiah mailto:miah@netcis.com
>
> -----BEGIN PGP SIGNATURE-----
> Version: 2.6
>
> iQEVAwUAO5WLyZHTj7BlqKb5AQFiIQf8DG8rppS8oNKQvmQts2rFQzx0MVizZZv/
> p12tm+bcToP8jg6OKL0hzkeL59k3RgJpbjSleHl6VHgGzZ4VfZuvtE7gwA0e/Ch8
> MQck+diQkDY14qM+qxdIhwjuSyt+qDTlOPge/MZKNvtGckYkQ9qKVHiWbKWuxlYS
> U4N8knpXHUZ9fM+hPPqi/0yNfwx6g7QbtLycYJzP0GIDSzP4y/P30HMkSJ9EUzP1
> MQCho4dj2K2WvMyrNVAO70Nj90j1ioU7vJE2LMooKrZmWBpBSMX6MMKr//lJP73H
> RTQLNZmRGbBtblq4QiXai6OpEYkaaE84iutfs9JbssOJ+S2cxNDM1g==
> =XNHF
> -----END PGP SIGNATURE-----
>
next prev parent reply other threads:[~2001-09-05 20:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 6:20 Jeremiah Johnson
2001-08-31 5:50 ` Steve Kieu
2001-08-31 15:46 ` Re[2]: " Jeremiah Johnson
2001-08-31 18:34 ` J Sloan
2001-09-03 2:25 ` Re[2]: " volodya
2001-09-05 2:19 ` Re[4]: " Jeremiah Johnson
2001-09-05 3:54 ` volodya
2001-09-05 14:15 ` Jeremiah Johnson
2001-09-05 20:28 ` volodya [this message]
2001-09-07 17:34 ` Re[6]: " Jeremiah Johnson
2001-09-07 17:32 ` volodya
2001-09-01 10:32 ` Matthias Andree
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=Pine.LNX.4.20.0109051626440.25127-100000@node2.localnet.net \
--to=volodya@mindspring.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=miah@netcis.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
all inboxes | Powered by JetHome®