All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: arno@wagner.name
Cc: netdev@vger.kernel.org, stephen@networkplumber.org
Subject: Re: Fw: [Bug 65261] New: Packet loss or excessive packet delay repeatedly for some seconds
Date: Sat, 23 Nov 2013 05:33:59 +0100	[thread overview]
Message-ID: <20131123043359.GC15822@order.stressinduktion.org> (raw)
In-Reply-To: <20131120122316.77ce76c5@nehalam.linuxnetplumber.net>

On Wed, Nov 20, 2013 at 12:23:16PM -0800, Stephen Hemminger wrote:
> 
> 
> Begin forwarded message:
> 
> Date: Wed, 20 Nov 2013 05:57:59 -0800
> From: "bugzilla-daemon@bugzilla.kernel.org" <bugzilla-daemon@bugzilla.kernel.org>
> To: "stephen@networkplumber.org" <stephen@networkplumber.org>
> Subject: [Bug 65261] New: Packet loss or excessive packet delay repeatedly for some seconds
> 
> 
> https://bugzilla.kernel.org/show_bug.cgi?id=65261
> 
>             Bug ID: 65261
>            Summary: Packet loss or excessive packet delay repeatedly for
>                     some seconds
>            Product: Networking
>            Version: 2.5
>     Kernel Version: 3.10.19
>           Hardware: x86-64
>                 OS: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: high
>           Priority: P1
>          Component: IPV4
>           Assignee: shemminger@linux-foundation.org
>           Reporter: arno@wagner.name
>         Regression: No
> 
> Created attachment 115261
>   --> https://bugzilla.kernel.org/attachment.cgi?id=115261&action=edit
> Kernel config 3.10.19
> 
> I recently upgraded my development-server/firewall/NAT-box from 3.10.17 to
> 3.10.19. Since then I noticed increased DNS lookup failures on a connected
> Windows box and occasional slow updates on putty-SSH logins when scrolling in
> an editor (joe, takes something like an estimated 100-300ms for screen
> updates). These update delays are repeatable for something like 10-20 seconds
> or more, e.g. inserting a line and then deleting again, then vanish. The delays
> make remote editing hard to do when they happen. The DNS lookup failures are
> really annoying. 
> 
> I have not found a way to reliably trigger the problem.
> 
> Going back to 3.10.17 fixed the issue as far as I can tell. (Several hours
> editing source code without it showing up.) The only change between the two
> configurations was that I added the scsi CDROM driver (which should not be able
> to cause this?).
> 
> The network connection has an iptables "all pass" on the server side for the
> affected connection. The client side is a Win7 machine. The network link is GbE
> with 2 Switches in there. No packet loss on ping/ping -f. Network hardware is 
> Intel 82574L Gigabit card on both sides.

Could you try dropwatch while the packet drops are happening?
Often it is helpful to check ip monitor all if events happen during bursty
losses.

Greetings,

  Hannes

  reply	other threads:[~2013-11-23  4:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-20 20:23 Fw: [Bug 65261] New: Packet loss or excessive packet delay repeatedly for some seconds Stephen Hemminger
2013-11-23  4:33 ` Hannes Frederic Sowa [this message]
2013-11-23 12:11   ` Arno Wagner
2013-11-23 16:45     ` Ben Hutchings
2013-11-23 20:20       ` Arno Wagner
2013-11-23 20:31         ` Ben Hutchings
2013-11-23 20:39         ` Hannes Frederic Sowa
2013-11-23 22:00           ` Arno Wagner
2013-11-23 22:17             ` Hannes Frederic Sowa
2013-11-23 22:11           ` Re2: " Arno Wagner
2013-11-23 22:18             ` Hannes Frederic Sowa
2013-11-23 23:01               ` Arno Wagner

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=20131123043359.GC15822@order.stressinduktion.org \
    --to=hannes@stressinduktion.org \
    --cc=arno@wagner.name \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.