From: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: Speedster <speedster@haveacry.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Netdev <netdev@vger.kernel.org>,
bugme-daemon@bugzilla.kernel.org,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [Bugme-new] [Bug 12327] New: Intermittent TCP issues with => 2.6.27
Date: Thu, 8 Jan 2009 21:39:30 +0200 (EET) [thread overview]
Message-ID: <Pine.LNX.4.64.0901082138060.31441@wrl-59.cs.helsinki.fi> (raw)
In-Reply-To: <20090108083753.14670943@extreme>
On Thu, 8 Jan 2009, Stephen Hemminger wrote:
> On Fri, 09 Jan 2009 00:04:42 +0900
> Speedster <speedster@haveacry.com> wrote:
>
> > Herbert Xu wrote:
> > >
> > > Can you please take a look at /proc/net/snmp on the host and the
> > > guest to see if IP InDiscards is non-zero?
> >
> > Both are 0
> >
> > > Also now that we know the problem is definitely in the host/guest
> > > please take another set of dumps on the interfaces leading to and
> > > within the guest to see exactly which path of the system is dropping
> > > the reply.
> >
> > Attached (all are the exact same attempted connection), and reveal some
> > interesting information.
> >
> > The path the inbound traffic should take is
> > 1. vlan50 (host)
> > 2. tap interface vnet3 (host) / eth0 (guest)
> > 3. ppp0 (guest)
> >
> > It looks as though when it is sent out the tap interface the payload
> > length is incorrect in the PPPoE section of the frame. When it arrives
> > via vlan50 it appears fine. Or at least that's what wireshark highlights
> > for me :)
>
> Maybe there is an issue that GRO receive isn't handling padding
> properly?
Hmm, is gro supposed to have something to do with 2.6.27??? Or are you
talking something else than Herbert's recent GRO stuff?
--
i.
next prev parent reply other threads:[~2009-01-08 19:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12327-10286@http.bugzilla.kernel.org/>
2008-12-30 5:41 ` [Bugme-new] [Bug 12327] New: Intermittent TCP issues with => 2.6.27 Andrew Morton
2008-12-31 20:32 ` Ilpo Järvinen
2008-12-31 23:22 ` Speedster
2009-01-02 8:34 ` Herbert Xu
2009-01-05 11:19 ` Speedster
2009-01-06 19:10 ` Ilpo Järvinen
2009-01-06 21:19 ` Speedster
2009-01-07 4:17 ` Herbert Xu
2009-01-07 13:49 ` Speedster
2009-01-08 3:07 ` Herbert Xu
2009-01-08 13:13 ` Ilpo Järvinen
2009-01-08 15:04 ` Speedster
2009-01-08 16:37 ` Stephen Hemminger
2009-01-08 19:39 ` Ilpo Järvinen [this message]
2009-01-08 19:54 ` Stephen Hemminger
2009-01-08 21:54 ` Herbert Xu
2009-01-09 0:14 ` John Dykstra
2009-01-09 0:30 ` John Dykstra
[not found] <e7c4531f0901081558n429f7275w717774dbe9ccd895@mail.gmail.com>
2009-01-09 3:14 ` Herbert Xu
2009-01-09 11:55 ` Herbert Xu
2009-01-09 12:04 ` Herbert Xu
2009-01-12 5:30 ` Patrick McHardy
2009-01-13 10:50 ` Speedster
2009-03-06 10:39 ` Dean Holland
2009-03-25 13:26 ` Ilpo Järvinen
2009-01-12 5:27 ` Patrick McHardy
2009-01-12 5:25 ` Patrick McHardy
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.64.0901082138060.31441@wrl-59.cs.helsinki.fi \
--to=ilpo.jarvinen@helsinki.fi \
--cc=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=herbert@gondor.apana.org.au \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.com \
--cc=speedster@haveacry.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).