From: Patrick Ringl <patrick_@freenet.de>
To: Herbert Xu <herbert@gondor.hengli.com.au>
Cc: netdev@vger.kernel.org, Patrick Ringl <patrick_@freenet.de>,
bridge@lists.linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [Bridge] 2.6.36-rc7: net/bridge causes temporary network I/O lockups [2]
Date: Mon, 18 Oct 2010 22:37:40 +0200 [thread overview]
Message-ID: <4CBCB014.9080108@freenet.de> (raw)
In-Reply-To: <20101018161656.GA2403@gondor.apana.org.au>
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
On 10/18/2010 06:16 PM, Herbert Xu wrote:
> On Sat, Oct 16, 2010 at 08:15:31PM +0200, Patrick Ringl wrote:
>
>> Hi,
>>
>> okay I narrowed down the issue. I watched all function calls of the
>> 'bridge' module with the help of a small systemtap probe of mine. I
>> first traced a timespan where the issue did not occur, then one where it
>> did and composed an intersection of these two:
>>
> I can't reproduce this problem here so I'll need your help to
> track it down.
>
> Can you see if you can relate the lock-ups to specific events
> such as a particular packet being sent through the bridge?
>
The problem is definitely somewhere in the 2.6.34 commit regarding IGMP
snooping (when disabling it, everything works). I have attached a
tcpdump log of data coming through the bridge and data coming through an
attached port (eth1). The lockups are easily spotted, since I use mtr to
constantly ping the problematic machine, and there aren't any
incoming/outgoing packets during the lockup.
> If we can recreate the problem on demand that that helps us to
> find the root cause.
>
> You mentioned that you took packet dumps on the system. If you
> can show us the packets through the bridge and its ports when
> the problem occurs that would be great.
>
> Thanks,
>
Anything else I could possibly provide? :-)
regards,
Patrick
[-- Attachment #2: dump_br0 --]
[-- Type: application/octet-stream, Size: 2764 bytes --]
[-- Attachment #3: dump_eth1 --]
[-- Type: application/octet-stream, Size: 2806 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Patrick Ringl <patrick_@freenet.de>
To: Herbert Xu <herbert@gondor.hengli.com.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: Mon, 18 Oct 2010 22:37:40 +0200 [thread overview]
Message-ID: <4CBCB014.9080108@freenet.de> (raw)
In-Reply-To: <20101018161656.GA2403@gondor.apana.org.au>
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
On 10/18/2010 06:16 PM, Herbert Xu wrote:
> On Sat, Oct 16, 2010 at 08:15:31PM +0200, Patrick Ringl wrote:
>
>> Hi,
>>
>> okay I narrowed down the issue. I watched all function calls of the
>> 'bridge' module with the help of a small systemtap probe of mine. I
>> first traced a timespan where the issue did not occur, then one where it
>> did and composed an intersection of these two:
>>
> I can't reproduce this problem here so I'll need your help to
> track it down.
>
> Can you see if you can relate the lock-ups to specific events
> such as a particular packet being sent through the bridge?
>
The problem is definitely somewhere in the 2.6.34 commit regarding IGMP
snooping (when disabling it, everything works). I have attached a
tcpdump log of data coming through the bridge and data coming through an
attached port (eth1). The lockups are easily spotted, since I use mtr to
constantly ping the problematic machine, and there aren't any
incoming/outgoing packets during the lockup.
> If we can recreate the problem on demand that that helps us to
> find the root cause.
>
> You mentioned that you took packet dumps on the system. If you
> can show us the packets through the bridge and its ports when
> the problem occurs that would be great.
>
> Thanks,
>
Anything else I could possibly provide? :-)
regards,
Patrick
[-- Attachment #2: dump_br0 --]
[-- Type: application/octet-stream, Size: 2764 bytes --]
[-- Attachment #3: dump_eth1 --]
[-- Type: application/octet-stream, Size: 2806 bytes --]
WARNING: multiple messages have this Message-ID (diff)
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: Mon, 18 Oct 2010 22:37:40 +0200 [thread overview]
Message-ID: <4CBCB014.9080108@freenet.de> (raw)
In-Reply-To: <20101018161656.GA2403@gondor.apana.org.au>
[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]
On 10/18/2010 06:16 PM, Herbert Xu wrote:
> On Sat, Oct 16, 2010 at 08:15:31PM +0200, Patrick Ringl wrote:
>
>> Hi,
>>
>> okay I narrowed down the issue. I watched all function calls of the
>> 'bridge' module with the help of a small systemtap probe of mine. I
>> first traced a timespan where the issue did not occur, then one where it
>> did and composed an intersection of these two:
>>
> I can't reproduce this problem here so I'll need your help to
> track it down.
>
> Can you see if you can relate the lock-ups to specific events
> such as a particular packet being sent through the bridge?
>
The problem is definitely somewhere in the 2.6.34 commit regarding IGMP
snooping (when disabling it, everything works). I have attached a
tcpdump log of data coming through the bridge and data coming through an
attached port (eth1). The lockups are easily spotted, since I use mtr to
constantly ping the problematic machine, and there aren't any
incoming/outgoing packets during the lockup.
> If we can recreate the problem on demand that that helps us to
> find the root cause.
>
> You mentioned that you took packet dumps on the system. If you
> can show us the packets through the bridge and its ports when
> the problem occurs that would be great.
>
> Thanks,
>
Anything else I could possibly provide? :-)
regards,
Patrick
[-- Attachment #2: dump_br0 --]
[-- Type: application/octet-stream, Size: 2764 bytes --]
[-- Attachment #3: dump_eth1 --]
[-- Type: application/octet-stream, Size: 2806 bytes --]
next prev parent reply other threads:[~2010-10-18 20:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 18:15 [Bridge] 2.6.36-rc7: net/bridge causes temporary network I/O lockups [2] Patrick Ringl
2010-10-16 18:15 ` Patrick Ringl
2010-10-16 18:15 ` Patrick Ringl
2010-10-18 16:16 ` [Bridge] " Herbert Xu
2010-10-18 16:16 ` Herbert Xu
2010-10-18 16:16 ` Herbert Xu
2010-10-18 20:37 ` Patrick Ringl [this message]
2010-10-18 20:37 ` Patrick Ringl
2010-10-18 20:37 ` Patrick Ringl
2010-10-20 6:16 ` [Bridge] " Herbert Xu
2010-10-20 6:16 ` Herbert Xu
2010-10-20 6:16 ` Herbert Xu
2010-10-21 22:18 ` [Bridge] " Patrick Ringl
2010-10-21 22:18 ` Patrick Ringl
2010-10-21 22:18 ` Patrick Ringl
2010-10-21 23:07 ` [Bridge] " Herbert Xu
2010-10-21 23:07 ` Herbert Xu
2010-10-21 23:07 ` Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2010-10-16 12:11 [Bridge] " 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=4CBCB014.9080108@freenet.de \
--to=patrick_@freenet.de \
--cc=bridge@lists.linux-foundation.org \
--cc=herbert@gondor.hengli.com.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 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.