From: Jarek Poplawski <jarkao2@gmail.com>
To: Caleb Cushing <xenoterracide@gmail.com>
Cc: Frans Pop <elendil@planet.nl>, Andi Kleen <andi@firstfloor.org>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: large packet loss take2 2.6.31.x
Date: Thu, 12 Nov 2009 11:38:36 +0000 [thread overview]
Message-ID: <20091112113836.GA7963@ff.dom.local> (raw)
In-Reply-To: <81bfc67a0911111448q2e7938fcq18adf2454d6bc8f1@mail.gmail.com>
On 11-11-2009 23:48, Caleb Cushing wrote:
> On Wed, Nov 11, 2009 at 5:05 PM, Frans Pop <elendil@planet.nl> wrote:
>> On Wednesday 11 November 2009, Andi Kleen wrote:
>>> Caleb Cushing <xenoterracide@gmail.com> writes:
>>>>> I'm attaching the bisection log and a 'good' dmesg output.
>>>>>
>>>>> c9fb3ded7a8a6769f3bcb3ef3d9aed61d3e376a9 is the first bad commit
>>> Just gives fatal: bad object c9fb3ded7a8a6769f3bcb3ef3d9aed61d3e376a9
>>> here on a standard Linus linux-2.6 tree.
>> Looks to be a commit from a stable update:
>>
>> commit c9fb3ded7a8a6769f3bcb3ef3d9aed61d3e376a9
>> Author: Alan Stern <stern@rowland.harvard.edu>
>> Date: Â Tue Sep 1 11:38:34 2009 -0400
>>
>> Â Â usb-serial: change referencing of port and serial structures
>>
>> Â Â commit 41bd34ddd7aa46dbc03b5bb33896e0fa8100fe7b upstream.
>>
>> Cheers,
>> FJP
>>
>
> yeah it is. it's from greg kroah-hartman's tree.
Could you answer the previous question too:
On 11-11-2009 22:47, Andi Kleen wrote:
...
> It might be also useful if you could describe what kind
> of network devices you use and how you determine
> the packet loss.
Btw, you didn't send the stats you compared, and your wireshark dump
doesn't show anything wrong either.
Jarek P.
next prev parent reply other threads:[~2009-11-12 11:38 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <81bfc67a0910310721p21046931o9b512cfd0a8a7acb@mail.gmail.com>
2009-10-31 18:44 ` large packet loss take2 2.6.31.x Frans Pop
2009-11-11 20:19 ` Caleb Cushing
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 [this message]
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=20091112113836.GA7963@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=andi@firstfloor.org \
--cc=elendil@planet.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=xenoterracide@gmail.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).