From: Eric Dumazet <eric.dumazet@gmail.com>
To: Rob Herring <robherring2@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: panics in tcp_ack
Date: Sun, 02 Jun 2013 17:26:07 -0700 [thread overview]
Message-ID: <1370219167.24311.108.camel@edumazet-glaptop> (raw)
In-Reply-To: <51ABE067.2050507@gmail.com>
On Sun, 2013-06-02 at 19:16 -0500, Rob Herring wrote:
> Sorry, this time with proper line wrapping...
>
> I'm debugging a kernel panic in the networking stack that happens with a
> cluster (20-40 nodes) of Calxeda highbank (ARM Cortex A9) nodes and
> typically only after 10-24 hours. The node are transferring files
> between nodes over TCP with 20 clients and servers per node. The kernel
> is based on ubuntu 3.5 kernel which is based on 3.5.7.11. So far testing
> has shown that 3.8.11 based (ubuntu raring) kernel is fixed. Attempts to
> bisect have not yielded results as it seems multiple problems mask the
> issue. Perhaps there is some new feature which has indirectly fixed the
> problem in 3.8.
Oh well, you said it was fixed in 3.8, sorry for my prior mail.
next prev parent reply other threads:[~2013-06-03 0:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-03 0:16 panics in tcp_ack Rob Herring
2013-06-03 0:24 ` Eric Dumazet
2013-06-03 0:26 ` Eric Dumazet [this message]
2013-06-03 0:36 ` Eric Dumazet
2013-06-03 2:23 ` Rob Herring
2013-06-03 3:03 ` Eric Dumazet
2013-06-03 3:18 ` Rob Herring
2013-06-03 3:32 ` Eric Dumazet
2013-06-03 3:41 ` Rob Herring
2013-06-03 13:05 ` Rob Herring
2013-06-03 13:25 ` Eric Dumazet
2013-06-03 15:51 ` Rob Herring
2013-06-03 15:58 ` Eric Dumazet
2013-06-14 19:12 ` Rob Herring
2013-06-14 20:52 ` Eric Dumazet
2013-06-06 17:21 ` Rob Herring
-- strict thread matches above, loose matches on Subject: below --
2013-06-03 0:13 Rob Herring
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=1370219167.24311.108.camel@edumazet-glaptop \
--to=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=robherring2@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