From: Stephen Hemminger <shemminger@vyatta.com>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 48601] New: Pauses while downloading
Date: Mon, 8 Oct 2012 09:29:49 -0700 [thread overview]
Message-ID: <20121008092949.39d6cc4e@nehalam.linuxnetplumber.net> (raw)
Begin forwarded message:
Date: Mon, 8 Oct 2012 09:12:17 +0000 (UTC)
From: bugzilla-daemon@bugzilla.kernel.org
To: shemminger@linux-foundation.org
Subject: [Bug 48601] New: Pauses while downloading
https://bugzilla.kernel.org/show_bug.cgi?id=48601
Summary: Pauses while downloading
Product: Networking
Version: 2.5
Kernel Version: 3.6
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: IPV4
AssignedTo: shemminger@linux-foundation.org
ReportedBy: colbec@start.ca
Regression: No
Using OpenSUSE 12.2, Gnome 3.6 with Network Manager.
Recently upgraded from kernel 3.5 to 3.6, at which point the issue began.
Observed symptoms: while downloading, the stream will stop at random points for
5 to 120+ seconds, and then resume the download.
Example 1: while browsing, click on a link one time in 10 (approx) will fail to
get the page, and a second click is successful. Sometimes it will begin to get
the page, then stop, use back button to get previous page back, click link
again and the page is fetched successfully.
Example 2: try to test download speed using speedtest.net, one test in two
shows a normal start to the download side of the test, during the test the
process stops, then recommences after a varying period 5 to 120+ seconds.
Pauses happen one or multiple times.
Example 3: attempt to download a 20MB mp4 using Firefox. Process begins
correctly, but during the download the process stops, again for 5-120 sec, and
resumes. Downloads take a long time, but will eventually complete. If I kick it
(pause, resume in download manager) it will complete faster.
I have replaced cables, NIC; return to kernel 3.5 eliminates the issue.
.config file was copied from a 3.4.2 kernel version, worked well for 3.5, and
also seemed to be good for 3.6 with the exception of failed webcam which needed
V4L reinstated.
--- Comment #1 from Alan <alan@lxorguk.ukuu.org.uk> 2012-10-08 15:03:59 ---
Please provide detailed information on the hardware or network setup. Without
that it's hard to do anything.
--- Comment #2 from colbec@start.ca 2012-10-08 15:43:58 ---
OK, first to note is that two Windows machines on the same network using the
same wireless route to the WAN do not show this issue. Since kernel 3.5 is
clear and only 3.6 is the problem this seems to rule out the network
components, but anyway I am connecting to the WAN through two Linksys WRT4GL
running DD-WRT. Route continues to WAN through a wireless high speed connection
via Motorola Canopy technology.
I have replaced the cabling with identical results.
I have added a PCI NIC (Realtek) which behaves the same way as the onboard NIC
(Atheros AR8131).
Memory 3.8 GiB, Intel Core 2 Quad Q8300 @ 2.5 GHz x 4
Graphics Intel G41 64 bit OS, Disk 500 GB.
Correction to Gnome version 3.4.2. (not stated 3.6)
I have a ream of further hardware info from Yast, please specify what detail
would be helpful.
reply other threads:[~2012-10-08 16:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20121008092949.39d6cc4e@nehalam.linuxnetplumber.net \
--to=shemminger@vyatta.com \
--cc=netdev@vger.kernel.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.