From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org
Cc: bugme-daemon@bugzilla.kernel.org, speedster@haveacry.com
Subject: Re: [Bugme-new] [Bug 12327] New: Intermittent TCP issues with => 2.6.27
Date: Mon, 29 Dec 2008 21:41:01 -0800 [thread overview]
Message-ID: <20081229214101.4c4f5ac1.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-12327-10286@http.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Mon, 29 Dec 2008 18:52:40 -0800 (PST) bugme-daemon@bugzilla.kernel.org wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=12327
>
> Summary: Intermittent TCP issues with => 2.6.27
> Product: Networking
> Version: 2.5
> KernelVersion: 2.6.27
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: IPV4
> AssignedTo: shemminger@linux-foundation.org
> ReportedBy: speedster@haveacry.com
>
>
> Latest working kernel version: 2.6.26.8
> Earliest failing kernel version: 2.6.27
> Distribution: Ubuntu
> Hardware Environment: amd64, KVM
> Software Environment:
> Problem Description:
>
> As reported in LP #296767
> (https://bugs.launchpad.net/ubuntu/+source/linux/+bug/296767) I am experiencing
> intermittent TCP issues over a PPP ADSL2+ connection with the only change being
> an upgrade to 2.6.27.
>
> A number of websites, ping, traceroute work correctly but I simply can't
> connect to several including:
>
> - store.apple.com
> - youtube.com
> - ANZ internet banking (anz.com.au)
> - MSN messenger
>
> I have also tried compiling a generic 2.6.28-rc4 kernel and this still suffers
> from the same issue, however if I reboot into the previous Ubuntu kernel
> (2.6.24) or a vanilla 2.6.26 kernel the issue disappears.
>
> Steps to reproduce:
>
> 1. Use a KVM guest as a gateway to a PPP internet connection
> 2. Boot with kernel <= 2.6.26
> 3. Observe functioning networking
> 4. Boot into 2.6.27+
> 5. Observe broken networking
next parent reply other threads:[~2008-12-30 5:41 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 ` Andrew Morton [this message]
2008-12-31 20:32 ` [Bugme-new] [Bug 12327] New: Intermittent TCP issues with => 2.6.27 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
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=20081229214101.4c4f5ac1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=netdev@vger.kernel.org \
--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).