public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Massimo Cetra <ctrix+debianbugs@navynet.it>
To: "Peter Huang(Peng)" <peter.huangpeng@huawei.com>
Cc: Massimo Cetra <ctrix+debianbugs@navynet.it>,
	netdev@vger.kernel.org, Eric Dumazet <eric.dumazet@gmail.com>
Subject: Re: fake rtable dst patch applied but kernel keeps panicing
Date: Thu, 19 Apr 2012 10:37:46 +0200	[thread overview]
Message-ID: <4F8FCEDA.20504@navynet.it> (raw)
In-Reply-To: <4F8FCB53.7070603@huawei.com>

On 19/04/2012 10:22, Peter Huang(Peng) wrote:
> Hi, Massimo
>
> can this be reproduce easily or depend on some HW or SW environment?
>
> This patch already verified on 2.6.32.36/54,3.3.1, 3.4.rc[23] for over
> 6 hours, but didn't encounter this problem.

The server is a Dell PowerEdge R410.

The network cards are:
01:00.0 Ethernet controller: Broadcom Corporation NetXtreme II BCM5716 
Gigabit Ethernet (rev 20)
01:00.1 Ethernet controller: Broadcom Corporation NetXtreme II BCM5716 
Gigabit Ethernet (rev 20)

The server is doing nothing except for routing packets and running 
virtual servers.

This server is guesting about 10 KVM virtual servers in a bridged 
configuration.


lamu:~# brctl show br0
bridge name     bridge id               STP enabled     interfaces
br0             8000.0024e869f8eb       yes             eth1
                                                         kvmnet-db0
                                                         kvmnet-devel0
                                                         kvmnet-kermit0
                                                         kvmnet-mail0
                                                         kvmnet-max0
                                                         kvmnet-repo0
                                                         kvmnet-voip0
                                                         kvmnet-wper0
                                                         kvmnet-wsos0


kvmnet-* interfaces are tun devices.

-------------------------

Whenever i add a couple of "virtual" bridges assigning an ip address to, 
for example, br0:1 br0:2, the panic happens a couple of times a day.

If i leave only br0 and br1 it's very hard to trigger (but this may be 
related to network traffic which, in this case, is very low).

By the way, i'm using this kernel (with and without the previous patch) 
on my workstation which has a br0 interface and some VM attached in the 
same way.
I am not experiencing crashes and the only difference is that i don't 
have, on my desktop, any br0:1 br0:2 interfaces.

Hope it helps.

Max

      reply	other threads:[~2012-04-19  8:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 10:08 fake rtable dst patch applied but kernel keeps panicing Massimo Cetra
2012-04-18 10:31 ` Eric Dumazet
2012-04-19  8:01   ` Massimo Cetra
2012-04-19  8:14     ` Eric Dumazet
2012-04-19  8:45       ` Eric Dumazet
2012-04-19 10:52         ` Massimo Cetra
2012-04-20 10:02         ` Massimo Cetra
2012-04-20 13:22           ` Eric Dumazet
2012-04-19  8:22 ` Peter Huang(Peng)
2012-04-19  8:37   ` Massimo Cetra [this message]

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=4F8FCEDA.20504@navynet.it \
    --to=ctrix+debianbugs@navynet.it \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=peter.huangpeng@huawei.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