From: Caleb Cushing <xenoterracide@gmail.com>
To: Frans Pop <elendil@planet.nl>
Cc: linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: large packet loss take2 2.6.31.x
Date: Wed, 11 Nov 2009 15:19:54 -0500 [thread overview]
Message-ID: <81bfc67a0911111219m1efff30cr3186987f9dbb3d4d@mail.gmail.com> (raw)
In-Reply-To: <200910311944.35922.elendil@planet.nl>
not to be impatient or ungrateful, but has anyone had time to look at
this? will I be able to upgrade to 31.6? will 32.0 work?
On Sat, Oct 31, 2009 at 1:44 PM, Frans Pop <elendil@planet.nl> wrote:
> Adding netdev in CC. Original message + attachments follow.
>
> =========
> so ever since arch rolled out 2.6.31.x I've been having problems with
> my network (again) where I've been losing a large amount of packets
> (just testing with mtr somewhere between 30/50%). first I figured it
> was the same problem as I had in 2.6.30.x (and maybe it is?) but that
> appeared to get fixed. when I started bisecting the bug wasn't
> apparent in 2.6.31.0 but I knew for sure it was in .5 (I couldn't
> remember if I had noticed it again in .3)
>
> I'm attaching the bisection log and a 'good' dmesg output.
>
> c9fb3ded7a8a6769f3bcb3ef3d9aed61d3e376a9 is the first bad commit
>
> I'm not going to pretend to understand why this patch is breaking my
> networking but between bisection and testing it appears to be... I've
> never bisected before and I'm definitely not a kernel hacker (I can
> barely read C).
>
> I should also note that the wireshark dump here
> http://bugzilla.kernel.org/show_bug.cgi?id=13835 is related to this.
> and if it's not the same bug then possibly a new one should be opened.
>
> P.S. I'm not subscribed to the list please CC me
>
> Caleb Cushing
> http://xenoterracide.blogspot.com
>
>
--
Caleb Cushing
http://xenoterracide.blogspot.com
next prev parent reply other threads:[~2009-11-11 20:19 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 14:21 Caleb Cushing
2009-10-31 18:44 ` Frans Pop
2009-11-11 20:19 ` Caleb Cushing [this message]
2009-11-11 21:47 ` Andi Kleen
2009-11-11 22:05 ` Frans Pop
2009-11-11 22:48 ` Caleb Cushing
2009-11-12 11:38 ` Jarek Poplawski
2009-11-12 13:46 ` Caleb Cushing
2009-11-12 19:04 ` Jarek Poplawski
2009-11-12 21:47 ` Jarek Poplawski
2009-11-13 16:25 ` Caleb Cushing
2009-11-13 17:21 ` Caleb Cushing
2009-11-13 21:16 ` Jarek Poplawski
2009-11-18 9:59 ` Caleb Cushing
2009-11-18 10:00 ` Caleb Cushing
2009-11-18 13:51 ` Jarek Poplawski
2009-11-18 18:21 ` Caleb Cushing
2009-11-18 20:10 ` Jarek Poplawski
2009-11-18 22:38 ` Jarek Poplawski
2009-11-22 19:35 ` Caleb Cushing
2009-11-22 20:50 ` Jarek Poplawski
2009-11-24 6:17 ` Caleb Cushing
2009-11-24 11:19 ` Jarek Poplawski
2009-11-24 13:46 ` Jarek Poplawski
2009-11-24 15:57 ` [E1000-devel] " Allan, Bruce W
2009-11-24 18:27 ` Jarek Poplawski
2009-11-25 14:06 ` Caleb Cushing
2009-11-25 16:47 ` Caleb Cushing
2009-11-25 19:11 ` Jarek Poplawski
2009-11-27 18:07 ` Caleb Cushing
2009-11-27 21:36 ` Jarek Poplawski
2009-11-27 22:35 ` Caleb Cushing
2009-11-27 22:42 ` Jarek Poplawski
2009-12-04 1:49 ` Caleb Cushing
2009-12-04 9:05 ` Jarek Poplawski
2009-12-04 18:28 ` Caleb Cushing
2009-12-04 20:44 ` Jarek Poplawski
2009-12-04 23:07 ` Caleb Cushing
2009-12-04 23:47 ` Jarek Poplawski
2009-12-05 7:06 ` Caleb Cushing
2009-12-05 7:29 ` Caleb Cushing
2009-12-05 13:57 ` Jarek Poplawski
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=81bfc67a0911111219m1efff30cr3186987f9dbb3d4d@mail.gmail.com \
--to=xenoterracide@gmail.com \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome