From: Patrick Ringl <patrick_@freenet.de>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Patrick Ringl <patrick_@freenet.de>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
bridge@lists.linux-foundation.org
Subject: Re: 2.6.36-rc7: net/bridge causes temporary network I/O lockups [2]
Date: Fri, 22 Oct 2010 00:18:38 +0200 [thread overview]
Message-ID: <4CC0BC3E.6080906@freenet.de> (raw)
In-Reply-To: <20101020061631.GA21679@gondor.apana.org.au>
[-- Attachment #1: Type: text/plain, Size: 727 bytes --]
On 10/20/2010 08:16 AM, Herbert Xu wrote:
> On Mon, Oct 18, 2010 at 10:37:40PM +0200, Patrick Ringl wrote:
>
>> Anything else I could possibly provide? :-)
>>
> Yes, testing :)
>
> First of all I'd like to rule out (or in) the IPv6 query code,
> which is clearly generating a bogus packet (wrong payload_len).
>
> So can you apply this patch and see if it makes the problem
> go away? Please take packet dumps so we know that the IPv6 query
> is no longer being sent.
>
Hi,
Hi,
sorry for the late response. I've been using your patch on 2.6.36 and
unfortunately, the bogus ipv6 packet is not the cause of the lockups. I
have attached two packet dumps (br0 and eth1) again.
regards,
Patrick
> Thanks,
>
[-- Attachment #2: n_br0 --]
[-- Type: application/octet-stream, Size: 1784 bytes --]
[-- Attachment #3: n_eth1 --]
[-- Type: application/octet-stream, Size: 1840 bytes --]
next prev parent reply other threads:[~2010-10-21 22:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 18:15 2.6.36-rc7: net/bridge causes temporary network I/O lockups [2] Patrick Ringl
2010-10-18 16:16 ` Herbert Xu
2010-10-18 20:37 ` Patrick Ringl
2010-10-20 6:16 ` Herbert Xu
2010-10-21 22:18 ` Patrick Ringl [this message]
2010-10-21 23:07 ` Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2010-10-16 12:11 Patrick Ringl
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=4CC0BC3E.6080906@freenet.de \
--to=patrick_@freenet.de \
--cc=bridge@lists.linux-foundation.org \
--cc=herbert@gondor.apana.org.au \
--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;
as well as URLs for NNTP newsgroup(s).